qq-mcp
Related Servers
Alternatives to qq-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to control and monitor QQ accounts through the NapCatQQ OneBot 11 protocol, covering private/group messaging, forwards, group administration, file transfer, OCR, friend and profile management, and real-time message listening. It also handles QR-code login, hot-switching between multiple QQ accounts, and one-click self-check, deployment, and updates.206MIT
- AlicenseAqualityCmaintenanceEnables users to send messages, manage QQ groups and channels, upload rich media, and receive gateway events through QQ official bot OpenAPI tools. It also provides a Chinese interactive CLI for the same operations.1333 npm1MIT
- 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
- AlicenseNot gradedqualityBmaintenanceEnables an AI QQ bot to call installed plugins as MCP tools for group management, long-term memory, text-to-speech, image generation, reminders, accounting, utilities, and mini-games. It also provides a web market for installing, configuring, and managing those plugins through SnowLuma/OneBot.6MIT
- 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
- AlicenseNot gradedqualityBmaintenanceGives AI assistants OAuth-secured access to a single QQ Mail mailbox over IMAP and SMTP, letting them search, read, organize, draft, and send email with attachments. Supports folder management, flag changes, threaded replies, and forwarding through natural language.MIT
TDQS
Scored across 260 tools
The surface contains numerous near-duplicate or heavily overlapping tools: send_text/send_message/send_msg/send_private_msg/send_group_msg, forward_messages/forward_friend_single_msg/forward_group_single_msg/send_forward_msg/send_group_forward_msg/send_private_forward_msg/upload_forward_msg, share_peer/send_ark_share/share_group_ex/send_group_ark_share, fetch_emoji_like/get_emoji_likes/get_msg_emoji_likes, and delete_group_file_folder/delete_group_folder appear to do the same thing. An agent would frequently have to guess between aliases and layered wrappers (NapCat-style vs SnowLuma-style vs OneBot-style) with no clear selection rule. Some families (group info, group admin, Qzone) are distinguishable, but the messaging and forwarding clusters are badly blurred.
Names mostly use verb_noun snake_case, but the set mixes prefixes and conventions: qq_login/qq_screenshot/qq_watchdog alongside bare send_text, get_msg, poke, mark_all_as_read, plus odd forms like nc_get_user_status, do_group_album_comment, clean_cache, and duplicate aliases such as get_group_album_list vs get_qun_album_list. There is no single predictable pattern an agent can rely on, and same-purpose tools land in different naming families.
260 tools is far beyond any reasonable agent-facing surface for a QQ client; almost every OneBot action plus Qzone CGI plus raw SSO/credential helpers is exposed individually. Many tools are redundant shims (aliases, escape hatches, capability probes, stream-test helpers) that inflate the list without adding capability. The server would have been far more coherent with a scoped core of 15-25 tools plus one escape hatch.
Coverage is effectively exhaustive: messaging, media, group info/admin/files/albums, friend handling, events, and extensive Qzone read/write operations are all present, with escape hatches (onebot_call, qzone_request, send_packet) filling any remaining gap. The only completeness concerns are minor (some operations only reachable via escape hatches), so the surface itself has no obvious dead ends.