mcp-qzone-safe
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QZONE_CONFIG | No | Path to the configuration file. Defaults to ~/.config/qzone-safe/config.json. | |
| QZONE_STATE_DIR | No | State directory for audit/rate-limit files. Defaults to ~/.local/share/qzone-safe. | ~/.local/share/qzone-safe |
| QZONE_ONEBOT_URL | No | OneBot gateway URL. Defaults to http://127.0.0.1:3000. | http://127.0.0.1:3000 |
| QZONE_ONEBOT_TOKEN | No | OneBot access token. | |
| QZONE_PUBLISH_ENABLED | No | Set to true to enable publishing posts. Publishing is disabled by default. | false |
| QZONE_BRIDGE_STATE_DIR | No | Optional shared state directory with the host (e.g. qq-bridge). If unset, the server runs independently without host integration. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| qzone_see_postsA | 查看某个 QQ 号的最新说说（只读）。返回 tid（评论/点赞要用）、正文摘要、图片数、评论数、总条数。target_uin 必须在白名单内。 |
| qzone_commentsA | 读取某条说说下面的评论（只读）。tid 从 qzone_see_posts 拿；能翻页（pos/num）。返回每条评论的作者/时间/内容，以及楼中楼回复。 |
| qzone_likeA | 给某条说说点赞。需要 target_uin + tid（先 qzone_see_posts 拿）。同一条 24h 内只能赞一次，有频率上限。 |
| qzone_commentA | 评论某条说说，或回复某条评论（楼中楼）。需要 target_uin + tid + content。要回复评论时，额外传 comment_id + comment_uin（从 qzone_comments 拿）。≤120 字，禁止 CQ 码。同一条 24h 内只能评一次，每小时最多 3 条、每天最多 10 条。 |
| friend_listA | 查看好友名册（谁写过定义、谁还没写）。返回每个好友的 uin / 名字 / 关系 / 语气 / 备注。 |
| friend_noteA | 给一个好友写下你的定义（名字/关系/该怎么跟他说话/备注）。传了哪项就更新哪项，notes 会追加。 |
| qzone_publishC | 【当前禁用】发表说说需要管理员在配置文件里设置 publishEnabled: true 并重启本服务。 |
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 7 tools
Most tools target clearly distinct resources/actions (read posts, read comments, like, comment, list friends, write friend note). However, qzone_comment (write a comment) and qzone_comments (read comments) differ by a single 's' and both read as plausible for either meaning, a genuine misselection risk. The descriptions disambiguate once read, but the names alone do not.
A two-prefix scheme (qzone_* for post interactions, friend_* for roster operations) is readable and roughly domain-driven. But within qzone_*, forms are mixed: verb phrases (qzone_see_posts, qzone_like, qzone_publish) alongside bare nouns (qzone_comments) and a near-duplicate singular/plural pair. friend_list/friend_note are noun phrases, adding to the inconsistency.
Seven tools is well within the sweet spot for a scoped Qzone interaction server. Each tool maps to a distinct operation (view posts, view comments, like, comment, list friends, annotate friend, publish) with no filler.
The read-and-interact lifecycle is covered: fetch posts, fetch comments, like, comment/reply, plus a friend roster and note-writing flow with whitelist constraints. Gaps are minor but real: no unlike, no delete/edit of comments or posts, and qzone_publish is hard-disabled, so post creation is a deliberate dead end agents cannot work around.