MCP · Personal Telegram Connection

Telegram MCP server for multiple personal accounts

Connect multiple personal Telegram accounts to Claude, ChatGPT, n8n, Make or another MCP client. Entergram keeps each account identity and permission scope attached while you search chats, prepare replies and move approved information into another system.

MCP Server URL https://mcp.entergram.com/mcp

Get Started Free View Setup Guide

Works with

Claude· ChatGPT· Grok· n8n· Make.com· Cursor· Zed· Windsurf

Telegram accounts

Your AI assistants

@alex_support Telegram · connected
@denis_sales Telegram · connected
@team_europe Telegram · connected
@team_apac Telegram · connected

Entergram One MCP Live

Claude MCP connected
ChatGPT MCP connected
Gemini MCP connected
Grok MCP connected

Ask your AI to

Summarise every chat still waiting for a reply across all four accounts.

The hard part

One Telegram MCP connection for multiple personal accounts

Most Telegram AI integrations stop at one bot or one account. Entergram is built for teams that operate several real Telegram identities: sales, support, regions, communities or client workspaces. Every tool call keeps the source account, chat and permission scope attached.

Connect multiple personal Telegram accounts to one workspace.
Ask Claude, ChatGPT, n8n, Make or another MCP client to work across selected accounts.
Keep account identity intact so replies, CRM updates and tickets go to the right place.

Hosted or self-hosted

A hosted MCP server, or your own Telethon script

Almost every Telegram MCP server you can find is a repository you run yourself, usually a Python process on top of Telethon or a thin wrapper around the Bot API. They are open source and Entergram is not. If you have one account and you want the code in front of you, a repo you can read end to end is the right answer, and this page will not pretend otherwise.

What those servers ask of you is the same every time. Register an application at my.telegram.org to get an api_id and an api_hash, run a login script once to produce a session string, keep that string where your process can read it, and keep the process alive. Then repeat it for the next account, because a session belongs to exactly one account.

Entergram trades that control for reach. One hosted endpoint covers every Telegram account connected to your seat. You add an account by scanning a QR code from Telegram Settings, then Devices, then Link Desktop Device, or by entering a phone number and the login code Telegram sends to your other signed-in devices. There is no api_id, no api_hash and no session string for you to generate, store or rotate.

There is no bot token either, because these are real personal accounts rather than the Bot API. That difference is not cosmetic. A Telegram bot can only message someone who has already started a chat with it, so it cannot send the first message in an outbound conversation. A personal account can.

Connecting the server is a copy and paste rather than a deploy. Settings → Workspace → Connectors → MCP holds one URL, the same one for every client. You paste it, your client sends you to the Entergram consent screen, and you approve scopes there. There is no OAuth client for you to register.

What each option asks of you

	Self-hosted Telethon server	Entergram MCP
Accounts per server	One. A session string belongs to a single account, so a second account means a second deployment.	Every Telegram account connected to your seat, with the source account kept on each call.
Credentials you hold	api_id, api_hash and a session string, per account, stored and rotated by you.	None. QR or phone login for the account, OAuth for the client.
Bot token	Required by the Bot API wrappers, which cannot message a person first.	None. Real personal accounts, so outbound first contact works.
Hosting	Your machine, container or VPS, kept running and patched.	Nothing to host. One hosted endpoint at https://mcp.entergram.com/mcp
Network identity	Whatever IP the box has, shared by every account running on it.	A dedicated proxy per account, assigned by Entergram and stable over time.
Pacing and rate limits	Yours to implement.	Telegram-aware pacing on sends, and live Telegram search is rate limited per account.
Access control	Anyone who can read the session file has the account.	OAuth with 13 permission scopes, approved and revoked per client.

Run your own server if you have one account, want the code in your own repository and are comfortable owning the session file. Use this one if you run several accounts and would rather not keep a session string per account on a machine you have to keep alive.

MCP · Personal Telegram Connection

Choose the tool for the workflow

Use a conversational client for research and drafting, or an automation platform for scheduled and repeatable work.

Claude

Anthropic

Settings → Connectors

Ask Claude across multiple Telegram accounts, or schedule a weekly Cowork briefing that summarizes each account and sends the result to Slack.

ChatGPT

OpenAI

Custom MCP connector

Research Telegram conversations in a long-running chat, monitor changes hourly where Tasks support connected apps, and prepare Zendesk or CRM updates with approval.

n8n

n8n.io

MCP node

Poll every 10 minutes, keep a cursor per Telegram account, bridge replies with Slack, and create deduplicated Zendesk or Linear work.

Make.com

Celonis

MCP module

Turn the same multi-account prompt into a visual weekly scenario: Slack report, Entergram comments, HubSpot or Salesforce updates, and Linear issues.

Cursor & IDEs

Cursor, Zed, Windsurf

MCP settings

Join Telegram evidence with repository context, turn repeated reports into one Linear issue, and write the engineering status back to each source chat.

Notion MCP

Notion + Entergram

Two-server MCP workflow

Give one compatible client two explicit tool boundaries: Entergram MCP works with authorized personal Telegram accounts, while Notion MCP works only inside the separately authorized Notion environment.

Stripe MCP

Stripe + Entergram

Two-server MCP workflow

Give one compatible client two explicit tool boundaries: Entergram MCP works with authorized personal Telegram accounts, while Stripe MCP works only inside the separately authorized Stripe environment.

Slack MCP

Slack + Entergram

Two-server MCP workflow

Give one compatible client two explicit tool boundaries: Entergram MCP works with authorized personal Telegram accounts, while Slack MCP works only inside the separately authorized Slack environment.

Grok

SpaceXAI

Custom MCP connector

Connect Grok to the Telegram accounts you actually use, not a separate bot. Entergram gives Grok one hosted MCP connection for searching chats, finding missed leads, summarizing conversations and preparing replies across several personal accounts.

Gemini

Google

Gemini CLI · MCP

Use Entergram as a Telegram MCP server for Google Gemini and the Gemini CLI - give Gemini secure, OAuth-scoped access to your real Telegram chats so it can surface missed messages, waiting clients and cold leads.

Perplexity

Perplexity AI

Connectors

Attach Entergram as an MCP connector in Perplexity and bring your real Telegram account into your research workflow - surface missed messages, waiting clients and cold leads without leaving Perplexity.

Goose

Block

config.yaml

Add Entergram as an MCP extension in Goose, Block’s open-source AI agent, and let it work your real Telegram account - surface missed messages, chase leads that went cold, and act on chats autonomously.

Raycast

Manage MCP Servers

Add Entergram as an MCP server in Raycast and reach your real Telegram account from a keystroke - check missed messages and waiting clients without opening Telegram.

Cline

Cline (VS Code)

MCP settings

Register Entergram as an MCP server in Cline, the VS Code AI agent, and reach your real Telegram account from your editor - catch missed messages and clients waiting on you without breaking flow.

opencode

SST

opencode.json

Add Entergram as an MCP server in opencode, SST’s open-source terminal AI agent, and let it work your real Telegram account - surface missed messages, chase leads that went cold, and act on chats from the command line.

Custom Apps

Any MCP client

OAuth + MCP URL

Any application that implements the MCP standard can connect to Entergram using the hosted endpoint.

Telegram MCP for CRM

Telegram MCP workflows for leading CRM platforms

Explore focused guides for the CRM platforms we have documented in depth, plus a reusable compatibility pattern for the wider CRM landscape. Entergram MCP reads authorized personal Telegram accounts while Claude, n8n, Make or your own agent calls the CRM separately.

Salesforce HubSpot Microsoft Dynamics 365 Zoho CRM Pipedrivemonday CRMFreshsalesSAP Sales CloudOracle SalesNetSuite CRMOdoo CRMCreatioSugarCRMCopperCloseInsightlyKeapamoCRMAttioHighLevel

Telegram MCP for ticketing

Telegram MCP workflows for leading ticketing platforms

Explore focused help-desk guides and the reusable operating pattern behind the broader directory. These are workflow explanations, not claims that Entergram replaces each vendor API or ships a native direct connector.

Zendesk Intercom Freshdesk Jira Service Management ServiceNowHelp ScoutGorgiasFrontZoho DeskSalesforce Service CloudHubSpot Service HubKustomerGladlyDixaRe:amazeLiveAgentKayakoHappyFoxHiverGroove

What is Telegram MCP?

What Telegram MCP does

Model Context Protocol gives compatible AI tools a standard way to request data or actions from another service. Entergram exposes authorized Telegram and CRM functions through a hosted MCP endpoint. Unlike a bot-only connector, it can work across multiple personal Telegram accounts while preserving the account ID, chat context and permission scope for every request.

Connect through OAuth and review the requested permission scopes.
Use one hosted endpoint with a compatible MCP client.
Revoke a connection when it is no longer needed.
Connect multiple personal Telegram accounts in one workspace.

Practical AI Prompts for Telegram Workflow

Wondering what you can actually ask your AI tools to do with Telegram MCP? Here are some real-world prompt ideas across message management, organization, and conversation support, designed to help you reclaim your inbox and let your attention focus elsewhere.

Message Management

Surface all unread messages flagged as important since yesterday.
Summarize the latest activity across all Telegram chats this week.
Draft quick, context-aware replies for new messages waiting in your customer service channel.
Give me a high-level overview of unread, non-urgent chats so nothing slips through.

Chat Organization

Analyze ongoing Telegram conversations and propose folders or labels.
Suggest a way to separate work, personal, and group discussions based on recent message content.
Find and list conversations related to current projects or key topics for easy reference.

Proactive Communication

Monitor select group chats for updates related to conference logistics or urgent tasks.
Review all chat transcripts and identify any questions that haven’t been answered yet.
Generate a professional reply to the most recent message from a client, ready to send.

These types of prompts help streamline your Telegram experience, letting your AI handle the busywork while you focus on what matters most.

Capabilities

Available actions

The actions available to a client depend on the permission scopes you approve.

Read and search your Telegram chats
Search Telegram live for people, groups and channels outside your workspace
View and manage contacts and custom fields
Send messages through your personal account
Access workspace and chat analytics
Create and manage support tickets
Run broadcasts to contact segments
Read and update custom field values
View team member activity and assignments

Tool reference

The 71 tools this MCP server exposes

One endpoint carries all of them, in the 9 groups below. The names are literal identifiers, so you can put one in a prompt when you want a specific call rather than letting the model pick. Which of them a client can actually reach depends on the OAuth scopes you approve, listed further down.

Accounts & workspace

5 tools

Identity and scope discovery. Every message call needs an account_id from list_accounts first - an AI client that skips this step will address the wrong Telegram account.

entergram_get_me
entergram_list_accounts
entergram_get_workspace
entergram_get_member
entergram_list_members

Chats & discovery

9 tools

Finding conversations. The workspace views carry CRM state (tickets, comments, custom fields); the live views carry current Telegram transport state and unread counts, and live search reaches people, groups and channels outside the workspace.

entergram_search_telegram
entergram_list_chats
entergram_get_chat
entergram_list_live_chats
entergram_get_live_chat
entergram_list_workspace_chats
entergram_get_workspace_chat
entergram_update_workspace_chat
entergram_get_chat_management

Messages

9 tools

Reading and writing message history, including edits, forwards and reactions. Sending is scoped per account, so nothing is global across your connected accounts.

entergram_list_messages
entergram_get_message
entergram_send_message
entergram_send_media_message
entergram_edit_message
entergram_delete_message
entergram_forward_messages
entergram_get_message_reactions
entergram_set_message_reactions

Contacts

3 tools

Who you are talking to, and where else you overlap with them. Shared-groups lookup is what makes questions like “which of my leads are in the same community?” answerable.

entergram_list_contacts
entergram_get_contact
entergram_list_contact_shared_groups

Tickets

10 tools

Full support-desk control: open, assign, prioritise, comment and close. Tickets link back to the chat they came from, so an AI client can move from conversation to queue in one step.

entergram_list_tickets
entergram_get_ticket
entergram_create_ticket
entergram_update_ticket
entergram_delete_ticket
entergram_list_chat_tickets
entergram_list_ticket_comments
entergram_create_ticket_comment
entergram_update_ticket_comment
entergram_delete_ticket_comment

CRM custom fields

11 tools

Your pipeline schema. Read the columns before writing values - checkboxes take booleans, multiselects take arrays of option values, dates take ISO 8601 strings.

entergram_list_custom_columns
entergram_get_custom_column
entergram_create_custom_column
entergram_update_custom_column
entergram_delete_custom_column
entergram_list_custom_column_options
entergram_create_custom_column_option
entergram_update_custom_column_option
entergram_delete_custom_column_option
entergram_get_chat_custom_fields
entergram_patch_chat_custom_fields

Ticket custom fields

9 tools

The same schema control for the ticket side - categories, severities, SLA tiers and anything else your desk tracks beyond status and priority.

entergram_list_ticket_custom_columns
entergram_get_ticket_custom_column
entergram_create_ticket_custom_column
entergram_update_ticket_custom_column
entergram_delete_ticket_custom_column
entergram_list_ticket_custom_column_options
entergram_create_ticket_custom_column_option
entergram_update_ticket_custom_column_option
entergram_delete_ticket_custom_column_option

Internal notes

4 tools

Comments on a chat that your customer never sees. Useful for letting an AI client leave its reasoning behind for a human teammate to pick up.

entergram_list_chat_comments
entergram_create_chat_comment
entergram_update_chat_comment
entergram_delete_chat_comment

Groups & channels

11 tools

Creating and administering Telegram groups and channels - membership, permissions, privacy and info - plus a raw command escape hatch for the rest.

