Skip to main content
Glama
skiddgoddamn

zaytsv-bot-graph-mcp

by skiddgoddamn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to zaytsv-bot-graph-mcp

No user-submitted related servers found.

    Related Servers

    • telegram-bot-mcp

      abramovmarketing88-byte
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enables interaction with the Telegram Bot API, allowing users to send messages, retrieve updates, and access chat information through natural language.
      -

    • io.github.daedalus/mcp

      daedalus
      A
      license
      A
      quality
      C
      maintenance
      MCP server that exposes a Telegram bot, enabling sending messages and retrieving updates through natural language.
      3
      20 PyPI
      1
      MIT

    • tgfmcp

      vaibhavpandeyvpz
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables Telegram bot interaction via Telegraf, providing tools for sending, replying, reacting, editing, deleting, forwarding messages, and receiving Telegram events over an optional notification channel.
      71 npm
      3
      MIT

    • telegram-api-mcp

      timoncool
      A
      license
      C
      quality
      C
      maintenance
      Ultimate MCP server for Telegram Bot API — 169 methods, full v9.6 coverage, meta-mode, rate limiting, and circuit breaker, enabling AI to control Telegram bots with natural language.
      100
      28
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 30 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (e.g., list_graphs, create_graph, publish_graph), but there is overlap among graph modification tools (update_graph, edit_graph_live, patch_graph) and creation tools (create_graph, create_graph_from_template, import_funnel). Detailed descriptions help, but an agent must read carefully to choose the right one.

    Naming Consistency4/5

    The majority follow a consistent verb_noun pattern (list_graphs, create_graph, delete_graph, rename_graph), but there are exceptions like article_list instead of list_articles, graph_analytics, and dry_run that break the convention. Overall, naming is readable and mostly predictable.

    Tool Count2/5

    With 30 tools, the server is over-scoped. The core graph management could be handled in fewer tools, and the inclusion of blog article tools (article_list, article_get, article_publish, article_update) is unrelated to bot graphs. Many operations are fragmented, making the toolkit feel bloated.

    Completeness4/5

    The graph lifecycle is thoroughly covered: create, get, update, delete, publish, clone, copy, rename, set active, dry run, and template creation. File and bot management are also present. Minor gaps exist (e.g., no article_delete, no single-file retrieval), but these do not affect the core domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources