website_to_json — website to json MCP Tool
website_to_json
(website to json) is one of 1 tool on the
website to json
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call website_to_json from your client
- Claude Code website to json website_to_json run in your project directory
- Claude Desktop website to json website_to_json ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor website to json website_to_json ~/.cursor/mcp.json
- VS Code website to json website_to_json .vscode/mcp.json
- Zed website to json website_to_json ~/.config/zed/settings.json
- Windsurf website to json website_to_json ~/.codeium/windsurf/mcp_config.json
- Cline website to json website_to_json ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI website to json website_to_json ~/.gemini/settings.json
- Grok website to json website_to_json .mcp.json (in your project root)
- ChatGPT website to json website_to_json Settings → Connectors → Advanced → Developer mode
- Claude.ai website to json website_to_json Settings → Connectors → Add custom connector
- LangChain website to json website_to_json pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http website-to-json https://data.dataleads.pro/mcp/website-to-json
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.