Google Maps Scraper MCP Server

Most search and retrieval work still happens through a UI a human drives. Google Maps Scraper MCP server moves it into the conversation instead. Live Google Maps business search, review, and photo data for AI agents over MCP.

The short version

Give your AI agent live Google Maps business search, review, and photo data through one secure Model Context Protocol connection.

This is a public discovery, configuration, and documentation repository. It contains:

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

The tools it exposes

The server publishes 6 tools. What each one is for:

• Cursor — The Cursor tool exposed by this server
• Codex — [mcp_servers.google-maps-scraper-mcp.headers] Authorization = "Bearer YOUR_API_KEY"
• Cline — The Cline tool exposed by this server
• search_google_maps — Search for businesses and places on Google Maps in real time
• get_place_reviews — Retrieve public reviews for a place using the fid returned by search_google_maps
• get_place_photos — Retrieve public photos for a place using the fid returned by search_google_maps

What it needs from you

Configuration is passed through the environment: YOUR_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Among the search and retrieval options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Google Maps Scraper's toolset — Cursor, Codex, Cline and 3 more — is a fair guide to whether it matches your workflow. It is maintained by com.gmapsextractor; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Google Maps Scraper's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.