Starter
For one person wiring up their first few sources.
$6$5/mo
billed monthly $60 billed annually, save 17%
Try free for 7 daysTry free for 7 days- 2 connectors at once
- 2 accounts across them
- 1 seat
- Unlimited conversations
Connect your store, CRM, subscription and Search Console accounts once, then ask from the Claude, ChatGPT, Grok, Perplexity, Claude Code, Codex, Cursor or Antigravity subscription you already pay for. With your approval it does the work too, like completing an order.
7 days free, then your plan starts. You add a card to begin, and you can cancel before the first charge.
Works with your stack
A lead arrives in one account and pays in another. One connection covers both, so the answer does not have to be assembled by hand from two tools that cannot see each other.
You sign in once and the login stays with us. Your assistant gets the answers it asks for, never the password or key behind them.
Your accounts are reachable only from your workspace, and everything your assistant asks for is written to an audit log.
The store, the CRM, the subscriptions and Search Console are four companies, four logins and four different ideas of what a week is. Behind one connection they answer the same question at the same time, so you ask once instead of opening each of them.
The CRM knows who got in touch. The store knows who paid. Your search analytics know what people typed to find you. None of them can say which search brought in the customer who paid, because that answer needs two of them at once.
Each number sits behind another login, on a dashboard that counts the week its own way.
Leads sit in one tool and orders in another. Matching them means exporting both and lining them up by hand, so it rarely gets done.
You already pay for an AI that can reason about a week of sales. It has no way into your accounts, so you paste numbers into the chat by hand, or you stop asking.
Four jobs, one shape: the question needs two accounts, and they are not in the same place.
No analyst. The numbers live in five places and the week ends before you reach the third.
Installs sit in the attribution tool, revenue in the subscription platform, and nothing joins them.
Every client wants the same answer on a different day, from a different stack.
The campaign went out, the chats came in, and whether either produced revenue is a reconciliation nobody has time for.
You ask in the assistant you already have open. It reaches the accounts, reads them, and answers there. No dashboard to sign into, no report to export, and nothing to check afterwards in a second window.
Proposed, not applied
With Ask before sending on, a send is held as a card with the exact text on it and reaches nobody until you approve that card.
A connection is one account, not one provider. Connect the same source as many times as you have logins for it, give each one a name you recognise, and decide separately who in your workspace may reach it.
You ask in the Claude or ChatGPT subscription you already have. There is nothing else to sign up for and nothing extra to pay per question.
Sign in with the provider, or paste a key. This is the only part that happens here, and it happens once. Your password or key stays with us, encrypted, and never reaches Claude or ChatGPT.
Whichever of Claude, ChatGPT, Grok, Perplexity, Claude Code, Codex, Cursor or Antigravity you use, it is one setting, added once. Each has a page here with its own steps.
You ask in the assistant you already use. We see the question it sends us and nothing else. Your conversation stays where it is.
One question, two accounts
Each of these needs two sources that have never heard of each other. Pick one and see what the assistant calls, and what comes back.
Of the leads that came in this week, how many placed an order, and which service did they ask about?
31 leads, 9 of them ordered. Seven asked about installation, two about maintenance. The installation enquiries converted at roughly twice the rate.
Which queries brought the most clicks last month, and did the products they landed on sell?
Three of the top five queries land on pages for products that sold nothing last month. The query that sells is fourth by clicks and first by revenue.
How many of last month's installs are still paying, and which source sent them?
Renewal is holding at about two in three. One source accounts for most of the installs and the fewest renewals: the cheapest traffic is also the shortest-lived.
Which products sold well on the marketplace last month but barely moved in my own store?
Four products sold at least three times as many units on the marketplace as in your store. Two of them cost less there, even after the commission comes off.
Connecting asks whether the assistant may suggest changes there. Say no and it can only ever read that account. Say yes on one of the 14 that allow it, and every change still waits for you.
A change to an account is never applied when the assistant decides it should be. You see exactly what would change first, the field and its new value, and nothing happens until you approve it. A message to the channel you linked goes straight out, unless you switch on Ask before sending.
Every plan reaches every connector that is live, and conversations are unlimited on all of them. What changes is how many connectors and accounts you connect at once and how many people share your workspaces. One plan covers every workspace you own. Each plan starts with 7 days free, and annual billing costs less.
For one person wiring up their first few sources.
$6$5/mo
billed monthly $60 billed annually, save 17%
Try free for 7 daysTry free for 7 daysFor teams running several accounts per channel.
$19$15.83/mo
billed monthly $190 billed annually, save 17%
Try free for 7 daysTry free for 7 daysFor data-heavy teams that want every connector we ship.
$49$40.83/mo
billed monthly $490 billed annually, save 17%
Try free for 7 daysTry free for 7 daysFor organizations with custom scale and security needs.
Contact us
Contact salesA remote MCP server that lets you run your business from the AI assistant you already use. You connect your store, CRM, subscription and Search Console accounts once, and Claude, ChatGPT, Grok, Perplexity, Claude Code, Codex, Cursor or Antigravity can then answer from them and, with your approval, do the work. There is no interface of ours between you and the answer.
Claude, ChatGPT, Grok, Perplexity, Claude Code, Codex, Cursor or Antigravity. You add HeyMetra once in each assistant, as a connector in Claude and Perplexity and as an MCP server in the others, and it is there in every conversation after that. When a team uses different assistants, each person reaches the same accounts that were shared with the workspace.
An ad-only MCP server can tell you what a campaign spent. Whether that spend turned into orders or subscriptions is recorded in the store or the subscription platform, which that server cannot reach. HeyMetra connects those accounts, the store, the CRM, the subscription platform and Search Console, in one server, so one question can follow a customer from the first visit to the order.
No. You ask in Claude, ChatGPT, Grok, Perplexity, Claude Code, Codex, Cursor or Antigravity, on the subscription you already pay for. We run no model of our own, so there is nothing to buy twice.
Not by us. We read from your accounts at the moment a tool is called and return the result to the app you asked in; we do not keep a copy to train anything on. What that app does with the result is governed by your agreement with its vendor, and that is worth reading: it is the same agreement that already covers everything else you do there.
It reads them, and it changes one only where you said it may. Every account starts read-only, and connecting asks whether the assistant may propose changes there. An account left read-only cannot be changed, and at several providers the permission we ask for cannot write at all. Where you said yes, nothing is applied on its own: the change waits for you with every detail written out. The same holds for a send to the one destination you linked.
Google Search Console, Trendyol, n11, Çiçeksepeti, Amazon Seller Central, WooCommerce, Stripe, Zoho CRM, Zoho SalesIQ, Zoho Marketing Automation, AppsFlyer, RevenueCat, Jira, PostHog, Adapty and App Store Connect. Each connector page says what it reads and what, if anything, it can change.
You can cancel anytime and keep access until the end of your billing period. Every plan also comes with an unconditional 7-day money-back guarantee: cancel within 7 days for a full refund, no questions asked.
A connector is the service, Meta Ads for example, and a connected account is one login inside it. An agency running eight clients on Meta Ads uses one connector and eight accounts.
Connect your accounts once, then ask from the assistant you already pay for.
7 days free, then your plan starts. You add a card to begin, and you can cancel before the first charge.
Two ways to ask AppsFlyer from Claude Code or ChatGPT: AppsFlyer's own MCP server, or one that also reads your subscription revenue. Steps for both.
What a mobile app owner can ask Claude or ChatGPT once Adapty, RevenueCat, App Store Connect and AppsFlyer are connected, and why the revenue figures differ.
MCP is an open standard that lets an AI assistant reach the apps and accounts you already use. What it is, where it came from, how it works, what it changes.
AdKit is a remote MCP server for ad accounts. HeyMetra also reaches where the money lands: store orders, CRM pipeline, subscriptions and search traffic.
An MCP connector gives an assistant real access to a real account. What makes one safe is the tool list, where the bounds live, and who approves a change.
ChatGPT can reason about your numbers but cannot see them, so you paste. What connecting the accounts changes, and what it does not.