# claude-ops-telegram-server [Health: Active]

**Category:** 💬 Communication  
**Repository:** https://github.com/Lifecycle-Innovations-Limited/claude-ops  
**GitHub Stars:** 427  
**npm Downloads (last month):** 131  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/claude-ops-telegram-server

## Description
Telegram personal-account MCP (MTProto user-auth). Read DMs, send messages, search across chats.

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "claude-ops-telegram-server": {
    "command": "npx",
    "args": ["-y","claude-ops-telegram-server"]
  }
}
```

## Documentation

## What claude-ops-telegram-server does

The claude-ops-telegram-server MCP server exposes a Telegram personal account for agent-driven messaging tasks. Its documented scope is focused on three operations: reading direct messages, sending messages, and searching across chats.

This makes it suitable for workflows where an agent needs to review Telegram conversations, locate relevant messages, or send a reply using the connected personal account. It is distinct from a bot-only integration in the supplied description: authentication is identified as MTProto user authentication.

The repository is named `claude-ops` and contains a much broader Claude Code business-operations plugin, including skills and integrations for areas such as infrastructure, CI/CD, inboxes, pull requests, and revenue reporting. The Telegram MCP listing should be evaluated specifically for its Telegram account capabilities rather than for every feature described in the wider repository README.

## How it works

The claude-ops-telegram-server MCP server uses Telegram’s MTProto user-authentication model to access the account. Once the account connection is available to the MCP client, an agent can use the documented Telegram functions to inspect direct messages, issue outbound messages, and search chat history.

The supplied material does not specify the MCP transport, authentication prompts, session-file behavior, chat filters, pagination rules, or whether message actions cover group chats, channels, or media. Those details should be confirmed in the repository before building a workflow that depends on them.

## Tools and capabilities

Documented capabilities include:

- Read Telegram direct messages.
- Send Telegram messages.
- Search across Telegram chats.
- Authenticate as a Telegram personal account through MTProto.

These capabilities support conversational triage, message lookup, and outbound replies. The available material does not name individual MCP tool identifiers or provide schemas for their arguments and return values.

## Limitations and notes

The claude-ops-telegram-server MCP server requires access to a Telegram personal account through MTProto user authentication. The excerpt does not state which credentials are required, how the initial login is completed, or how an authenticated session is stored and renewed.

No standalone installation command for the Telegram server is provided in the supplied material. The README does document installation commands for the broader `claude-ops` Claude Code plugin and its installer, but those commands should not be assumed to install this MCP server directly.

The material also does not confirm compatibility with Claude Desktop, Cursor, Windsurf, or Cline. It references Claude Code for the broader project, but that is not sufficient evidence for compatibility with the clients listed here.

## Getting started with this claude-ops-telegram-server MCP server
Always refer to the official documentation for the most accurate and up-to-date information.

_Full upstream README: https://allmcps.com/mcp/claude-ops-telegram-server/readme_