Telegram MCP (chaindead) — Install & Live Demo

Name: Telegram MCP (chaindead) MCP Server
Author: chaindead

Why use it

Key features

Manage Telegram dialogs, drafts, read statuses, and messages from any MCP client.
Maintained by chaindead (community)
Written in Go
328+ GitHub stars at last check
Open source on GitHub

Live Demo

What it looks like in practice

telegram-mcp-chaindead.replay ▶ ready

0/0

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "telegram-mcp-chaindead": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/chaindead/telegram-mcp"
      ]
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "telegram-mcp-chaindead": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/chaindead/telegram-mcp"
      ]
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "telegram-mcp-chaindead": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/chaindead/telegram-mcp"
      ]
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "telegram-mcp-chaindead": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/chaindead/telegram-mcp"
      ]
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "telegram-mcp-chaindead",
      "command": "TODO",
      "args": [
        "See README: https://github.com/chaindead/telegram-mcp"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

{
  "context_servers": {
    "telegram-mcp-chaindead": {
      "command": {
        "path": "TODO",
        "args": [
          "See README: https://github.com/chaindead/telegram-mcp"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add telegram-mcp-chaindead -- TODO 'See README: https://github.com/chaindead/telegram-mcp'

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use Telegram MCP (chaindead)

Use Telegram MCP (chaindead) for its primary workflow

👤 Developers using AI coding agents ⏱ ~10 min beginner

When to use: You need the capability: Manage Telegram dialogs, drafts, read statuses, and messages from any MCP client.

Prerequisites

MCP server installed — See https://github.com/chaindead/telegram-mcp for install instructions

Flow

Install

Install Telegram MCP (chaindead) following the README at https://github.com/chaindead/telegram-mcp✓ Copied

→ MCP server appears in your client's available tools/skills
Invoke

Use Telegram MCP (chaindead) to complete the task described in its docs.✓ Copied

→ Agent calls the relevant tool/skill and returns a result

Outcome: Working integration with the capabilities advertised by the project.

Pitfalls

README is the source of truth; details here may lag upstream — Check https://github.com/chaindead/telegram-mcp for the latest setup steps and tool list

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills