emailmd
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Read and reply to your personal Telegram chats and all your Slack workspaces.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 7/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 7/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
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.
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.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: 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
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
SettingsDeveloperEdit Config
{
"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
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
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-mcpDescriptions 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
A · Use an app that can connect Telegram Slack MCP
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)
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.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: 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
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
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user telegram-slack --env TELEGRAM_API_HASH=your-value --env SLACK_USER_TOKENS=your-value -- npx -y telegram-slack-mcpReplace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
You should see Telegram Slack MCP listed as connected
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
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-mcpDescriptions 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)
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.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: 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
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
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
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
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-mcpDescriptions 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)
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.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: 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
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
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
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
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-mcpDescriptions 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.
JSON settings are under “For developers” below
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-mcpClaude 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"
}
}
}
}TELEGRAM_API_ID envTELEGRAM_API_HASH secret required envTELEGRAM_ALLOW_SEND envSLACK_USER_TOKENS secret required envSLACK_ALLOW_SEND envCHAT_MCP_DATA_DIR envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
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
Runs on your computer; the tool list appears in your AI app after you install it.
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
The registry name was verified with the GitHub account nileshpatil6, which owns the repo
Code last changed 3 months ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for telegram-slack-mcp@0.5.1
Checks only this package version, not every dependency · checked Nov 16, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/nileshpatil6-telegram-slack-mcp)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.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
You need to fill in: TELEGRAM_API_HASH, SLACK_USER_TOKENS
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).
The GitHub repo last changed 3 months ago, and the latest version (0.5.1) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Python (uv) on your computer.
In the same category: emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD
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
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Build and fix Discord bots from a chat. Kite hosts them 24/7, with no code to deploy.
Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.
Infobip MCP server for omnichannel communication and messaging. SMS, RCS, WhatsApp, Viber and more.
CAD in ChatGPT and Claude: editable parts, STEP/STL/drawings, in-chat 3D, automatic checks.
| This one Telegram Slack MCP | emailmd | Kite Discord Bot Builder | e2a — email for AI agents | Infobip MCP | kernelCAD | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Cloud or install on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | Yes | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | Yes | No |
| Basic checks | 3/3 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 |
| License | MIT | MIT | AGPL-3.0 | Apache-2.0 | MIT | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
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.
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?"*
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.
Pick whichever runtime you already have. Both ship the same tools.
claude mcp add telegram -- npx -y telegram-slack-mcp telegram
claude mcp add slack -- npx -y telegram-slack-mcp slack
claude mcp add telegram -- uvx telegram-slack-mcp telegram
claude mcp add slack -- uvx telegram-slack-mcp slack
/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" } } } }
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
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-app-manifest.yaml — it prefills every scope.xoxp-…, not xoxb-).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.
| tool | what 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` |
| tool | what 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.
| variable | default | meaning |
|---|---|---|
TELEGRAM_API_ID | — | from my.telegram.org |
TELEGRAM_API_HASH | — | from my.telegram.org |
TELEGRAM_ALLOW_SEND | 0 | 1 lets Claude send Telegram messages as you |
SLACK_USER_TOKENS | — | one xoxp- token per workspace, comma separated |
SLACK_ALLOW_SEND | 0 | 1 lets Claude post to Slack as you |
CHAT_MCP_DATA_DIR | ~/.chat-mcp | where the Telegram session is stored |
Sending is off by default in both servers. Reading is the safe default; you opt into writing deliberately.
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.
Read this part.
~/.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.~/.chat-mcp drops the local session."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-).
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
MIT