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