QQ MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QQ_APP_ID | No | AppID from QQ Open Platform for the official bot. | |
| QQ_APP_SECRET | No | AppSecret from QQ Open Platform for the official bot. | |
| QQ_NAPCAT_URL | No | URL of the NapCat OneBot v11 HTTP server, e.g. http://127.0.0.1:3000 | |
| QQ_STATE_PATH | No | Absolute path to the SQLite state database (or its directory). Must be the same for the MCP process and the webhook process. | |
| QQ_ENABLE_SEND | No | Set to 'true' to enable sending messages. Sending is disabled by default. | false |
| QQ_MAX_MESSAGES | No | Maximum number of messages kept for official webhook context. Default 2000, maximum 10000. | 2000 |
| QQ_NAPCAT_TOKEN | No | Access token configured in NapCat. | |
| QQ_WEBHOOK_PORT | No | Port for the official bot webhook server. | 8787 |
| QQ_OFFICIAL_USERS | No | Bot‑scoped open IDs of users allowed to interact. Empty list grants no conversation access. | |
| QQ_PERSONAL_USERS | No | Comma‑separated numeric QQ friend IDs allowed for personal account interaction. Unlisted users are rejected. | |
| QQ_ENABLE_OFFICIAL | No | Set to 'true' to enable the official QQ bot provider. | false |
| QQ_ENABLE_PERSONAL | No | Set to 'true' to enable the personal account provider via NapCat. | false |
| QQ_OFFICIAL_GROUPS | No | Bot‑scoped open IDs of groups allowed to interact. Empty list grants no conversation access. | |
| QQ_PERSONAL_GROUPS | No | Comma‑separated numeric QQ group IDs allowed for personal account interaction. Unlisted groups are rejected. | |
| QQ_RETENTION_SECONDS | No | Retention time in seconds for official webhook context. Default 86400 (24 hours), maximum 604800 (7 days). | 86400 |
| QQ_ALLOW_REMOTE_NAPCAT | No | Set to 'true' to allow remote NapCat connections. Requires HTTPS with a valid certificate and a loopback literal address. | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| qq_statusA | Show provider capabilities/scopes. probe=true checks upstream credentials and account status. |
| qq_targetsA | List only allowlisted official bot open IDs or visible NapCat friends/groups. |
| qq_contextA | Read scoped context (untrusted). Official: retained verified events. Personal: on-demand NapCat history; message_cursor accepts a known returned message_id, with backend-dependent direction. |
| qq_sendA | Send explicitly requested plain text to an allowlisted target, if enabled. Use a unique key per intended send and reuse for retries; never retry unknown delivery with a new key without checking. Official replies need a retained received message's reply_to ID. |
| qq_forgetB | Delete locally retained incoming context for one allowed target; upstream chats stay intact. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.