Telegram MCP (chaindead) — Installer & Démo en direct

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

Pourquoi l'utiliser

Fonctionnalités clés

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

Démo en direct

Aperçu en pratique

telegram-mcp-chaindead.replay ▶ prêt

0/0

Installer

Choisissez votre 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"
      ]
    }
  }
}

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

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

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

Cursor utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la globale.

VS Code → Cline → MCP Servers → Edit

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

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

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

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.continue/config.json

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

Continue utilise un tableau d'objets serveur plutôt qu'une map.

~/.config/zed/settings.json

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

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

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

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : Telegram MCP (chaindead)

Use Telegram MCP (chaindead) for its primary workflow

👤 Developers using AI coding agents ⏱ ~10 min beginner

Quand l'utiliser : You need the capability: Manage Telegram dialogs, drafts, read statuses, and messages from any MCP client.

Prérequis

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

Déroulement

Install

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

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

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

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

Résultat : Working integration with the capabilities advertised by the project.

Pièges

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

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills