Telegram Bot MCP Server runs on your own machine — the client starts it, so there is no endpoint to ping. 277 installs a week from npm. Last commit 24 Oct 2026.
Self-hosted Telegram Bot MCP server for rich text, media and interactive buttons.
What the code does
We read the source, 23 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
child = spawn(process.execPath, [resolvedNext, ...nextArgs], { cwd: workspace, env, stdio: 'inherit' });
const snapshot = Object.fromEntries(Object.entries(process.env).filter(([key]) => key.startsWith('TELEGRAM_')));
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
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 telegram-bot-mcp-server -e 'MCP_API_KEY=<MCP_API_KEY>' -- npx -y @cyuanxv/telegram-bot-mcp-server{
"mcpServers": {
"telegram-bot-mcp-server": {
"command": "npx",
"args": [
"-y",
"@cyuanxv/telegram-bot-mcp-server"
],
"env": {
"MCP_API_KEY": "<MCP_API_KEY>"
}
}
}
}[mcp_servers.telegram-bot-mcp-server]
command = "npx"
args = ["-y", "@cyuanxv/telegram-bot-mcp-server"]
env = { MCP_API_KEY = "<MCP_API_KEY>" }{
"mcpServers": {
"telegram-bot-mcp-server": {
"command": "npx",
"args": [
"-y",
"@cyuanxv/telegram-bot-mcp-server"
],
"env": {
"MCP_API_KEY": "<MCP_API_KEY>"
}
}
}
}{
"servers": {
"telegram-bot-mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@cyuanxv/telegram-bot-mcp-server"
],
"env": {
"MCP_API_KEY": "<MCP_API_KEY>"
}
}
}
}Put your own value in place of
<MCP_API_KEY> (Choose a strong local MCP access key. Use the same key in the Authorization header).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
TELEGRAM_BOT_TOKEN (Your own Telegram Bot token. Required for real Bot operations), TELEGRAM_CHAT_ID (Your own default Telegram chat ID).
Alternatives to Telegram Bot MCP Server
same job, measured the same waySelf-hosted MCP server: Telegram userbot control (Telethon) via HTTP and MCP.
Self-hosted, consent-based access to Telegram accounts and bots for MCP clients
Telegram for AI agents: messages, chats, media, and contacts in bot and user-account modes.
MCP server for Telegram Archive — search messages, browse chats, and access history
Hosted Telegram MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
MCP server that exposes a Telegram bot
Free hosted MCP server: new Upwork jobs for your agent and Telegram alerts within a minute.
A dynamic, self-refreshing MCP gateway for the complete Telegram Bot API
Telegram Bot MCP Server — questions
Answers built from our own checks of this server.