Link a Telegram chat to your workspace.
An answer nobody reads is not an answer. Have it delivered to Telegram, where the team already is.
https://mcp.heymetra.com/mcp
1. Create a bot with @BotFather
In Telegram, open a chat with @BotFather and send /newbot. It asks for a display name and then a username, which must end in 'bot'. It replies with the token.
The bot is yours, not HeyMetra's. It lives in your Telegram account, you can rename or delete it at any time, and deleting it is how you cut this connection off at the source.
2. Copy the token and paste it into HeyMetra
One line: digits, a colon, then letters and digits. Choose Telegram on the Connections screen and paste it. Saving checks it against Telegram immediately and shows you which bot answered.
Anyone holding this token can post as your bot, so treat it like a password. If it leaks, /revoke in BotFather issues a new one and cancels the old; then paste the new one here.
3. Open the link HeyMetra gives you and press Start
The token proves which BOT will send; it does not say which CHAT to send to. HeyMetra hands you a one-time link to your own bot. Open it, press Start, and the chat it opens is the one messages arrive in.
This step cannot be skipped and cannot be done from our side: Telegram does not let a bot message somebody who has never written to it. The link is good for fifteen minutes and can be used once.
4. Send the test message
From the Connections screen. It proves the whole path (token, bot and chat) rather than just the token, and it is the only step that does.
5. Add HeyMetra to the assistant you use
Claude, ChatGPT, Cursor or Codex. Your assistant can then send to this chat. It shows you the exact text first and nothing goes until you approve it.
Watch what you paste:
- Anything starting
@is that is the bot's username, not its token. The token is the long line BotFather sent you, digits then a colon then letters. and will be refused by name.
Add HeyMetra once and it is there in every conversation. The address is the same everywhere:
https://mcp.heymetra.com/mcp
npx add-mcp https://mcp.heymetra.com/mcpadd-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. Run against this endpoint before it was written here.
Claude — Settings → Customize → Connectors → Add custom connector
Paste the address above into Settings → Customize → Connectors → Add custom connector.
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
Paste the address above into Settings → Security and login → Developer mode, then chatgpt.com/plugins.
The address has to end in /mcp here.
Full walkthrough: heymetra.com/mcp/chatgpt/
Grok — grok.com/connectors → New Connector → Custom
Paste the address above into grok.com/connectors → New Connector → Custom.
XAI calls this “bring your own MCP”.
Full walkthrough: heymetra.com/mcp/grok/
Perplexity — Settings → Connectors → Custom connector → Remote
Paste the address above into Settings → Connectors → Custom connector → Remote.
Perplexity documents it as a Pro, Max and Enterprise feature.
Full walkthrough: heymetra.com/mcp/perplexity/
Claude Code — claude mcp add --transport http
claude mcp add --transport http heymetra https://mcp.heymetra.com/mcpOr 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
[mcp_servers.heymetra]
url = "https://mcp.heymetra.com/mcp"Under an [mcp_servers.] section, then codex mcp login.
Full walkthrough: heymetra.com/mcp/codex/
Cursor — ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
"mcpServers": {
"heymetra": { "url": "https://mcp.heymetra.com/mcp" }
}
}Leave the static OAuth fields empty; HeyMetra does not need them.
Full walkthrough: heymetra.com/mcp/cursor/
Antigravity — ~/.gemini/config/mcp_config.json, or .agents/mcp_config.json in a project
{
"mcpServers": {
"heymetra": { "serverUrl": "https://mcp.heymetra.com/mcp" }
}
}The key is serverUrl, not url, unlike every other JSON client.
Full walkthrough: heymetra.com/mcp/antigravity/
Send a message to the linked Telegram chat. You see the exact text first, and it is sent only once you approve. It cannot be recalled.
Propose a change to this account. Nothing is sent until you approve it, and HeyMetra cannot undo it afterwards.
Permissions are switched on per connection, and one you leave off is a tool your assistant never sees.
| Permission | What it covers | Changes anything? |
|---|---|---|
| Send messages | Let your assistant send to this chat, with your approval each time. Turn it off and only the test button can reach it. | Yes — every change waits for your approval |
| Full account access | Lets your assistant read anything in this account to answer your questions. The figures are the provider's own, not ones HeyMetra has checked. It can also propose changes: none is applied until you approve it, and HeyMetra cannot undo one afterwards. | Yes — every change waits for your approval |
What each permission lets an assistant do, in full
- Send a message to the linked Telegram chat. You see the exact text first, and it is sent only once you approve. It cannot be recalled.
- Ask anything about this account and get the answer from its live data. Reads only, and the figures are the provider's own rather than ones HeyMetra has checked.
- Propose a change to this account. Nothing is sent until you approve it, and HeyMetra cannot undo it afterwards.
Anything that would change something comes back as a proposal you approve, inside bounds that live in code rather than in a prompt: at most 20 messages a rolling day, counted separately from account changes, and an approval that expires after 30 minutes. How that works.
Saving fails and says Telegram rejected the token.
Why: Usually the bot's username was pasted instead of its token, or the token was revoked in BotFather after being copied. Telegram answers 404 for a malformed token and 401 for a revoked one; both mean the same thing here.
Fix: Send /token to @BotFather and pick the bot. It shows the current token, which is the long line with a colon in it.
The token saved, but the test message never arrives and nothing says why.
Why: The Start step has not happened. A bot cannot open a conversation in Telegram; the person has to write to it first. Until Start arrives there is no chat to deliver to.
Fix: Open the link from the Connections screen again and press Start. Ask for a fresh link if more than fifteen minutes have passed.
The link opens Telegram but nothing seems to happen.
Why: The link carries a one-time code, and it is consumed the first time it is opened. Opening the same one twice does nothing the second time.
Fix: Ask for a new link on the Connections screen.
Messages arrive for one person, and a colleague wants them too.
Why: The link is redeemed by whoever opens it, so the chat belongs to that person. It is a private chat between them and the bot.
Fix: Have the colleague open their own link from their own HeyMetra account. A Telegram connection carries one chat, so a second person is a second link rather than a shared one.
Connect your own bot and press Start to link the chat, then send a test message from HeyMetra to confirm it arrives. After that, your assistant can send to that same chat. It shows you the exact text first and nothing is sent until you approve it. Whoever is in that chat sees it, and a sent message cannot be recalled. Your assistant can also ask the bot about that chat, and the bot sees only what is addressed to it: the one chat you linked.
About Telegram
Telegram is a channel you own outright. There is no HeyMetra app to install: you create a bot in BotFather, in your own account, and give HeyMetra its token. Nothing about it belongs to us. Revoke the token and the connection is over the same second, with nothing to ask us for.
What it reaches is one conversation: the chat you open with the bot by pressing Start. A Telegram bot sees only what is addressed to it, so it cannot wander into somebody else's messages. Groups and channels are not supported: one bot, one chat, on purpose.
The reason to read Telegram through HeyMetra rather than through a server that only knows Telegram is everything else it can answer in the same breath:
Ads — Google Ads · Meta
Analytics — Google Analytics 4 · Google Search Console · PostHog
Ecommerce — Shopify · Trendyol · WooCommerce
Revenue & CRM — Stripe · HubSpot · Zoho CRM · Zoho SalesIQ · Zoho Marketing Automation
Mobile — AppsFlyer · RevenueCat · Adapty · App Store Connect
Work — Google Calendar · Google Meet · Jira
Channels — Slack · Telegram
The full catalogue is at heymetra.com/connectors/.
- Telegram connector page
- HeyMetra — what the product is
- Setup for every assistant
- Security and limits
- Pricing
- HeyMetra's own repository
Built by Zeisoft, who make HeyMetra. Not affiliated with Telegram. This README is generated from HeyMetra's live connector catalogue and refreshed daily; corrections are welcome as issues.