Fetch MCP Server: Setup Guide, Use Cases & Limitations

What Is Fetch MCP Server?

Fetch MCP Server enables Claude to make HTTP requests directly from a conversation — supporting GET and POST methods and returning parsed web content in multiple formats. It is maintained by the Model Context Protocol team as part of the official modelcontextprotocol/servers monorepo.

Quick Facts

What You Can Do With It

• API calls: Send GET or POST requests to external APIs and receive structured responses inside your Claude session.
• REST API testing: Quickly inspect endpoint responses, headers, and status codes without leaving your workflow.
• Web scraping: Fetch the raw or parsed content of a public URL to extract data for analysis or summarization.
• Content fetching: Pull documentation pages, JSON feeds, or plain-text resources on demand during a conversation.

How to Set It Up

Claude Code picks up MCP servers defined in .claude/mcp.json at the project or user level. Add the following entry:

{
  "mcpServers": {
    "fetch": {
      "command": "npx",
      "args": ["@modelcontextprotocol/server-fetch"]
    }
  }
}
**Claude Desktop** reads from `claude_desktop_config.json` (location: `~/Library/Application Support/Claude/` on macOS, `%APPDATA%\Claude\` on Windows). Add the same block under `mcpServers`:

```json
{
  "mcpServers": {
    "fetch": {
      "command": "npx",
      "args": ["@modelcontextprotocol/server-fetch"]
    }
  }
}

No API key or environment variable is required to start the server. Restart Claude Desktop after editing the config file. For Claude Code, the server is available immediately in any session that resolves the config file.

If you prefer a pinned version over npx resolution, install the package globally first:

npm install -g @modelcontextprotocol/server-fetch

Then replace "npx" with "node" and point args to the installed binary path.

Works Best With

Fetch MCP Server is verified compatible with both Claude Code and Claude Desktop. Claude Code is the natural fit for developer workflows — you can make API calls and inspect responses inline while writing or debugging code. Claude Desktop works well for ad-hoc content fetching or research tasks where you want to pull live web content into a conversation.

Known Limitations

• No built-in authentication handling: The server does not manage OAuth flows, cookie sessions, or token refresh. For protected endpoints, you must pass credentials explicitly in request headers or query parameters, which means sensitive tokens may appear in conversation context.
• No JavaScript rendering: Fetched pages are retrieved as static HTTP responses. Sites that require JavaScript execution to render content will return incomplete or empty HTML.
• Rate limiting is your responsibility: There is no built-in throttling or retry logic. If a target API enforces rate limits, repeated requests from Claude will consume your quota without automatic backoff.
• Response size: Very large responses may be truncated depending on Claude’s context window limits.
• HTTPS only for external resources: Requests to localhost or internal network addresses may work depending on your environment, but behavior is not guaranteed across all host configurations.

Community Resources

• GitHub Issues — modelcontextprotocol/servers — bug reports, feature requests, and usage questions for all official MCP servers including Fetch
• MCP Discord (via Anthropic) — community discussion on MCP integrations and server configuration
• r/ClaudeAI on Reddit — search “fetch MCP” for user-reported configurations and workarounds