Data · Local MCP server
Claude Ops Telegram Server
Telegram personal-account MCP (MTProto user-auth). Read DMs, send messages, search across chats.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.auroracapital/claude-ops-telegram-server- Version
- 0.2.1
- Status
- Active
- Category
- data
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-04-19
- Updated
- 2026-04-19
- Publisher
- auroracapital (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/auroracapital) · how
- Listed under
- Telegram MCP servers
- Repository
- github.com/Lifecycle-Innovations-Limited/claude-ops (folder claude-ops/telegram-server)
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | claude-ops-telegram-server | 0.2.1 | stdio |
How to connect Claude Ops Telegram Server
Claude Ops Telegram Server runs locally from a Node.js package published to the npm registry: claude-ops-telegram-server version 0.2.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 claude-ops-telegram-server@0.2.1. It reads these environment variables: TELEGRAM_API_ID (required, secret), TELEGRAM_API_HASH (required, secret), TELEGRAM_PHONE (required, secret) and TELEGRAM_SESSION (required, secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"claude-ops-telegram-server": {
"command": "npx",
"args": [
"-y",
"claude-ops-telegram-server@0.2.1"
],
"env": {
"TELEGRAM_API_ID": "<secret>",
"TELEGRAM_API_HASH": "<secret>",
"TELEGRAM_PHONE": "<secret>",
"TELEGRAM_SESSION": "<secret>"
}
}
}
}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 from auroracapital (GitHub)
| Server | Runs |
|---|---|
| Upres CliUpRes MCP: list models, credits, submit 4K image and video upscale jobs. | Local · stdio |
More data servers
| Server | Runs |
|---|---|
| ClarigridRead-only electricity, gas, and weather data with structured provenance and units. | Remote · HTTPLive check: sign-in required |
| ClariLayerIndividual-analyst context layer: recall, remember, and reconcile your data and engineering context. | Remote · HTTPLive check: sign-in required |
| Clarity by Health AICondition-aware ingredient and product checks for agents, with evidence tiers and citations. | Remote · HTTPLive check: ✓ handshake |
| classifier.dev docsClassifier.dev documentation as tools: list, read and search the reference, benchmark and guides. | Remote · HTTPLive check: ✓ handshake |
| Claudeers MCP ServerSearch the Claudeers registry of Claude tools, ranked by maintenance and community signals. | Remote · HTTPLive check: ✓ handshake |
| ClaudeInk - Knowledge VaultSave, search, and compile valuable knowledge from your Claude conversations. | Local · stdio |
| Clauselane Contract Register ToolsClauselane: the monthly US search demand across the tools this product ships, read from monthly... | Local · stdio |
| ClavioReal-time data resolver for agents. 200 countries, 169k cities, FX, weather, Africa/MENA. | Local · stdio |