GeoGridAPI MCP server
OfficialRelated Servers
Alternatives to GeoGridAPI MCP server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to run Google Maps geo-grid rank scans and local SEO research, including keyword discovery, rank maps, competitor leaderboards, and rank lookups at specific places. It connects stdio MCP clients to a hosted endpoint using a single API token, so every tool is scoped to the user's account.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to search Google Maps places and retrieve reviews, photos, scrape jobs, results, and exports through a hosted MCP API.MIT
- -licenseNot gradedqualityCmaintenanceEnables AI assistants to perform comprehensive SEO and GEO measurements, including site audits, keyword research, ranking tracking, and brand visibility analysis across search engines and generative AI platforms.-
- AlicenseNot gradedqualityBmaintenanceEnables agents to analyze a business's Google Maps visibility, compare it with local competitors, and scan an area for prioritized improvement opportunities through SerpApi-backed tools.MIT
- FlicenseNot gradedqualityBmaintenanceEnables turning Google Maps queries into structured lead lists, extracting business names, phone numbers, websites, and reviews with asynchronous job control.-
- AlicenseNot gradedqualityFmaintenanceGive your AI agent live Google Maps search, review, and photo data through one secure MCP connection.1MIT
TDQS
Scored across 13 tools
Most tools have distinct purposes: find_business, run_grid, estimate_grid, get_balance, and the schedule family are clearly separated. However, run_grid vs run_grids (single vs batch) and get_grid vs get_batch vs get_history vs list_grids form a cluster of result-retrieval tools that could be confused without careful reading, though the descriptions do clarify each.
All 13 tools follow a consistent snake_case verb_noun pattern (find_business, run_grid, get_grid, list_schedules, schedule_grid, update_schedule, delete_schedule). Verbs are used predictably for their action type, making the naming highly readable.
13 tools is well within the ideal 3-15 range and each tool earns its place: search, grid execution, batch execution, result retrieval, cost estimation, balance, and full schedule lifecycle. No obvious filler or redundancy.
The surface covers the full lifecycle well: business search, grid run/estimate/get, batch run/status, history, balance, and complete schedule CRUD (create, list, update, delete). Minor gaps exist — there is no single get_schedule detail call and no way to cancel or delete already-run grids, but these are workable omissions.