Skip to main content
Glama
HUliangwei

qq-onebot-mcp

by HUliangwei
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to qq-onebot-mcp

No user-submitted related servers found.

    Related Servers

    • astral-bridge

      oines
      A
      license
      B
      quality
      B
      maintenance
      Connects QQ via NapCat OneBot v11 to an Astral Code app-server, exposing MCP tools for sending messages, files, images, and fetching conversation history.
      10
      1
      Apache 2.0

    • Amadeus-QQ-MCP

      JulesLiu390
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables AI clients to send and receive QQ messages through NapCatQQ (OneBot v11) for both private and group chats. It supports message context management, real-time WebSocket listening, and human-like typing simulation.
      7
      25
      MIT

    • NapCat MCP Server

      ptrel1
      F
      license
      C
      quality
      B
      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
      -

    • Agent Bridge

      chaojixiaoyezi
      F
      license
      B
      quality
      B
      maintenance
      MCP server that bridges multiple AI agents for unified local chat, supporting private messages, chat rooms, role queues, and broadcast with fixed identities and rate limiting.
      14
      1
      -

    • qq-mcp-server

      print-yuhuan
      A
      license
      Not graded
      quality
      D
      maintenance
      A MCP server that exposes QQ bot capabilities over Streamable HTTP, enabling clients to query bot status, read group and friend info, fetch chat history, and send group/private text messages.
      2
      MIT

    • qq-bot-sender-mcp

      hiwow
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables sending text, Markdown, images, and files to individual QQ contacts via MCP protocol, suitable for pushing task results, screenshots, or documents to QQ.
      -
    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

    A4.2/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: sending, receiving (with two variants for context), status, profile retrieval, disc-change signal, and lifecycle management (attach/detach). No overlap causes ambiguity.

    Naming Consistency5/5

    All tools follow the consistent `qq_` prefix followed by an action verb (send, poll, wait, status, get, take, attach, detach). Naming is uniform, snake_case, and predictable.

    Tool Count5/5

    With 8 tools, the server is well-scoped for a QQ bridge: it covers messaging, inbox handling, status, profile, and session control without excess. This is within the ideal 3-15 tool range.

    Completeness4/5

    Core private-message workflows and lifecycle are covered: send, receive, status, claim/release, and disc-change. Missing group-message tools and whitelist management, though these may be intentionally out of scope for a private-owner bridge.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources