Google Maps Lead Finder Agent API & MCP

Connects MCP clients to GMaps Lead Finder through a Bearer-authenticated remote endpoint.

Install Google Maps Lead Finder Agent API & MCP

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)

~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "google-maps-lead-finder-agent-api-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "google-maps-lead-finder-agent-api-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Hosted endpoint

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint

https://gmapsleadfinder.com/mcp

Overview

Google Maps Lead Finder Agent API & MCP MCP server connects Claude, Cursor, Codex, and other MCP clients to GMaps Lead Finder through a remote MCP endpoint. Requests use Bearer authentication, and the service exposes documented tools for lead-finding workflows. Reach for it when an agent needs to work with GMaps Lead Finder rather than a locally hosted MCP process. Usage limits apply.

Use cases

Connect Claude to GMaps Lead Finder
Configure Cursor to call remote lead-finding tools
Authorize Codex with a Bearer token
Check documented MCP tool support before building an agent workflow

Key features

Remote MCP endpoint
Bearer authentication
Documented lead-finding tools
Claude, Cursor, and Codex connectivity
Usage limits

Tools10

What Google Maps Lead Finder Agent API & MCP lets your agent do. Expand a tool for its parameters.

Verified live~847 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

8/8 checks healthy over the last 29d

What it can do

From the 10 tools this server returned when we ran it.

Handles credentials · 1Makes network requests · 5Read-only tools · 10

Observed 2026-10-15 in an isolated sandbox. A description of reach, not a security audit.

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

MaintenanceActively maintainedStatus declared by the project or listing owner.

Availability100%Our rolling endpoint + install checks that succeeded.

Tools exposed10Callable tools this server registers over MCP.

Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Google Maps Lead Finder Agent API & MCP works

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.

Read the full README

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Google Maps Lead Finder Agent API & MCP

Google Maps Lead Finder Agent API & MCP is an MCP server that connects MCP clients to GMaps Lead Finder through a remote MCP endpoint. It exposes documented tools for lead-finding workflows, uses Bearer authentication, and applies usage limits. Claude, Cursor, Codex, and other compatible MCP clients can connect.

You connect an MCP client to the remote endpoint rather than installing a local package.

Use Bearer authentication when connecting to the remote MCP endpoint. The available description confirms that a Bearer credential is required, but it does not explain how to obtain the credential or where each client expects it in configuration.

Yes, Cursor is named as a supported MCP client. Configure Cursor to use the remote endpoint and provide the required Bearer authentication details, following the service documentation for the exact connection format.

Check the linked GMaps Lead Finder documentation before estimating call volume or designing automated workflows.

Related MCP servers

All in Search & Data Extraction All alternatives

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Google Maps Lead Finder Agent API & MCP AllMCPs Directory Badge

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/google-maps-lead-finder-agent-api-mcp?style=directory)](https://allmcps.com/mcp/google-maps-lead-finder-agent-api-mcp)

HTML Embed

<a href="https://allmcps.com/mcp/google-maps-lead-finder-agent-api-mcp"><img src="https://allmcps.com/api/badge/google-maps-lead-finder-agent-api-mcp?style=directory" alt="Google Maps Lead Finder Agent API & MCP on AllMCPs" /></a>