MCP Server

The Aptoide Connect MCP server connects your AI assistant — Claude, Gemini, ChatGPT, or any other MCP client — directly to your Aptoide Connect account, so you can ask about your data in plain language instead of writing API calls or clicking through Console reports:

• "How much revenue did my app make last month?"
• "What's my top country for installs?"
• "Why did this wallet transaction fail?"

Who this is for

Any Aptoide Connect developer who wants to explore their app statistics, wallet activity, in-app product catalog, or the Aptoide Connect documentation conversationally. Typical use cases:

• "What was my revenue for [app] in the last 30 days?"
• "Which countries are driving the most installs for [app]?"
• "How much is in my wallet this month, across all my apps?"
• "What happened with transaction [id]?"
• "What in-app products does [app] have, and at what prices?"
• "Create a new consumable for [app] — I'll give you the sku, price and store listing."
• "Raise the price of [sku] to EUR 1.99."
• "My in-app purchases aren't completing. Here are my Billing SDK logs — what's wrong?"
• "Why is this endpoint returning a 402?"

Prerequisites

• An Aptoide Connect developer account that has an active subscription.
• An API key, generated from API Keys in the Developer Console. This is the only credential involved — there is no separate MCP-specific sign-up.
• An MCP client that supports remote servers with OAuth, such as Claude, Gemini, or ChatGPT.

Connecting your AI assistant

Authentication is OAuth only. Every MCP client has its own way of adding a remote server, so check your client's documentation for where custom MCP servers or connectors are configured. Whichever client you use, the flow is the same:

1. Add the server by URL in your MCP client: https://mcp.connect.aptoide.com.

   ⚠️

   Use the bare URL, with no /mcp sub-path — https://mcp.connect.aptoide.com/mcp returns a 404.

2. The client opens a browser to a consent page hosted by Aptoide Connect.

3. Paste your Aptoide Connect API Key into that page and click Authorize.
4. Once the key is accepted, your client shows the connection as active.

🌏

Using the MCP server from China

If you are connecting from mainland China, you may have difficulty reaching the MCP server or completing the OAuth flow. In that case, try connecting while on a VPN.

The tabs below cover the most common clients. Any other MCP client that supports remote servers with OAuth connects the same way, configured wherever that client keeps its MCP server settings.

Claude

Claude

1. Open Settings → Connectors on claude.ai and choose Add custom connector.
2. Enter https://mcp.connect.aptoide.com as the URL, leaving the OAuth client ID and secret blank.
3. Click Connect and complete the consent page.

See Anthropic's guide to custom connectors using remote MCP.

Claude Code

1. Add the server:

claude mcp add --transport http aptoide-connect https://mcp.connect.aptoide.com

2. In a session, run /mcp, pick aptoide-connect, and choose Authenticate.

See the Claude Code MCP documentation.

ChatGPT

ChatGPT

1. In Settings → Connectors → Advanced settings, enable Developer mode (required for custom MCP connectors, available on paid plans).
2. Add a new connector with https://mcp.connect.aptoide.com as the MCP server URL and OAuth as the authentication method.
3. Complete the consent page when it opens.

See OpenAI's guide to connectors in ChatGPT.

Codex

Recent Codex versions support remote MCP servers with OAuth:

1. Add the server to the mcp_servers section of ~/.codex/config.toml with https://mcp.connect.aptoide.com as the URL.
2. Complete the OAuth login from the CLI.

See the Codex documentation for the exact configuration for your version.

Gemini

Gemini

The Gemini web app does not currently support custom MCP connectors. Gemini CLI is the way in.

Gemini CLI

1. Add the server to your ~/.gemini/settings.json (or a project-level .gemini/settings.json):

{
    "mcpServers": {
        "aptoide-connect": {
            "httpUrl": "https://mcp.connect.aptoide.com"
        }
    }
}

2. In a Gemini CLI session, run /mcp auth aptoide-connect and complete the consent page that opens. /mcp shows the connection status of all configured servers at any time.

See the Gemini CLI MCP documentation.

Qwen

Qwen

The Qwen web app does not currently support custom MCP connectors. Qwen Code is the way in.

Qwen Code

Qwen Code is configured the same way as Gemini CLI:

1. Add the server to your ~/.qwen/settings.json:

{
    "mcpServers": {
        "aptoide-connect": {
            "httpUrl": "https://mcp.connect.aptoide.com"
        }
    }
}

2. Authenticate from a session and complete the consent page.

Kimi

Kimi

The Kimi web app does not currently support custom MCP connectors. Kimi Code is the way in.

Kimi Code

1. Add the server with OAuth authentication:

kimi mcp add --transport http --auth oauth aptoide-connect https://mcp.connect.aptoide.com

2. Authenticate — a browser opens to the consent page:

kimi mcp auth aptoide-connect

In a session, /mcp shows connected servers and their tools. See the Kimi Code CLI MCP documentation.

DeepSeek

DeepSeek

The DeepSeek web app does not currently support custom MCP connectors. DeepSeek Harness is the way in.

DeepSeek Harness

