Back to features

Telegram CRM

Telegram CRM API & MCP Server — Plug Telegram Into Your Stack

Public REST API and MCP server for Entergram. Sync Telegram chats and contacts into your warehouse, fire broadcasts from external events, let AI agents triage your inbox. Scoped, rotatable, IP-restrictable keys. Pro plan.

AI

What you can build with the API + MCP

Two endpoints, one mental model: scoped keys read and write workspace data. The REST API is for code (sync jobs, internal tools, automations). The MCP server is the same surface exposed to AI agents — Claude, GPT, Make.com — so an LLM can read chats, look up custom-field values, create tickets, fire a broadcast, all gated by the scopes you grant.

Read the developer docs
  • —

    Sync Telegram into your warehouse / CRM

    Pull chats, contacts and custom-field values out of Entergram on a schedule. Drop them into BigQuery, Postgres, Hubspot or Salesforce so the rest of the business can join them with non-Telegram data.

  • —

    Fire broadcasts from external events

    When a payment fails in Stripe, when a deal closes in your CRM, when a monitoring alert trips — POST to Entergram and a broadcast goes out to the right tagged segment with the right template.

  • —

    AI agents that triage your inbox

    Point Claude or GPT at your workspace via the MCP server. The agent can read recent chats, look up the contact's stage and ARR, leave an internal comment, open a ticket, even draft a reply for you to send. Scopes decide exactly what it's allowed to do.

What you can build with the API + MCP

Entergram's REST API and MCP server let you wire your Telegram CRM into the rest of your stack — data warehouses, AI agents, low-code automations, internal tools, your own product. Workspace-scoped keys, least-privilege scopes, optional IP allowlist, MCP support for Claude/GPT/Make.com agents.

Start free trial

Frequently asked questions

Frequently asked questions

What can I actually do with the MCP server?
Anything an AI agent should be able to do for you. With the right scopes, an agent can: read recent Telegram chats, look up a contact's stage / ARR / custom fields, leave an internal comment, create or update a ticket, change ticket status, fire a broadcast from a template, add a tag, set a reminder. The scopes you grant decide exactly what's allowed — least privilege is the recommended default.
What scopes are available?
workspace.read · members.read · accounts.read · contacts.read · chats.read · chats.write · custom_fields.read · custom_fields.write. Pick the minimum your integration needs — least privilege limits blast radius if a key leaks.
Concrete examples — what do real teams build?
A trading team syncs every Telegram chat into BigQuery hourly so analysts can join with on-chain data. A SaaS support team has Claude triage the inbox overnight via MCP — it tags urgent cases and opens tickets so the team starts the day with a sorted queue. A growth team fires a Telegram broadcast from a Make.com scenario whenever a Stripe upgrade event lands.
How do I rotate a leaked key?
Developers tab → find the key by its prefix → Revoke (immediate). Then create a new key with the same scopes and IP allowlist, deploy it to your integration, and check the old key's last-used info to confirm no more traffic. Keys are stored as one-way hashes — the raw key only exists at the moment of creation.
Can the MCP/API see another workspace's data?
No. Every API call and MCP request is scoped to the workspace that issued the key. A key from workspace A literally cannot read workspace B — the scoping is enforced server-side on every query.
What HTTP errors might I see?
401 = key is expired, revoked, or wrong for the workspace. 403 = the key lacks the needed scope, or the request came from an IP outside the allowlist. 429 = you've hit a rate limit; back off and retry.
Start free trial