Connect Telegram to Claude Code

Let Claude reply in chats and post to channels in Telegram. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Telegram to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Telegram, you add a Telegram MCP server: a small hosted service that exposes Telegram's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Telegram account. No API keys pasted into config files.

claude mcp add --transport http telegram https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Telegram once connected?

Full read-write Telegram access lets Claude send a message into a specific chat, reply to a user in a support thread, post an update to a channel you administer, pin or edit a message, and forward content between chats once you approve. Triage and outbound replies happen inside Telegram, not in a separate window.

Send a message or reply into a specific chat or group thread
Post an announcement to a channel your bot administers
Pin, edit, or delete a message your bot has access to
Forward a message from one chat to another after you approve
Answer an inbound support message your bot received, with the prior context preserved
Set or update a bot reply once you confirm the wording

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Telegram access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Telegram API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Telegram changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Telegram connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Telegram connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Telegram account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Telegram's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Telegram?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Telegram account it signs in with. Revoking access is one click in Telegram.

More on the Telegram connector

Telegram connector for claude.ai WhatsApp Business + Claude Code Webex + Claude Code RingCentral + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us