AppBrain MCP server
The AppBrain MCP server lets an AI assistant use AppBrain’s data directly. Connect it once and ask questions in plain language — “which keywords is my competitor beating me on in Germany?”, “has my photo editor lost rank this month?” — and the assistant calls AppBrain for you and reasons about the answer.
It speaks the Model Context Protocol, so it works with Claude, Cursor, and any other MCP-capable client.
Endpoint:
https://api.appbrain.com/mcpThe AppBrain MCP server is currently in beta. If you hit a rough edge, email contact@appbrain.com.
Connect
Copies a one-line instruction. Paste it to Claude, Cursor, or whichever assistant you want to connect — it fetches the setup steps and does the rest.
You are already talking to an assistant that can read a URL and act on it, so the fastest way to connect is to let it do the setup: copy the line above, paste it into your assistant, and it adds the server, walks you through signing in, and checks the connection worked.
To do it yourself, point any MCP client at the endpoint above as a remote or HTTP MCP server. There is no API key to configure. The first request comes back unauthorized, your client opens AppBrain in a browser, and you sign in there.
On the sign-in screen you decide three things:
- What it may do. Read your keyword and app data; track and untrack keywords; export earnings, billing and promotion reports. Each is separate — grant only what you want it to have.
- Which developer accounts it may see. Tick as many as you like. If you have several accounts and want to ask about all of them, tick all of them.
- Which account pays. Only asked when you tick more than one. App data tools cost API credits; this decides whose.
Everything you have connected is listed on your connected applications page, where you can change the accounts and permissions later, or disconnect a client. An OAuth grant is scoped to what it needs, expires, and can be revoked on its own without disturbing anything else.
What the assistant can do
| Tool | What it answers |
|---|---|
whoami | Which account is connected, and what it is subscribed to |
keyword_rankings | Who ranks for a keyword in a country, right now |
keyword_rank_history | How ranks for a keyword moved over time |
app_rank_history | How one app moved across all its keywords |
keyword_overview | All your apps, their current ranks and suggested keywords |
tracked_keywords_list | What you’re tracking, and your remaining quota |
tracked_keywords_add | Start tracking keywords, in one or more countries |
tracked_keywords_remove | Stop tracking keywords |
competitors_list | Your saved competitors and how much keyword overlap you have |
competitors_discover | Apps that share keywords with yours but aren’t saved yet |
competitor_keywords | Head-to-head comparison; which keywords are opportunities |
keyword_report_generate | Start a keyword research report for an app |
keyword_report_get | Fetch a report once it’s ready |
keyword_reports_list | Your previous reports |
app_info | Everything known about one app, including the SDKs it uses |
app_search | Find apps matching a query, on Google Play or the App Store |
app_browse | Top apps by category, sort order and filter |
device_stats_top_by_country | The most-used Android devices in a country |
list_countries | Supported countries and their minimum CPI bids |
list_libraries | Every SDK and library AppBrain detects |
export_report_csv | Your promotion, publisher, billing, earning, SDK or ranking data as CSV |
Rankings are per country, so ask for one — “in the US”, “in Germany”. Reports take about 30–120 seconds; the assistant starts one and picks it up when it’s done.
Tools that change something — tracking and untracking keywords, generating reports — are marked as such, so a well-behaved client asks you before running them.
Credits
The keyword tools are free to call. The app data tools consume info API credits exactly like the equivalent REST endpoints:
app_info— 1 credit per app, free for your own appsapp_searchandapp_browse— 4 credits, plus 2 more for every 10 results beyond the first 10
An assistant works much faster than a person, so these tools have their own hourly limits and a lower cap on results per call than the REST API allows. If you want a large sweep, the CLI is the better tool.
Free vs. subscription
Every tool works on a free account. An active AppBrain Intelligence subscription removes
the free-tier cap on how many keyword/country pairs you can track. If a tool reports a missing
subscription, ask the assistant to run whoami — it shows exactly what each connected account has.
Troubleshooting
The client keeps asking you to sign in. Your client has to support the OAuth sign-in flow for remote MCP servers. If it only offers a field for an API key, it cannot connect yet — ask the assistant which kind of remote server it supports.
“Select at least one developer account.” The sign-in screen needs at least one account ticked, and at least one permission. If you have no developer account on AppBrain yet, create one first.
Rate limits. The endpoint is rate-limited per connection. An assistant looping over many keywords can hit that; ask it to work through them in smaller batches.
A keyword with no data. The first time anyone asks about a keyword, AppBrain has to scrape Google Play for it. If that takes more than a few seconds the tool says so and the assistant should ask again shortly — the scrape keeps running in the background.