# Telegram MCP server

> Send messages, manage bots, and trigger chat workflows.

- Provider: Telegram
- Category: Communication (https://mcpheaven.com/catalog/category/communication)
- Status: Planned
- Slug: `telegram`
- Verified: 2026-11-10
- JSON: https://mcpheaven.com/api/v1/capabilities/telegram
- HTML: https://mcpheaven.com/catalog/telegram

## Why it is in the catalog

Widely used for bot-driven agent interfaces; available MCP servers are community maintained.

## Questions

### Is there an official Telegram MCP server?

Widely used for bot-driven agent interfaces; available MCP servers are community maintained. mcpheaven lists Telegram so agents can find it by task and reach it through one MCP endpoint.

### What can an AI agent do with Telegram?

Send messages, manage bots, and trigger chat workflows. Agents find it by describing the task, for example with the search_capabilities tool.

### How do I connect Telegram to Claude, Codex or Cursor?

Add mcpheaven once as an MCP server (https://mcpheaven.com/mcp) with an API key, then ask your agent for the task. It calls get_capability with the slug "telegram" for details.

### Is the Telegram integration available?

The Telegram integration is planned. Agents can already discover it through mcpheaven's search, and it will become callable once the integration ships.

## Connect

MCP endpoint: `https://mcpheaven.com/mcp` (Streamable HTTP, JSON-RPC). Without a key: public catalog, 120 calls per hour per address. With a key (`Authorization: Bearer mch_…`, free at https://mcpheaven.com/signup): plan quota and private capabilities.

```bash
claude mcp add --transport http mcpheaven https://mcpheaven.com/mcp --header "Authorization: Bearer mch_…"
```

```json
{ "mcpServers": { "mcpheaven": { "url": "https://mcpheaven.com/mcp", "headers": { "Authorization": "Bearer mch_…" } } } }
```

REST: `GET https://mcpheaven.com/api/v1/capabilities?q=<task>` · OpenAPI: https://mcpheaven.com/openapi.json · Server card: https://mcpheaven.com/.well-known/mcp.json