An agent on your own Telegram account.
telemcp is a Telegram MCP server for Claude, Cursor, Codex or OpenClaw. Your agent signs in like a new device and answers your private chats in your words while you work. Not a bot.
Early access by invite. No price is published yet.
No bot to create and no server to run. The session shows under Settings, Devices on your phone, and ends there with one tap.
Works today with Claude Code, Claude desktop, Cursor, Codex, OpenClaw, and any MCP client that can send a header. ChatGPT once sign-in ships.
Plate 1Telegram for Mac, 14:07 to 14:09. Priya asks about the first cut; the agent answers from Jonas's own account with the link he cleared for her. Jonas is an example, not a customer.
Chats
Plate 2The same phone at 17:58, on an afternoon without telemcp.
Four chats waited until six.
Jonas edits films for small production companies. The people who pay him, and the people he pays, write on Telegram. An edit suite is a dark room with the phone face down.
At six he turns it over. Priya needed the first cut for a four o'clock call. Tomasz wanted an invoice. Henrik had a note on the grade. Elif was new and wrote once.
None of these needed Jonas. They needed someone who knew what he would say, and could say it from his account.
Set up from inside your agent.
Add telemcp to the agent you already use, then ask it to connect your Telegram. The login is Telegram's own, a code to your phone. Nothing to install or host. Ten minutes on the Tuesday in question.
Add telemcp to your agent.
Your invite is a mail with two lines, a server URL and a key. In Claude desktop they go in as a connector or a short config entry; in Claude Code, Cursor, Codex or OpenClaw it is one line in the settings. The exact lines are in the appendix at the foot of this page.
Your early access is ready
Hi Jonas,
Your account is open. Add these two lines to the agent you use. The key goes in a header, never in the URL.
https://••••••••••••/mcp••••••••••••••••••••••••Claude desktop takes them under Settings, Connectors, or as a short config entry. Claude Code, Cursor, Codex and OpenClaw take one line each.
Then ask your agent to connect your Telegram.
Plate 3The invite, in Mail. Two lines, server and key, for the agent you already use.
Ask it to connect your Telegram.
Say "connect my Telegram". Telegram sends a login code to your phone, the way it does for any new device. You tell your agent the code; with two-step verification it asks for your password too. Prefer a QR code? Ask for one and scan it under Settings, Devices.
This code can be used to log in to your Telegram account. We never ask it for anything else.13:38
Plate 4Telegram's own login code, then its new login notice. The code is an example.
Tell it what to answer.
In plain words, in the chat you already have open. Who gets what, who hears "tonight", when to stop. From then on your agent picks up each new message as it arrives, and telemcp only sends what your agent tells it to send.
Plate 5The brief, typed where the agent already runs. Everything in Plate 1 follows from these three lines.
Priya wrote at 14:07, had her answer at 14:08 and had read it by 14:09, from Jonas's own account, while he sat in the edit.
Early access, by invite. One email when yours is ready; no price is published yet, and you see it before you pay anything.
Everything it does, in one chat.
Five functions the server exposes today, numbered where they show in one chat on Telegram for Mac, later the same Tuesday. Private chats only.
Your agent asks telemcp to wait, and the request is held open for up to 55 seconds at a time until something comes in. No server, no webhook needed. If the agent was closed, it catches up on what it missed.
Text up to 4,096 characters, sent from your account, to the person who wrote. The reply reads as you.
One attachment per message, from a link. The invoice, the still, the review notes.
Every sent message reports sent, delivered, read or failed, with the reason when it fails.
Anyone already in your chats is fair game. Earlier messages can be read back through the plain HTTPS API so a reply fits the conversation, and it knows how many sends and new people it has left today.
Plate 6Telegram for Mac, the same Tuesday at 16:21. Tomasz gets the invoice from a link the agent was given. The numbers in the margin are the list on the left.The five functions above, in this one chat.
Ceilings that come with the account.
It is your real account, so the ceilings are part of the service itself: identical for everyone, and nothing you, your agent or a support request can change.
Logs out all devices except for this one.
Plate 7Telegram, Settings, Devices, with the telemcp session listed next to the MacBook. End it there in one tap.
There is no model in telemcp. It is the signed-in device: the agent you connected does the thinking and the writing, and nothing leaves the account that the agent did not hand over. No groups, no channels.
No service can guarantee that Telegram leaves an account alone. What telemcp does is keep every account well inside the lines above, and stop the moment Telegram objects.
Ask your agent to disconnect, or open Telegram, Settings, Devices, and end the session like any other device. Your chats stay on your phone either way.
Three more chats.
The same Tuesday, and one other afternoon. A note that is for Jonas, someone new who wrote first, and a still sent from a link.
Plate 8Henrik, 13:42. A note that is for Jonas gets the "tonight" answer, and the agent has caught up on what arrived before it was connected.
Plate 9Elif, 13:42. Someone new. She wrote first, so the agent may answer. It cannot start a chat with a stranger.
Plate 10Amaka, 15:03, another afternoon. A photo from a link the agent was given, with the frame named so she can ask for another.
Who it is for.
A freelancer whose clients write on Telegram, so that status questions, files and “can we move it” get an answer while the work gets done. A founder who does support from a personal account, where the people who have the number keep writing to the same name. A creator whose community sends DMs and gets replies in their voice, with the links and files they would send themselves. And an OpenClaw or Claude operator who wants the agent on a real account rather than a bot username: their own chats, under fixed ceilings, with one session they can end.
Asked before joining.
What is a Telegram MCP server?
telemcp is an MCP server that connects an AI agent to Telegram. Your agent, in Claude, Cursor, Codex or OpenClaw, uses it to read new messages and send replies from your own Telegram account. There is no model in telemcp; it signs in and carries what the agent you connected wrote, and nothing else goes out.
Is there a Telegram MCP server that uses my own account, not a bot?
Yes. telemcp signs in to your existing Telegram account the way the Telegram app does on a new device. People see messages from you, not from a bot. Telegram sends a login code to your phone, you give it to your agent, and with two-step verification it asks for your password too.
Can my AI agent message people who never wrote to me on Telegram?
Not yet. Today it can write to people who are already in your chats, for example anyone who wrote to you first. Starting a chat with a new person by username is not available.
Does telemcp work with Claude, Cursor, Codex or ChatGPT?
Claude Code, Claude desktop, Cursor, Codex and OpenClaw work today, and so does any MCP client that can send a header over Streamable HTTP. ChatGPT connectors cannot send a key header yet, so ChatGPT is not supported; sign-in support is planned.
Do I need a server or webhooks to receive Telegram messages?
No. Your agent asks telemcp for new messages and the request waits up to 55 seconds until one arrives, so nothing has to run on a server of yours. If your agent was closed and kept its place, it catches up on what arrived in the meantime. Webhooks exist for people who want them.
Will Telegram flag my account if an AI agent uses it?
No service can guarantee that Telegram leaves an account alone. What telemcp does is keep every account inside fixed ceilings: a pause whenever Telegram asks the account to slow down, no fourth message to anyone who has not answered, and per UTC day 50 sends with at most 10 of them to people who never wrote. If Telegram flags the account, sending stops.
How much does telemcp cost?
Prices are not published yet. During early access every invited account gets one connected Telegram account with the ceilings above. You see the price before you pay anything.
How do I disconnect my Telegram from telemcp?
Ask your agent to disconnect, or open Telegram on your phone, go to Settings, Devices, and end the session. Either way telemcp is signed out and your chats stay on your phone.
Your Telegram, answered. Still yours.
No bot to create and no server to run. The session shows under Settings, Devices on your phone, and ends there with one tap. Early access, by invite; no price is published yet.
AppendixThe setup lines, for people who would rather type them.
The server URL and the key are in your invite; the key goes in a header, never in the URL. Streamable HTTP only, no SSE and no stdio server.
claude mcp add --transport http telemcp <server URL from your invite> --header "X-API-Key: <your key>"
then /mcp inside Claude Code lists the tools"telemcp": {
"command": "npx",
"args": ["mcp-remote", "<server URL from your invite>", "--header", "X-API-Key:<your key>"]
}
in claude_desktop_config.json, under mcpServers. Accounts with the request headers beta can add a custom connector instead.{ "mcpServers": { "telemcp": {
"url": "<server URL from your invite>",
"headers": { "X-API-Key": "<your key>" } } } }
~/.cursor/mcp.jsoncodex mcp add telemcp --url <server URL from your invite> --bearer-token-env-var TELEMCP_API_KEYopenclaw mcp doctor telemcp --probe
add the server under Settings, MCP, or as mcp.servers.telemcp with transport "streamable-http" and the X-API-Key headerAny MCP client that can send a header over Streamable HTTP works; one that cannot can go through the mcp-remote bridge. The same operations exist as a plain HTTPS API from your own code, plus a message list that is REST only.
The tools, by name: connect_telegram, get_telegram_status, submit_telegram_code, submit_telegram_password, disconnect_telegram, list_accounts, wait_for_messages (a long poll held open up to 55 seconds, 25 by default, with a cursor), send_message, get_message, get_usage, and the webhook tools (create, test, health, re-enable, signing). Every tool answer starts with the HTTP status and carries the body as JSON. Webhooks fire for message received, sent, delivered, read and failed, and for account connected, disconnected, restricted and limit reached, signed with HMAC SHA-256.