local_search — google maps mcp server MCP Prompt
local_search
is one of 2 prompts on the
google maps mcp server
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke local_search from your client
- Claude Code google maps mcp server Prompt/local_search run in your project directory
- Claude Desktop google maps mcp server Prompt/local_search ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor google maps mcp server Prompt/local_search ~/.cursor/mcp.json
- VS Code google maps mcp server Prompt/local_search .vscode/mcp.json
- Zed google maps mcp server Prompt/local_search ~/.config/zed/settings.json
- Windsurf google maps mcp server Prompt/local_search ~/.codeium/windsurf/mcp_config.json
- Cline google maps mcp server Prompt/local_search ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI google maps mcp server Prompt/local_search ~/.gemini/settings.json
- Grok google maps mcp server Prompt/local_search .mcp.json (in your project root)
- ChatGPT google maps mcp server Prompt/local_search Settings → Connectors → Advanced → Developer mode
- Claude.ai google maps mcp server Prompt/local_search Settings → Connectors → Add custom connector
- LangChain google maps mcp server Prompt/local_search pip install langchain-mcp-adapters
Other prompts on this server
google maps mcp server also offers 1 resource — data you attach as context, where a prompt is something you run.
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.