telegram-mcp

Give your AI tools direct access to Telegram. Read chats, send messages, search history, manage groups, download media — all via the Model Context Protocol.

telegram-mcp is an MCP server that connects your Telegram account to Claude Code, Cursor, Windsurf, or any AI tool that supports MCP. Instead of switching to Telegram, you ask the AI to check your messages, reply to someone, or find that link from last week — and it does.

What makes this different:

• Your real account. Uses MTProto (Telethon), not the Bot API. You see everything you'd see in the Telegram app — private chats, groups, channels, media.
• 40 tools. Chats, messages, search, media, contacts, groups, channels, scheduling, reactions, admin tools, and more.
• Passive caching. Messages are cached in local SQLite as you use the server. No explicit sync step — the cache builds itself. Gives you searchable history that grows over time.
• Security first. Session files stored with restricted permissions. No credentials in config files. Rate limiting built in.

Quick Start

This is not a bot. There is no bot to add. No third party gives you a phone number. You log in as yourself, with the same phone number you already use for Telegram. If an AI tool tells you to "add a bot to give you a number", ignore it — and never share a Telegram login code with anyone, ever.

If you're asking Claude (or another AI agent) to install this for you: the agent can wire up the MCP server config and clone the repo, but the agent cannot complete the login step. Login is interactive — Telegram sends a code to your phone, and you type it into a terminal prompt yourself. You must run telegram-mcp login in a real terminal once, then the agent can use the server.

Install from PyPI

uv tool install telegram-mcp-jgalea

Or with pip:

pip install telegram-mcp-jgalea

Both provide the telegram-mcp command.

Install from source

git clone https://github.com/jgalea/telegram-mcp.git
cd telegram-mcp
uv sync

Authenticate

Run the login command once to create your Telegram session:

telegram-mcp login

You'll need a Telegram API ID and hash first. To get them:

1. Go to my.telegram.org and log in with your phone number
2. Click API development tools
3. If you already have an app, use those credentials. Telegram only allows one API app per account, and the same api_id/api_hash work for any Telegram project.
4. If not, fill in the form: App title (e.g. "telegram-mcp"), Short name (anything), Platform: "Other". Description can be left blank. Click Create application.
5. Copy the App api_id (a number) and App api_hash (a hex string)

The login command will prompt for these if not already configured, then ask for:

1. Your phone number
2. The verification code Telegram sends you
3. Your 2FA password (if enabled)

The session is saved to ~/.telegram-mcp/session.session. You only need to do this once.

Connect to Claude Code

Add to your MCP config (~/.claude.json):

{
  "mcpServers": {
    "telegram": {
      "command": "telegram-mcp",
      "args": ["serve"]
    }
  }
}

If installed from source:

{
  "mcpServers": {
    "telegram": {
      "command": "uv",
      "args": ["run", "--directory", "/path/to/telegram-mcp", "telegram-mcp", "serve"]
    }
  }
}

Troubleshooting

Tools return errors or empty results

You almost certainly haven't logged in yet. Installing the MCP server and logging into Telegram are two separate steps — installation alone is not enough. Run telegram-mcp login in a real terminal and complete the phone + code + 2FA flow. After that, restart Claude Code (or your MCP client) so the proxy picks up the new session.

You can confirm the session is healthy with the get_status tool — it returns {"connected": true, "authorized": true} when ready.

Claude says "this MCP can only access a bot conversation"

This is a hallucination. The server uses MTProto (Telethon) and logs in as your full Telegram account — every chat, group, channel, and contact you can see in the Telegram app is accessible. There is no bot involved. If this message appears, the underlying cause is almost always that the login step hasn't been done; see above.

Claude tells me to add a bot or give my number to a bot

Do not. This is unsafe advice, never required, and never part of this MCP's setup. Telegram login codes are how attackers steal accounts — never enter them into any bot or third-party service. The only place to type your code is the telegram-mcp login prompt running in your own terminal.

Daemon won't start / "another telegram-mcp daemon is running"

Check for a stale lock: ls ~/.telegram-mcp/daemon.lock and lsof ~/.telegram-mcp/daemon.sock. If no process is actually running, remove the stale socket file (rm ~/.telegram-mcp/daemon.sock) and retry. The lock auto-releases when the daemon exits cleanly or crashes.

"Not configured" / "Not authorized" errors

Same root cause as the first item — run telegram-mcp login. "Not configured" means ~/.telegram-mcp/config.json is missing API credentials; "Not authorized" means the credentials are there but no Telegram session exists yet.

Tools

Chats

Messages — Read

Messages — Write

Messages — Manage

Media

Contacts

Users

Groups & Channels

Account & Utility

Architecture

telegram-mcp/
├── src/telegram_mcp/
│   ├── __init__.py
│   ├── server.py        # MCP server, tool definitions, stdio entry point
│   ├── client.py        # Telethon wrapper — all Telegram API calls
│   ├── cache.py         # SQLite write-through cache
│   └── login.py         # Interactive login CLI
├── tests/
├── pyproject.toml
├── README.md
└── LICENSE

How it works

1. server.py starts an MCP server on stdio, registers all tools, and handles incoming requests
2. Each tool calls methods on client.py, which wraps Telethon's async API into clean functions
3. cache.py intercepts results from client.py and writes messages to a local SQLite database. Search tools query Telegram live and merge with cached results for deeper history.
4. login.py is a standalone CLI that runs the interactive Telethon auth flow and saves the session file

Data flow

Claude Code → MCP request → server.py → client.py → Telegram API
                                              ↓
                                          cache.py → ~/.telegram-mcp/cache.db

Storage

All data lives in ~/.telegram-mcp/:

~/.telegram-mcp/
├── config.json          # API ID, API hash
├── session.session      # Telethon session file (auth state)
└── cache.db             # SQLite message cache

Cache behavior

The cache is passive and transparent: