# io.github.nileshpatil6/telegram-slack-mcp (io.github.nileshpatil6/telegram-slack-mcp@0.5.1) > Source: > Published: 2026-08-31 16:56:54+00:00 [← Index](/leaderboard) # io.github.nileshpatil6/telegram-slack-mcp Read and reply to your personal Telegram chats and all your Slack workspaces. The current version, v0.5.1, was published to the official MCP registry on 2026-08-31. It is distributed as telegram-slack-mcp on npm and as telegram-slack-mcp on PyPI, filed under Chat & Messaging by this index, and declares 6 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; [the index's current counts](/stats) put this record in context. ## Using io.github.nileshpatil6/telegram-slack-mcp in Claude, Cursor, Gemini CLI, Cline, or Zed? MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and **HOLDs the call** when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use **Install this server** for that). Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less ``` uv tool install mcpindex-gate && mcpindex-config-wire ``` [method](/methodology) Verdict not yet evaluated for this tool. The semantic screen takes adversarial cases first; coverage rolls out as the corpus expands (15/150 labels to graduation). The deterministic conformance probe is built but has not yet run on the public corpus, so a recorded verdict here is REVIEW or UNVERIFIED, never a clearing ALLOW. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: [the eval, four-state verdict, honest limits](/methodology). Own this server? [Screen its description →](/screen) ## That verdict was true at screening time (snapshot 2026-08-31). Contracts can change after screening, with no version bump. The gate pins io.github.nileshpatil6/telegram-slack-mcp’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday. [See your first HOLD in 2 minutes →](/guides/install-the-gate-first-hold) Related: [how to trust an MCP server](/guides/how-to-trust-an-mcp-server) · [screen before install](/guides/screen-mcp-server-before-install) · [silent contract drift](/guides/mcp-silent-contract-drift) `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 [methodology](/methodology) [sendifaicom.sendifai/platform](/server/com-sendifai-platform) 335 MCP tools, 75 playbooks. AI-native CRM, email/SMS, events, OAuth. [WhatsApp Web MCP Serverio.github.mario-andreschak/mcp-whatsapp-web](/server/io-github-mario-andreschak-mcp-whatsapp-web) MCP server for WhatsApp via whatsapp-web.js: send/receive messages, media, chats, groups, contacts [MCP Registry Monitorio.github.nirholas/mcp-notify](/server/io-github-nirholas-mcp-notify) Monitor MCP registry for new servers - Discord Slack notifications alerts