Subscription revenue, MRR, trials and refunds over any range.
Your subscription revenue lives in Adapty. What you paid to get those subscribers does not. Ask about both in the same sentence.
https://mcp.heymetra.com/mcp
How did subscription revenue move day by day this month?
How many trials started last month, and how many expired?
How much came back as refunds last month?
What are revenue, MRR, active subscriptions and new trials this month?
Which of my apps is making the most MRR?
No dashboard, no export, no query language. You ask in the assistant you already use and the answer comes back with the account it came from.
1. Open the app you want to read
Sign in at app.adapty.io and pick the app from the switcher at the top. An Adapty key belongs to ONE app, so the app you are looking at now is the app this connection will answer for.
A portfolio is one connection per app, not one for the account. Five apps means doing this five times, and each connection gets its own name here, which is what you will call it when you ask a question about it.
2. Go to App settings → General and find Api keys
It is at app.adapty.io/settings/general. Scroll to the section headed Api keys; it lists a Public SDK Key and a Secret Key together.
Adapty's own pages call this screen both 'App settings → General' and 'Settings → General'. They are the same screen.
3. Copy the Secret Key
The one that starts with secret_live_. Not the one that starts with public_live_: that is the Public SDK Key, it belongs inside your app, and it cannot read any of these figures.
If you paste the public one HeyMetra will say so by name rather than letting Adapty answer with a bare login error.
4. Paste it into HeyMetra and give the connection a name
On the Connections screen choose Adapty, paste the key, and name it after the app, such as 'Cleanr' rather than 'Adapty'. The key is stored encrypted and never shown again. HeyMetra checks it works before saving anything, so a rejected key never leaves a connection that looks healthy.
5. Add HeyMetra to the assistant you use
Claude, ChatGPT, Cursor or Codex, with the details HeyMetra gives you. The Adapty tools appear there once the connection is saved.
Watch what you paste:
- Anything starting
public_live_is the Public SDK Key, which belongs in your app and will be refused by name.
Add HeyMetra once and it is there in every conversation. The address is the same everywhere:
https://mcp.heymetra.com/mcp
npx add-mcp https://mcp.heymetra.com/mcpadd-mcp is a third-party installer that writes the configuration for Claude Code, Codex, Cursor, Antigravity, VS Code and seventeen other agents. It infers the name from the address, so the server lands as heymetra. Run against this endpoint before it was written here.
Claude — Settings → Customize → Connectors → Add custom connector
Paste the address above into Settings → Customize → Connectors → Add custom connector.
On Team and Enterprise plans only an owner can add it, under Organization settings.
Full walkthrough: heymetra.com/mcp/claude/
ChatGPT — Settings → Security and login → Developer mode, then chatgpt.com/plugins
Paste the address above into Settings → Security and login → Developer mode, then chatgpt.com/plugins.
The address has to end in /mcp here.
Full walkthrough: heymetra.com/mcp/chatgpt/
Grok — grok.com/connectors → New Connector → Custom
Paste the address above into grok.com/connectors → New Connector → Custom.
XAI calls this “bring your own MCP”.
Full walkthrough: heymetra.com/mcp/grok/
Perplexity — Settings → Connectors → Custom connector → Remote
Paste the address above into Settings → Connectors → Custom connector → Remote.
Perplexity documents it as a Pro, Max and Enterprise feature.
Full walkthrough: heymetra.com/mcp/perplexity/
Claude Code — claude mcp add --transport http
claude mcp add --transport http heymetra https://mcp.heymetra.com/mcpOr a .mcp.json in the project root; /mcp inside a session shows what connected.
Full walkthrough: heymetra.com/mcp/claude-code/
Codex — ~/.codex/config.toml
[mcp_servers.heymetra]
url = "https://mcp.heymetra.com/mcp"Under an [mcp_servers.] section, then codex mcp login.
Full walkthrough: heymetra.com/mcp/codex/
Cursor — ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
"mcpServers": {
"heymetra": { "url": "https://mcp.heymetra.com/mcp" }
}
}Leave the static OAuth fields empty; HeyMetra does not need them.
Full walkthrough: heymetra.com/mcp/cursor/
Antigravity — ~/.gemini/config/mcp_config.json, or .agents/mcp_config.json in a project
{
"mcpServers": {
"heymetra": { "serverUrl": "https://mcp.heymetra.com/mcp" }
}
}The key is serverUrl, not url, unlike every other JSON client.
Full walkthrough: heymetra.com/mcp/antigravity/
Propose a change to this account. Nothing is sent until you approve it, and HeyMetra cannot undo it afterwards.
Permissions are switched on per connection, and one you leave off is a tool your assistant never sees.
| Permission | What it covers | Changes anything? |
|---|---|---|
| Full account access | Lets your assistant read anything in this account to answer your questions. The figures are the provider's own, not ones HeyMetra has checked. It can also propose changes: none is applied until you approve it, and HeyMetra cannot undo one afterwards. | Yes — every change waits for your approval |
What each permission lets an assistant do, in full
- Ask anything about this account and get the answer from its live data. Reads only, and the figures are the provider's own rather than ones HeyMetra has checked.
- Propose a change to this account. Nothing is sent until you approve it, and HeyMetra cannot undo it afterwards.
Anything that would change something comes back as a proposal you approve, inside bounds that live in code rather than in a prompt: ±50% on a budget, 5 campaigns per action and 20 changes a rolling day, and an approval that expires after 30 minutes. How that works.
The key is rejected and it was copied straight from the Api keys screen.
Why: Two keys sit on that screen and only the Secret Key reads analytics. The Public SDK Key is for the app itself.
Fix: Check what you pasted starts with secret_live_ rather than public_live_, and copy the other one.
A connection that worked for months suddenly answers with a login error.
Why: Somebody generated a new key in Adapty and deleted the old one. Generating alone does not break anything; pressing the trash icon beside the previous key does.
Fix: Copy the current Secret Key from App settings → General and paste it into this connection with the pencil. The connection keeps its name and everything pointing at it.
You have a token from 'adapty auth login' and it is not accepted.
Why: That is the Developer CLI token, from Settings → Developer API. It authorises the command-line tool and nothing else.
Fix: Use the Secret Key from App settings → General instead. It starts with secret_live_ and is copied, not issued by a login flow.
Revenue and MRR answer, but proceeds and net revenue come back as 'not reported for this app'.
Why: Those two need store payment data, and Adapty only has it once App Store Connect or Google Play reporting is wired into that app. Until then Adapty has no figure to give, so HeyMetra says so rather than showing revenue in their place.
Fix: Connect the store's reporting in Adapty. Everything that does not depend on it keeps answering in the meantime.
Answers come back slowly, or one in a batch fails.
Why: Adapty's analytics API allows two requests a second per key, and a question that spans several charts or several apps makes one call each.
Fix: Ask again. HeyMetra reports a busy moment as a temporary gap rather than as no data, so the figure is never quietly replaced by a zero.
Connect with each app's secret key. An Adapty key belongs to one app, so a portfolio is one connection per app. Then ask your assistant about revenue, proceeds, net revenue, MRR, ARR, ARPU, ARPPU, subscriptions and trials, refunds and installs, each as a total and day by day. An app that ships on both stores can be asked about the App Store and Google Play separately instead of only about the two added together. HeyMetra does not read paywall and A/B figures. Revenue is dated by transaction and sits before the store's fee, and every answer states its basis so it is not compared with cohort-based ad figures by accident. When you connect, you choose whether your assistant may also propose changes.
About Adapty
Adapty runs mobile in-app subscriptions and paywall analytics: revenue, conversion, retention, and paywall A/B tests across iOS and Android. It’s where subscription growth and paywall performance are measured.
The reason to read Adapty through HeyMetra rather than through a server that only knows Adapty is everything else it can answer in the same breath:
Ads — Google Ads · Meta
Analytics — Google Analytics 4 · Google Search Console · PostHog
Ecommerce — Shopify · Trendyol · WooCommerce
Revenue & CRM — Stripe · HubSpot · Zoho CRM · Zoho SalesIQ · Zoho Marketing Automation
Mobile — AppsFlyer · RevenueCat · Adapty · App Store Connect
Work — Google Calendar · Google Meet · Jira
The full catalogue is at heymetra.com/connectors/.
- Adapty connector page
- HeyMetra — what the product is
- Setup for every assistant
- Security and limits
- Pricing
- HeyMetra's own repository
Built by Zeisoft, who make HeyMetra. Not affiliated with Adapty. This README is generated from HeyMetra's live connector catalogue and refreshed daily; corrections are welcome as issues.