English Français العربية

io.github.Shreyas-Profile/telegram-mcp

Official registry AI and agents

Telegram bridge for your MCP-compatible agent. Bidirectional, no LLM in our stack.

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http telegram-mcp 'https://telegram.regiq.in/api/mcp' --header 'Authorization: <Bearer <apiKey> — get yours at https://telegram.regiq.in after Google sign-in.>'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "telegram-mcp": {
            "type": "http",
            "url": "https://telegram.regiq.in/api/mcp",
            "headers": {
                "Authorization": "<Bearer <apiKey> — get yours at https://telegram.regiq.in after Google sign-in.>"
            }
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. telegram-mcp
  2. Use it (hosted)
  3. Tools
  4. Slash commands (platform-handled)
  5. Self-host
  6. Architecture
  7. License

telegram-mcp

Built by **Shreyas** · Shipped by **Globalion**

Bidirectional Telegram ⇆ agent bridge. No LLM in our stack.

Your agent (Claude Desktop, Cursor, a custom script) is the brain. Our platform is the pipe: we take messages you send on Telegram, store them, and hand them to your agent when it polls. When your agent has something to say back, it pushes through us to your Telegram.

  • Bring your own agent. Any MCP client works.
  • No inference in the middle. We don't call an LLM. No vendor lock-in.
  • Bidirectional. get_new_messages pulls inbound, send_telegram_message pushes outbound.
  • Platform slash-commands. /help, /clear, /recent, /window, /usage all work even if your agent is offline.

Hosted at telegram.regiq.in or self-host with the Docker Compose below.

Use it (hosted)

  1. Visit https://telegram.regiq.in, sign in with Google.
  2. DM @BotFather → /newbot. Paste the token in your dashboard.
  3. On the dashboard: Generate MCP API key, copy it.
  4. Add to Claude Desktop's claude_desktop_config.json (or Cursor / any MCP client):
      {
    "mcpServers": {
      "telegram": {
        "url": "https://telegram.regiq.in/api/mcp",
        "headers": {
          "Authorization": "Bearer YOUR_KEY_HERE"
        }
      }
    }
  }
  5. Send /start to your bot on Telegram.

Now your agent can call get_new_messages to see what you sent it, and send_telegram_message to reply.

Tools

ToolDirectionNotes
get_new_messages()user → agentReturns inbound messages since the last pull. Read-once.
send_telegram_message(text)agent → userDelivers text to the user's Telegram bot.
list_recent_messages(max=20)readLast N stored messages, both directions. No cursor advance.
clear_history()actionWipes stored history for the user.

Slash commands (platform-handled)

Handled by the platform directly — your agent isn't involved. So /help works even when nothing is polling.

CommandEffect
/startRegisters this Telegram chat with your account.
/helpLists commands.
/recent [N]Shows the last N stored messages.
/clearWipes history.
/window NSets the history window (default 20).
/usageStored message count.

Self-host

You'll need:

  • Docker + Compose
  • A Google OAuth client — Cloud Console. Scopes: openid, email, profile. Redirect: <PUBLIC_BASE_URL>/api/auth/callback/google
  • A public HTTPS domain for Telegram webhooks (Cloudflare Tunnel or ngrok http 3012 locally)

No LLM key required. Your agent brings its own model.

git clone https://github.com/globalion/telegram-mcp
cd telegram-mcp
cp .env.example .env
# fill NEXTAUTH_SECRET, GOOGLE_*, PUBLIC_BASE_URL
docker compose up -d
# open http://localhost:3012

Architecture

  Telegram app                                Your MCP agent
     ▲   │                                      ▲   │
     │   │ text                          poll   │   │ push
     │   ▼                                      │   ▼
   ┌──────────────────────────────────────────────────┐
   │  Our platform (Hetzner)                          │
   │  - /api/telegram/webhook/<per-user-secret>       │
   │    · slash-commands answered here                │
   │    · plain text stored, no reply                 │
   │  - /api/mcp   Bearer-auth JSON-RPC               │
   │    · get_new_messages, send_telegram_message     │
   │    · list_recent_messages, clear_history         │
   │  - Postgres: User, ApiKey, TelegramLink, Message │
   └──────────────────────────────────────────────────┘

Per-user webhook URL segment is a random secret so a leaked bot token can't be pointed at someone else's account. Google sign-in is identity + ban anchor only — per-message identity comes from the MCP API key + chatId.

License

MIT. See LICENSE.

Frequently asked questions

What is io.github.Shreyas-Profile/telegram-mcp?

Telegram bridge for your MCP-compatible agent. Bidirectional, no LLM in our stack.

How do I install io.github.Shreyas-Profile/telegram-mcp?

It runs as a remote server. In Claude Code: claude mcp add --transport http telegram-mcp 'https://telegram.regiq.in/api/mcp' --header 'Authorization: <Bearer <apiKey> — get yours at https://telegram.regiq.in after Google sign-in.>'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.Shreyas-Profile/telegram-mcp need an API key?

Yes. It expects Authorization, which you set in its configuration.

Is io.github.Shreyas-Profile/telegram-mcp open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.github.Shreyas-Profile/telegram-mcp?

It is published by globalion. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.