Entergram MCP
https://mcp.entergram.com/mcpAuthorized personal Telegram accounts, chats, messages and governed actions.
Two-server MCP workflow
Connect Slack MCP to personal Telegram accounts
Give one compatible client two explicit tool boundaries: Entergram MCP works with authorized personal Telegram accounts, while Slack MCP works only inside the separately authorized Slack environment.
Architecture
One client, two permission boundaries
Compatible MCP client
Claude · Cursor · ChatGPT · MCP clientsChooses tools, follows the operating instruction and requests approval where policy requires it.
Slack MCP
https://mcp.slack.com/mcpUser-authorized Slack data and actions exposed by the official Slack MCP server.
Intent boundary
Why the integration and MCP pages stay separate
Connect multiple personal Telegram accounts to Slack: The broad integration page owns connection choices, APIs, automation platforms, field mapping and deterministic workflows.
This page owns the narrower Slack Telegram MCP intent: endpoints, client orchestration, scopes, prompts, approval boundaries and cross-server safety.
High-value routines
What the combined MCP workflow can do
Turn a qualified Telegram issue into the right Slack thread
Read the governed Telegram message, choose the approved Slack channel, create or update one thread with a concise summary and retain the mapping needed to return an approved response.
Guardrail: Do not export unrelated private chat; map Telegram chat and message IDs to the Slack channel and thread timestamp.Audit log of every chat a seat can access
Entergram relays every Telegram chat that seat can access into that channel.
Guardrail: Keep the channel private and its membership as tight as access to the accounts.Escalation summaries in a separate channel
Post a sanitized summary with owner and source link.
Guardrail: Build it over the Entergram MCP or API in n8n or your own service; the native app only relays.Retention set before the audit
Set Slack retention on the audit channel to match that period.
Guardrail: Test a Telegram-side deletion before citing the channel as proof.Setup
Connect Slack MCP and Telegram MCP
- 01
Copy your MCP URL in Entergram
Go to Settings → Workspace → Connectors → MCP and copy your MCP server URL: https://mcp.entergram.com/mcp
- 02
Add the MCP URL in your app
In your AI tool or automation platform, add a custom connector or MCP node. Paste the Entergram MCP URL: https://mcp.entergram.com/mcp
- 03
Connect and authorize
Click Connect, review the permissions on Entergram's authorization page, and click Allow access. Your Telegram workspace is now connected.
- 04
Add the official Slack MCP server
Add https://mcp.slack.com/mcp as a separate server and complete the current Slack authorization flow. Grant only the workspace and actions the routine needs.
- 05
Test a read-only cross-server request
Resolve the Telegram account and the intended Slack destination before any write. Confirm both stable IDs and stop on an ambiguous match.
Conceptual multi-server configuration
{
"mcpServers": {
"entergram": {
"url": "https://mcp.entergram.com/mcp"
},
"slack": {
"url": "https://mcp.slack.com/mcp"
}
}
}Security model
Keep the agent inside a narrow operating contract
- Each teammate connects their own Slack, and routing is one channel per seat, not one per Telegram account.
- The relay is one way: nothing written in Slack is sent to Telegram.
- Slack is an internal record surface, not a substitute Telegram inbox.
- Anyone in the channel can read every chat relayed into it, so membership needs careful governance.
- What happens to the Slack copy after a message is deleted on the Telegram side is not confirmed yet.
- Slack MCP and Entergram MCP require separate authorization, scopes and audit controls.
- Using the channel as a record is only as durable as the Slack retention policy applied to it.
- Never put Slack or Entergram credentials in prompts or source-controlled configuration.
Official sources
Verify both systems before deployment
Official documentation: Slack 1 ↗
Official documentation: Slack 2 ↗
Technical details reviewed 31 August 2026. Endpoints, tools, client support and authorization behavior can change.
Frequently asked questions
Slack Telegram MCP questions
Is Slack Telegram MCP one server?+
No. A compatible client connects to two separately authorized servers: Entergram MCP for personal Telegram accounts and the official Slack MCP server for Slack data and actions.
What MCP server URLs are used?+
Entergram uses https://mcp.entergram.com/mcp and Slack uses https://mcp.slack.com/mcp. Verify both endpoints in current official documentation before deployment.
Can Telegram MCP connect multiple personal Telegram accounts?+
Yes. Entergram is designed for multiple personal Telegram accounts in one workspace. The MCP client receives only the accounts and scopes you authorize, and each request keeps its source account identity so messages are not mixed together.
Does Telegram have an official MCP server?+
No. If you are asking does Telegram have MCP support built in, the answer is that Telegram does not publish an MCP server, so every MCP for Telegram you find is either a community project or a hosted service. The open-source Telegram MCP servers you will find are community projects, and almost all of them connect a single account, either through a bot token or through a user session you host and maintain yourself. Entergram is a hosted MCP server that connects every personal Telegram account on your seat through one OAuth connection, with the account identity and permission scope preserved on every request.
How is this different from the Slack Telegram integration page?+
The broad page covers APIs, webhooks, no-code tools, mapping and deterministic automation. This page is specifically about an MCP client coordinating two separately authorized servers.
Telegram MCP
Connect an MCP client to Entergram
Add the hosted endpoint, review the requested scopes and authorize the connection.