MCP connectors

Entergram ships a hosted MCP server. Point an AI client at it and the agent can read chats, send messages, manage tickets and update custom fields in plain language.

The first prompt is useful. The real upgrade is turning the prompt you keep repeating into a routine: a morning inbox brief, a Friday account recap, or a clean handoff from Telegram to your support desk.

Settings → Developers → MCP

Connecting a client

Go to Settings → Developers → Connectors (API & MCP) and pick your platform - Claude, ChatGPT, Perplexity, Make, n8n or Custom.
Copy the MCP server URL.
Paste it into your AI app as a connector.

“To connect, just paste this URL into {platform}, no other setup needed.”
Authorize the scopes you want to grant.

That’s it for most clients. Everything else is under Advanced settings.

Client authentication

Method	Use it for
Browser sign-in, no secret (public + PKCE)	Claude Web, Claude Desktop, local apps
Client secret in request body (`client_secret_post`)	Server-side automation
Client secret in Authorization header (`client_secret_basic`)	Server-side automation

Claude Web and local apps should usually use browser sign-in with PKCE. Server-side automation can use a client secret.

For a public client: “This client uses browser sign-in with PKCE. Leave the client secret blank in Claude.”

Scopes

Grant the minimum the agent actually needs.

Scope	Grants
`workspace.read`	Workspace details
`members.read`	Team members
`accounts.read`	Connected accounts
`contacts.read`	Contacts
`chats.read` / `chats.write`	Chats / edit chats
`chat_custom_fields.read` / `.write`	Chat custom fields / edit them
`messages.read` / `messages.write`	Messages / send messages
`custom_fields.read` / `.write`	Custom fields / edit them
`tickets.read` / `tickets.write`	Tickets / edit tickets
`offline_access`	Stay connected (refresh tokens)

messages.write lets an agent send Telegram messages as you. Grant it deliberately.

Two kinds of client

	Personal agents	Workspace clients
Scope	Your seat only	The whole workspace
Who manages	You	Owners and admins
Typical use	Claude Desktop, Codex, your own n8n	Shared team integrations
Available scopes	Seat-safe read scopes, actor-scoped chat custom fields, offline access	Full scope set

Members can create personal clients. Only owners and admins can create workspace clients.

Which Telegram accounts can MCP use?

For a personal connector, look at Settings → Accounts while signed in as that member. Those connected Telegram accounts are the connector’s account boundary. The Seats & Members table is only an administrative summary of who has which connections; it does not add a teammate’s accounts to your personal connector.

Three more controls narrow what an agent can do:

OAuth scopes decide the data and actions available. For example, accounts.read lists accounts, chats.read exposes eligible chats and messages.write permits sending.
Excluded chats stay out of MCP results and actions even though their Telegram account remains connected. Manage them from Accounts → Exclude chats. See Excluded chats.
Client type matters. A personal connector stays with the authorizing member’s connected accounts. A workspace client is administered by an owner or admin and can use workspace-level data permitted by its scopes and workspace controls.

TG Limit does not control MCP usage. A value such as 3/5 means three Telegram connections are used out of five allowed for that seat. It is not a tool-call or message rate limit. See Seats, members & roles.

To let two seats work with the same Telegram identity, connect the same Telegram account in both seats. Each connection consumes one slot in its seat and appears under that member’s Accounts section.

What an agent can actually do

Practically everything in the product, driven by a sentence:

“Send our promo to every chat whose Customer tier field is VIP.”
“Mark every unread group as read and set its Campaign field to Q3.”
“Open a high-priority ticket for every chat that hasn’t had a reply in 5 days, and assign them to me.”
“Which chats have no Stage set? Set them all to New.”

Broadcasts, bulk edits, custom columns and tickets are all reachable.

Put one useful habit on autopilot

Start with work your team already does every week. For example:

Every Friday at 4 PM, review this week’s messages in our active customer chats. Add an internal comment to each chat with the decisions, open questions and next step. Keep it under 120 words. Never send the summary to Telegram. Skip chats with no meaningful activity.

Run the prompt manually once, review the result, then schedule it in the tool where your team already works:

Where	Best for
Claude Cowork scheduled tasks	Recurring briefs, summaries and CRM housekeeping using your connected tools
ChatGPT scheduled tasks	Weekly check-ins and monitoring; available app actions depend on your plan, workspace controls and approvals
n8n or Make	Exact schedules, event-triggered flows and multi-step handoffs such as Entergram → Zendesk
Your own MCP client	Custom approval rules, logs and business logic

The quiet win is continuity: Monday’s operator can understand Friday’s conversation without rereading 200 messages.

A smooth Zendesk handoff

Use Entergram as the live Telegram context and Zendesk as the formal support record. A workflow can create or update the Zendesk ticket, place its ID in an Entergram custom field, and leave a private Entergram comment with the ticket link. When the ticket changes, sync only the status and owner fields you actually need instead of copying the whole conversation between systems.

For cross-app or unattended workflows, test with a non-sensitive chat first, grant the smallest scopes possible, and keep approval enabled for messages, ticket changes and other write actions.

Requirements

API & MCP is a Pro feature.
Personal clients are private to your seat; workspace clients need owner/admin rights.

Security notes

Client secrets are shown once. Entergram stores only a hash, after the dialog closes you can rotate the secret, never reveal it.
Redirect URIs: one per line, HTTPS required outside localhost.
PKCE is mandatory for public clients and recommended even for confidential ones.
Revoking a grant immediately removes stored refresh tokens; the client must complete OAuth again to reconnect.
Archiving a client disables it and revokes its active grants and refresh tokens.

Connect Entergram to Claude
Connect Entergram to ChatGPT
Personal agents
Workspace OAuth clients
Public API keys, for integrations that aren’t MCP clients