@retensy/mcp
Related Servers
Alternatives to @retensy/mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to interact with, test, click buttons on, and verify Telegram bots end-to-end via MTProto, including messaging, inline queries, media exchange, and automated test suites.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants like Claude, Cursor, and Copilot to manage Telegram bots through 68 tools covering the TeleBotHost Developer API, including bot management, messaging, and analytics.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with the Telegram Bot API, allowing them to send messages, forward messages, get bot information, and receive updates.11 npm3MIT
- AlicenseAqualityDmaintenanceEnables AI agents to send and receive messages, media, and files on Telegram, and manage chats via a bot token.17MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to create, edit, and manage Telegraph pages programmatically with support for Markdown content, templates, and page export/backup functionality.1315 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to autonomously interact with, test, click buttons on, and verify Telegram bots end-to-end via the MTProto protocol.MIT
TDQS
Scored across 30 tools
The graph-mutation cluster (update_graph, edit_graph_live, patch_graph, clone_graph, copy_graph) has genuinely overlapping purposes, and several tools create graphs (create_graph, create_graph_from_template, import_funnel). The very detailed descriptions explicitly tell the agent which to pick and when, which rescues the set from being confusing, but the boundaries are still fuzzy.
Most tools follow a clear snake_case verb_noun pattern (list_graphs, create_graph, delete_file). However, the blog tools break the convention with noun_verb order (article_list, article_get, article_publish, article_update), and a few outliers (dry_run, graph_analytics) drop the verb entirely.
30 tools is on the heavy side and spans two loosely related domains (funnel/graph builder plus a blog article API). The overlapping graph-editing tools suggest some redundancy, though the overall breadth is defensible given the platform's scope.
The graph/funnel lifecycle is well covered (create, get, list, clone, copy, update, publish, delete, active-switch, analytics, dry-run) and files/templates/users/links each have read and write paths. Minor gaps remain: articles have list/get/publish/update but no delete, and there is no bot create/edit beyond list_bots.