Telegram MCP for managing dialogs, messages, drafts, read statuses, and more.
Most team communication work still happens through a UI a human drives. Telegram MCP server moves it into the conversation instead. Telegram MCP for managing dialogs, messages, drafts, read statuses, and more.
The server is a bridge between the Telegram API and the AI assistants and is based on the Model Context Protocol.
The Model Context Protocol (MCP) is a system that lets AI apps, like Claude Desktop or Cursor, connect to external tools and data sources. It gives a clear and safe way for AI assistants to work with local services and APIs while keeping the user in control.
The server publishes 9 tools. What each one is for:
Version — URLCapabilities — The Capabilities tool exposed by this serverOrganization — The Organization tool exposed by this serverCommunication — The Communication tool exposed by this serverHomebrew — The Homebrew tool exposed by this serverMacOS — The MacOS tool exposed by this serverLinux — The Linux tool exposed by this serverWindows — The Windows tool exposed by this serverAuthorization — Before you can use the server, you need to connect to the Telegram APIThe server ships on npm as You, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Configuration is passed through the environment: TG_APP_ID, TG_API_HASH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Telegram's toolset — Version, Capabilities, Organization and 6 more — is a fair guide to whether it matches your workflow. It is maintained by chaindead; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Version | URL |
| Capabilities | The Capabilities tool exposed by this server. |
| Organization | The Organization tool exposed by this server. |
| Communication | The Communication tool exposed by this server. |
| Homebrew | The Homebrew tool exposed by this server. |
| MacOS | The MacOS tool exposed by this server. |
| Linux | The Linux tool exposed by this server. |
| Windows | The Windows tool exposed by this server. |
| Authorization | Before you can use the server, you need to connect to the Telegram API. |
for Cursor:
```json
{
"mcpServers": {
"telegram-mcp": {
"command": "telegram-mcp",
"env": {
"TG_APP_ID": "<your-app-id>",
"TG_API_HASH": "<your-api-hash>"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| TG_APP_ID | Configuration value read at startup. | Optional |
| TG_API_HASH | Configuration value read at startup. | Optional |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.