get_page_contents — FetchMCP API MCP Tool Read-only
get_page_contents
(get page contents) is one of 2 tools on the
FetchMCP API
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_page_contents from your client
- Claude Code FetchMCP API get_page_contents run in your project directory
- Claude Desktop FetchMCP API get_page_contents ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor FetchMCP API get_page_contents ~/.cursor/mcp.json
- VS Code FetchMCP API get_page_contents .vscode/mcp.json
- Zed FetchMCP API get_page_contents ~/.config/zed/settings.json
- Windsurf FetchMCP API get_page_contents ~/.codeium/windsurf/mcp_config.json
- Cline FetchMCP API get_page_contents ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI FetchMCP API get_page_contents ~/.gemini/settings.json
- Grok FetchMCP API get_page_contents .mcp.json (in your project root)
- ChatGPT FetchMCP API get_page_contents Settings → Connectors → Advanced → Developer mode
- Claude.ai FetchMCP API get_page_contents Settings → Connectors → Add custom connector
- LangChain FetchMCP API get_page_contents pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http fetchmcp https://fetchmcp.net/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 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.