Connect Entergram to Claude in Two Minutes with the New MCP Connector

Telegram operators don't need another dashboard — they need their CRM to show up in the tools they're already typing into. Claude is one of those tools. With the new Entergram MCP connector, you can ask Claude things like 'which chats went silent this week?' or 'draft a follow-up to every Dormant contact tagged price-blocker' without ever leaving the conversation. Your workspace data flows in over OAuth, scoped to whatever you allow.

MCP — the Model Context Protocol — is the open standard Anthropic shipped for letting LLMs talk to real systems. Until now, getting your CRM into Claude meant building a custom integration. With our remote MCP endpoint, it's a paste-the-URL-and-go affair.

There are two tabs involved: claude.ai and Entergram. The full walkthrough is in the Claude MCP Connector help doc; here's the condensed version.

1. In Claude: go to claude.ai/customize/connectors and click Add a new connector. Name it Entergram. In the Remote MCP URL field, paste https://mcp.entergram.com/mcp. Expand Advanced Settings and leave it open.

2. In Entergram: Settings → Developer → Create new OAuth client → click the Preset: Claude Web Connector button. Confirm the scopes you want Claude to see, hit Create, then Copy client ID.

3. Back in Claude: paste the Client ID under Advanced Settings. Leave Client Secret empty — the preset uses public-client OAuth (PKCE), no secret required. Click Add a connector, then Connect, then Allow on Entergram's consent screen. That's it.

Because Claude Web is a browser-based client, distributing a static secret would defeat the purpose. The Preset issues a public OAuth client with PKCE, which proves possession without a shared secret. The first time someone runs the auth flow, the consent screen makes the scope explicit. From then on, every tool call is signed with the user's session — revoke the OAuth client and the connection breaks immediately.

If you've previously issued API keys from the Developer tab, the model is the same: keys are workspace-scoped, hashed, and revocable. The MCP connector is just OAuth instead of a long-lived bearer token.

Once the connector is live, the obvious moves are the boring ones — 'show me the 10 most recent chats', 'export contacts tagged VIP'. Where it gets useful is the second-tier asks that previously meant a CSV export and a spreadsheet:

• Group all Dormant contacts by reason tag and tell me which cohort is biggest right now.
• Draft three different reactivation messages targeted at contacts where Last Reply > 60 days, in the same tone as my last broadcast.
• Summarize what changed in the chat with @example since yesterday and surface anything that looks like a renewal signal.
• List every workspace member who hasn't logged in this week and what tickets are sitting in their queue.

Claude calls the MCP endpoint, the endpoint runs a real query against your workspace, and the answer is grounded in your actual data — not a hallucination.

Three things worth doing before you connect a workspace to Claude:

1. Pick the smallest scope set you can live with. If you only want read access for analytics, uncheck the write scopes when creating the OAuth client. You can always edit and reconnect later.
2. Use a workspace OAuth client per Claude account, not a shared one. That way, revoking a single user's access doesn't break the team's connector.
3. Review the OAuth client's last-used timestamp periodically. Same audit hygiene as API keys — if it's been idle for a quarter, revoke it.

Revocation is one click on either side: Connectors → Entergram → Disconnect in Claude, or Settings → Developer → Revoke in Entergram. Both take effect immediately.

The MCP endpoint exposes the same surfaces our REST API exposes today — workspaces, chats, contacts, custom columns, broadcasts, analytics. As we ship new capabilities (the upcoming tickets automations, the scheduled-broadcast retries), they land in MCP at the same time, so any LLM that speaks MCP — Claude, Cursor, Zed, anything else that adopts the standard — gets them automatically.

If you're already on the Pro plan and you've issued API keys before, the connector is probably the faster path for everything except machine-to-machine automation. Try it on a single workspace first, see what your team actually asks Claude, and scope the OAuth client accordingly.

Setup walkthrough with screenshots: Claude MCP Connector help doc.