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