Productivity · Local MCP server
Telegram Slack MCP
Read and reply to your personal Telegram chats and all your Slack workspaces.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.nileshpatil6/telegram-slack-mcp- Version
- 0.5.1
- Status
- Active
- Category
- productivity
- Transport
- stdio (local process)
- Package
- npm, PyPI
- Published
- 2026-08-31
- Updated
- 2026-08-31
- Publisher
- nileshpatil6 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/nileshpatil6) · how
- Listed under
- Slack MCP servers, Telegram MCP servers
- Repository
- github.com/nileshpatil6/telegram-slack-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | telegram-slack-mcp | 0.5.1 | stdio |
| PyPI | telegram-slack-mcp | 0.2.2 | stdio |
How to connect Telegram Slack MCP
Telegram Slack MCP runs locally from a Node.js package published to the npm registry: telegram-slack-mcp version 0.5.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y telegram-slack-mcp@0.5.1. It reads these environment variables: TELEGRAM_API_ID, TELEGRAM_API_HASH (secret), TELEGRAM_ALLOW_SEND, SLACK_USER_TOKENS (secret), SLACK_ALLOW_SEND and CHAT_MCP_DATA_DIR; set them in the client's configuration for this server. Required arguments: server.
Telegram Slack MCP runs locally from a Python package published to PyPI: telegram-slack-mcp version 0.2.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx telegram-slack-mcp.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"telegram-slack-mcp": {
"command": "npx",
"args": [
"-y",
"telegram-slack-mcp@0.5.1"
],
"env": {
"TELEGRAM_API_ID": "<value>",
"TELEGRAM_API_HASH": "<secret>",
"TELEGRAM_ALLOW_SEND": "<value>",
"SLACK_USER_TOKENS": "<secret>",
"SLACK_ALLOW_SEND": "<value>",
"CHAT_MCP_DATA_DIR": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| Techtenstein LinkedinEnrich LinkedIn profiles, companies, and prospect searches. For sales, recruiting, B2B. | Local · stdio |
| Techtenstein PdfPDF text and table extraction plus metadata. Supports OCR for scanned documents. | Local · stdio |
| Teedy MCPTeedy document management: login, documents, files. | Local · stdio |
| TeleBoostTelegram CRM: manage contacts, conversations, tickets, campaigns and analytics. | Remote · HTTPLive check: sign-in required |
| Telitask MCPTeliTask MCP server - manage contacts, tasks, and calls from AI assistants. | Local · stdio |
| tell.devMessage someone through your coding agent. Their agent gets your note and explains it. | Remote · HTTPLive check: sign-in required |
| TelldoneVoice-first planning - notes, tasks, events and AI reports. 21 tools. iOS + Apple Watch. | Local · HTTP |
| TelofyAI phone receptionist for small businesses: read calls, leads and booked appointments. | Remote · HTTPLive check: ✓ handshake |