Skip to main content
Glama

maps-fetcher-mcp

MCP-Server + CLI: Rufe jeden Google-Maps-Ort per Link ab – vollständige Geschäftsdaten plus ALLE Galerie-Fotos und -Videos in maximaler Auflösung.

Installation

pip install maps-fetcher-mcp          # or: uv pip install maps-fetcher-mcp
maps-fetcher-setup                    # one-time: browser download (~120MB)

Related MCP server: Local Business Data MCP Server

Als MCP-Server verwenden (beliebiger MCP-Client)

{
  "mcpServers": {
    "maps_fetcher": {
      "command": "maps-fetcher-mcp"
    }
  }
}

Funktioniert mit: Hermes Agent, Claude Desktop, Cursor, opencode, Cline, Zed – alles, was MCP (stdio) spricht.

Als CLI verwenden

maps-fetcher "https://maps.app.goo.gl/XXXX"                  # everything
maps-fetcher "https://maps.app.goo.gl/XXXX" --include info   # metadata only (~20s)
maps-fetcher "https://maps.app.goo.gl/XXXX" --include photos
maps-fetcher "https://maps.app.goo.gl/XXXX" --include videos
maps-fetcher --list                                          # what's been fetched

Verfügbare Tools (MCP)

Tool

Zweck

Typische Zeit

get_place_info

Nur Metadaten: Name, Telefon, Bewertung, Adresse, Öffnungszeiten, Koordinaten

~20s

get_place_media

Nur Medien (kind: photos / videos / both)

40-220s

fetch_maps_place

Alles auf einmal (include: all/info/photos/videos/media)

60-220s

list_maps_places

Zuvor abgerufene Orte

sofort

Derselbe Ort, der innerhalb von 24 Stunden erneut abgerufen wird, nutzt das Scrape erneut (~2s).

Was es verarbeitet

  • Kurzlinks werden aufgelöst und kanonisiert; Suchlinks werden sauber abgelehnt

  • Video-Kacheln, die als Fotos getarnt sind; DASH/HLS-Manifeste mit Audio gemuxt

  • Abgelaufene URLs, Avatar-Müll, Bewegungsunschärfe-Frames, wahrnehmungsbezogene Duplikate (unter Quarantäne, nicht gelöscht), lückenlose Dateinummerierung

  • Nichtdeterministisches Lazy-Loading der Galerie: Scrape wird wiederholt und zusammengeführt

  • Bot-Erkennung (reCAPTCHA / ungewöhnlicher Datenverkehr) mit sauberen Fehlern; Stealth-Browser über Patchright, einfacher Playwright-Fallback

  • Sicherheit: Google-Host-Allowlist für alle Medien-Downloads, Größenlimits pro Datei und pro Ort, Schutz vor Dekompressionsbomben, keine Geheimnisse

Ausgabe

<root>/<place-slug>/
  photos/photo_01.jpg ...   videos/video_01.mp4 ...   quarantine/
  info_pw.json              contact_sheet.jpg

Standard-Root: /mnt/d/Projects/maps-data-fetcher/places (WSL-Layout; überschreibbar mit output_dir oder MAPS_FETCHER_ROOT).

Grenzen

Inoffizielles Scraping – gut für Batch-Sammlungen bei geringem Volumen. Google-Markup-Änderungen können es brechen (Fixes sind meist klein). Nicht für Produktion mit hohem Volumen; nutze dafür die kostenpflichtige Google Places API. CAPTCHAs werden erkannt und gemeldet, nicht automatisch gelöst.

Entwicklung

Quellcode-Layout: maps_fetcher/core.py (Engine), mcp_server.py (MCP-Tools), cli.py (CLI), setup.py (Browser-Installationshelfer).

Available Tools

4 tools
fetch_maps_placeA

Fetch a Google Maps place by link (maps.app.goo.gl/... or full google.com/maps URL). Downloads gallery media at max resolution plus business metadata (name, phone, website, rating, address, plus code, hours, coordinates).

Args: url: Google Maps place link (single place only, not search links). output_dir: optional root directory (default: /mnt/d/Projects/maps-data-fetcher/places). A per-place subfolder is created with photos/, videos/, info_pw.json, contact_sheet.jpg. include: "all" (default) | "info" (metadata only, fast) | "photos" | "videos" | "media" (photos+videos). meta_only: deprecated alias for include="info".

Returns JSON summary: place data, media counts, output paths. Typical run: info ~20-40s, full fetch 60-220s.

Inputs: url (required), include, meta_only, output_dir. Returns: result

get_place_infoA

Fast metadata-only fetch: name, phone, website, rating, address, plus code, hours, coordinates. No media downloaded. Use when the agent only needs business info. ~20-40s.

Inputs: url (required), output_dir. Returns: result

get_place_mediaA

Media-only fetch: downloads gallery photos and/or videos, skips verbose metadata in the response. Use when the agent only needs the images/videos.

Args: kind: "both" (default) | "photos" | "videos". Returns JSON: place name, counts, output dirs.

Inputs: url (required), kind, output_dir. Returns: result

list_maps_placesC

List previously fetched places under the output root with photo/video counts and metadata.

Inputs: output_dir. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 4 tools

    Disambiguation2/5

    There is significant overlap: fetch_maps_place with include='info' does exactly what get_place_info does, and with include='media' does what get_place_media does. While the descriptions clarify the intended use cases, an agent may struggle to pick the right tool since fetch_maps_place is a superset. The tools are not clearly distinct in purpose.

    Naming Consistency2/5

    The naming mixes conventions: 'get_place_info' and 'get_place_media' follow a get_place_N pattern, but 'fetch_maps_place' uses a different verb (fetch) and noun order, and 'list_maps_places' uses plural. The pattern is not consistent across all tools, though the tools are readable.

    Tool Count4/5

    At 4 tools, the server is well-scoped for a maps fetcher. However, the presence of get_place_info and get_place_media is redundant given fetch_maps_place can achieve the same via its include parameter, suggesting the count could be trimmed to 2–3 tools without losing functionality.

    Completeness4/5

    The core lifecycle for fetching Google Maps place data is covered: retrieving metadata, media, or both, plus listing previously fetched places. There are no obvious dead ends for the stated purpose. Missing delete/update operations are not essential for a fetcher, so the surface feels complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables web searching via Google Search and AI Mode, plus advanced web scraping capabilities including content extraction in multiple formats, link extraction, and batch scraping of multiple URLs.
      14 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables access to Google Maps business data including search, reviews, photos, and geocoding. Supports searching businesses by location, area, or coordinates, retrieving detailed business information, reviews, and performing reverse geocoding operations.
      13
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables advanced web crawling and content extraction with JavaScript support, AI-powered analysis, PDF/Office document processing, YouTube transcript extraction, Google search integration, and multi-format data export capabilities.
      2
      -