explore_locality_data — DataGraph MCP Prompt

explore_locality_data is one of 3 prompts on the DataGraph MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke explore_locality_data from your client

• Claude Code DataGraph Prompt/explore_locality_data run in your project directory
• Claude Desktop DataGraph Prompt/explore_locality_data ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor DataGraph Prompt/explore_locality_data ~/.cursor/mcp.json
• VS Code DataGraph Prompt/explore_locality_data .vscode/mcp.json
• Zed DataGraph Prompt/explore_locality_data ~/.config/zed/settings.json
• Windsurf DataGraph Prompt/explore_locality_data ~/.codeium/windsurf/mcp_config.json
• Cline DataGraph Prompt/explore_locality_data ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI DataGraph Prompt/explore_locality_data ~/.gemini/settings.json
• Grok DataGraph Prompt/explore_locality_data .mcp.json (in your project root)
• ChatGPT DataGraph Prompt/explore_locality_data Settings → Connectors → Advanced → Developer mode
• Claude.ai DataGraph Prompt/explore_locality_data Settings → Connectors → Add custom connector
• LangChain DataGraph Prompt/explore_locality_data pip install langchain-mcp-adapters

Other prompts on this server

• analyze_gosr_dataset
• cypher_query_builder

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.