Local Rank and Map Pack Tracker MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. The server lists its tool without a token, but a call needs one. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| track_local_rankingsA | Check where a business ranks on Google for each keyword in each location, with the search placed at that location. Give keywords, locations (place names or coordinates), and target_domain and or business_name. One row per keyword and location: organic_position (up to 50 deep), local_pack_position (the 3 result map pack on page one), local_finder_position (top 20 map list), the matched listing's rating, review count, category, phone, and website, the top 10 organic domains and top map listings, and, with state_key, the previous positions and the change. An empty position means not found in the positions checked. Blocked rows come back free with a row_status saying so. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges per rank check and per extra Google page read. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of selecting the wrong tool or confusing overlapping purposes. Its purpose is clearly scoped to local rank and map pack tracking.
The single tool name track_local_rankings follows a clear verb_noun snake_case convention. There are no inconsistent naming styles to compare against.
A single tool is thin for a server surface, even though this tool is unusually comprehensive. It bundles many related operations into one monolithic call rather than exposing separate capabilities.
The tool covers core rank tracking deeply: organic, local pack, local finder, listing metadata, top competitors, state comparison, blocked rows, and errors. Minor gaps remain around managing or retrieving prior runs beyond the state_key mechanism.