Log inSubmit server
Entergram — Telegram MCP for Multiple Accounts logo

Entergram — Telegram MCP for Multiple Accounts

Connect multiple real Telegram accounts to MCP clients for chat search, messaging, and CRM contact, field, and ticket management.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Entergram — Telegram MCP for Multiple Accounts

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "entergram-telegram-mcp-for-multiple-accounts": {
      "command": "npx",
      "args": [
        "-y",
        "@entergram/mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @entergram/mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 14d ago.

Overview

Entergram — Telegram MCP for Multiple Accounts MCP server connects real Telegram accounts in a shared workspace to MCP-compatible AI clients. It exposes a hosted Streamable HTTP endpoint protected by OAuth, with an optional local stdio bridge for hosts that cannot connect to remote MCP servers directly. Agents can search chats, send messages, find contacts, and manage CRM contacts, custom fields, pipeline data, and tickets across all accounts or within one account. Reach for it when a team needs AI access to several Telegram accounts rather than a single bot integration.

Use cases

  • Search conversations across multiple Telegram accounts
  • Send follow-up messages from a selected account
  • Manage CRM contacts and custom fields from chat context
  • Review and update support tickets across accounts

Key features

  • Multi-account Telegram access
  • Workspace-wide or account-scoped chat search
  • Telegram message reading and sending
  • CRM contacts, custom fields, tickets, pipeline stages, and tags
  • OAuth-protected Streamable HTTP gateway
  • Optional local stdio bridge

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

7/7 checks healthy over the last 47d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 1d ago via OSV.dev · @entergram/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars7Stargazers on the source repository.
npm downloads36Package downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Entergram — Telegram MCP for Multiple Accounts works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Entergram — Telegram MCP for Multiple Accounts

Entergram — Telegram MCP for Multiple Accounts is an MCP server that connects real Telegram accounts in a shared workspace to MCP-compatible AI clients. Its main tools let agents search chats, send messages, find contacts, and manage CRM contacts, custom fields, pipeline data, and tickets across multiple accounts or within one selected account.

Install the optional local bridge with `npm install -g @entergram/mcp`, or run it with `npx -y @entergram/mcp serve`. For clients that support remote MCP over HTTP, add `https://mcp.entergram.com/mcp` directly and complete the client’s OAuth login flow; the npm package is not required for that route.

Use the hosted gateway or the local stdio bridge, depending on whether your Cursor setup can connect to a remote OAuth-protected Streamable HTTP server.

Connect the real Telegram accounts to the same Entergram workspace, then authorize the MCP connection through the hosted gateway. The server can expose those accounts through one MCP connection, allowing searches across the workspace or operations scoped to a particular account.

Update the selected OAuth client so it allows the requested scopes, then run `entergram-mcp login` again. Workspace operations such as member access, message writing, and custom-field management may require a workspace client with those scopes enabled.

Related MCP servers

All in Communication All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewEntergram — Telegram MCP for Multiple Accounts AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/entergram-telegram-mcp-for-multiple-accounts?style=directory)](https://allmcps.com/mcp/entergram-telegram-mcp-for-multiple-accounts)
HTML Embed
<a href="https://allmcps.com/mcp/entergram-telegram-mcp-for-multiple-accounts"><img src="https://allmcps.com/api/badge/entergram-telegram-mcp-for-multiple-accounts?style=directory" alt="Entergram — Telegram MCP for Multiple Accounts on AllMCPs" /></a>