Sensor Tower MCP Server Pro
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SENSOR_TOWER_API_TOKEN | Yes | Primary API token for Sensor Tower (required) | |
| SENSOR_TOWER_API_TOKEN_2 | No | Second backup API token for failover | |
| SENSOR_TOWER_API_TOKEN_BACKUP | No | First backup API token for failover |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_app_metadataC | Get comprehensive app metadata including descriptions, ratings, and more. |
| get_download_estimatesB | Fetch download estimates for apps by country and date. |
| get_revenue_estimatesB | Fetch revenue estimates for apps by country and date. |
| top_in_app_purchasesB | Retrieve top in-app purchases for the requested app IDs. |
| get_usage_active_usersC | Get usage intelligence active users data. |
| version_historyA | Get version history for a particular app. |
| get_category_historyC | Get category ranking history for apps. |
| compact_sales_report_estimatesC | Get download and revenue estimates in compact format. |
| category_ranking_summaryB | Get today's category ranking summary for a particular app. |
| app_analysis_retentionA | Get retention analysis data for apps. ⚠️ IMPORTANT: date_granularity only supports "all_time" or "quarterly". When using "quarterly", end_date is required. |
| downloads_by_sourcesB | Get app downloads by sources (organic, paid, browser). |
| app_analysis_demographicsC | Get demographic analysis data for apps. |
| app_update_timelineC | Get app update history timeline. |
| get_publisher_appsC | Retrieve apps for the specified publisher. |
| get_unified_publisher_appsC | Retrieve unified publisher details and associated apps. |
| get_app_ids_by_categoryB | Retrieve app IDs by category and release/update date filters. |
| get_country_codesA | Get list of available country codes for Sensor Tower API. |
| get_category_idsB | Get list of category IDs for iOS or Android. |
| get_chart_typesA | List available ranking chart identifiers used by Sensor Tower. |
| health_checkC | Lightweight status endpoint for monitoring and orchestration. |
| get_store_summaryA | Get app store summary statistics. ⚠️ TEMPORARILY DISABLED: This endpoint is currently returning 500 Internal Server Error from Sensor Tower's API. This is a server-side issue. Please contact Sensor Tower support or try again later. |
| get_featured_today_storiesB | Retrieve featured Today stories from the App Store. |
| get_featured_appsB | Retrieve featured apps on the App Store Apps & Games pages. |
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 23 tools
Several tools have overlapping purposes, such as version_history and app_update_timeline both covering app update history, and compact_sales_report_estimates duplicating download/revenue estimates. While descriptions hint at differences, the boundaries are unclear, making misselection likely.
Naming is inconsistent: many tools use get_ prefix (get_app_metadata, get_download_estimates), but others are noun phrases without verbs (version_history, category_ranking_summary, downloads_by_sources, top_in_app_purchases). No uniform verb_noun or noun_verb pattern emerges.
At 23 tools, the set is on the heavy side but appropriate for a broad analytics platform covering many data types. Not excessive enough to warrant a 2, but above the ideal 3-15 range.
The tool set covers major Sensor Tower capabilities: metadata, estimates, usage, rankings, retention, demographics, publisher info, and reference data. Missing review-level data or advanced ad intelligence, but core workflows are represented. Slight gaps around update/delete operations are irrelevant for a read-only analytics API.