# Google Maps Lead Finder Agent API & MCP [Verified owner] [Health: Active]

**Category:** 🔎 Search & Data Extraction  
**Repository:** https://gmapsleadfinder.com/docs/agent  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/google-maps-lead-finder-agent-api-mcp

## Description
Connect Claude, Cursor, Codex, or other MCP clients to GMaps Lead Finder through a remote MCP endpoint with Bearer authentication, documented tools, and usage limits.

## Tools
Capabilities this server exposes over MCP:

- **gmaps_me** — Get current GMaps Lead Finder plan and credit balance for the authenticated API key.
- **gmaps_create_job** — Create a Maps search job for exactly one keyword. Shares the single in-flight job limit with the web app (409 if another job is running).
- **gmaps_get_job** — Get maps job status and per-keyword file metadata. Poll until status is completed, partial, or failed.
- **gmaps_get_results** — Fetch paginated place rows as JSON for a finished maps job (respects user export column preferences).
- **gmaps_create_reviews_job** — Create a Google Maps reviews scrape job for exactly one place (Maps URL, maps.app.goo.gl / goo.gl/maps short link, or business_id 0x…:0x…). Shares the single in-flight job limit with maps jobs (409 if busy).
- **gmaps_get_reviews_job** — Get reviews job status. Poll until status is completed, partial, or failed.
- **gmaps_get_reviews_results** — Fetch paginated review rows as JSON for a finished reviews job.
- **gmaps_create_photos_job** — Create a Google Maps photos scrape job for exactly one place (Maps URL, maps.app.goo.gl / goo.gl/maps short link, business_id 0x…:0x…, or Place ID ChIJ…). Shares the single in-flight job limit (409 if busy).
- **gmaps_get_photos_job** — Get photos job status. Poll until status is completed, partial, or failed.
- **gmaps_get_photos_results** — Fetch paginated photo rows as JSON for a finished photos job.

## Claude Desktop Quick Installation
No generated config for this server: it installs through its own setup steps.

The project's own setup steps (from https://gmapsleadfinder.com/docs/agent), copied verbatim. Run them in order; they are not an mcpServers config.

1. Add to Claude Code:

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

## Documentation

## What Google Maps Lead Finder Agent API & MCP does

Google Maps Lead Finder Agent API & MCP provides an MCP connection to GMaps Lead Finder. It is intended for AI clients that support remote MCP connections and need access to the service's documented lead-finding tools.

This makes the endpoint and authentication details central to using the integration. It is a fit for workflows where an agent should invoke GMaps Lead Finder through MCP instead of interacting with the product outside the agent client.

## How it works

An MCP client connects to the remote endpoint provided by GMaps Lead Finder. The client authenticates requests with a Bearer token, then can use the documented tools exposed by the service. The available description does not provide the endpoint URL, request examples, tool names, parameter schemas, or response formats, so those details should be taken from the linked agent documentation before implementation.

Google Maps Lead Finder Agent API & MCP is subject to usage limits. Any automated workflow should account for those limits rather than assuming unlimited tool calls.

## Setup and configuration

Setup requires an MCP client that can connect to a remote MCP endpoint and send Bearer-authenticated requests. Obtain the endpoint and Bearer credential from the GMaps Lead Finder documentation or account setup, then configure them in the selected client according to that client's remote MCP configuration format.

It also does not state whether credentials can be supplied through environment variables or must be entered directly in client configuration. Avoid assuming a local installation is needed; the described connection method is remote.

## Tools and capabilities

Google Maps Lead Finder Agent API & MCP exposes documented tools supplied by GMaps Lead Finder. The source description does not list their individual names or describe their input and output fields, so this listing cannot reliably enumerate specific operations. Consult the linked documentation for the authoritative tool catalog and schemas.

At a capability level, the integration is designed to make GMaps Lead Finder available to an MCP-compatible agent. Its practical usefulness depends on the tools enabled by the remote service, the client's MCP support, valid Bearer authentication, and remaining usage allowance.

## Limitations and notes

The available description confirms remote access, Bearer authentication, documented tools, and usage limits, but does not provide detailed quotas, pricing, data coverage, error behavior, or client configuration examples. Those details should be verified in the service documentation before production use.

Google Maps Lead Finder Agent API & MCP should therefore be evaluated against the exact lead-finding operations required by the workflow. In particular, confirm that the documented tools support the intended task and that the service's usage limits accommodate expected call volume.

_Full upstream README: https://allmcps.com/mcp/google-maps-lead-finder-agent-api-mcp/readme_