Claude · Anthropic
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.
https://mcp.entergram.com/mcp 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.
{
"mcpServers": {
"entergram": {
"url": "https://mcp.entergram.com/mcp"
}
}
}Once your personal account is connected, Claude can reason across every chat at once. Try prompts like:
Works in Claude (web & desktop) and Claude Code.
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.
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.
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.
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.
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/mcpBuilding 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" } } }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.
Authorizing the connector gives Claude 70 tools across 9 groups. This is the full surface — nothing is hidden behind a higher tier, though what any given connection can actually call depends on the access level you grant it below.
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_meentergram_list_accountsentergram_get_workspaceentergram_get_memberentergram_list_membersFinding conversations. The workspace views carry CRM state (tickets, comments, custom fields); the live views carry current Telegram transport state and unread counts.
entergram_list_chatsentergram_get_chatentergram_list_live_chatsentergram_get_live_chatentergram_list_workspace_chatsentergram_get_workspace_chatentergram_update_workspace_chatentergram_get_chat_managementReading and writing message history, including edits, forwards and reactions. Sending is scoped per account, so nothing is global across your connected accounts.
entergram_list_messagesentergram_get_messageentergram_send_messageentergram_send_media_messageentergram_edit_messageentergram_delete_messageentergram_forward_messagesentergram_get_message_reactionsentergram_set_message_reactionsWho 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_contactsentergram_get_contactentergram_list_contact_shared_groupsFull 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_ticketsentergram_get_ticketentergram_create_ticketentergram_update_ticketentergram_delete_ticketentergram_list_chat_ticketsentergram_list_ticket_commentsentergram_create_ticket_commententergram_update_ticket_commententergram_delete_ticket_commentYour 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_columnsentergram_get_custom_columnentergram_create_custom_columnentergram_update_custom_columnentergram_delete_custom_columnentergram_list_custom_column_optionsentergram_create_custom_column_optionentergram_update_custom_column_optionentergram_delete_custom_column_optionentergram_get_chat_custom_fieldsentergram_patch_chat_custom_fieldsThe 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_columnsentergram_get_ticket_custom_columnentergram_create_ticket_custom_columnentergram_update_ticket_custom_columnentergram_delete_ticket_custom_columnentergram_list_ticket_custom_column_optionsentergram_create_ticket_custom_column_optionentergram_update_ticket_custom_column_optionentergram_delete_ticket_custom_column_optionComments 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_commentsentergram_create_chat_commententergram_update_chat_commententergram_delete_chat_commentCreating and administering Telegram groups and channels — membership, permissions, privacy and info — plus a raw command escape hatch for the rest.
entergram_list_groupsentergram_get_groupentergram_list_group_membersentergram_create_group_chatentergram_create_channelentergram_invite_chat_membersentergram_remove_chat_memberentergram_update_chat_infoentergram_update_chat_permissionsentergram_update_chat_privacyentergram_run_chat_commandConnecting 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 agentWorkspace connectorRevocationWorth knowing before you build a workflow on top of it.
Other connectors
We respect your right to privacy. Choose which cookies to allow — your choice applies across our site. Cookie Policy
Required for the site to work, including remembering your privacy choices. Always on.
Help us understand which pages are popular and how visitors use the site.
