Telegram MCP (chaindead) — Instalar & Demo en vivo

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

Por qué usarlo

Características clave

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

Demo en vivo

Cómo se ve en la práctica

telegram-mcp-chaindead.replay ▶ listo

0/0

Instalar

Elige tu cliente

~/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"
      ]
    }
  }
}

Abre Claude Desktop → Settings → Developer → Edit Config. Reinicia después de guardar.

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

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

Cursor usa el mismo esquema mcpServers que Claude Desktop. La configuración del proyecto prevalece sobre la global.

VS Code → Cline → MCP Servers → Edit

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

Haz clic en el icono MCP Servers de la barra lateral de Cline y luego en "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

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

Mismo formato que Claude Desktop. Reinicia Windsurf para aplicar.

~/.continue/config.json

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

Continue usa un array de objetos de servidor en lugar de un mapa.

~/.config/zed/settings.json

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

Añádelo a context_servers. Zed recarga en caliente al guardar.

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

Un solo comando. Verifica con claude mcp list. Quita con claude mcp remove.

Casos de uso

Usos del mundo real: Telegram MCP (chaindead)

Use Telegram MCP (chaindead) for its primary workflow

👤 Developers using AI coding agents ⏱ ~10 min beginner

Cuándo usarlo: You need the capability: Manage Telegram dialogs, drafts, read statuses, and messages from any MCP client.

Requisitos previos

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

Flujo

Install

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

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

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

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

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

Errores comunes

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

Más

Recursos

📖 Lee el README oficial en GitHub

🐙 Ver issues abiertas

🔍 Ver todos los 400+ servidores MCP y Skills