/ Verzeichnis / Playground / Telegram MCP (chaindead)
← Alle Server ↗ GitHub
● Community chaindead ⚡ Sofort

Telegram MCP (chaindead)

von chaindead · chaindead/telegram-mcp

Manage Telegram dialogs, drafts, read statuses, and messages from any MCP client.

Telegram MCP (chaindead) is a Model Context Protocol server by chaindead. Manage Telegram dialogs, drafts, read statuses, and messages from any MCP client. See the source repo for setup, supported clients, and configuration details.

▶ Demo ansehen 📦 Installieren 💡 Anwendungsfälle

Warum nutzen

Hauptfunktionen

Live-Demo

In der Praxis

telegram-mcp-chaindead.replay ▶ bereit
0/0

Installieren

Wählen Sie Ihren 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"
      ]
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

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

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "telegram-mcp-chaindead": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/chaindead/telegram-mcp"
      ]
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

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

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

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

Continue nutzt ein Array von Serverobjekten statt einer Map.

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

In context_servers hinzufügen. Zed lädt beim Speichern neu.

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

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: Telegram MCP (chaindead)

Use Telegram MCP (chaindead) for its primary workflow

👤 Developers using AI coding agents ⏱ ~10 min beginner

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

Voraussetzungen
  • MCP server installed — See https://github.com/chaindead/telegram-mcp for install instructions
Ablauf
  1. Install
    Install Telegram MCP (chaindead) following the README at https://github.com/chaindead/telegram-mcp✓ Kopiert
    → MCP server appears in your client's available tools/skills
  2. Invoke
    Use Telegram MCP (chaindead) to complete the task described in its docs.✓ Kopiert
    → Agent calls the relevant tool/skill and returns a result

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

Fallstricke
  • 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

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen