Skip to main content
Glama
irmia2026

onebot11-mcp

by irmia2026
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to onebot11-mcp

No user-submitted related servers found.

    Related Servers

    • qq-agent

      XXXXXQ-0206
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes read-only tools over a local OneBot 11 / NapCat endpoint for a logged-in QQ account, letting agents list sessions, fetch chat history and surrounding context, resolve forwarded messages, search messages, and inspect files or media, with message sending gated off by default.
      MIT

    • qq-onebot-mcp

      HUliangwei
      F
      license
      A
      quality
      B
      maintenance
      Enables MCP hosts to bridge with QQ via NapCat/OneBot 11, allowing whitelisted private messages to reach an agent with full tool access while group mentions are answered by a sandboxed pure LLM without system access.
      8
      -

    • NapCat MCP Server

      ptrel1
      F
      license
      C
      quality
      C
      maintenance
      Enables interaction with NapCat QQ bot APIs for group management, messaging, and system operations. Supports HTTP and WebSocket modes with security features like group restrictions and readonly mode.
      57
      4
      -

    • Telegram Bot MCP

      pixellover1433
      F
      license
      Not graded
      quality
      A
      maintenance
      Exposes Telegram Bot API operations as MCP tools, enabling managing messages, chats, and forum topics via a FastMCP server.
      -

    • discord-mcp

      nesquickwe
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to control a logged-in Discord account through 70+ tools: browsing guilds and channels, sending and reacting to messages, moderating members, managing channels, roles, emojis, and webhooks, plus searching and analyzing captured message history stored in SQLite. Authenticates using tokens already cached by the local Discord client, requiring no bot account or manual token setup.
      128 npm
      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

    B3.4/5.0

    Scored across 27 tools

    Disambiguation5/5

    Every tool targets a distinct resource plus action: get_* queries are cleanly separated by target (version, login, status, friend_list, group_list, group_info, member_list, member_info, msg, forward_msg, image, record, cookies, csrf_token), and set_* management actions each modify a clearly different attribute. There is no meaningful overlap between any two tools.

    Naming Consistency4/5

    The get_/set_ verb_noun pattern dominates and is applied consistently across the large majority of tools, and what reads as 'set' vs 'kick/admin/ban' maps to the underlying OneBot action names. Minor deviations like send_like and delete_msg break the prefix scheme but remain readable and memorable.

    Tool Count4/5

    27 tools is on the heavy side, but they map one-to-one onto distinct OneBot11 API actions (queries, media, credentials, group administration, requests), so each largely earns its place. It is slightly over the ideal range but not bloated with redundancy.

    Completeness3/5

    The set covers querying, media retrieval, credentials, and extensive group administration, but the most essential chat operation — sending a message (send_msg / send_group_msg / send_private_msg) — is entirely absent, along with message history and friend-request listing. For a messaging bot this is a notable and surprising gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources