How to Connect Google Gemini to Your Telegram Chats

You connect Google Gemini to your Telegram chats by registering Entergram's hosted MCP server, https://mcp.entergram.com/mcp, with the Gemini CLI and signing in to Entergram once in your browser. After that, Gemini can read your chats, contacts and CRM data through your real personal Telegram account, and act on them within the scopes you granted. Setup is three steps and one small JSON block, shown below.

The Gemini CLI is the path the Gemini Telegram MCP page documents in full. Any other MCP-compatible client running a Gemini model can use the same URL, registered however that client expects.

• A Pro workspace. API & MCP is part of the Entergram Pro plan. On a lower plan the CLI will still list the server, then every call will be refused, which looks like a broken config but is not one.
• At least one connected Telegram account on your seat. A personal connector can only use the Telegram accounts listed under Settings → Accounts for your own member.
• A browser on the machine for the first sign-in. The consent screen needs one, so a headless server has to be authorized from a workstation first.

Step 1: Copy your MCP URL in Entergram

Go to Settings → Workspace → Connectors → MCP and copy the MCP server URL. It is the same for every client:

https://mcp.entergram.com/mcp

Step 2: Register the server with the Gemini CLI

Add Entergram under mcpServers in ~/.gemini/settings.json. Because the server is remote HTTPS, the key is httpUrl, not a command-and-args entry:

{
  "mcpServers": {
    "entergram": {
      "httpUrl": "https://mcp.entergram.com/mcp"
    }
  }
}

The file in your home directory applies to every project on that machine. To limit Telegram access to one repository, put the same block in .gemini/settings.json inside that repository instead.

Step 3: Relaunch the CLI and authorize

The CLI reads its configuration at startup, so exit the session completely and start it again. Sign in to Entergram in the browser window that opens and grant the scopes you want Gemini to have. Nothing in settings.json is a credential: the file only says where the server lives, and access comes from that OAuth sign-in.

Once authorized, list the registered MCP servers in the CLI and the Entergram tools appear under entergram.

What Gemini can do depends on which kind of client you authorize, as described on the MCP connectors help page:

A personal agent cannot send Telegram messages. If reads work but sends are refused, that is the scope boundary, not an error. An owner or admin has to authorize a workspace connector, and you run the consent flow again against it. Either way, grant the smallest set of scopes the job needs: messages.write lets an agent send messages as you.

To cut access, revoke the client in Entergram under Settings → Workspace → Connectors → MCP. Deleting the mcpServers entry only stops the CLI from calling the server; it does not invalidate the grant.

The Entergram MCP server connects to your personal Telegram account, not a bot, so Gemini works with the same chats you see. Prompts that work well in the CLI:

• "Which chats have unanswered questions from the last three days?"
• "List contacts in my customer group who aren't in the community group."
• "Post the release notes from CHANGELOG.md to the beta channel." (needs a workspace connector)
• "I typoed the version number in that announcement, fix it." (needs a workspace connector)
• "Give me this week's ticket counts by assignee as TSV."

The CLI prints each tool call it makes, so you can watch the mechanics on a read-only job before trusting it with a write.

• Message tools need an explicit account. There is no implicit default, so a script should resolve the account list first and pass the account id down.
• Nothing arrives unprompted. MCP is request and response. Gemini learns about a new message only when you or a scheduled job you own asks it to look.
• No elevated access. Gemini sees exactly what your connected Telegram accounts see. A group you left is a group it cannot read, and chats you exclude under Accounts → Exclude chats stay out of MCP results.

• The server never appears in the MCP list. Usually malformed JSON: one trailing comma makes the CLI drop the whole settings file. Check that the entry uses httpUrl and sits inside mcpServers.
• Edits to settings.json seem to do nothing. Exit the session fully and relaunch. A running process keeps the tool list it built at startup.
• It works in one directory and not another. You have two settings files. Check whether the entergram entry lives in ~/.gemini or in a repository's .gemini folder.
• Every call returns 403. Check the plan first (MCP needs Pro), then the role: anything past the personal agent scope set requires an owner or admin.

The Entergram MCP server is the same for every client. Set it up once and you can connect whichever AI client you prefer, or several:

• Connect Claude to Telegram via Entergram
• Connect ChatGPT to Telegram via Entergram
• Connect any AI tool to Telegram MCP

For the full Gemini tool list, project-scope examples and scheduled jobs, see the Gemini Telegram MCP page. For what the server does across every client, start at the Telegram MCP server page.