QQ MCP
Related Servers
Alternatives to QQ MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseAqualityBmaintenanceEnables models to read QQ Zone posts and comments, like, reply, and optionally publish posts through a OneBot v11 gateway. All write actions are gated by allowlists, deduplication, rate limits, length checks, and audit logging.7359 npm2MIT
- FlicenseAqualityBmaintenanceEnables 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-
- FlicenseCqualityDmaintenanceEnables 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.574-
- AlicenseNot gradedqualityBmaintenanceEnables MCP-capable models to read QQ messages, reply in group and private chats, send images and favorite stickers, poke users, and manage pacing, deduplication, and concurrency during ongoing chat tasks through a local SnowLuma OneBot interface.MIT
- AlicenseAqualityCmaintenanceExposes NapCat/OneBot v11 QQ-bot APIs as MCP tools for any MCP client, and includes an LLM-driven QQ bot with memory, knowledge base, tool calling, web search, multimodal recognition, and permission controls.45MIT
TDQS
Scored across 5 tools
Each tool targets a distinct concern: status checks provider capabilities, targets lists allowed destinations, context reads scoped history, send transmits messages, and forget deletes retained context. There is no meaningful overlap between tool purposes.
All tools share a consistent qq_ prefix and lowercase snake_case style, making them recognizable as a set. The pattern mixes resource nouns (status, targets, context) with action verbs (send, forget), but the naming remains predictable and readable.
Five tools is a well-scoped count for a QQ MCP server covering capability checking, target discovery, context reading, sending, and local deletion. Each tool earns its place without redundancy or bloat.
The tool surface covers the core workflow of inspecting status, listing targets, reading context, sending messages, and forgetting local context. Minor gaps exist such as no explicit sent-message management or target modification, but these are likely outside the server's intended scope.