GeoGridAPI MCP server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEOGRIDAPI_API_KEY | Yes | Your GeoGridAPI API key. Required for tool calls. Keys starting with gga_test_ return sample grids; keys starting with gga_live_ measure real grids. | |
| GEOGRIDAPI_MCP_URL | No | Hosted GeoGridAPI MCP server URL to relay to. | https://api.geogridapi.io/mcp |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_businessA | Search Google Maps listings by name and city. Returns place_id values to use with run_grid. Free. |
| run_gridA | Measure where a Google Business Profile ranks on Google Maps for a keyword, on every point of a grid around it. Shapes: square (size 3, 5, 7 or 9) or circle, diamond, hexagon, cross, ellipse, rectangle (density low, medium or high, up to 49 points). Costs one credit per point (square 3×3 = 9, 7×7 = 49, 9×9 = 81; medium circle = 29; points at sea are skipped and not charged), refunded if the grid fails. Test keys (gga_test_) return free mock grids. Waits up to wait_seconds, then returns the grid id if it is still running. |
| get_gridA | Status and result of a grid created with run_grid or the API: ranks matrix (north at the top), competitors most often in the top 3, change since the previous grid of the same listing, and the map as an image once completed. |
| get_balanceB | Credits left on the account (1 credit = 1 grid point). Free. |
| list_gridsA | The account's grids, newest first, optionally for one listing (place_id) or one exact keyword. Returns grid_id values to use with get_grid, get_history or schedule_grid. Free. |
| get_historyA | How a listing's ranking evolves for a keyword: every completed grid of the same map (same format, radius and center), oldest first, with the change between the first and the last. Give grid_id, or place_id and keyword (the latest grid sets the format). Free. |
| estimate_gridA | Exact number of points and credits a grid would cost before running it (points at sea are removed for shapes), and the balance after. Same parameters as run_grid. Free: nothing is reserved or charged. |
| schedule_gridA | Rerun an existing grid (same listing, keyword, format and radius) every week (weekday 1 = Monday … 7 = Sunday) or every month (month_day 1 to 28), around 7 am Paris time. Each run costs the grid's credits; the schedule stops and the account gets an email when the balance runs out. |
| list_schedulesA | The account's repeated grids: rhythm, status (active, paused, or stopped and why), next run and credits per month. Free. |
| update_scheduleA | Pause a repeated grid (status paused) or resume it (status active; a schedule stopped for lack of credits restarts too). |
| delete_scheduleA | Stop repeating a grid for good. Grids already run are kept. |
| run_gridsA | Run up to 50 grids in one call, all with the same format: one listing with several keywords, or several listings with one keyword. Each item needs place_id or query, and a keyword. Costs one credit per point of each grid (refunded if a grid fails); refused upfront when the balance cannot cover them all. Grids start as slots free up (10 at a time). Waits up to wait_seconds, then returns the batch so far: call get_batch for the rest. |
| get_batchA | Progress of a batch started with run_grids: each grid waiting, running, completed with its average rank and top 3, or failed and why. Free. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| local_audit | Map of a listing for one keyword |
| who_ranks_ahead | Competitors in the top 3 |
| several_keywords | One listing, up to 50 keywords |
| ranking_trend | Progress since the first map |
| track_listing | Same map every week or month |
| client_report | Map image and summary |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.