Skip to main content
Glama
BK927
by BK927

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
QQ_APP_IDNoAppID from QQ Open Platform for the official bot.
QQ_APP_SECRETNoAppSecret from QQ Open Platform for the official bot.
QQ_NAPCAT_URLNoURL of the NapCat OneBot v11 HTTP server, e.g. http://127.0.0.1:3000
QQ_STATE_PATHNoAbsolute path to the SQLite state database (or its directory). Must be the same for the MCP process and the webhook process.
QQ_ENABLE_SENDNoSet to 'true' to enable sending messages. Sending is disabled by default.false
QQ_MAX_MESSAGESNoMaximum number of messages kept for official webhook context. Default 2000, maximum 10000.2000
QQ_NAPCAT_TOKENNoAccess token configured in NapCat.
QQ_WEBHOOK_PORTNoPort for the official bot webhook server.8787
QQ_OFFICIAL_USERSNoBot‑scoped open IDs of users allowed to interact. Empty list grants no conversation access.
QQ_PERSONAL_USERSNoComma‑separated numeric QQ friend IDs allowed for personal account interaction. Unlisted users are rejected.
QQ_ENABLE_OFFICIALNoSet to 'true' to enable the official QQ bot provider.false
QQ_ENABLE_PERSONALNoSet to 'true' to enable the personal account provider via NapCat.false
QQ_OFFICIAL_GROUPSNoBot‑scoped open IDs of groups allowed to interact. Empty list grants no conversation access.
QQ_PERSONAL_GROUPSNoComma‑separated numeric QQ group IDs allowed for personal account interaction. Unlisted groups are rejected.
QQ_RETENTION_SECONDSNoRetention time in seconds for official webhook context. Default 86400 (24 hours), maximum 604800 (7 days).86400
QQ_ALLOW_REMOTE_NAPCATNoSet 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 5 tools

Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues