Skip to main content
Glama
haoan33

OmniQQ-MCP

by haoan33
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to OmniQQ-MCP

No user-submitted related servers found.

    Related Servers

    • 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
      -

    • 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
      -

    • 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 MCP

      BK927
      A
      license
      A
      quality
      C
      maintenance
      Enables interaction with QQ through official bot APIs or personal accounts bridged via NapCat/OneBot v11, including status checks, target listing, bounded context retrieval, and plain-text sending to allowlisted conversations.
      5
      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.2/5.0

    Scored across 74 tools

    Disambiguation4/5

    Most tools target clearly distinct OneBot/NapCat actions (send private vs group, group file vs folder, profile vs signature vs status), and detailed descriptions help disambiguate. However, a few overlaps exist: send_msg duplicates the specific private/group send tools, call_napcat_api overlaps all named tools as a fallback, and several recent/history/system-message tools could be confused at a glance.

    Naming Consistency5/5

    Names are consistently snake_case and follow predictable verb-first patterns: get_*, set_*, send_*, delete_*, upload_*, list_*, and clear_*. Minor outliers like check_napcat_environment or deploy_or_update_napcat still fit the snake_case convention and remain readable.

    Tool Count2/5

    74 tools is far above the typical well-scoped range and feels heavy even for a broad OneBot 11 wrapper. The server also provides call_napcat_api and list_supported_napcat_actions as generic passthroughs, making many named convenience tools partially redundant.

    Completeness5/5

    The surface covers the domain comprehensively: account login/switch/deploy, messaging, group administration, files, friends, profile, history, recent events, OCR, and a generic passthrough for uncovered OneBot actions. No obvious lifecycle or CRUD gap remains for the stated QQ/NapCat control purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources