Claude · Anthropic

Claude Telegram MCP - talk to your real account

Add Entergram as a custom MCP connector in Claude or Claude Code, then talk to your real Telegram account in plain language - find the messages you missed, the clients you forgot to reply to, and the opportunities that went quiet.

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

Start free View all connectors

Claude supports the Model Context Protocol through custom connectors. Point it at Entergram's hosted MCP server and Claude reads and acts on your real personal Telegram account - full OAuth security, no bot account, no code, and your phone number and API keys never leave Entergram.

Paste-ready configuration

{
  "mcpServers": {
    "entergram": {
      "url": "https://mcp.entergram.com/mcp"
    }
  }
}

Connect Claude in 3 steps

Works in Claude (web & desktop) and Claude Code.

01
Copy your MCP URL in Entergram
Open Entergram and go to Settings → Workspace → Connectors → MCP. Copy the server URL shown there - it goes straight into Claude's custom-connector dialog in the next step.
02
Add the connector in Claude
In Claude, go to Settings → Connectors → Add custom connector and paste the Entergram MCP URL: https://mcp.entergram.com/mcp. In Claude Code, run `claude mcp add` with the same URL.
03
Authorize and start asking
Click Connect, log in with your Entergram account, and click Allow access - the connector goes live and Claude can immediately reason over your chats, contacts, tickets and analytics.

Where the Claude connector works

Claude web & desktop

The main path, and the one most people want. Settings → Connectors → Add custom connector, paste the URL, click Connect. Available on Free, Pro, Max, Team and Enterprise - Claude does not gate custom connectors behind a paid plan, so you can test this on a free account before committing.

Claude Code

Add the same hosted server to the CLI and your terminal agent can triage Telegram between builds - useful when a deploy needs a heads-up sent to a client group.

claude mcp add --transport http entergram https://mcp.entergram.com/mcp

Claude Agent SDK

Building your own agent on top of Claude? Declare Entergram in the SDK's MCP server config and your agent inherits the same 70 tools, with the same OAuth consent screen for whoever runs it.

{ "mcpServers": { "entergram": { "url": "https://mcp.entergram.com/mcp" } } }

Ask Claude things you could never ask Telegram

Once your personal account is connected, Claude can reason across every chat at once. Try prompts like:

“How many messages did I miss this week, and which ones are from clients?”
“Which conversations am I forgetting to reply to? Sort by how long they’ve been waiting.”
“Quantify my missed opportunities - leads who messaged me twice and never got an answer.”
“Summarize the feedback clients sent me in the last 7 days, grouped by positive and negative.”
“Find every chat where someone asked about price and I never responded.”
“Draft replies to my five oldest unanswered client messages and let me approve each one.”

What actually happens when you ask

Claude doesn't get raw database access - it calls structured tools, the same ones you'd call programmatically. Here is the mapping between a plain-language question and the calls behind it.

You ask

“Summarize my unread chats from today and flag anything that looks like a complaint.”

Tools called

entergram_list_accountsentergram_list_live_chatsentergram_list_messages

You get

Claude resolves your account, pulls the live view with unread counts, reads recent history per thread, then reasons over the text to classify tone. Forty unread threads collapse into a one-page briefing with complaints called out.

You ask

“Which VIP contacts haven't had a reply from us in 24 hours?”

Tools called

entergram_list_custom_columnsentergram_list_contactsentergram_list_messages

You get

It reads your CRM schema first to find the VIP column, filters contacts by that option value, then checks whether the last message in each thread was inbound or outbound. You get a list with wait times - and can follow up with “draft a check-in for each”.

You ask

“Open a high-priority billing ticket for the chat with Lena and assign it to support.”

Tools called

entergram_list_chatsentergram_create_ticketentergram_list_ticket_custom_columns

You get

Claude finds the chat, reads the ticket schema to map “high priority” and “billing” onto your real option values, and creates the ticket linked back to the conversation. It appears in your queue immediately, without you leaving the chat.

You ask

“Tag every chat from the last 7 days that mentions a refund as urgent.”

Tools called

entergram_list_messagesentergram_get_chat_custom_fieldsentergram_patch_chat_custom_fields

You get

A bulk operation that would be an afternoon of manual filtering. Claude scans message content, builds the match list, and patches the custom field on each chat - then reports exactly which chats it touched so you can spot-check.

You ask

“What was our average first-response time this week, by team member?”

Tools called

entergram_list_workspace_chatsentergram_list_messagesentergram_list_members

You get

Ad-hoc analytics you never had to pre-configure. Claude identifies the first inbound message and first outbound reply per thread, computes the delta, and aggregates by sender - then will happily compare it to last week if you ask.

You ask

“Leave an internal note on the Acme thread explaining where we left off.”

Tools called

entergram_list_chatsentergram_create_chat_comment

You get

The note is visible to your team inside Entergram and never to the customer. This is how you hand a thread from Claude back to a human - the reasoning stays attached to the conversation.

User story · Head of support

