
Claude Ops Telegram Server
io.github.auroracapitalPublished by GitHub account auroracapitalv0.2.1Updated Oct 24, 2026
Telegram personal-account MCP (MTProto user-auth). Read DMs, send messages, search across chats.
The publisher's own server: Claude Platform Docs
Overview
Local MCP server that signs in as your personal Telegram account to list chats, read messages, search conversations and send replies.
- What you can do
- List recent conversations (DMs, groups, channels) with unread counts
- Fetch messages from a specific chat
- Search messages full-text across all conversations
- Send a message to a chat or user
- When to use it
- Useful when you want an assistant to triage your own Telegram inbox — checking unread DMs, pulling message history, searching across chats and replying — which a BotFather bot cannot do because bots cannot read private user-to-user chats.
- Requirements
- Runs locally over stdio with Node.js and npm dependencies installed. Needs a personal Telegram application from my.telegram.org, plus the environment variables TELEGRAM_API_ID, TELEGRAM_API_HASH, TELEGRAM_PHONE and TELEGRAM_SESSION. The session is created once by running the auth command, which prompts for an SMS code and optional 2FA password. Network access to Telegram's API is required.
Installation
In SourceWeft
- Open Claude Ops Telegram Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
claude-ops Telegram MCP Server
User-auth Telegram MCP server for the /ops:ops-inbox skill. Authenticates as a personal Telegram account via MTProto (gram.js), not as a BotFather bot, so it can read and reply to real DM conversations.
Why user-auth, not bot?
Bots cannot read messages sent in private chats between two users — only messages sent directly to the bot. For the /ops:ops-inbox use case (managing the owner's personal inbox), we must authenticate as the user's account.
Setup
1. Get API credentials
Go to https://my.telegram.org/apps and create a personal application (not a bot). You'll get:
api_id(integer)api_hash(32-char string)
2. Install dependencies
3. First-run authentication (interactive)
The script will prompt for an SMS code and (if enabled) your 2FA password. On success it prints a TELEGRAM_SESSION string — save this securely (it's your session token).
4. Configure MCP server in Claude Code
Add to ~/.claude/settings.json:
Export the env vars from a secret manager (Doppler, 1Password, direnv — never commit):
Restart Claude Code to load the MCP server.
Tools
Security
- Never commit
TELEGRAM_SESSION— it's equivalent to your password - Session tokens are device-bound; if stolen, log out via Telegram app → Settings → Devices
- All credentials come from environment variables; nothing is hardcoded in this repo
- The server runs over stdio (local only); no network exposure beyond Telegram's official API
Troubleshooting
"Session is no longer valid": Re-run node index.js --auth to generate a fresh session.
"TELEGRAM_API_ID is required": The env vars aren't being passed to the MCP server. Check your ~/.claude/settings.json env block.
Rate limiting: Telegram enforces per-account limits. If you hit one, wait 15-30 minutes before retrying.
Source: claude-ops/telegram-server/README.md at commit fea4d55
Tools
0Version history
1- v0.2.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Claude integrations
Claude Platform Docs
com.claude.platformOfficial publisher
Remote MCP server that lets an assistant search and read the Claude Platform documentation and API reference.

Insta Edits for Claude
Published by GitHub account faisalkhanzemi
Bridges Claude Code to Instagram Edits for Mac, keeping the full 274-tool video editor in sync so an assistant can edit Reels.

Claude Checkpoint Mcp
Published by GitHub account daniel-munoz
Local MCP server that saves a Claude Code session's working state to a JSON file in the project and turns it back into a compact resume brief.

Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen
Published by GitHub account spk-c
Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen's local MCP server; no sign-in required; STDIO; 18 tools.

AVE for Claude Code — Local Video Editing
Published by GitHub account lemberalla
Local AVE timeline editing and exports for Claude Code only. Existing AVE connection required.