Add the Telegram MCP server to Cursor

Config last verified Jun 1, 2026

The exact config to run Telegram in Cursor — paste it in, restart, and the tools load.

Prerequisites

Cursor installed.
TELEGRAM_API_ID — Your Telegram API ID from my.telegram.org.
TELEGRAM_API_HASH — Your Telegram API hash from my.telegram.org.
TELEGRAM_SESSION_STRING — Telethon session string authorizing your Telegram user account.

Setup

1. Open `~/.cursor/mcp.json`

2. Add this configuration

Add to ~/.cursor/mcp.json

~/.cursor/mcp.json

json

{
  "mcpServers": {
    "telegram": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/chigwell/telegram-mcp",
        "telegram-mcp"
      ],
      "env": {
        "TELEGRAM_API_ID": "<TELEGRAM_API_ID>",
        "TELEGRAM_API_HASH": "<TELEGRAM_API_HASH>",
        "TELEGRAM_SESSION_STRING": "<TELEGRAM_SESSION_STRING>",
        "TELEGRAM_EXPOSED_TOOLS": "<TELEGRAM_EXPOSED_TOOLS>"
      }
    }
  }
}

3. Restart Cursor and confirm the Telegram tools load.

Gotchas

Cursor keeps MCP servers under an "mcpServers" object in ~/.cursor/mcp.json for global use, and also reads a project-scoped .cursor/mcp.json so a repository can ship its own servers. Remote servers are configured with a bare "url" field and connect natively, with OAuth handled in-app when a server requires it.

← Back to the Telegram MCP server