Guides

Agent API & MCP

Connect Claude, Cursor, Codex, or any MCP client to GMaps Lead Finder over HTTPS. For install-first marketing and example prompts, see Agents. Prefer Remote MCP here; use the HTTP API reference when you need raw endpoints.

Your personal key starts with gmf_. Pass it from the client—it is not a server-wide secret. Plans that include API are listed on Pricing. Open Account → API key

Back to Agents HTTP API reference

Endpoint & authorization

Remote MCP is Streamable HTTP. Point your client at the URL below and send your gmf_ key in the Authorization header on every request.

Endpoint

url

https://gmapsleadfinder.com/mcp

Authorization

http

Authorization: Bearer gmf_<your_key>

Tools: gmaps_me, gmaps_create_job, gmaps_get_job, gmaps_get_results.

Remote MCP (recommended)

Hosted at https://gmapsleadfinder.com/mcp. Add it once; Claude, Cursor, Codex, Claude Desktop, and other MCP clients call tools over HTTPS with your key.

Commands below use gmf_YOUR_API_KEY until your key is available. After sign-in, open Account → API key to copy your gmf_ key.

claude mcp add --transport http gmaps-finder https://gmapsleadfinder.com/mcp \
  --header "Authorization: Bearer gmf_YOUR_API_KEY"

HTTP API

Need REST instead of MCP? Use Bearer gmf_… against /api/v1. Full request and response details are in the HTTP API reference.

API and the Online Lead Extractor share one running job per user (HTTP 409 if busy).

Full HTTP API reference

Limits & errors

One keyword per API job. Respect credit balance from /me. Concurrent job attempts return 409. Unauthorized or ineligible keys return 401/403—confirm your plan on Pricing and regenerate keys in Account if needed.

OpenAPI

Machine-readable stub available at /openapi-agent.yaml.

/openapi-agent.yaml

Get API key Back to Agents View pricing