Enterprise Telegram bot management for any AI agent — users, payments, analytics, and more.
Paid Telegram Bot is a production-grade MCP server that gives any AI agent full enterprise Telegram bot management capabilities. Unlike basic Telegram MCP servers that only send and receive messages, this server includes a built-in SQLite database, token bucket rate limiting, priority message queue, Stripe + Telegram Stars payment processing, multi-user subscription management, deep link onboarding, analytics dashboards, and security event logging — all accessible through 40+ MCP tools.
**How it works**: The server runs as a persistent local process alongside your MCP client. It manages a Telegram bot via long-polling, stores user data and payment records in a local SQLite database, enforces rate limits against Telegram's API caps, and exposes everything as MCP tools your AI agent can call.
**Who it's for**: Developers, indie hackers, agencies, and businesses who want their AI agent (Claude, Cursor, Windsurf, Claude Code, or any MCP-compatible client) to manage a Telegram bot with enterprise features — from personal assistants to monetized SaaS bots serving thousands of users.
**Free tier** includes 12 basic tools for personal bot setup and messaging. **Pro tier** (license required) unlocks 40+ tools including user management, subscription plans, payment processing, analytics, deep links, group mode, event subscriptions, and chat history search.
Set these up before or after installing:
Environment variable: TELEGRAM_BOT_TOKEN
Sign up freeEnvironment variable: MCP_LICENSE_KEY
Purchase above for keyEnvironment variable: STRIPE_PROVIDER_TOKEN
Sign up freeOnce installed, try these example prompts and explore these capabilities:
Add this to your MCP configuration file:
{
"mcpServers": {
"paid-telegram-bot": {
"env": {
"MCP_LICENSE_KEY": "your-mcp-license-key-here",
"TELEGRAM_BOT_TOKEN": "your-telegram-bot-token-here",
"STRIPE_PROVIDER_TOKEN": "your-stripe-provider-token-here"
},
"args": [
"paid-telegram-bot"
],
"command": "uvx"
}
}
}This MCP server has concerning authentication implementation with hardcoded tokens, dependency risks from unverified packages, and excessive permissions that extend far beyond typical communication server needs. The license validation mechanism appears suspicious and the server requests broad system access including filesystem and environment variables. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity).
Scanned 8 files · 7 findings
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Be the first to review this server!