Problem it solves

You’re implementing against an unfamiliar API and need to read the docs. The old workflow: open browser, find the page, read it, switch back to Claude, paste the relevant parts, explain the context. When you’re integrating with three different services in an afternoon, that context-switching adds up.

Fetch MCP lets Claude read any public URL directly. Point it at a documentation page, a GitHub README, a changelog, an RFC — Claude fetches the content, converts it to clean markdown, and reads it as part of your session. No copy-pasting required.

How to install

Terminal window
claude mcp add --transport stdio fetch -- npx -y @modelcontextprotocol/server-fetch

No API keys needed. This is an official Anthropic reference implementation. Restart Claude Code after running the command and confirm with /mcp.

How to use

Pass URLs to Claude directly in your prompts:

Claude will fetch the page, parse it, and use the content to inform its response — just like it would if you’d pasted the text manually, but faster and without the copy-paste step.

Pro tips

Pair with Brave Search for full research flow. Brave Search finds the right URL; Fetch reads the full content. The workflow looks like: “Search for the Astro content collections docs, then fetch the top result and show me how to define a custom schema.” Two MCP servers working together to handle the full research loop.

Read changelogs before upgrades. Before bumping a major dependency version, ask Claude to fetch the changelog and summarize breaking changes. Takes 10 seconds and can save an hour of debugging.

Fetch OpenAPI specs directly. If a service you’re integrating with publishes an OpenAPI or Swagger spec at a public URL, fetch it: “Read https://api.example.com/openapi.json and generate a TypeScript client.” Claude will work from the real spec, not from its potentially outdated training data.

When NOT to use

Fetch MCP cannot access pages that require login — authenticated dashboards, private GitHub repos, anything behind a paywall or auth wall. For those, you still need to copy-paste content manually. Also, very large pages may be truncated; for those cases, consider fetching a more specific subpage or section of the docs rather than the top-level URL.