Skip to content

docs: add iFlow Search MCP server example#29365

Open
zhengyanglsun wants to merge 1 commit into
anomalyco:devfrom
zhengyanglsun:docs/iflow-search-mcp
Open

docs: add iFlow Search MCP server example#29365
zhengyanglsun wants to merge 1 commit into
anomalyco:devfrom
zhengyanglsun:docs/iflow-search-mcp

Conversation

@zhengyanglsun
Copy link
Copy Markdown

@zhengyanglsun zhengyanglsun commented May 26, 2026

Issue for this PR

Closes #

No tracking issue — the Examples section of mcp-servers.mdx explicitly invites PRs that document additional MCP servers, so I went straight to a PR per that guidance.

Type of change

  • Bug fix
  • New feature
  • Refactor / code improvement
  • Documentation

What does this PR do?

Adds one new example block, ### iFlow Search, to the Examples section of packages/web/src/content/docs/mcp-servers.mdx, right after the existing Grep by Vercel example.

iFlow Search is a community/third-party MCP stdio server published on npm as @iflow-ai/search-mcp and listed in the MCP Registry as io.github.zhengyanglsun/iflow-search. It exposes three tools:

  • iflow_web_search
  • iflow_image_search
  • iflow_web_fetch

The new section mirrors the structure of the existing Sentry / Context7 / Grep by Vercel entries: short description with links, an opencode.json snippet, and a usage hint. It uses the stable npm package (npx -y @iflow-ai/search-mcp) and a type: "local" mcp block, which matches the existing @modelcontextprotocol/server-everything stdio example already in the page.

Security choices made deliberately so users don't accidentally commit a credential:

  • The IFLOW_API_KEY is not placed in opencode.json. The docs tell users to export it in the shell (or pull from a secret manager) that launches OpenCode.
  • The environment block in the example only carries a non-secret attribution value (IFLOW_MCP_CLIENT: "opencode").
  • The shell example uses the placeholder YOUR_IFLOW_API_KEY, not a real key.

No runtime code changes; this is docs-only. No implied OpenCode endorsement — the section is labeled community/third-party.

How did you verify your code works?

  • Read the file end-to-end and aligned the new block with the existing example sections (Sentry / Context7 / Grep by Vercel / @modelcontextprotocol/server-everything) so that headings, code fences, file-title hints, and highlight ranges follow the same pattern.
  • git diff --check — clean (no whitespace errors).
  • git diff --stat — change is scoped to one file: packages/web/src/content/docs/mcp-servers.mdx (+34 / -0).
  • Manual secret scan over the diff for sk-, ghp_, github_pat_, npm_, Bearer <token>, real IFLOW_API_KEY=... literals, and tunnel URLs (trycloudflare.com, ngrok.io) — only the placeholder YOUR_IFLOW_API_KEY is present.
  • Upstream PR CI passed: check-standards, check-compliance, check-duplicates, add-contributor-label are all green.
  • I did not run astro build locally for the packages/web site — the change is structurally identical to the three existing example blocks already in the same file, and pulling the full Astro / Starlight / Cloudflare adapter toolchain just to re-render a prose addition felt disproportionate. Happy to run the build if a maintainer prefers.

Screenshots / recordings

N/A — text-only docs addition, no UI change.

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR

@github-actions github-actions Bot added needs:compliance This means the issue will auto-close after 2 hours. and removed needs:compliance This means the issue will auto-close after 2 hours. labels May 26, 2026
@github-actions
Copy link
Copy Markdown
Contributor

Thanks for updating your PR! It now meets our contributing guidelines. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant