Log inSubmit server
Telegram Slack MCP logo

Telegram Slack MCP

Reads and searches personal Telegram chats and multiple Slack workspaces, with sending disabled until explicitly enabled.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Telegram Slack MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "telegram-slack-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "telegram-slack-mcp"
      ],
      "env": {
        "TELEGRAM_API_ID": "YOUR_VALUE_HERE",
        "TELEGRAM_API_HASH": "YOUR_VALUE_HERE",
        "TELEGRAM_ALLOW_SEND": "YOUR_VALUE_HERE",
        "SLACK_USER_TOKENS": "YOUR_VALUE_HERE",
        "SLACK_ALLOW_SEND": "YOUR_VALUE_HERE",
        "CHAT_MCP_DATA_DIR": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y telegram-slack-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 10d ago.

Overview

The telegram-slack-mcp MCP server connects Claude to personal Telegram accounts through MTProto and to Slack workspaces through user OAuth tokens. It exposes tools for listing, reading, searching, summarizing, and optionally sending messages, plus viewing shared media and files. Telegram uses a saved local session, while Slack accepts one user token per workspace. Reach for it when an agent needs access to existing conversations rather than messages sent to a bot.

Use cases

  • Search Telegram conversations for a specific message
  • Summarize unread messages across Slack workspaces
  • Read a Telegram photo or Slack-shared image
  • Draft replies from recent chat history
  • Post replies after enabling sending

Key features

  • Personal Telegram access through MTProto
  • Multi-workspace Slack access with user tokens
  • Message, channel, chat, and thread search
  • Unread summaries across conversations
  • Telegram media and Slack file retrieval
  • Opt-in message sending

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

4/4 checks healthy over the last 39d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12d ago via OSV.dev · telegram-slack-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads257Package downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Telegram Slack MCP works

What telegram-slack-mcp does

The telegram-slack-mcp MCP server gives an MCP client access to existing conversations in a personal Telegram account and one or more Slack workspaces. It can list chats, channels, and direct messages; read messages and threads; search message text; and produce unread summaries.

Telegram access uses MTProto, the protocol used by the official Telegram application. This allows the server to work with the account's existing direct messages, groups, and channels instead of limiting access to messages addressed to a bot. Slack access uses user OAuth tokens, with one token supplied for each workspace.

Both services can expose shared content for inspection. Telegram's read_media returns a requested photo or file, while Slack's read_file can return an image shared in Slack. Sending is available through send_message for each service, but it is disabled by default.

How it works

The telegram-slack-mcp MCP server runs locally and communicates directly with Telegram or Slack using the credentials supplied for the selected service. It does not use a project-hosted intermediary. Messages are returned to the MCP client only when the client invokes a tool to request them.

For Telegram, the first login creates a session under ~/.chat-mcp. The QR flow lets the user link the account from Telegram's device settings, and the session persists for later use. A phone-number login flow is also available, but its phone number and login code become tool arguments in the conversation.

Slack tools accept an optional workspace filter. Leaving it blank allows operations across connected workspaces; a workspace selector is useful when channel names overlap. Search supports qualifiers such as in:#channel and from:@user.

Setup and configuration

Install either the Node package with npx or the Python package with uvx. The repository documents configurations for Claude, Claude Desktop, Cursor, and Claude Code. The command takes a service argument such as telegram or slack.

Telegram requires TELEGRAM_API_ID and TELEGRAM_API_HASH from Telegram's API development tools. After starting the server, use the login tool or run the documented login command to create the local session.

Slack requires a Slack app, the permissions from the supplied app manifest, and a user OAuth token beginning with xoxp- for each workspace. Tokens can be entered through the login tool or provided as a comma-separated SLACK_USER_TOKENS value.

CHAT_MCP_DATA_DIR changes the location used for the Telegram session. TELEGRAM_ALLOW_SEND=1 enables Telegram sending, and SLACK_ALLOW_SEND=1 enables Slack posting. Without those settings, the write tools remain off.

Tools and capabilities

Telegram includes login and account-identification tools, chat listing with unread and chat-type filters, message reading, full-text search, unread summaries, media retrieval, and optional replies. Chat references can use a username, numeric ID, or part of a name.

Slack includes login and account-identification tools, channel and DM listing, channel or DM reading, thread reading, message search, unread summaries, file retrieval, and optional posts. Most Slack operations accept a workspace argument.

Limitations and notes

The server requires personal account credentials rather than a Telegram bot token. Slack setup is manual because the project does not provide an OAuth callback server; users create the app and obtain user tokens themselves.

Reading is the default behavior. Enabling either sending variable allows the corresponding service to post as the connected user, so it should be treated as an explicit configuration change.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Telegram Slack MCP

telegram-slack-mcp is an MCP server that connects Claude to personal Telegram accounts and Slack workspaces. Its main tools list, read, search, and summarize chats, channels, direct messages, and threads, with tools for viewing shared media or files. Telegram uses MTProto, while Slack uses user OAuth tokens.

Install it with either `npx -y telegram-slack-mcp telegram` or `uvx telegram-slack-mcp telegram` for Telegram, and use `slack` instead of `telegram` for Slack.

Set `TELEGRAM_API_ID` and `TELEGRAM_API_HASH`, then run the Telegram server and complete login with the QR flow or the phone-number fallback. The QR flow saves a session under `~/.chat-mcp` after linking the account from Telegram's device settings.

Provide one Slack user OAuth token beginning with `xoxp-` for each workspace in `SLACK_USER_TOKENS`, separated by commas, or enter them through the Slack login tool. Create and install the Slack app separately in each workspace before supplying its token.

Yes, but sending is disabled by default. Set `TELEGRAM_ALLOW_SEND=1` to enable Telegram replies or `SLACK_ALLOW_SEND=1` to enable Slack posts. The corresponding `send_message` tool then posts as the connected user, including optional Telegram replies or Slack thread posts.

Related MCP servers

All in Communication All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewTelegram Slack MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/telegram-slack-mcp?style=directory)](https://allmcps.com/mcp/telegram-slack-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/telegram-slack-mcp"><img src="https://allmcps.com/api/badge/telegram-slack-mcp?style=directory" alt="Telegram Slack MCP on AllMCPs" /></a>