TG multi-account MCP runs on your own machine — the client starts it, so there is no endpoint to ping.
Self-hosted, consent-based access to Telegram accounts and bots for MCP clients
Today is the operative word: we check TG multi-account MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add tg-account-mcp -- uvx tg-account-mcp
{
"mcpServers": {
"tg-account-mcp": {
"args": [
"tg-account-mcp"
],
"command": "uvx"
}
}
}
[mcp_servers.tg-account-mcp]
command = "uvx"
args = ["tg-account-mcp"]
{
"mcpServers": {
"tg-account-mcp": {
"args": [
"tg-account-mcp"
],
"command": "uvx"
}
}
}
{
"mcpServers": {
"tg-account-mcp": {
"args": [
"tg-account-mcp"
],
"command": "uvx"
}
}
}
This one needs environment variables set before it will start:
TG_MCP_STATE_DIR (Private directory initialized with tg-mcp setup).
The author declared them in the registry entry; get the values from the project itself.
Telegram for AI agents: messages, chats, media, and contacts in bot and user-account modes.
Self-hosted MCP server: Telegram userbot control (Telethon) via HTTP and MCP.
MCP server for Telegram Archive — search messages, browse chats, and access history
Self-hosted MCP server for unified IMAP/SMTP mailbox access: read, list, and send email.
Telegram MCP server: read, send, and search messages and manage chats via your account.
Self-hosted multi-agent collaboration and audit layer for AI-assisted engineering teams
Share one project context across ChatGPT, Claude, Telegram and any MCP client.
Multi-account MCP for Gmail, Calendar, Drive, Docs, and Sheets — 61 tools, token-efficient, macOS…
Answers built from our own checks of this server.