de en es ja ko ru zh

Google Maps MCP Server

Name: Google Maps MCP Server
Author: devsanthoshmk

by devsanthoshmk

Overview Schema Related Servers Score Discussions

Python

Hybrid

🗺️ Google Maps MCP сервер (`gmaps-mcp`)

MCP Version Python License: MIT

Самодостаточный, легковесный Google Maps Model Context Protocol (MCP) сервер, построенный на официальном MCP Python SDK. Он предоставляет AI-агентам (таким как Claude Desktop, Cursor, Cline и Antigravity) структурированные результаты поиска, информацию о местах, рейтинги, контактные данные, координаты и ссылки на Google Maps.

⚡ Ключевые возможности

Установка одной командой: Запускается мгновенно из любого места через uvx без ручной настройки окружения.
100% автономность: Движок парсинга встроен нативно в процесс через asyncio и aiohttp — не требуется внешних подпроцессов, безголовых браузеров или ключей API.
Богатые структурированные данные о местах: Возвращает идентификаторы мест, названия бизнесов, категории, адреса, местные и международные номера телефонов, URL-адреса веб-сайтов, координаты (lat/long), звездные рейтинги, количество отзывов и прямые ссылки на Google Maps.
Stdio и Streamable HTTP: Встроенная поддержка stdio для десктопных AI-клиентов и streamable-http для удаленных/контейнеризированных развертываний.
Чистый JSON-RPC: Все внутреннее логирование строго направляется в stderr, поддерживая поток протокола stdio на 100% совместимым.

Related MCP server: Google Maps MCP Server

🚀 Быстрый старт

Запуск напрямую с помощью uvx:

# Run directly from GitHub repository
uvx --from git+https://github.com/<your-username>/gmaps-mcp.git gmaps-mcp

Или из локального клона:

uv run gmaps-mcp

🛠️ Настройка MCP-клиента

1. Claude Desktop

Добавьте это в ваш claude_desktop_config.json (~/Library/Application Support/Claude/claude_desktop_config.json на macOS, или %APPDATA%\Claude\claude_desktop_config.json на Windows):

{
  "mcpServers": {
    "google-maps": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/<your-username>/gmaps-mcp.git",
        "gmaps-mcp"
      ]
    }
  }
}

Если запуск из локальной папки:

{
  "mcpServers": {
    "google-maps": {
      "command": "uv",
      "args": [
        "run",
        "--directory",
        "/absolute/path/to/gmap-mcp",
        "gmaps-mcp"
      ]
    }
  }
}

2. Cursor IDE

В Cursor откройте Settings → Features → MCP (или отредактируйте .cursor/mcp.json в вашем проекте):

{
  "mcpServers": {
    "google-maps": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/<your-username>/gmaps-mcp.git",
        "gmaps-mcp"
      ]
    }
  }
}

3. Cline (расширение VS Code)

В настройках Cline (cline_mcp_settings.json):

{
  "mcpServers": {
    "google-maps": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/<your-username>/gmaps-mcp.git",
        "gmaps-mcp"
      ]
    }
  }
}

🧰 Доступные инструменты

1. `search_google_maps`

Поиск по Google Maps для бизнесов, достопримечательностей, услуг и ориентиров.

Параметр	Тип	По умолчанию	Описание
`query`	`string`	(обязательно)	Поисковый запрос (например, `"coffee in Koramangala Bangalore"`, `"dentists near Connaught Place Delhi"`, `"Italian restaurants in New York"`).
`limit`	`integer`	`10`	Максимальное количество результатов для возврата (от `1` до `50`).
`country`	`string`	`"in"`	Двухбуквенный код страны ISO для локализации региона (например, `"in"`, `"us"`, `"gb"`, `"de"`, `"fr"`, `"ae"`).
`language`	`string`	`"en"`	Код языка для результатов (например, `"en"`, `"hi"`, `"es"`, `"fr"`).

Структура вывода

{
  "query": "coffee in Koramangala Bangalore",
  "country": "in",
  "language": "en",
  "total_results": 2,
  "places": [
    {
      "place_id": "ChIJ80IECk8UrjsRqCffDjE09lw",
      "name": "Dyu Art Cafe",
      "category": "Art cafe",
      "address": "KHB MIG Colony, 1st Cross Rd, Koramangala 8th Block, Bengaluru, Karnataka 560095",
      "phone": "096113 19774",
      "international_phone": "+91 96113 19774",
      "website": "http://www.dyuartcafe.com/",
      "domain": "dyuartcafe.com",
      "latitude": 12.9373076,
      "longitude": 77.6176544,
      "rating": 4.4,
      "review_count": 21440,
      "google_maps_url": "https://www.google.com/maps/place/?q=place_id:ChIJ80IECk8UrjsRqCffDjE09lw"
    }
  ]
}

2. `get_place_details`

Получение подробной информации об одном конкретном месте или бизнесе по его идентификатору места или названию.

Параметр	Тип	По умолчанию	Описание
`place`	`string`	(обязательно)	Google Place ID (например, `"ChIJ12k5kG_iDDkRwuzibQwYZ4M"`) или точное название бизнеса/достопримечательности (например, `"AIIMS New Delhi"`).
`country`	`string`	`"in"`	Двухбуквенный код страны ISO (по умолчанию: `"in"`).
`language`	`string`	`"en"`	Код языка для ответа (по умолчанию: `"en"`).