DeepSeek Harness (dsh), DeepSeek's open-source agent runtime, connects to remote MCP servers through its @deepseek-ai/dsh-mcp-client plugin — but that client only passes static headers and has no OAuth flow of its own, and this server requires OAuth. Until Harness gains OAuth support, DeepSeek's first-party tools cannot connect to this server; to use DeepSeek models with it, use an MCP client that supports OAuth and lets you choose your model.

Available tools

Each tool maps to one Aptoide Connect API endpoint and returns that endpoint's response as-is.

Tool	What it does	Access
search_documentation	Answers product questions — what a parameter accepts, what a limit is, what an error code means.	Read-only
list_available_applications	Lists the apps on the account, their exact package names, and what statistics each supports.	Read-only
get_application_statistics_chart	Revenue, installs, or downloads for one app over a date range.	Read-only
get_application_statistics_top	Ranks one app's revenue, installs, or downloads by country or by partner.	Read-only
list_application_statistics_reports	Monthly performance report CSVs for one app — download links, or the report contents themselves, for periods a single statistics call can't cover.	Read-only
get_wallet_transactions_totals	Summed wallet amounts (revenue, credit, debit) over a date range, across all apps.	Read-only
list_wallet_transactions	Individual wallet transactions with amounts, fees, status, payment method, country.	Read-only
get_wallet_transaction_details	Full detail on one specific wallet transaction.	Read-only
list_wallet_transaction_reports	Monthly wallet transaction report CSVs — download links for the raw data, or their contents.	Read-only
list_application_consumables	Lists an app's in-app products, with id, sku, status, and price.	Read-only
get_application_consumable	Full detail on one in-app product, including every price and locale set on it.	Read-only
add_application_consumable	Creates a new in-app product.	Write — creates a live product, and products cannot be deleted: a mistaken creation can only be set INACTIVE, never removed.
update_application_consumable	Edits an in-app product — only the fields you give change. An id that doesn't exist fails cleanly instead of creating anything.	Write — changes a live product that may be on sale right now, so a careless price or locale edit is immediately visible to buyers.
analyze_billing_sdk_transaction	Looks up one Billing SDK transaction, and the purchase attached to it, to explain what its status means and what to do next.	Read-only
analyze_billing_sdk_logs	Runs Billing SDK log output through the log analyzer to identify the flows and errors in it. Paste the logs as they are — the analyzer matches on the raw lines.	Read-only

⚠️

Tools marked Write make real changes to your live Aptoide Connect data, and some of those changes cannot be undone. Review what your assistant is about to do before confirming.

Privacy

The MCP server is a thin, stateless layer over the Aptoide Connect API. What that means for your data:

• Your API key is never stored. It is encrypted into the OAuth tokens your AI client holds, decrypted only in memory to serve each request, and never written to a database, logged, or exposed to the assistant.
• Your conversations are never seen. The server receives only the tool calls your assistant explicitly makes — never the chat around them. Content you deliberately pass to a tool, such as Billing SDK logs, is processed to answer that call.
• API requests are logged like any other API traffic. Each tool call becomes one Aptoide Connect API request, and its metadata (endpoint, parameters, response status, account) is retained for 30 days for quotas and service metrics — the same treatment direct API calls get.
• What happens to results after they reach your assistant is governed by your AI provider's privacy policy — the same as anything else in your conversations with it.

For how Aptoide Connect handles your data in general, see the Privacy Policy and Terms & Conditions.

FAQ

Does the AI assistant ever see my API key? No. The key is entered once, on the consent page, over HTTPS — never in the chat. It is sealed into encrypted tokens that only the MCP server can open, so neither the assistant nor the AI provider ever holds it in usable form.

How do I disconnect or revoke access? Disable the API key you used — flip its Active toggle off on the API Keys page of the Developer Console. Every connection made with that key stops working immediately, and you can re-enable the key later if you want it back. Removing the connector on the client side also works, but disabling the key is the guarantee.

What can the assistant see once connected? Only what the tools on this page expose, for the account the API key belongs to: the account's apps, their statistics and reports, wallet activity, in-app product catalogs, Billing SDK transaction lookups, and this documentation. Nothing else on the account is reachable — there is no tool for settings, users, submissions, or anything not listed above, and no way to reach any other account.

Can it change anything on my account? Yes — it can create and edit in-app products, and those are the only writes. Everything else is read-only, and there is no way to delete anything. MCP clients ask for your approval before a write tool runs, so nothing changes silently.

Why don't the revenue numbers match my wallet balance? Revenue tools default to amountType: wallet — your take-home after VAT and revenue share. amountType: global is gross consumer spend including VAT, and the gap between the two moves with each buyer's country. When a number looks off, first check which of the two is being quoted.

How far back can I ask about? Statistics cover the last 6 months, at most 120 days per question — for longer periods the assistant switches to the monthly reports, which have no window limit. Wallet transactions go back about 24 months.

Why am I getting "Active account subscription required"? The API — and therefore the MCP server — needs your account to have an active subscription. A 402 means the subscription is missing or expired.

Are there usage limits? Yes — each endpoint has a daily quota per account. Hitting one returns a 429 telling the assistant exactly that, and quotas reset at midnight UTC.

---

Need help beyond what the assistant can answer? See Support Tools for Connectoide, the Billing SDK analyzers, and how to reach our Support team directly.