Telegram Bridge MCP
No Claw? No Problem.
Anthropic restricted Claude Code's native instance API — but this bridge doesn't care. It's a standard Model Context Protocol server. Any IDE, any model, any agent framework that speaks MCP connects out of the box — no proprietary lock-in, no webhooks, no public URL required.
What Is This?
Telegram Bridge MCP connects AI assistants to Telegram bidirectionally. It lets any MCP-compatible client send messages, ask questions, receive voice replies, and run multiple concurrent agent sessions — all through a single bot you control.
Works with: VS Code (GitHub Copilot Chat), Claude Code, Cursor, Windsurf, Copilot CLI, and any MCP-compatible host.
Highlights
| Feature | Description |
|---|
| Two-way messaging | Text, Markdown, files, voice notes |
| Interactive controls | Inline buttons, confirmations, questions |
| Super tools | Self-pinning checklists and emoji progress bars that update in-place |
| Voice | Auto-transcription (bundled Whisper ONNX, no ffmpeg) + TTS (local Kokoro, OpenAI, or bundled ONNX) |
| Multi-session | Multiple agents share one bot with isolated queues, token auth, and color identity |
| Animations | Cycling status frames while your agent works |
| Reminders | Scheduled synthetic events delivered via dequeue |
| Slash commands | Dynamic bot menu; commands arrive as structured events |
| No webhooks | Pure long-polling — no public URL, no reverse proxy |
Quick Start
Tip: If your AI has web access, paste this to get started (requires web access):
Set me up: https://github.com/electrified-cortex/Telegram-Bridge-MCP
Manual setup (step by step)
1. Clone and build
git clone https://github.com/electrified-cortex/Telegram-Bridge-MCP.git
cd Telegram-Bridge-MCP
pnpm install && pnpm build
2. Create a bot
Message @BotFather on Telegram:
/newbot
Copy the token it gives you.
3. Pair interactively
pnpm pair
The wizard prompts for your bot token and Telegram user ID, writes a .env file, and verifies connectivity.
4. Configure your MCP host
See docs/setup.md for per-client config snippets (VS Code, Claude Code, Cursor, Docker).
Transports
| Transport | Entry Point | Best For |
|---|
| Streamable HTTP | pnpm start -- --http | Multiple clients sharing one server (recommended) |
| stdio | node dist/index.js | Single client, no persistent server |
| Launcher bridge | node dist/launcher.js | Auto-starts HTTP if needed, bridges stdio ↔ HTTP |
Streamable HTTP MCP config example
Claude Code / Cursor / other MCP hosts
{
"mcpServers": {
"telegram": {
"type": "streamable-http",
"url": "http://127.0.0.1:3099/mcp"
}
}
}
VS Code (.vscode/mcp.json)
{
"servers": {
"telegram": {
"type": "streamable-http",
"url": "http://127.0.0.1:3099/mcp"
}
}
}
stdio MCP config example
Claude Code / Cursor / other MCP hosts
{
"mcpServers": {
"telegram": {
"command": "node",
"args": ["/path/to/Telegram-Bridge-MCP/dist/index.js"],
"env": {
"BOT_TOKEN": "your-token",
"ALLOWED_USER_ID": "your-user-id"
}
}
}
}
VS Code (.vscode/mcp.json)
{
"servers": {
"telegram": {
"type": "stdio",
"command": "node",
"args": ["/path/to/Telegram-Bridge-MCP/dist/index.js"],
"env": {
"BOT_TOKEN": "your-token",
"ALLOWED_USER_ID": "your-user-id"
}
}
}
}
Tools — The v7 API
Version 7 consolidates the entire API into 4 tools with type-based routing. Call help(topic?) at any time for interactive documentation discovery.
send — Outbound Messaging
