HeyMetra

com.heymetraPublished by heymetra.comOfficial publisherv0.1.1Updated Oct 24, 2026

Ask across your ads, analytics, store, CRM and subscription accounts; writes wait for approval.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that lets an assistant query ads, analytics, store, CRM and subscription accounts together, with writes held for human approval.

What you can do
  • Ask cross-account questions across connected ads, analytics, ecommerce, revenue, CRM and mobile subscription accounts
  • Read spend, traffic, store and revenue data side by side to judge whether a campaign paid for itself
  • Propose account changes such as budget adjustments, which return as an approval card instead of running
  • Send messages through connected channels such as Slack, Telegram and email, subject to daily limits
  • Pass a request or correction about missing connectors to the provider in your own words
When to use it
Useful for founders, small teams, growth marketers, agencies and mobile app owners who need answers that span several platforms at once, such as spend against subscription revenue, without building dashboards or moving data by hand.
Requirements
A remote endpoint at mcp.heymetra.com/mcp over Streamable HTTP; OAuth 2.1 sign-in through the assistant, with no password or key pasted into config. A paid HeyMetra plan is required, and each provider account must be connected and authorised at the provider.
Before you install
It is paid with no free plan or trial. Twenty-three of the tools can change accounts; they return a proposal for a person to approve, bounded by limits such as ±50% budget change, a 10,000 currency ceiling, 20 account-changing writes and 20 messages per rolling day, and approvals expire after 30 minutes. Connected account data is sent to HeyMetra, which states it holds no SOC 2, ISO or penetration-test certification.

Installation

In SourceWeft

  1. Open HeyMetra in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.heymetra%2Fheymetra/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

README

[HeyMetra — a remote MCP server for marketing and revenue data]

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.

[MCP Registry] [Transport] [Auth] [Website]

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

bash
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 — Settings → Customize → Connectors → Add custom connector

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/

ChatGPT — Settings → Security and login → Developer mode, then chatgpt.com/plugins

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/

Grok — grok.com/connectors → New Connector → Custom

xAI calls this "bring your own MCP". It asks for the MCP server URL and nothing else.

Full walkthrough: heymetra.com/mcp/grok/

Perplexity — Settings → Connectors → Custom connector → Remote

Perplexity documents remote connectors as a Pro, Max and Enterprise feature.

Full walkthrough: heymetra.com/mcp/perplexity/

Claude Code — one command
bash
claude mcp add --transport http heymetra https://mcp.heymetra.com/mcp

Or 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
toml
[mcp_servers.heymetra]url = "https://mcp.heymetra.com/mcp"

Then codex mcp login.

Full walkthrough: heymetra.com/mcp/codex/

Cursor — ~/.cursor/mcp.json, or .cursor/mcp.json in a project
json
{  "mcpServers": {    "heymetra": { "url": "https://mcp.heymetra.com/mcp" }  }}

Leave the static OAuth fields empty — they exist for servers that cannot register themselves, and this one can.

Full walkthrough: heymetra.com/mcp/cursor/

Antigravity — ~/.gemini/config/mcp_config.json, or .agents/mcp_config.json in a project
json
{  "mcpServers": {    "heymetra": { "serverUrl": "https://mcp.heymetra.com/mcp" }  }}

The 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.

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:

BoundValue
Budget change in one action±50%
Absolute budget ceiling10,000 in the account's currency
Campaigns touched by one action5
Account-changing writes per rolling day20
Messages sent per rolling day20, counted separately
Approval expires after30 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.

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

Productheymetra.com
Pricingheymetra.com/pricing/
Connectorsheymetra.com/connectors/
Setup per assistantheymetra.com/mcp/
Security and limitsheymetra.com/security/
Comparisonsheymetra.com/compare/
MCP server directoryheymetra.com/mcp/directory/
Writingheymetra.com/blog/
Aboutheymetra.com/about/
Contact[email protected]

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.

Built by Zeisoft Yazılım Limited Şirketi — İzmir, Türkiye

Source: README.md at commit c3117f0

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.1LatestSep 18, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.