heymetra

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.

该来源不提供完整文件导出（国内平台多为平台内托管），仅存元数据与原链

接入信息

传输形态: http
鉴权方式: 鉴权未知
端点: https://heymetra.run.tools

鉴权方式未标注，请核对官方文档后再接入——不要直接使用以下片段

{
  "mcpServers": {
    "heymetra": {
      "url": "https://heymetra.run.tools"
    }
  }
}

能力清单

工具	说明
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 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_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 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_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 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_status	Who 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_history	What 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_connectors	Every 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_feedback	Sends 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.

纠错与举报（发现条目失效、署名有误或涉及侵权？）

提交举报 / 纠错

侵权举报经核验成立后，我们会即时下线该条目并删除已存的内容副本。