A weekly multi-account Telegram briefing, delivered to Slack

This is the difference between asking Claude for a summary once and giving the team a routine they can depend on. The account boundary is part of the instruction, so three Telegram identities become three named sections rather than one misleading pile of messages.

Monday starts with one report, not three Telegram inbox audits

A support lead manages a founder account, a sales account and a shared support account. Important decisions are scattered across all three, while the rest of the company starts its week in Slack.

The instruction

Every Monday at 08:00, list every connected Telegram account first. For each account, read the previous seven days of chats and report: unanswered customer messages, new sales opportunities, complaints, tickets opened or closed, and decisions the team promised to follow up. Keep each account in its own section. Post the final report to #telegram-weekly in Slack. Do not send Telegram replies; draft suggested replies under the relevant item.

What the team gets

The support lead opens Slack to a report that names the Telegram account, customer, last inbound message, wait time and proposed owner. Teammates can act without borrowing access to the founder's Telegram account, and the Entergram comments preserve the weekly context beside the original chats.

What Claude can do with your Telegram

-Search and summarize conversations across all connected accounts
-Surface unanswered and overdue chats automatically
-Look up contacts and their custom CRM fields
-Draft and send messages on your behalf with approval
-Quantify missed opportunities and client feedback
-Create and update support tickets from a chat

What you're actually authorizing

Connecting is a standard OAuth login: Claude sends you to Entergram's consent screen, you approve, and you can revoke anytime from Settings → Workspace → Connectors → MCP. Your Telegram phone number and session credentials never leave Entergram - Anthropic never sees them. There are two access levels, and the difference matters.

Personal agent: Any workspace member can create one. Limited to safe scopes: read access to workspace, accounts, contacts, chats, messages and tickets, plus read-and-write on the custom fields of your own chats. This is the right choice for a personal Claude account.
Workspace connector: Owner and admin only. Holds the full scope set - including sending messages, writing to any chat's custom fields, and administering groups. Shared with the team, so use it for a connector that runs on behalf of the whole workspace rather than one person.
Revocation: Immediate, from either side. Disconnect the Entergram connector inside Claude, or open Settings → Workspace → Connectors → MCP in Entergram and click Revoke. Existing tokens stop working the moment you do.

What this connector can't do

Worth knowing before you build a workflow on top of it.

It needs a Pro plan. MCP access is a Pro-plan feature in Entergram - the connector will authorize but tool calls fail on lower tiers.
It is not a background agent. Claude only acts while you're in a conversation with it; nothing runs on a schedule unless you drive it from Claude Code or the Agent SDK.
Sending is scoped per account. There is no “send to everyone” call - every message tool needs an explicit account_id, so a mistake can't fan out across all your connected accounts.
It can't read chats you can't read. The connector inherits your Telegram permissions exactly; it sees what you see, and nothing in a group you were never in.
Message history depth follows Telegram's own limits, not Entergram's - very old history in a large group may not be retrievable in one pass.
Custom-field writes need the schema to exist first. Claude can populate a pipeline column, but it can't invent one that isn't in your workspace unless you grant a workspace connector.

Claude connector troubleshooting

Claude says the URL is invalid

Re-copy the MCP server URL from Settings → Workspace → Connectors → MCP and check for a trailing space - pasting from a chat message is the usual culprit. The URL is identical for every user and every app: https://mcp.entergram.com/mcp

The Entergram login page never loads

Claude opens the consent screen in a pop-up. Allow pop-ups for claude.ai, make sure you're already signed in to Entergram in the same browser, then click Connect again.

Tools return 403 errors

Two causes. Either your Entergram account lacks owner/admin access for a workspace connector - create a personal agent instead - or your plan doesn't include MCP access, which is a Pro-plan feature.

Claude doesn't show any Entergram tools

The connector authorized but the tool list didn't refresh. Toggle the connector off and on in Settings → Connectors, or start a new conversation - Claude reads the tool list at conversation start.

It's acting on the wrong Telegram account

Ask Claude to call entergram_list_accounts and name the account explicitly in your prompt. Nothing is global across accounts, so an unspecified account_id means it picked one for you.

The connection drops after a while

OAuth tokens expire. Click Connect again in Claude and re-approve access - you won't have to re-copy the URL.

Claude + Telegram FAQ

Does this work with Claude Code?

Yes. Claude Code supports MCP servers - add the Entergram MCP URL with `claude mcp add` and authorize via OAuth. The same connector works in the Claude desktop and web apps.

Is this a Telegram bot?

No. Entergram connects your real personal Telegram account through a hosted MCP server, so Claude sees the same chats you do - not a separate bot account.

Can it really tell me which messages I missed?

Yes. Because Claude can read across all your connected chats at once, it can count unread and unanswered messages, rank them by how long they’ve waited, and flag the ones from clients or leads.

Is it secure?

Yes. The connection uses OAuth 2.0 with scoped permissions. You authorize exactly what Claude can access, your credentials never touch Claude, and you can revoke access at any time.

Practical guides