Cline · VS Code
Register Entergram as an MCP server in Cline, the VS Code AI agent, and reach your real Telegram account from your editor - catch missed messages and clients waiting on you without breaking flow.
https://mcp.entergram.com/mcp Cline loads MCP servers from inside VS Code. Add Entergram's URL to its settings and Cline can read and act on your real personal Telegram account without leaving the editor - OAuth-secured, with no bot account and no API keys.
{
"mcpServers": {
"entergram": {
"url": "https://mcp.entergram.com/mcp"
}
}
}Works with the Cline extension in VS Code.
In Entergram, visit Settings → Workspace → Connectors → MCP and copy the server URL. Cline keeps it in its own MCP settings file, separate from your VS Code settings.
In Cline’s MCP settings (cline_mcp_settings.json), register the Entergram MCP URL: https://mcp.entergram.com/mcp.
Save the file, let Cline restart the server, then finish the OAuth sign-in. Cline surfaces each Entergram call for your approval before it runs.
The route that involves no JSON. Click the server icon at the top of the Cline pane, open the Remote Servers tab, name the entry entergram, paste the URL and click Add. Cline writes the config for you and shows a status light next to the server, which is the fastest way to tell a bad paste from a bad plan.
The file itself lives in the extension's global storage - on macOS at ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json, with the same path shape under the VS Code user directory on Windows and Linux. Editing it by hand is worth it when you want the autoApprove array under version control alongside your other machine setup.
{
"mcpServers": {
"entergram": {
"url": "https://mcp.entergram.com/mcp",
"disabled": false,
"autoApprove": []
}
}
}The setting that decides whether the connector feels useful or exhausting. Naming individual tools in autoApprove lets lookups run without a prompt while anything that writes, sends or deletes still stops for a human. Start with the four below and widen it only once a workflow has proven itself.
"autoApprove": [
"entergram_list_accounts",
"entergram_list_chats",
"entergram_list_messages",
"entergram_get_contact"
]With your personal account connected, Cline can check Telegram without you leaving VS Code. Try:
Cline is an agent that plans several steps ahead, then executes them one call at a time with an Approve or Reject button in front of each. That rhythm changes what a connector is for: the reads blur past, and the writes are where you actually pay attention. These are the runs worth handing it.
You ask
«Turn this morning's bug reports into tickets, one at a time.»
Tools called
entergram_list_live_chatsentergram_list_messagesentergram_create_ticket
You get
Cline reads the unread view, groups what it finds into distinct problems, and then proposes a ticket per problem. Each creation surfaces as its own approval, so rejecting one skips it and leaves the rest of the plan intact. What was forty minutes of copy-paste becomes a queue of yes-or-no decisions.
You ask
«We deployed twenty minutes ago. Has anything broken?»
Tools called
entergram_list_live_chatsentergram_get_live_chatentergram_list_messages
You get
A smoke test against the only monitor that catches the failures your dashboards miss. Cline narrows to conversations with activity since the deploy window, reads what came in, and separates ordinary traffic from anything that reads like a regression. All reads, so with auto-approve on it runs uninterrupted.
You ask
«Last night's outage tickets are all still marked normal. Raise the severity on the ones from paying customers.»
Tools called
entergram_list_ticketsentergram_list_ticket_custom_columnsentergram_update_ticket
You get
It reads the ticket schema before writing so that severity maps onto your real option values rather than a guess, then updates each match. Because every update is a separate approval, you get to see the list one row at a time and stop the moment one of them looks wrong.
You ask
«Acknowledge everyone who reported the export bug so they know it's been seen.»
Tools called
entergram_list_messagesentergram_set_message_reactions
You get
A reaction is the cheapest possible response and the one developers never get around to. Cline finds the reporting messages across threads and reacts to each, which costs nothing and buys hours of patience from people who otherwise assume they were ignored.
You ask
«Draft the release note for the beta group and stop before sending.»
Tools called
entergram_list_groupsentergram_list_group_membersentergram_send_message
You get
The plan finishes with a send that never fires until you press Approve, and the drafted text is right there to edit first. Checking the member list beforehand is the detail that matters: it is how you notice the announcement is about to reach a group that still contains last quarter's customers.
You ask
«Write up what you did in this run as an internal note on each chat you touched.»
Tools called
entergram_list_chat_commentsentergram_create_chat_comment
You get
An audit trail the agent generates about itself, attached to the conversations rather than lost in a closed editor tab. It reads what is already noted so it does not repeat a teammate, then appends its own summary as a comment nobody outside your workspace can see.
User story · Support engineer
Cline is a good fit when the user wants to watch the agent connect Telegram evidence to code and explicitly approve the records it creates in Entergram and Linear.
Product complaints arrive across several Telegram accounts and groups. Support can describe symptoms, engineering can inspect code, but the weekly handoff creates duplicate Linear issues with little evidence and no status written back to customers' chats.
The instruction
Review this week's defect-like messages across every connected Telegram account. Group by likely root cause, not by chat. For each group, inspect the relevant repository code and draft one Linear issue with evidence, reproduction steps and acceptance criteria. Search Linear for an existing issue first. For every source chat, draft an internal Entergram comment containing the issue ID, current owner and a customer-safe summary. Ask me to approve each Linear create/update and each batch of Entergram comments.
What the team gets
Engineering receives fewer, better issues; support sees the owner and status in the original chat; and the approval log shows exactly which external records Cline changed.
Cline's approval prompt is the gate you see. The OAuth scopes are the gate you set once and then stop thinking about, and they are the stricter of the two - approving a call can never grant a permission the token was not issued with. Decide the access level before you tune autoApprove, because the token is the ceiling and the approval list only decides how often you are asked about what is already permitted. Revoking takes two clicks in Entergram under Settings → Workspace → Connectors → MCP.
Personal agentWorkspace connectorRevocationThe honest trade-offs of an in-editor agent with a human in the middle.
Practical guides
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 site use and attribute sign-ups to referral partners. Optional.