Telegram-slack-mcp Server

Telegram-slack-mcp is an MCP integration. Read and reply to your personal Telegram chats and all your Slack workspaces.

Packages and local setup

The published npm package is telegram-slack-mcp, version 0.5.1. Its declared MCP transport is stdio.

The package declares TELEGRAM_API_ID: api_id from https://my.telegram.org (Telegram server only); TELEGRAM_API_HASH: api_hash from https://my.telegram.org (Telegram server only); TELEGRAM_ALLOW_SEND: Set to 1 to allow sending Telegram messages as you. Off by default.; SLACK_USER_TOKENS: One Slack user token (xoxp-) per workspace, comma separated (Slack server only); SLACK_ALLOW_SEND: Set to 1 to allow posting to Slack as you. Off by default.; CHAT_MCP_DATA_DIR: Where the Telegram session is stored. Defaults to ~/.chat-mcp.

This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

The published pypi package is telegram-slack-mcp, version 0.2.2. Its declared MCP transport is stdio.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.5.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related communication MCP servers for tools that cover the same kind of work.