Claude Ops Telegram Server runs on your own machine — the client starts it, so there is no endpoint to ping. 27 installs a week from npm. Last commit 17 Sep 2026.
Telegram personal-account MCP (MTProto user-auth). Read DMs, send messages, search across chats.
We read the source, 23 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
этот файл ставится пользователю, но в репозитории его нет
const result = spawnSync(bin, args, { encoding: 'utf8', env });
return subprocess.run(
shell=True,
const from = path.join(srcDir, "bin", name);
"description": "Optional default webhook URL (https://discord.com/api/webhooks/…) for /ops:comms discord send. Shared with the ops-fires notification sink (which also reads discord_webhook_url). If already configured via /ops:setup or stored in keychain/Doppler, leave bla…
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add claude-ops-telegram-server -- npx -y claude-ops-telegram-server
{
"mcpServers": {
"claude-ops-telegram-server": {
"args": [
"-y",
"claude-ops-telegram-server"
],
"command": "npx"
}
}
}
[mcp_servers.claude-ops-telegram-server]
command = "npx"
args = ["-y", "claude-ops-telegram-server"]
{
"mcpServers": {
"claude-ops-telegram-server": {
"args": [
"-y",
"claude-ops-telegram-server"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"claude-ops-telegram-server": {
"args": [
"-y",
"claude-ops-telegram-server"
],
"command": "npx"
}
}
}
This one needs environment variables set before it will start:
TELEGRAM_API_ID (Numeric API ID from https://my.telegram.org/apps (create a personal app, not a bot).), TELEGRAM_API_HASH (API hash from the same my.telegram.org/apps page.), TELEGRAM_PHONE (Your Telegram phone number in E.164 format (e.g. +14155551234).), TELEGRAM_SESSION (gram.js StringSession token. Generate once via: node index.js --auth (prompts for SMS code + optional 2FA). Store in your secret manager — never commit.).
The author declared them in the registry entry; get the values from the project itself.
Telegram MCP server: read, send, and search messages and manage chats via your account.
MCP server for Telegram Archive — search messages, browse chats, and access history
Unofficial Telegram MCP server — read, search, reply and react in your own Telegram account.
Telegram for AI agents: messages, chats, media, and contacts in bot and user-account modes.
AI-native Microsoft Teams integration — read chats, send messages, search people
Unified inbox MCP for WhatsApp, Telegram, Email, voice — read/send messages, search, AI agents.
Read, search, and send personal WhatsApp messages from any MCP client, behind a send-confirm gate.
Connect Claude to Microsoft Teams — read/send messages, list channels, search chats.
Answers built from our own checks of this server.