Gemini · Google
Use Entergram as a Telegram MCP server for Google Gemini and the Gemini CLI — give Gemini secure, OAuth-scoped access to your real Telegram chats so it can surface missed messages, waiting clients and cold leads.
https://mcp.entergram.com/mcp Both the Gemini CLI and MCP-compatible Gemini clients can register external MCP servers. Add Entergram's URL and Gemini gains scoped, OAuth-secured access to your real personal Telegram account — no bot to maintain, nothing to code, no API keys to store.
{
"mcpServers": {
"entergram": {
"httpUrl": "https://mcp.entergram.com/mcp"
}
}
}With your personal account connected, Gemini can analyze every chat at once. Try prompts like:
Works with the Gemini CLI and MCP-compatible Gemini clients.
Start in Entergram — Settings → Workspace → Connectors → MCP holds your server URL. Copy it to the clipboard, since the Gemini CLI reads it from a config file rather than an input box.
Add Entergram to your Gemini CLI MCP configuration with the URL: https://mcp.entergram.com/mcp.
Run the CLI again so it picks up the new server, sign in to Entergram in the browser it opens, and grant scoped access to your workspace.
The primary path, and what most people mean by Gemini MCP. Add the server to ~/.gemini/settings.json under mcpServers with httpUrl pointing at the hosted endpoint, restart the CLI, and the tools are available in every project on that machine. Because it is remote HTTPS there is no npx wrapper or stdio bridge to keep alive.
{ "mcpServers": { "entergram": { "httpUrl": "https://mcp.entergram.com/mcp" } } }The same block placed in .gemini/settings.json inside a repository applies to that checkout only. Useful when one repo is the deploy pipeline that announces releases to a Telegram channel and the rest of your work has no business touching chats — and it keeps the configuration in version control where a teammate can read it.
mkdir -p .gemini && $EDITOR .gemini/settings.jsonThe endpoint is model-agnostic. An IDE agent, a scripted harness or an in-house tool running Gemini underneath registers Entergram however its own MCP config expects and receives the identical tool list. The consent screen belongs to Entergram, so whoever runs the client authorizes as themselves rather than inheriting somebody else's grant.
In the CLI these are one-line invocations you can put behind a shell alias or a git hook. Each plain-language request expands into a sequence of tool calls, and the CLI prints which ones it made — so you can watch the mechanics before you trust it with a write. Everything below assumes the server is registered and authorized once; after that it is just typing.
You ask
“Post the release notes from CHANGELOG.md to the beta channel.”
Tools called
entergram_list_accountsentergram_list_groupsentergram_send_message
You get
The post-deploy step nobody remembers. Gemini already has the changelog in context from the repo, picks the account that administers the channel, matches the channel by name, and posts. Hang it off a successful build and the announcement stops depending on somebody's memory.
You ask
“Who is in the beta channel that we have never marked as a paying customer?”
Tools called
entergram_list_group_membersentergram_list_contactsentergram_get_chat_custom_fields
You get
A set difference across two systems that normally live in different browser tabs. It enumerates the channel roster, matches those people against your contact list, then reads the CRM fields to see who carries the customer flag. What comes back is the unconverted half of your community, by name.
You ask
“Send the failing test output to the Acme thread with a short explanation.”
Tools called
entergram_list_chatsentergram_send_media_message
You get
The file is already on disk next to you, which skips the whole upload dance. Gemini attaches the artifact and writes the covering line itself — the difference between a client seeing a wall of stack trace and a client seeing what broke and when it will be fixed.
You ask
“Create a launch channel, name it properly and add the release team.”
Tools called
entergram_create_channelentergram_update_chat_infoentergram_invite_chat_members
You get
Three steps in Telegram's own UI collapse into one sentence. The channel is created, title and description are set from what you described, and the invite list is resolved from your contacts. This one needs a workspace connector — group administration is not in the personal agent scope set.
You ask
“I typoed the version number in that announcement, fix it.”
Tools called
entergram_list_messagesentergram_edit_message
You get
It reads back recent history to identify the message you mean, then edits in place instead of posting a correction underneath. Telegram keeps the message where it was, so nobody who already read it gets pinged again and the channel history stays clean.
You ask
“Give me this week's ticket counts by assignee as TSV.”
Tools called
entergram_list_ticketsentergram_list_ticket_custom_columnsentergram_list_members
You get
Output formatting is where a terminal client earns its keep. It pulls the queue, resolves the category and severity columns to their real option values, maps assignee IDs to human names, and prints tab-separated rows you can pipe straight into a spreadsheet or a chart script. Ad-hoc reporting, with nobody having to build a report first.
List the registered MCP servers after connecting and all 70 tools appear under entergram, grouped the way they are below. Tool names are literal identifiers, which counts for more in a terminal than in a chat window: you can name a call directly in a prompt when you want deterministic behaviour instead of letting the model pick its own route. The CLI prints each call and its arguments as it goes, which makes an unfamiliar tool list quick to learn.
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_commandNothing in settings.json is a credential. The file only tells the CLI where the server lives; access comes from an OAuth login you complete in a browser, and the resulting token belongs to you rather than to the checkout. Google receives no Telegram credentials at any point — the phone number and session stay inside Entergram. Two scope sets exist, and which one you need depends on whether the CLI is expected to write.
Personal agent scope setWorkspace connector scope setKilling the connectionMost of these only bite once you try to run the CLI unattended.
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.
