Google Maps Mcp Server

io.github.TheNextGenNexusPublished by GitHub account TheNextGenNexusv1.0.1Updated Oct 27, 2026

Search local businesses, generate leads, and validate emails via Google Maps data

VerifiedSTDIODesktop onlyLocation & LifestyleWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Local MCP bridge that lets an assistant search Google Maps business listings, build B2B lead lists, and validate emails through Apify.

What you can do
  • Search local businesses on Google Maps by query.
  • Generate B2B lead lists with contact details from business listings.
  • Validate email addresses found in those listings.
  • Forward each tool call to the nexgendata Apify endpoint and return the results.
When to use it
Useful when you want an assistant to research local businesses, assemble prospect or lead lists with contact information, or check whether emails scraped from listings look valid, without leaving the chat.
Requirements
Runs locally over stdio, typically via npx or a global npm install, so Node.js and npm are needed. An Apify API token in the APIFY_TOKEN environment variable is optional; without it the server uses a rate-limited public endpoint. Network access to Apify is required.
Before you install
Tool calls are forwarded to a third-party Apify endpoint, so search queries and business data leave your machine. Lead generation collects contact information, which may carry privacy and anti-spam obligations. The README marks APIFY_TOKEN as optional while the manifest lists it as required, so check which applies. Scraped emails may be inaccurate; validation results should not be treated as guaranteed.

Installation

In SourceWeft

  1. Open Google Maps Mcp Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Google Maps MCP Server

Search local businesses, generate leads, and validate emails via Google Maps data — powered by nexgendata on Apify.

Quick Start

Using npx (recommended)

bash
npx @nexgendata/google-maps-mcp-server

Install globally

bash
npm install -g @nexgendata/google-maps-mcp-server

Configure with Claude Desktop

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

json
{      "mcpServers": {            "google-maps-mcp-server": {                  "command": "npx",                  "args": [                        "-y",                        "@nexgendata/google-maps-mcp-server"                  ],                  "env": {                        "APIFY_TOKEN": "your-apify-token-optional"                  }            }      }}

Configure with Cline

Add the same configuration to your Cline MCP settings.

Available Tools

ToolDescription
search_local_businessesSearch for local businesses on Google Maps
generate_leadsGenerate B2B leads with contact info from Google Maps
validate_emailsValidate email addresses found from business listings

Environment Variables

VariableRequiredDescription
APIFY_TOKENNoYour Apify API token for authenticated access. Without it, the server uses the public endpoint (rate-limited).

How It Works

This MCP server acts as a local stdio bridge to the nexgendata Apify MCP endpoint. When you call a tool, it forwards the request to Apify and returns the results.

Links

License

MIT

Source: servers/google-maps-mcp-server/README.md at commit 26dc208

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.