App Store Trends API MCP Server

App Store Trends API MCP server exists for a simple reason — assistants are far more useful when they can act on App Store Trends API directly instead of describing what you should do. App downloads and chart ranking trends for iOS and Android. Free key at trendsapi.ai.

What you get

res = requests.post( "https://api.trendsapi.ai/api", headers={"Authorization": "Bearer YOUR_API_KEY"}, json={"mode": "get_growth", "source": "app downloads", "keyword": "chatgpt", "percent_growth": ["3M", "12M"]}, ) print(res.json()) ```

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Configuration and credentials

You will need 2 environment variables: AUTH_HEADER, YOUR_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by ai.trendsapi; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against App Store Trends API's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the app store trends api mcp server does with a few real requests.