🌐 Удаленное развертывание (Streamable HTTP)

Сервер поддерживает современный транспорт Streamable HTTP для развертывания за обратными прокси или в облачных хостингах:

# Start Streamable HTTP server on port 8000
uv run gmaps-mcp --transport streamable-http --host 0.0.0.0 --port 8000

MCP-эндпоинт будет доступен по адресу: http://<host>:8000/mcp

🧪 Разработка и тестирование

Запуск модульных и интеграционных тестов с помощью uv:

# Run pytest test suite
uv run --with pytest --with pytest-asyncio pytest tests/ -v

# Run the server locally with debug logs
uv run gmaps-mcp --log-level DEBUG

📦 Структура проекта

gmap-mcp/
├── pyproject.toml              # Packaging & dependencies (PEP 517/621)
├── README.md                   # Setup guide and MCP client docs
├── src/
│   └── gmaps_mcp/
│       ├── __init__.py         # Package entry
│       ├── schemas.py          # Pydantic data models (Place, Search, Details)
│       ├── server.py           # MCPServer instance & CLI runner
│       ├── tools.py            # MCP Tool definitions & detailed descriptions
│       └── scraper/
│           ├── __init__.py     # Scraper API
│           └── crawler.py      # Async Google Maps parser & extraction engine
└── tests/
    ├── test_schemas.py         # Schema tests
    ├── test_crawler.py         # Parser unit tests
    └── test_server.py          # MCP Server registration & tool calling tests

📜 Атрибуция и лицензия

Ядро парсера адаптировано и модуляризировано из christivn/mapScraper (коммит 1b38cf3e153294e3dad2f6cb5862be0201a54065).
Лицензировано под MIT License.

Available Tools

2 tools

get_place_detailsA

Retrieve detailed information for a single specific Google Maps place or business. Looks up a place using its unique Google Place ID (e.g., 'ChIJ...' or 'place_id:ChIJ...') or specific landmark/business name. Returns complete structured details including address, phone number, website, rating, coordinates, and Google Maps URL.

ParametersJSON Schema

Name	Required	Description	Default
`place`	Yes	The place identifier to fetch details for. Can be either: 1. A Google Place ID (e.g., 'ChIJ12k5kG_iDDkRwuzibQwYZ4M' or 'place_id:ChIJ...') 2. An exact place / business name and location (e.g., 'AIIMS New Delhi' or 'Taj Mahal Palace Mumbai').
`country`	No	Two-letter ISO country code for region localization (default: 'in').	in
`language`	No	Language code for the response (default: 'en').	en

Output Schema

ParametersJSON Schema

Name	Required	Description
`found`	No	Whether the place was successfully found
`place`	No	The retrieved place object if found, otherwise null
`query_or_id`	Yes	The place query or Place ID searched for

TDQS

A4.2/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It discloses the lookup behavior (by ID or name) and the return fields (address, phone, etc.), but does not mention rate limits, authentication requirements, or what happens if the place is not found. Adequate but not comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the main purpose, and each sentence adds essential information. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity, the description covers the key purpose, parameter usage, and return value hints. The presence of an output schema reduces the need to describe return values. Minor gaps exist (e.g., error behavior), but overall it is sufficiently complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value by explaining the two formats for the 'place' parameter (Google Place ID vs. name/location), which goes beyond the schema's description. This additional context justifies a 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly specifies the verb 'retrieve' and the resource 'detailed information for a single specific Google Maps place or business'. It distinguishes from sibling tool 'search_google_maps' by emphasizing single-place lookup vs. searching.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use this tool (to get details for a known place via ID or name) and implicitly distinguishes from searching. It does not explicitly state when not to use it or mention alternatives beyond the sibling context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_google_mapsA

Search Google Maps for local businesses, places, points of interest, and services. Returns structured place data including business name, Google Place ID, category, formatted street address, phone numbers, website URL, geo-coordinates (latitude/longitude), star rating, total review count, and direct Google Maps URL.

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of place results to return (between 1 and 50, default is 10).
`query`	Yes	The search query for Google Maps. Can be a business category, specific place name, service, or landmark along with a location. Examples: 'coffee shops in Koramangala Bangalore', 'dentists near Connaught Place Delhi', 'Italian restaurants in Bandra Mumbai', 'hospitals in Hyderabad', 'electricians near Indiranagar', 'museums in London'.
`country`	No	Two-letter ISO 3166-1 alpha-2 country code to localize search results and map boundaries. Default is 'in' (India). Other examples: 'us' (United States), 'gb' (United Kingdom), 'ca' (Canada), 'au' (Australia), 'de' (Germany), 'fr' (France), 'sg' (Singapore), 'ae' (UAE).	in
`language`	No	Language code for the results (e.g. 'en' for English, 'hi' for Hindi, 'es' for Spanish, 'fr' for French, 'de' for German, 'ja' for Japanese). Default is 'en'.	en

Output Schema

