The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the HeyMetra listing page.
Manage your business with your AI assistant.
A remote MCP server for the accounts your business already runs on — ads, analytics, store, CRM, mobile subscriptions. Connect them once, then ask about all of them together from Claude, ChatGPT, Cursor or whichever assistant you already pay for.
Most MCP servers cover one vendor. Connect the Google Ads one and it will tell you what you spent; it cannot tell you what you earned, because the money arrived in Stripe, or Shopify, or Adapty, and that is a different server with a different login.
HeyMetra is one server over all of them. Spend, traffic, store and revenue answer the same question at the same time, which is the only way a question like "did that campaign pay for itself?" has an answer at all.
Two consequences worth knowing before you read further:
Of those tools, 31 read and 23 write. Every one of the 23 stops and asks a person first. See Writes stop for a person.
Not for you if you want a chat product or a dashboard. HeyMetra is neither, and it is paid — no free plan, no trial. The current plans are on the pricing page.
The address is the same everywhere:
Your assistant will send you through a sign-in once, and HeyMetra never sees a password for any connected account — authorisation happens at the provider.
add-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. For the assistants that keep the setting in their own UI rather than a file, use the steps below.
Anthropic calls a connected MCP server a connector. Add it from Claude's own settings; on Team and Enterprise plans only an owner can add it, under Organization settings.
Full walkthrough: heymetra.com/mcp/claude/
The endpoint has to include its /mcp path here. OpenAI has moved this setting more than once, so if the menu disagrees with this line, trust the menu and tell us.
Full walkthrough: heymetra.com/mcp/chatgpt/
xAI calls this "bring your own MCP". It asks for the MCP server URL and nothing else.
Full walkthrough: heymetra.com/mcp/grok/
Perplexity documents remote connectors as a Pro, Max and Enterprise feature.
Full walkthrough: heymetra.com/mcp/perplexity/
Or a .mcp.json in the project root. /mcp inside a session shows what connected.
Full walkthrough: heymetra.com/mcp/claude-code/
~/.cursor/mcp.json, or .cursor/mcp.json in a projectLeave the static OAuth fields empty — they exist for servers that cannot register themselves, and this one can.
Full walkthrough: heymetra.com/mcp/cursor/
~/.gemini/config/mcp_config.json, or .agents/mcp_config.json in a projectThe key is serverUrl, not url — the one thing Antigravity spells differently from every other JSON client.
Full walkthrough: heymetra.com/mcp/antigravity/
New to any of this? What an MCP server is, and how it differs from an API.
Questions that need two accounts at once are the point:
Which channel actually paid for itself last month — spend against subscription revenue, not installs?
Search Console clicks fell last week. Which queries lost them, and did orders move with them?
Compare cost per trial across platforms for the last 28 days.
Which leads in the CRM came from the campaign that started on Monday?
Cut the budget on the ad set with the worst cost per purchase by 20%.
The last one does not run. It comes back as a change for you to approve.
A tool that would change an account returns the proposed change instead of executing it. You approve it, and the payload you approved is the payload that runs — the model does not get to reconsider after the fact.
The bounds are values in code, not instructions in a prompt:
| Bound | Value |
|---|---|
| Budget change in one action | ±50% |
| Absolute budget ceiling | 10,000 in the account's currency |
| Campaigns touched by one action | 5 |
| Account-changing writes per rolling day | 20 |
| Messages sent per rolling day | 20, counted separately |
| Approval expires after | 30 minutes |
The last one matters more than it looks: an approval card left open overnight is a decision made against yesterday's numbers.
What HeyMetra does not claim: no SOC 2, no ISO certification, no penetration test. The security page says so in those words, along with what is actually in place.
Every connector in the catalogue, by category. Which of these you can connect today is on each connector's own page — that list moves, and a README is the wrong place to freeze it.
The ones you can connect today also have a repository of their own, marked repo below: setup steps, what you can ask it, what it may and may not touch, and what to do when the provider refuses. Each one is generated from the same catalogue and refreshed daily.
Ads — Google Ads · Meta
Analytics — Google Analytics 4 · Google Search Console repo
Ecommerce — Shopify · Trendyol repo · WooCommerce repo
Revenue & CRM — Stripe · HubSpot · Zoho CRM repo · Zoho SalesIQ repo · Zoho Marketing Automation repo
Mobile — AppsFlyer repo · RevenueCat · Adapty repo · App Store Connect repo
Channels (delivery, not data) — Slack repo · Telegram repo · Email
Missing one you need? Ask for it inside the assistant — HeyMetra can pass a request or a correction to us in your own words — or write to us.
Published in the Official MCP Registry as com.heymetra/heymetra.
| Product | heymetra.com |
| Pricing | heymetra.com/pricing/ |
| Connectors | heymetra.com/connectors/ |
| Setup per assistant | heymetra.com/mcp/ |
| Security and limits | heymetra.com/security/ |
| Comparisons | heymetra.com/compare/ |
| MCP server directory | heymetra.com/mcp/directory/ |
| Writing | heymetra.com/blog/ |
| About | heymetra.com/about/ |
| Contact | hello@heymetra.com |
This repository is documentation. HeyMetra itself is a hosted service and its source is not public; there is nothing to install or run from here. Corrections and questions are welcome as issues — a wrong setup line is worth reporting, because the reader follows it, fails, and concludes the product is broken.