entergram_list_groups
entergram_get_group
entergram_list_group_members
entergram_create_group_chat
entergram_create_channel
entergram_invite_chat_members
entergram_remove_chat_member
entergram_update_chat_info
entergram_update_chat_permissions
entergram_update_chat_privacy
entergram_run_chat_command

OAuth permissions

Permission scopes

Review the requested scopes and grant the minimum access required for the workflow.

workspace.read Workspace details Read workspace name and configuration

members.read Team members View workspace member list

accounts.read Connected accounts Read connected Telegram accounts

contacts.read Contacts Access contact profiles and data

chats.read Chats Read conversation lists and metadata

chats.write Edit chats Update chat state and perform actions

messages.read Messages Read message history in authorized chats

messages.write Send messages Send messages through connected accounts

tickets.read Tickets Read support ticket data

tickets.write Edit tickets Create and update tickets

custom_fields.read Custom fields Read custom field values

custom_fields.write Edit custom fields Update custom field values

offline_access Stay connected Maintain connection without re-authenticating

Connect in 3 Steps

Menus differ by client, but the connection follows the same three steps.

01
Copy your MCP URL in Entergram
Go to Settings → Workspace → Connectors → MCP and copy your MCP server URL: https://mcp.entergram.com/mcp
02
Add the MCP URL in your app
In your AI tool or automation platform, add a custom connector or MCP node. Paste the Entergram MCP URL: https://mcp.entergram.com/mcp
03
Connect and authorize
Click Connect, review the permissions on Entergram's authorization page, and click Allow access. Your Telegram workspace is now connected.

Why multiple accounts is the hard part

Most Telegram MCP servers connect one account. That is a reasonable default for a personal assistant setup, and it is why almost every open-source implementation stops there. It stops being reasonable the moment a business asks an AI tool to do something useful across an operation that runs on more than one account.

The difficulty is not opening more connections. It is keeping them distinguishable. When an agent reads a conversation, it has to know which of your accounts that conversation belongs to, because the answer changes what a correct reply looks like. A message to a counterparty from the desk's trading account reads differently from the same words sent by the support account, and an agent that cannot tell them apart will eventually send the wrong thing from the wrong identity.

Entergram keeps the account ID, chat context and permission scope attached to every request. An agent working across a seat can ask a question that spans accounts, such as which conversations have gone quiet this week, and still get an answer that says which account each one belongs to. When it prepares a reply, the account that owns the conversation is the account that sends it.

The permission scope matters as much as the identity. The MCP covers the accounts on your seat and nothing beyond it, the OAuth flow shows the scopes being requested before you approve them, and a connection can be revoked when it is no longer needed. The workspace privacy controls still apply underneath, so an agent cannot read around a restriction that a human on the same seat would hit.

This is also what makes the scheduled use cases work. A weekly briefing that summarizes each connected account, a triage pass that opens tickets from conversations that need one, a newsletter that reads the chat, detects the language and localizes before sending: each of these is ordinary once the agent can tell your accounts apart, and impossible when it cannot.

Telegram CRM Platform

Related Entergram tools

Use the CRM, API or setup documentation when the workflow needs more than an MCP connection.

Telegram Sales CRM Multi-account inbox, broadcasts, custom columns, lead management, and more. Telegram support software Shared inbox, SLA tickets, a Kanban board and an AI agent that triages and drafts replies. Telegram Analytics Response time, reply rate, a 7×24 heatmap and per-agent SLA across every connected account. Telegram CRM API REST API and webhooks for sync jobs, internal tools and programmatic Telegram automation. Telegram Team Inbox Seats, roles and a shared workspace where each agent's own chats stay private.

FAQ

Telegram MCP - FAQ

Can Telegram MCP connect multiple personal Telegram accounts?

Yes. Entergram is designed for multiple personal Telegram accounts in one workspace. The MCP client receives only the accounts and scopes you authorize, and each request keeps its source account identity so messages are not mixed together.

Is there an official Telegram MCP server?

Telegram does not publish one. The open-source Telegram MCP servers you will find are community projects, and almost all of them connect a single account, either through a bot token or through a user session you host and maintain yourself. Entergram is a hosted MCP server that connects every personal Telegram account on your seat through one OAuth connection, with the account identity and permission scope preserved on every request.

Is my data safe?

The connection uses OAuth with PKCE and scoped permissions. Review what a client requests, avoid granting unnecessary write access and revoke connections you no longer use.

Do I need a paid plan?

The MCP connector is available on Entergram plans that include API access. Check the pricing page for current plan details.

Can I connect multiple AI tools at the same time?

Yes. Authorize each tool separately so its permissions can be reviewed and revoked independently.

What happens if I revoke access?

The client can no longer make new requests through that connection. Data previously copied or stored by the client is governed by that client’s own retention policy.