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
      C
      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
      26
      MIT

    • NapCat MCP Server

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

      Reshwell
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables an AI agent to fetch queued OneBot v11 QQ private and group messages, retrieve inbound images for vision-capable models, and send text, images, or files with request-id deduplication. Also exposes acknowledgment, message history, conversation and contact listing, delivery status, and bridge health so agents can drive a persistent SQLite-backed QQ message loop.
      MIT

    • 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
    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 distinct OneBot actions with clear resource+action boundaries. However, send_msg overlaps with send_private_msg/send_group_msg, and call_napcat_api acts as a catch-all that could be used for any specific tool's purpose, creating some selection ambiguity.

    Naming Consistency5/5

    All tool names use snake_case and follow a verb_noun pattern (e.g., get_group_list, set_group_ban, send_private_msg). Even multi-verb names like deploy_or_update_napcat remain consistent and readable.

    Tool Count1/5

    74 tools is far beyond the typical 3-15 range and qualifies as extreme mismatch. The presence of call_napcat_api and list_supported_napcat_actions makes many specific tools redundant, increasing context load without clear benefit.

    Completeness5/5

    The server covers messaging, group/friend management, file operations, account management, history, and system deployment. The generic call_napcat_api ensures no dead ends for rare actions, providing complete lifecycle coverage for QQ bot automation.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources