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