fetch_url_content — Web Content Extract Mcp MCP Tool Read-only
fetch_url_content
(fetch url content) is one of 5 tools on the
Web Content Extract Mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call fetch_url_content from your client
- Claude Code Web Content Extract Mcp fetch_url_content run in your project directory
- Claude Desktop Web Content Extract Mcp fetch_url_content ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Web Content Extract Mcp fetch_url_content ~/.cursor/mcp.json
- VS Code Web Content Extract Mcp fetch_url_content .vscode/mcp.json
- Zed Web Content Extract Mcp fetch_url_content ~/.config/zed/settings.json
- Windsurf Web Content Extract Mcp fetch_url_content ~/.codeium/windsurf/mcp_config.json
- Cline Web Content Extract Mcp fetch_url_content ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Web Content Extract Mcp fetch_url_content ~/.gemini/settings.json
- Grok Web Content Extract Mcp fetch_url_content .mcp.json (in your project root)
- ChatGPT Web Content Extract Mcp fetch_url_content Settings → Connectors → Advanced → Developer mode
- Claude.ai Web Content Extract Mcp fetch_url_content Settings → Connectors → Add custom connector
- LangChain Web Content Extract Mcp fetch_url_content pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http web_content_extract_mcp https://web-content-extract-mcp.mcpize.run/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.