Telegram MCP (chaindead) — Instalar & Demo ao vivo

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

Por que usar

Principais recursos

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 ao vivo

Como fica na prática

telegram-mcp-chaindead.replay ▶ pronto

0/0

Instalar

Escolha seu 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"
      ]
    }
  }
}

Abra Claude Desktop → Settings → Developer → Edit Config. Reinicie após salvar.

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

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

Cursor usa o mesmo esquema mcpServers que o Claude Desktop. Config de projeto vence a global.

VS Code → Cline → MCP Servers → Edit

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

Clique no ícone MCP Servers na barra lateral do Cline, depois "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

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

Mesmo formato do Claude Desktop. Reinicie o Windsurf para aplicar.

~/.continue/config.json

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

O Continue usa um array de objetos de servidor em vez de um map.

~/.config/zed/settings.json

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

Adicione em context_servers. Zed recarrega automaticamente ao salvar.

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

Uma linha só. Verifique com claude mcp list. Remova com claude mcp remove.

Casos de uso

Usos do mundo real: Telegram MCP (chaindead)

Use Telegram MCP (chaindead) for its primary workflow

👤 Developers using AI coding agents ⏱ ~10 min beginner

Quando usar: You need the capability: Manage Telegram dialogs, drafts, read statuses, and messages from any MCP client.

Pré-requisitos

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

Fluxo

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.

Armadilhas

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

Mais

Recursos

📖 Leia o README oficial no GitHub

🐙 Ver issues abertas

🔍 Ver todos os 400+ servidores MCP e Skills