# Entergram — Telegram MCP for Multiple Accounts [Health: Active]

**Category:** 💬 Communication  
**Repository:** https://github.com/EntergramCRM/Telegram-MCP  
**GitHub Stars:** 7  
**npm Downloads (last month):** 36  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/entergram-telegram-mcp-for-multiple-accounts

## Description
Hosted Telegram MCP for multiple real accounts in one workspace. Search chats, send messages, and manage CRM contacts, custom fields, and tickets through an OAuth-protected Streamable HTTP endpoint. The public repository provides the optional local stdio bridge.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "entergram-telegram-mcp-for-multiple-accounts": {
    "command": "npx",
    "args": ["-y","@entergram/mcp"]
  }
}
```

## Documentation

## What Entergram — Telegram MCP for Multiple Accounts does

Entergram — Telegram MCP for Multiple Accounts provides MCP access to real Telegram accounts connected to an Entergram workspace. Multiple accounts can be used through one MCP connection, and operations can either search the workspace as a whole or target a specific account. This makes the service suitable for teams that separate sales, support, or other communication work across several Telegram identities.

The service extends beyond message access. Agents can search chats and contacts, send Telegram messages, and work with CRM data associated with conversations. Supported CRM areas include contacts, custom fields, tickets, pipeline stages, and tags, subject to the permissions granted to the OAuth client.

## How it works

The primary connection is the hosted Streamable HTTP gateway at `https://mcp.entergram.com/mcp`. MCP clients connect to that endpoint and complete the host’s OAuth login flow. Modern clients such as Claude Code and Codex can use this route without installing the npm package.

The repository also provides the `@entergram/mcp` helper CLI. Its local stdio mode is intended for hosts that can launch a command but cannot connect to a remote MCP endpoint with OAuth. In that mode, the CLI handles login, token storage, OAuth client registration options, and the bridge between the local MCP process and the hosted gateway.

## Setup and configuration

For the remote setup, add the gateway URL to the MCP client and then start that client’s login flow. Claude Code can add the server with its HTTP transport, while Codex can place the URL in its TOML MCP configuration. The CLI can print JSON or TOML configuration for hosts that need generated settings.

Install the local bridge globally with `npm install -g @entergram/mcp`, or run it through `npx`. Authenticate with `entergram-mcp login`, then start the bridge with `entergram-mcp serve`. `entergram-mcp whoami` checks the current identity, and `entergram-mcp logout` removes the local session. Session files are stored under `~/.entergram-mcp/` by default.

The production gateway is built in, but `ENTERGRAM_MCP_GATEWAY_URL` or the `--gateway-url` option can point the CLI at another gateway. Authentication modes include automatic selection, a preconfigured client, dynamic client registration, and client metadata documents. Requested scopes must be allowed by the selected OAuth client; broader workspace operations may require a workspace client.

## Tools and capabilities

Entergram — Telegram MCP for Multiple Accounts supports:

- Searching chats across every connected account or one selected account
- Reading and sending Telegram messages
- Searching and managing CRM contacts
- Reading and writing supported custom fields
- Working with tickets, pipeline stages, and tags
- Using OAuth scopes to control workspace, account, chat, message, contact, field, and ticket access

## Limitations and notes

The public repository contains the helper CLI and local bridge, not the hosted gateway implementation. The remote HTTP connection is preferred when the MCP host supports it. The service uses genuine Telegram accounts rather than bot tokens, so access depends on the accounts connected to the Entergram workspace.

OAuth scope configuration affects which operations are available. An `invalid_scope` error means the client does not allow a requested scope. If the local bridge cannot authenticate, log in again using the same environment, authentication mode, and client settings used by the host.

_Full upstream README: https://allmcps.com/mcp/entergram-telegram-mcp-for-multiple-accounts/readme_