maps-fetcher-mcp
Related Servers
Alternatives to maps-fetcher-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables 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.13MIT
- FlicenseNot gradedqualityDmaintenanceEnables 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-
- AlicenseAqualityBmaintenanceEnables AI assistants to search places, retrieve place details, reviews, photos, business posts, and contributor review histories from Google Maps through natural language, with no API keys or paid billing required.6MIT
- AlicenseNot gradedqualityDmaintenanceEnables 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.6 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to search and scrape Google Maps places data (name, rating, address, etc.) directly without an API key.-
- FlicenseNot gradedqualityCmaintenanceMCP server for extracting Google Maps photos as structured JSON, supporting search by place name, URL, or ID, with category filters and stable photo IDs. Enables users to pull full-size image URLs, thumbnails, and gallery metadata for any business or landmark directly through natural language.-
TDQS
Scored across 4 tools
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.
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.
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.
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.