ParametersJSON Schema

Name	Required	Description
`query`	Yes	The search query that was executed
`places`	No	List of matched Google Maps places
`country`	Yes	The ISO 3166-1 alpha-2 country code used (e.g., 'in', 'us')
`language`	Yes	The language code used for results (e.g., 'en', 'hi')
`total_results`	Yes	Number of places returned in this response

TDQS

A3.9/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden. It states it returns structured place data listing 10 fields, which is helpful. However, it does not disclose potential rate limits, API quota implications, or any constraints on search frequency or result freshness. The behavioral disclosure is adequate but not comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that front-loads the main action. It then lists the return fields, which is useful but slightly verbose for a search tool. It earns its place without unnecessary fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (4 params, 1 required, no nested objects) and presence of an output schema, the description is fairly complete. It explains the search scope and return fields. It could be improved by noting that results are limited by Google's ranking (not just the limit parameter) and how to formulate effective queries beyond the examples.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds no parameter-level detail beyond what the schema already provides. It lists the return fields but not how parameters affect them. Since the schema is already thorough, no penalty is applied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses specific verbs ('Search') and resources ('Google Maps for local businesses, places, points of interest, and services'), clearly distinguishing it from its sibling tool 'get_place_details' which would provide details on a specific place.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies this tool is for broad searches (businesses, places, POIs), and the sibling tool name 'get_place_details' suggests the alternative for specific place info. However, no explicit when-to-use or when-not-to-use guidance is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

2 tool updatesv0.1.0Aug 18, 2026
- First observedget_place_details
- First observedsearch_google_maps

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.7/5.0

Disambiguation4/5

The two tools have distinct purposes: search_google_maps finds places by query, and get_place_details retrieves details for a known place ID. There is slight overlap in the returned fields, but the use cases are clearly different.

Naming Consistency4/5

Both tools use a clear verb_noun pattern (search/get + google_maps/place_details). The naming is consistent, though 'get_place_details' could be more symmetrical as 'get_google_maps_place' for perfect parity.

Tool Count2/5

Only two tools for a Google Maps server is very limited. Maps APIs typically support additional operations like directions, geocoding, or place photos, so the tool count feels too small for the implied scope.

Completeness2/5

The core search and detail retrieval are present, but critical operations like navigation (directions), geocoding (address to coordinates and reverse), and place photo fetching are missing, creating significant gaps for common map-related tasks.

Maintenance

ActivityMaintained

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Google Maps Scraper
com.gmapsextractor
Live Google Maps business search, review, and photo data for AI agents over MCP.
Web Scraping Location Services
21
HasData AOAuth
com.hasdata.mcp
Direct access to 40+ scraping and search tools. Extract structured data from Google (Search, Maps, Trends), Amazon, Airbnb, Social Media, and any web page directly into your AI agent.
Browser Automation RAG Systems Web Scraping
2
HasData Google MapsOAuth
com.hasdata
Google Maps places, reviews, contributor history, photos and posts as JSON. No Google Cloud.
Location Services Web Scraping
16
mcp A
com.googleapis.mapstools
Ground your AI applications with trusted geospatial data from Google Maps.
Location Services Search AI & Machine Learning
52

Related MCP Servers

Google Maps MCP Server
Location Services Search
iceener
F
license
Not graded
quality
C
maintenance
Enables location-aware AI agents to search for nearby places, get detailed place information including hours and ratings, and calculate routes with turn-by-turn directions using Google Maps APIs.
Updated a month ago (2026-07-27 13:22 UTC)
22
-
Google Maps MCP Server
Location Services Search Travel & Transportation
arthurkatcher
A
license
A
quality
B
maintenance
Enables AI assistants to access Google Maps services including places search, details, directions, geocoding, and nearby search through natural language.
Updated 4 months ago (2026-05-04 08:04 UTC)
6
2
MIT
maps-scrapper
Web Scraping Browser Automation Location Services
rahul-bhatt43
F
license
Not graded
quality
C
maintenance
Enables AI assistants to search and scrape Google Maps places data (name, rating, address, etc.) directly without an API key.
Updated a month ago (2026-08-10 05:14 UTC)
-
gmapsscraper
Web Scraping Location Services Search
gmapsscraper
A
license
A
quality
B
maintenance
Enables AI assistants to scrape Google Maps business data (names, addresses, phones, emails, websites, ratings, etc.) through natural language queries, with tools for synchronous and asynchronous scraping and credit checking.
Updated a month ago (2026-08-04 04:55 UTC)
4
49
3
MIT

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/devsanthoshmk/gmaps-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

🗺️ Google Maps MCP сервер (gmaps-mcp)

⚡ Ключевые возможности

🚀 Быстрый старт

🛠️ Настройка MCP-клиента

1. Claude Desktop

2. Cursor IDE

3. Cline (расширение VS Code)

🧰 Доступные инструменты

1. search_google_maps

Структура вывода

2. get_place_details

🌐 Удаленное развертывание (Streamable HTTP)

🧪 Разработка и тестирование

📦 Структура проекта

📜 Атрибуция и лицензия

Available Tools

Output Schema

TDQS

Output Schema

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers