[Agents] Clarify that only one MCP server is needed#31750
[Agents] Clarify that only one MCP server is needed#31750ask-bonk[bot] wants to merge 2 commits into
Conversation
Co-authored-by: irvinebroque <irvinebroque@users.noreply.github.com>
Review✅ No issues found in commit Code ReviewThis code review is in beta and may not always be helpful — use your judgment. No code review issues found. ConventionsChecks PR title, description, and redirect checklist. No convention issues found. Style Guide ReviewNo style-guide issues found. RedirectsNo missing redirect entries found. CommandsOnly codeowners can run commands. Post a comment with the command to trigger it.
|
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
|
/bonk address all PR review feedback and update this PR |
| ## Optional product-specific MCP servers | ||
|
|
||
| In addition to the Cloudflare API MCP server, Cloudflare provides product-specific MCP servers for targeted use cases: | ||
| The following product-specific MCP servers are available for targeted use cases. These are **optional** — the [Cloudflare API MCP server](#cloudflare-api-mcp-server) already covers the full Cloudflare API. |
There was a problem hiding this comment.
| The following product-specific MCP servers are available for targeted use cases. These are **optional** — the [Cloudflare API MCP server](#cloudflare-api-mcp-server) already covers the full Cloudflare API. | |
| The following product-specific MCP servers are available for targeted use cases. These are **optional** — the [Cloudflare API MCP server](#cloudflare-api-mcp-server) already covers the full Cloudflare API. Most people should just use the main Cloudflare API MCP server. |
|
|
||
| The [Cloudflare API MCP server](https://github.com/cloudflare/mcp) provides access to the entire [Cloudflare API](/api/) — over 2,500 endpoints across DNS, Workers, R2, Zero Trust, and every other product — through just two tools: `search()` and `execute()`. | ||
| :::tip[You only need one MCP server] | ||
| The [Cloudflare API MCP server](https://github.com/cloudflare/mcp) at `https://mcp.cloudflare.com/mcp` provides access to the entire [Cloudflare API](/api/) — over 2,500 endpoints across DNS, Workers, R2, Zero Trust, and every other product. You do **not** need to install the product-specific servers listed below unless you have a specialized use case that requires them. |
There was a problem hiding this comment.
This MCP server now exposes a tool for reading docs
update docs accordingly
this shouldn't be a tip element
it should just be clear that this is the only MCP server you need, and doesn't need to mention the product-specific MCP servers at all
Co-authored-by: irvinebroque <irvinebroque@users.noreply.github.com>
|
All PR review feedback has been addressed. Here's what I changed:
Validation passes cleanly:
|
|
/bonk address all remaining PR feedback |
|
Preview URL: https://f3bf3ae3.preview.developers.cloudflare.com Files with changes (up to 15) |
Summary
Made two changes to
src/content/docs/agents/model-context-protocol/cloudflare/servers-for-cloudflare/index.mdxto make it unmistakably clear that users only need one MCP server:Added a prominent tip callout right under the "Cloudflare API MCP server" heading stating that the Cloudflare API MCP server covers the entire API and product-specific servers are optional.
Renamed the subsequent section from "Product-specific MCP servers" to "Optional product-specific MCP servers" and added an explicit note that these are optional because the Cloudflare API MCP server already covers the full Cloudflare API.
All checks pass (
pnpm run check,pnpm run format:core:check).Closes #31749
github run