Add the Telegram MCP server to Windsurf

Config last verified Jun 1, 2026

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

Prerequisites

Windsurf 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 `~/.codeium/windsurf/mcp_config.json`

On Windows the file lives at %USERPROFILE%\.codeium\windsurf\mcp_config.json.

2. Add this configuration

Add to ~/.codeium/windsurf/mcp_config.json

~/.codeium/windsurf/mcp_config.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 Windsurf and confirm the Telegram tools load.

Gotchas

Windsurf's Cascade reads MCP servers from an "mcpServers" object in ~/.codeium/windsurf/mcp_config.json. Unlike most clients, remote servers are configured with the "serverUrl" field rather than "url", so a config that uses "url" silently fails to connect. Native remote transport is supported without an OAuth flow.

← Back to the Telegram MCP server