MCP server that exposes a Telegram bot
MCP server that exposes a Telegram bot
pip install mcp-telegram-bot
TELEGRAM_BOT_TOKEN environment variableexport TELELEGRAM_BOT_TOKEN="your-bot-token-here"
mcp-telegram-bot
mcp-name: io.github.daedalus/mcp-telegram-bot
git clone https://github.com/daedalus/mcp-telegram-bot.git
cd mcp-telegram-bot
pip install -e ".[test]"
# run tests
pytest
# format
ruff format src/ tests/
# lint
ruff check src/ tests/
# type check
mypy src/
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
uvx mcp-telegram-botMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-daedalus-mcp-telegram-bot": {
"command": "uvx",
"args": [
"mcp-telegram-bot"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencemcp-telegram-botpypiio.github.daedalus/mcp-telegram-bot works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.