HeyMetra

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.

Code

Copy

https://mcp.heymetra.com/mcp

What this is

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:

• The model is yours. HeyMetra has no chat interface and buys no inference. Your assistant calls our tools using the subscription you already have, which is why a seat costs what it costs.
• The tool list is yours too. A workspace sees tools for the accounts it has connected and nothing else. There is no fixed catalogue of 54 tools sitting in your assistant's context — only the ones that can actually answer.

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.

Who it's for

• Founders and small teams with no analyst. "How did we do last week?" should not require a dashboard tour.
• Marketing and growth with budget split across platforms. "Where are we burning money?" is a cross-account question by definition.
• Agencies where every client wants their own report, yesterday.
• Mobile app owners — ad spend lives in one place and subscription revenue in another. This is the gap HeyMetra was built around: AppsFlyer, Adapty, RevenueCat and App Store Connect sit beside Google Ads and Meta, on one connection.

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.

Connect it

The address is the same everywhere:

https://mcp.heymetra.com/mcp

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.

One command

npx add-mcp https://mcp.heymetra.com/mcp

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.

Or by hand

claude mcp add --transport http heymetra https://mcp.heymetra.com/mcp

[mcp_servers.heymetra]
url = "https://mcp.heymetra.com/mcp"

{
  "mcpServers": {
    "heymetra": { "url": "https://mcp.heymetra.com/mcp" }
  }
}

{
  "mcpServers": {
    "heymetra": { "serverUrl": "https://mcp.heymetra.com/mcp" }
  }
}

New to any of this? What an MCP server is, and how it differs from an API.

What you can ask

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.

Writes stop for a person

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:

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.

Connectors

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.

How it works

• Transport — Streamable HTTP. SSE is not offered.
• Authorisation — OAuth 2.1. The server publishes an RFC 9728 protected-resource document, so a client discovers where to sign in rather than being told. Nothing is pasted into a config file except the address above.
• Per-workspace surface — tools are resolved per request from the accounts that workspace has connected. A revoked token stops working on the next call, not whenever the transport session happens to end.
• Change notifications — connect an account mid-conversation and the tool list updates in place.

Published in the Official MCP Registry as com.heymetra/heymetra.

Links

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.