heymetra

Connect your store, CRM, subscription and Search Console accounts once.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

  • Get Account Status: HeyMetra's own account for this workspace: which plan it is on and what that includes, how much of each limit is used, whether the subscription is live and when it renews, your rol
  • Get Connection Status: Returns which data sources this workspace has connected and which need reconnecting, plus every workspace this person can ask about. A connection carrying `reconsent` still work
  • Get Connector Guide: How to connect one named HeyMetra connector: what it is, the exact steps, what it asks for, what it lets an assistant do, and example questions it answers. Answers 'how do I conne

What data it sees

Do you need an account

No: the server works without sign-in

Connect your store, CRM, subscription and Search Console accounts once. Then work from the Claude, ChatGPT, Grok, Perplexity, Claude Code, Codex, Cursor or Antigravity subscription you already pay for.

How to connect

How to connect heymetra to Claude

The server address to paste into Claude settings:

https://heymetra.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect heymetra to ChatGPT

The server address to paste into ChatGPT settings:

https://heymetra.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect heymetra to Cursor

The server address to paste into Cursor settings:

https://heymetra.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (7)

Raw names from tools/list. Only developers need these.

get_account_statusHeyMetra's own account for this workspace: which plan it is on and what that includes, how much of each limit is used, whether the subscription is live and when it renews, your role, and every workspace you belong to with its own plan. Answers 'what plan am I on', 'what am I close to running out of' and 'which workspaces do I have'. Not a customer's own subscription data — that is what the Adapty, RevenueCat and Stripe tools read.
get_connection_statusReturns which data sources this workspace has connected and which need reconnecting, plus every workspace this person can ask about. A connection carrying `reconsent` still works and still answers everything it did before — HeyMetra has widened what it asks for since it was made, and `reconsent.how_to_fix` is what to tell the customer. Offer it; do not report the connection as broken. Call it first when the question names a client or an account, and use the ids it reports for the `workspace` and `account_alias` parameters. If the customer asks for a source that appears in neither list, HeyMetra does not have it yet — offer to pass the request on and send it with `submit_feedback` rather than ending the conversation at 'not available'.
get_connector_guideHow to connect one named HeyMetra connector: what it is, the exact steps, what it asks for, what it lets an assistant do, and example questions it answers. Answers 'how do I connect Google Ads', 'what will Shopify ask me for' and 'what can I ask once Adapty is connected'. Not this connection's current health — call get_connection_status for that.
get_team_statusWho is in this HeyMetra workspace, the role each of them holds and whether that role can change things, plus invitations that have been sent and not yet accepted. Answers 'who has access to our accounts'.
get_usage_historyWhat assistants have been doing in this HeyMetra workspace: recent tool calls with their outcome, including the refused ones, and a count per tool. Answers 'what have my assistants been asking' and 'why does it keep failing'. A member sees only their own calls.
list_connectorsEvery connector HeyMetra offers — data sources and delivery channels — with what it is, whether it is open to connect yet, and whether this workspace has it connected already. Answers 'what can I connect to HeyMetra' and 'what data sources do you support'. For the connect steps and what one connector asks for, call get_connector_guide with its name.
submit_feedbackSends a request or a problem report from this customer straight to the HeyMetra team, and records it against their workspace. Use it in two situations. First, when they want a data source, a channel or a capability HeyMetra does not have — Odoo, another CRM, a marketplace, anything absent from get_connection_status: do not simply tell them it is unavailable, offer to send it on as a request and then call this with kind=connector_request. Second, when they say a figure looks wrong, a total does not match their own dashboard, or something is broken — that report is the most useful thing this product can be told, so open a record for it with kind=data_dispute and name the tool whose answer they are disputing. OFFER first and send what they confirm, in THEIR OWN WORDS: do not summarise the complaint in yours, because a paraphrased bug report is a worse bug report. It costs nothing, needs no live subscription, and changes nothing in any of their connected accounts.