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