Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Telegram Slack MCP

by nileshpatil6version 0.5.1i★ 0iRuns on your computerRepository ↗
Registry nameio.github.nileshpatil6/telegram-slack-mcp

How to install

What it does

Read and reply to your personal Telegram chats and all your Slack workspaces.

  • Connects Runs on your computer
  • Account or key Needs TELEGRAM_API_HASH, SLACK_USER_TOKENS
  • Category Chat & email

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity0/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness7/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score7/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Telegram Slack MCP. Follow https://mcp.popnx.com/i/nileshpatil6-telegram-slack-mcp.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

You need a Telegram Slack MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Telegram Slack MCP for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "telegram-slack": { "command": "npx", "args": [ "-y", "telegram-slack-mcp" ], "env": { "TELEGRAM_API_HASH": "your-value", "SLACK_USER_TOKENS": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For TELEGRAM_API_HASH, SLACK_USER_TOKENS, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Telegram Slack MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Telegram Slack MCP key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    How to get a key is in the maker’s README below

  3. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  4. Paste these settings and save the file

    {
      "mcpServers": {
        "telegram-slack": {
          "command": "npx",
          "args": [
            "-y",
            "telegram-slack-mcp"
          ],
          "env": {
            "TELEGRAM_API_HASH": "your-value",
            "SLACK_USER_TOKENS": "your-value"
          }
        }
      }
    }

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Quit Claude and open it again

  6. Try it

    Use Telegram Slack MCP and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Telegram Slack MCP or shows a Telegram Slack MCP tool in the answer, you are connected

4 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • TELEGRAM_API_ID api_id 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_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

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Telegram Slack MCP yet

Telegram Slack MCP runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Telegram Slack MCP

  • You need a Telegram Slack MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • You need a Telegram Slack MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)
  • You need a Telegram Slack MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)
  • You need a Telegram Slack MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)

B · Others in Chat & email that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

You need a Telegram Slack MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Telegram Slack MCP for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user telegram-slack --env TELEGRAM_API_HASH=your-value --env SLACK_USER_TOKENS=your-value -- npx -y telegram-slack-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For TELEGRAM_API_HASH, SLACK_USER_TOKENS, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Telegram Slack MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Telegram Slack MCP key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    How to get a key is in the maker’s README below

  3. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  4. Paste this command and press Enter

    claude mcp add --scope user telegram-slack --env TELEGRAM_API_HASH=your-value --env SLACK_USER_TOKENS=your-value -- npx -y telegram-slack-mcp

    Replace “your-value” with your key before pressing Enter

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Type /mcp in Claude Code

    You should see Telegram Slack MCP listed as connected

  6. Try it

    Use Telegram Slack MCP and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Telegram Slack MCP or shows a Telegram Slack MCP tool in the answer, you are connected

4 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • TELEGRAM_API_ID api_id 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_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

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

