A Applytix DocsConnect
MCP Connector · Beta

Your app numbers.
Right inside Claude.

Connect your Applytix account to Claude and ask about your metrics in plain language, using data Applytix already combines from App Store Connect, RevenueCat, Google Play and ads and analyzes up front. No dashboard needed.

What it is

Analyzed, not raw

More than rows from a database. app_health returns the finished verdict, "declining, because trial conversion dropped 30%", not a table to work out yourself.

Read only

Connected through sign-in, the connector only answers questions about your numbers. Only a key that explicitly carries that permission can propose or change bids and budgets.

Connect once

In claude.ai and Claude Desktop you sign in once with your Applytix account, no key needed. Claude Code and scripts use team keys.

1 · Connect to Claude

In claude.ai or Claude Desktop, go to Settings → Connectors and add a custom connector with this address:

URLhttps://www.applytix.io/mcp

Claude opens the Applytix sign-in. You choose the team whose apps Claude should see and allow access. No key is needed for this. The connection only reads and can be disconnected at any time.

The Applytix tools then show up in Claude right away. Claude Code connects with a key, see below.

2 · Key for Claude Code

Claude Code and scripts connect with a team key instead of a sign-in. A team admin creates it; every key belongs to exactly one account and reads only that account's apps. Until the settings UI arrives, this works through the API:

Create key
curl -sS "https://hotsrjmkyecfzgtgqayc.supabase.co/functions/v1/manage-applytix-key" \
  -H "Authorization: Bearer <your-applytix-jwt>" \
  -H "apikey: <supabase-anon-key>" \
  -H "Content-Type: application/json" \
  -d '{"action":"create_mcp_key","team_id":"<team-id>","name":"Claude"}'

The key (atx_mcp_…) is shown only once. Store it safely right away. Only its hash is stored, so it cannot be retrieved again.

Then one command in the terminal:

bash
claude mcp add --transport http applytix \
  https://www.applytix.io/mcp \
  --header "Authorization: Bearer atx_mcp_YOUR_KEY"

3 · Just ask

Ask like you would ask a colleague. Claude picks the right tool by itself.

How did Vorly do last week?get_metrics
Which app is dropping the most right now?top_movers
How is Besser Sprechen doing, and why?app_health
Compare the last 7 days with the 7 before.compare_period
What do the new reviews say?reviews_summary
Which keywords went up organically?aso_summary

Tools

Every tool is automatically limited to your account. Without further permission a key only reads; proposing needs the propose permission, accepting needs approve.

  • list_appsWhich apps are connected to the account. The starting point.
  • get_metricsMRR, downloads, revenue, trials, ad spend and store funnel for a period.
  • app_healthThe finished verdict (growing / stable / declining / attention_needed) with insights.The star
  • compare_periodDeltas (absolute and percent) between two periods.
  • top_moversWhich app moves the most across the portfolio, up and down.
  • reviews_summaryCount, average, sentiment, topics and notable reviews.
  • aso_summaryNotable organic keyword rank movements.
  • list_campaignsAd campaigns with status, daily budget and the limits Tix enforces.
  • list_keywordsKeywords of an Apple Ads campaign with bid and the latest Tix verdict.
  • diagnose_keywordOne keyword by the rules Tix itself uses: verdict, history, which limits apply right now.
  • get_ad_changesSubmitted proposals and their status, with Apple's response.
  • propose_ad_changesPROPOSE bids, daily budgets or keyword status. The default is a dry run; nothing is executed until a person approves it on the web. Only with a key that carries the propose permission (create_mcp_key with "scopes":["read","propose"]).
  • list_pending_proposalsAll open proposals from every source (Tix, agent), with reasoning and whether they can be accepted.
  • review_proposalsAccept or reject open proposals. Accepting executes them, through the same path as approval on the web and with the same guardrails; an acceptance counts like a click by the person who owns the key and is logged with source MCP and the key ID. Only with a key that carries the approve permission (create_mcp_key with "scopes":["read","approve"]).

Periods: yesterday · last_7d · last_30d · last_90d · or {from,to}. They always end on the last complete day, because today's value is incomplete (Apple and RevenueCat settle 1 to 3 days late).

How isolation works

Your key or your connection resolves to exactly one team. Every tool derives its data only from that team's apps; a foreign app or account identifier resolves to nothing. Cross-account access is impossible by construction and covered by an automated test.

Security

  • A connection from claude.ai is valid for the connector only: it can change neither your account nor anything in Applytix. You can disconnect it at any time in Claude's connector settings.
  • Treat atx_mcp_… like a password. It grants read access to your metrics.
  • Only the SHA-256 hash is stored; the plain text appears once, when the key is created.
  • A leaked key becomes invalid immediately via revoke_mcp_key.
  • Without its permission no key changes anything: proposing needs propose, executing needs approve, and both can only be granted when the key is created.