Programmatic access to cross-store analytics, app health, reviews, and more. Connect your scripts, dashboards, or AI assistants directly to your app data.
Connect AI assistants like Claude, Cursor, or ChatGPT directly to your BoostOps data via the Model Context Protocol.
Traditional JSON API for scripts, integrations, and custom dashboards. Standard HTTP with scoped API keys.
Machine-readable summary of BoostOps capabilities for AI agents that browse the web. Like robots.txt, but for LLMs.
All API and MCP access uses API keys created in the BoostOps dashboard under Settings > API Keys. Keys use the format bops_sk_... and support scoped permissions.
The Model Context Protocol lets AI assistants call tools on your behalf. Connect Claude, Cursor, or any MCP-compatible client to query your BoostOps data conversationally.
Add this to your MCP client configuration (e.g. Claude Desktop claude_desktop_config.json):
// claude_desktop_config.json { "mcpServers": { "boostops": { "url": "https://api.boostops.io/mcp", "headers": { "Authorization": "Bearer bops_sk_your_key_here" } } } }
| Tool | Description |
|---|---|
list_apps |
List all apps in your studio with store metadata |
get_app_metrics |
Daily analytics (DAU, revenue, installs) for an app, filterable by date range |
get_portfolio_summary |
Studio-wide KPIs with period-over-period comparison |
get_app_health |
Crash rates, ANR, store vitals across all platforms |
get_app_reviews |
Recent reviews with ratings, filterable by store and rating |
reply_to_review |
Post a reply to a store review |
get_ad_spend |
Ad spend totals and daily breakdown across all ad platforms |
get_blended_roas |
Return on ad spend with revenue and spend by channel |
get_attribution_data |
Channel-level install attribution and campaign performance |
get_store_ratings |
Current store ratings and review counts |
get_revenue_breakdown |
Revenue split by IAP vs ads, by platform |
compare_platforms |
Side-by-side comparison of metrics across stores |
get_anomalies |
Detect anomalies in DAU, revenue, and ratings |
get_portfolio_summary
Your portfolio is up 12% in revenue this week ($4,230 vs $3,780 last week). DAU is stable at ~2.1k. Roulette Merge drove most of the growth with a 23% revenue increase, while Idle Farm dipped 5%.
get_app_health
Roulette Merge Android crash rate spiked to 2.1% yesterday (from 0.8% baseline). Likely related to the v2.3.1 release. iOS and Microsoft Store are clean. I'd recommend checking the Firebase Crashlytics dashboard for that build.
Standard HTTP JSON API for programmatic access. All endpoints require an API key passed as a Bearer token.
https://api.boostops.io/api/v1
| Method | Endpoint | Description | Scope |
|---|---|---|---|
| GET | /apps |
List all apps | read:apps |
| GET | /apps/:id/metrics |
App metrics (DAU, revenue, installs) | read:metrics |
| GET | /apps/:id/attribution |
Attribution data | read:attribution |
| GET | /apps/:id/anomalies |
Anomaly detection | read:metrics |
| GET | /portfolio/summary |
Studio-wide KPIs | read:portfolio |
BoostOps publishes standard discovery files so AI agents can automatically find and understand our API without manual configuration.
/llms.txt
LLM-readable site summary
Markdown file at the site root describing BoostOps capabilities, available tools, and integration endpoints. Any LLM browsing the site can read this to understand what's available.
View file →/.well-known/mcp/
MCP server discovery
Standard server-card.json (SEP-1649) and manifest (SEP-1960) files. MCP-aware clients can auto-discover the BoostOps MCP endpoint, supported capabilities, and auth requirements.
<meta> tags
In-page signals for AI agents
HTML meta tags and comments on every page signal that a structured API exists. Agents reading the page source see <meta name="ai-capabilities"> and a plaintext comment directing them to the API before resorting to browser automation.
Create an API key and start querying your app data in under a minute.