You need a Telegram Slack MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Telegram Slack MCP for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "telegram-slack": { "command": "npx", "args": [ "-y", "telegram-slack-mcp" ], "env": { "TELEGRAM_API_HASH": "your-value", "SLACK_USER_TOKENS": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For TELEGRAM_API_HASH, SLACK_USER_TOKENS, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Telegram Slack MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Telegram Slack MCP key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    How to get a key is in the maker’s README below

  3. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  4. Fill in your key

    In the Telegram Slack MCP settings, TELEGRAM_API_HASH, SLACK_USER_TOKENS is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Open the AI chat in Cursor in Agent mode

  6. Try it

    Use Telegram Slack MCP and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Telegram Slack MCP or shows a Telegram Slack MCP tool in the answer, you are connected

4 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • TELEGRAM_API_ID api_id 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_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

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

You need a Telegram Slack MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Telegram Slack MCP for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "telegram-slack": { "type": "stdio", "command": "npx", "args": [ "-y", "telegram-slack-mcp" ], "env": { "TELEGRAM_API_HASH": "your-value", "SLACK_USER_TOKENS": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For TELEGRAM_API_HASH, SLACK_USER_TOKENS, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Telegram Slack MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Telegram Slack MCP key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    How to get a key is in the maker’s README below

  3. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  4. Fill in your key

    In the Telegram Slack MCP settings, TELEGRAM_API_HASH, SLACK_USER_TOKENS is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Open the AI chat in VS Code in Agent mode

  6. Try it

    Use Telegram Slack MCP and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Telegram Slack MCP or shows a Telegram Slack MCP tool in the answer, you are connected

4 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • TELEGRAM_API_ID api_id 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_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

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Telegram Slack MCP💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user telegram-slack --env TELEGRAM_API_HASH=your-value --env SLACK_USER_TOKENS=your-value -- npx -y telegram-slack-mcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "telegram-slack": {
      "command": "npx",
      "args": [
        "-y",
        "telegram-slack-mcp"
      ],
      "env": {
        "TELEGRAM_API_HASH": "your-value",
        "SLACK_USER_TOKENS": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "telegram-slack": {
      "command": "npx",
      "args": [
        "-y",
        "telegram-slack-mcp"
      ],
      "env": {
        "TELEGRAM_API_HASH": "your-value",
        "SLACK_USER_TOKENS": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "telegram-slack": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "telegram-slack-mcp"
      ],
      "env": {
        "TELEGRAM_API_HASH": "your-value",
        "SLACK_USER_TOKENS": "your-value"
      }
    }
  }
}

Values you fill in

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

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
84/wk
Connection
Runs on your computer
Latest versioni
0.5.1
Published to registryi
Aug 31, 2026
Code last changedi
Aug 31, 2026
Maker
nileshpatil6
Packages
npm: telegram-slack-mcp
pypi: telegram-slack-mcp
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account nileshpatil6, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 3 months ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for telegram-slack-mcp@0.5.1

Checks only this package version, not every dependency · checked Nov 16, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/nileshpatil6-telegram-slack-mcp.svg)](https://mcp.popnx.com/en/servers/nileshpatil6-telegram-slack-mcp)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Chat & emaili

  • More stars than 0% of the other 2018 servers in this category
  • Published to the registry more recently than 23% of the other 2018 servers in this category
  • Basic checks equal to or better than 99% of the other 2018 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Telegram Slack MCP safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: TELEGRAM_API_HASH, SLACK_USER_TOKENS

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 3 months ago, and the latest version (0.5.1) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Python (uv) on your computer.

What can I use instead?

In the same category: emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

emailmd

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

by anypostWidely used↓ 5.4K/wk★ 1.4KUpdated 5 days ago

Computer or cloud✓ service owner · emailmd.dev

Infobip MCP

Infobip MCP server for omnichannel communication and messaging. SMS, RCS, WhatsApp, Viber and more.

by infobipEarly★ 36Updated 13 months ago

Runs in the cloud✓ service owner · infobip.com

kernelCAD

CAD in ChatGPT and Claude: editable parts, STEP/STL/drawings, in-chat 3D, automatic checks.

by w1neEarly★ 35Updated 23 days ago

Runs in the cloud✓ service owner · kernelcad.com
Compared with similar ones
This one
Telegram Slack MCP
emailmdKite Discord Bot Buildere2a — email for AI agentsInfobip MCPkernelCAD
Runs whereInstalls on your computerCloud or install on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyYesNoNoNoNoNo
Add with + in ClaudeNoNoNoNoYesNo
Basic checks3/35/54/44/44/44/4
LicenseMITMITAGPL-3.0Apache-2.0MITMIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

telegram-slack-mcp

Give Claude your actual chats.

Two MCP servers that connect Claude to your *personal* Telegram and Slack accounts — your real DMs, groups, and channels, not a bot inbox.

claude mcp add telegram -- npx -y telegram-slack-mcp telegram

claude mcp add slack -- npx -y telegram-slack-mcp slack

Then just talk:

*"what's unread on telegram from actual people?"*

*"read my last 30 messages with Priya and draft a reply"*

*"search all my slack workspaces for the deploy postmortem"*

*"what's in the screenshot Priya sent me?"*


Why this exists

Most Telegram integrations use the Bot API, which only sees messages sent *to a bot you created*. It cannot read your existing conversations. telegram-slack-mcp uses MTProto, the same protocol the official app uses, authenticating as you — so Claude sees the chats you actually have.

For Slack, the usual connector is scoped to one workspace. telegram-slack-mcp takes one user token per workspace and treats them as a single surface, so "search everywhere" means everywhere.

Install

Pick whichever runtime you already have. Both ship the same tools.

Node
claude mcp add telegram -- npx -y telegram-slack-mcp telegram

claude mcp add slack -- npx -y telegram-slack-mcp slack

Python
claude mcp add telegram -- uvx telegram-slack-mcp telegram

claude mcp add slack -- uvx telegram-slack-mcp slack

Claude Code plugin
/plugin marketplace add nileshpatil6/telegram-slack-mcp

/plugin install telegram@telegram-slack-mcp /plugin install slack@telegram-slack-mcp

Other MCP clients (Claude Desktop, Cursor, …)

{

"mcpServers": { "telegram": { "command": "npx", "args": ["-y", "telegram-slack-mcp", "telegram"], "env": { "TELEGRAM_API_ID": "1234567", "TELEGRAM_API_HASH": "your_hash" } }, "slack": { "command": "npx", "args": ["-y", "telegram-slack-mcp", "slack"], "env": { "SLACK_USER_TOKENS": "xoxp-one,xoxp-two" } } } }

Setup

Telegram — 2 minutes
  1. Go to https://my.telegram.org → API development tools → create an app.
  2. Copy the api_id and api_hash, and set them:
   claude mcp add telegram      -e TELEGRAM_API_ID=1234567      -e TELEGRAM_API_HASH=your_hash      -- npx -y telegram-slack-mcp telegram
  1. Link your account. Either ask Claude — "log into telegram" — or do it yourself in a terminal, which needs no MCP client at all:
   TELEGRAM_API_ID=1234567 TELEGRAM_API_HASH=your_hash npx -y telegram-slack-mcp login
   # PowerShell

$env:TELEGRAM_API_ID="1234567"; $env:TELEGRAM_API_HASH="your_hash" npx -y telegram-slack-mcp login

Either way you scan a QR and the session is saved to ~/.chat-mcp.

Through Claude:

It calls login, which returns a link to a page showing a QR code (and the code as text, if your client renders it). Scan it from Telegram on your phone — Settings → Devices → Link Desktop Device — then it calls login_status to confirm. No phone number, no SMS code, no 2FA password typed anywhere. On the same machine you can click "open in Telegram Desktop" instead of scanning.

The session is saved to ~/.chat-mcp and persists; you do this once.

Can't scan? Use the phone-number flow

login_start(phone) sends you a code, login_complete(code, password?) finishes. Note that with this path your phone number and login code pass through the conversation as tool arguments, so they land in the model's context. The QR flow keeps them out of it.

Slack — 5 minutes
  1. Go to https://api.slack.com/apps → Create New App → From a manifest.
  2. Paste slack-app-manifest.yaml — it prefills every scope.
  3. Install to Workspace, then copy the User OAuth Token (xoxp-…, not xoxb-).
  4. Repeat step 3 for each workspace you want. Same app, one token each.
  5. Ask Claude: "connect my slack" — the login tool prompts for the tokens, verifies each one against Slack, and saves them to ~/.chat-mcp. Nothing to put in your config.

Prefer environment variables? That still works:

   claude mcp add slack -e SLACK_USER_TOKENS=xoxp-aaa,xoxp-bbb -- npx -y telegram-slack-mcp slack

Slack has no local OAuth flow, which is why you create the app yourself: Slack's OAuth requires a client secret and an HTTPS redirect URL, so a package distributed over npm cannot complete it without either shipping a secret publicly or running a callback server. This project has no server, so it asks for the token instead.

Tools

Telegram
toolwhat it does
login()scan a QR to link your account — no phone number or code
login_status()check whether the QR has been scanned yet
login_start(phone)fallback: send yourself a login code
login_complete(code, password?)finish login, save the session
whoami()which account is connected
list_chats(limit, query, unread_only, kind)recent chats; kind filters to dm, group, channel, bot…
read_chat(chat, limit, before_id)messages of one chat — chat takes @username, id, or part of a name
search_messages(query, chat?, limit)full-text search, one chat or all
unread_summary(limit, per_chat, kind)catch-up view; kind: "dm" skips the channel noise
read_media(chat, message_id, max_kb)view a photo or file — returns the actual image, not just its type
send_message(chat, text, reply_to?)reply as you — off unless `TELEGRAM_ALLOW_SEND=1`
Slack
toolwhat it does
login()prompts for your xoxp- tokens, verifies them, saves them
whoami()every connected workspace and who you are in each
list_channels(limit, query, workspace, types)channels across workspaces
list_dms(limit, workspace)1:1 and group DMs
read_channel(channel, limit, workspace, before_ts)one channel or DM
read_thread(channel, thread_ts, limit, workspace)replies inside a thread
search_messages(query, limit, workspace)supports in:#chan, from:@user
unread_summary(limit, per_chat, workspace)what's unread everywhere
read_file(file_id, workspace, max_kb)view a file shared in Slack — returns the actual image
send_message(channel, text, workspace, thread_ts?)post as you — off unless `SLACK_ALLOW_SEND=1`

Every Slack tool takes an optional `workspace` (any substring of the name). Leave it blank to act across all of them; it's only required when a channel name exists in more than one, and the error tells you which.

Configuration

variabledefaultmeaning
TELEGRAM_API_ID—from my.telegram.org
TELEGRAM_API_HASH—from my.telegram.org
TELEGRAM_ALLOW_SEND01 lets Claude send Telegram messages as you
SLACK_USER_TOKENS—one xoxp- token per workspace, comma separated
SLACK_ALLOW_SEND01 lets Claude post to Slack as you
CHAT_MCP_DATA_DIR~/.chat-mcpwhere the Telegram session is stored

Sending is off by default in both servers. Reading is the safe default; you opt into writing deliberately.

Privacy

Nothing is sent to any server belonging to this project. There is no such server.

telegram-slack-mcp runs entirely on your machine. The only network traffic it makes is directly to Telegram's and Slack's own APIs, using your own credentials. There is no telemetry, no analytics, no crash reporting, no license check, no "phone home" — grep the source, there is no endpoint to find.

The data path is exactly this:

your machine  <-->  Telegram / Slack APIs      (your credentials, your account)

your machine <--> Claude (only what you ask Claude to read)

Your credentials never reach Claude. Your session file and xoxp- tokens stay in ~/.chat-mcp and in your environment; the servers use them locally to make API calls and pass back only the messages themselves.

What *does* reach Claude is the chat content you ask about — because that is the point of the tool. If you ask Claude to read a conversation, that conversation goes into your Claude conversation and is handled under Anthropic's privacy policy, exactly like text you paste in yourself. Nothing else is read, and nothing is read in the background: the servers only act when Claude calls a tool.

The author of this project cannot see any of it.

Security

Read this part.

  • These act as you, not as a bot. Anything sent shows as sent by your account, and people in those chats cannot tell the difference.
  • The stored session is a full credential. ~/.chat-mcp/telegram.session and your xoxp- tokens are equivalent to being logged in as you. Anyone who copies them has your account. They never leave your machine, and nothing here phones home.
  • Everything Claude reads enters the model's context. Don't point this at accounts holding data you would not send to a model.
  • Telegram calls this a userbot. Automating a personal account is restricted by Telegram's ToS. Light personal read-and-reply use is common and low risk; bulk automation gets accounts banned. Your call, your account.
  • Revoke any time: Telegram → Settings → Devices, or delete the token in Slack's app settings. Deleting ~/.chat-mcp drops the local session.

Troubleshooting

"Telegram not logged in yet" — run the login flow: ask Claude to log in with your phone number. It persists after that; if it keeps reappearing, check that CHAT_MCP_DATA_DIR is writable.

"Missing Telegram credentials" — TELEGRAM_API_ID / TELEGRAM_API_HASH aren't reaching the server. With claude mcp add, pass them with -e.

Slack returns nothing at all — you're almost certainly authorized against an empty or wrong workspace. Run whoami to see which workspaces are actually connected.

`"#general" exists in several workspaces` — pass workspace to disambiguate; the error lists your options.

Slack search returns `not_allowed_token_type` — the token is a bot token (xoxb-). You need the User OAuth token (xoxp-).

Development

git clone https://github.com/nileshpatil6/telegram-slack-mcp

cd telegram-slack-mcp npm install && npm run build node dist/cli.js telegram # run the server on stdio

cd python && python -m build # build the Python distribution

License

MIT