M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionLangGraph.js AI Agent TemplateProduction-ready Next.js + LangGraph.js template with dynamic MCP tool loading and human-in-the-loop approvalTelegram MCP ServerTelegram MCP server powered by Telethon to let MCP clients read chats, manage groups, and send/modify messages, media, contacts, and settings.
FMRS51 / 100 · D70 / 100 · B
Reliability5 / 209 / 20
Security and permissions12 / 2016 / 20
Maintenance11 / 2014 / 20
Documentation14 / 2017 / 20
Setup experience9 / 2014 / 20
Best for
  • Teams comfortable with TypeScript/Next.js who want to build their own agent product on top of this scaffold
  • Developers evaluating or demoing MCP dynamic tool loading and human-in-the-loop approval patterns
  • Deployments with existing PostgreSQL/Docker infrastructure willing to self-host a full stack app
  • Developers who want to integrate Telegram into MCP clients like Claude
  • Automation scenarios that need to manage multiple Telegram accounts
  • Building custom Telegram bots or workflows
  • Scenarios that require secure file operation path restrictions
Not for
  • Users who just want to plug a single 'tool server' into Claude Desktop or another MCP client — this project is not that kind of drop-in MCP server
  • Users unwilling to operate a database, object storage, and a full front/back-end stack themselves
  • Use cases requiring official LangChain- or MCP-protocol-team maintenance and support guarantees
  • Use cases requiring official Bot API features (this server uses a user client)
  • Non-technical users who want a fully managed solution
  • Multiple processes using the same session without lock management
Required permissions
  • Database read/write access (PostgreSQL) for conversation history and stored MCP server configs
  • Object storage read/write access (S3-compatible storage / MinIO) for file uploads
  • Outbound network access to call OpenAI/Google/Anthropic model APIs
  • Ability to execute local commands or reach remote HTTP endpoints as configured by the user when they register stdio/HTTP MCP servers
  • Requires Telegram API ID and API Hash
  • Requires the user's Telegram session string (equivalent to account access)
  • Can send messages, media, contacts, and settings to any allowed chat
  • Can create or modify groups, channels, and chat settings
  • Can access and operate on the user's media files and contacts
Risks and side effects
  • Users can register arbitrary stdio commands as MCP servers via the settings UI; trusting an unverified command can lead to local command execution
  • An optional 'auto-approval' mode skips the human-in-the-loop review of tool calls, amplifying the impact of mistaken or malicious tool invocations
  • API keys and database connection strings are stored as environment variables and must be protected (`.env.local`)
  • The app exposes an OpenAPI explorer at `/api-docs`, so production access controls should be reviewed
  • Session string leakage could lead to account compromise
  • Sending messages may raise privacy or security concerns
  • Prompt injection: Telegram content may be maliciously crafted, so precautions are needed
  • Risk of using unofficial PyPI package name; avoid pip install telegram-mcp
  • Concurrent clients using the same session may cause AuthKeyDuplicatedError
Supported clientsClaude Desktop, Cursor, Claude Code, Codex
Tools076