docs: add iFlow Search MCP server example#29365
Open
zhengyanglsun wants to merge 1 commit into
Open
Conversation
Contributor
|
Thanks for updating your PR! It now meets our contributing guidelines. 👍 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue for this PR
Closes #
No tracking issue — the Examples section of
mcp-servers.mdxexplicitly invites PRs that document additional MCP servers, so I went straight to a PR per that guidance.Type of change
What does this PR do?
Adds one new example block,
### iFlow Search, to the Examples section ofpackages/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-mcpand listed in the MCP Registry asio.github.zhengyanglsun/iflow-search. It exposes three tools:iflow_web_searchiflow_image_searchiflow_web_fetchThe new section mirrors the structure of the existing Sentry / Context7 / Grep by Vercel entries: short description with links, an
opencode.jsonsnippet, and a usage hint. It uses the stable npm package (npx -y @iflow-ai/search-mcp) and atype: "local"mcp block, which matches the existing@modelcontextprotocol/server-everythingstdio example already in the page.Security choices made deliberately so users don't accidentally commit a credential:
IFLOW_API_KEYis not placed inopencode.json. The docs tell users to export it in the shell (or pull from a secret manager) that launches OpenCode.environmentblock in the example only carries a non-secret attribution value (IFLOW_MCP_CLIENT: "opencode").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?
@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).sk-,ghp_,github_pat_,npm_,Bearer <token>, realIFLOW_API_KEY=...literals, and tunnel URLs (trycloudflare.com,ngrok.io) — only the placeholderYOUR_IFLOW_API_KEYis present.check-standards,check-compliance,check-duplicates,add-contributor-labelare all green.astro buildlocally for thepackages/website — 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