qzone-mcp
qzone-mcp
Independent local MCP wrapper for astrbot_plugin_qzone_ultra + NapCat.
This is an independent community integration. It is not affiliated with, endorsed by, or maintained by QZoneUltra, NapCatQQ, AstrBot, or Tencent.
Architecture:
Codex -> MCP (stdio) -> adapter -> QzoneUltra daemon (127.0.0.1) -> QZone
NapCat (127.0.0.1) -> credentials -> adapter -> daemon /bind
The Ultra source is treated as an external dependency and is not modified or copied into this project.
Credits and licensing
astrbot_plugin_qzone_ultra is an external runtime dependency by 雪碧bir, licensed under MIT. Its source is not bundled in this repository.
NapCatQQ supplies the external QQ login and OneBot runtime. Its source and binaries are not bundled in this repository. Users must install it separately and comply with its own Limited Redistribution License, including its non-commercial-use terms.
This MCP wrapper is licensed under the MIT license in LICENSE.
See THIRD_PARTY_NOTICES.md for the exact upstream references used by this project.
Safety boundary
NapCat and Qzone daemon URLs are rejected unless they use
127.0.0.1orlocalhost.Cookie/CSRF values are only used internally for daemon binding.
MCP results are recursively sanitized to remove credential-like keys.
Cookie values are not intentionally logged.
Install
Keep/clone QzoneUltra somewhere on disk and install its own requirements there.
Install this MCP:
cd D:\qzone-mcp
python -m pip install -e .Set environment variables from
.env.examplein your Codex MCP configuration.
Example Codex MCP config:
[mcp_servers.qzone]
command = "python"
args = ["-m", "qzone_mcp"]
[mcp_servers.qzone.env]
NAPCAT_URL = "http://127.0.0.1:3000"
NAPCAT_TOKEN = "YOUR_NAPCAT_TOKEN"
QZONE_ULTRA_ROOT = "D:\\path\\to\\astrbot_plugin_qzone_ultra"
QZONE_DATA_DIR = "D:\\qzone-mcp-data"
QZONE_MEDIA_ROOT = "D:\\qzone-mcp-media"
QZONE_DAEMON_PORT = "18999"
QZONE_AUTO_START_DAEMON = "true"
QZONE_AUTO_BIND = "true"If an Ultra daemon is already running, set QZONE_DAEMON_SECRET to the same secret and optionally set QZONE_AUTO_START_DAEMON=false.
First test
Ask Codex to call qzone_status first. It should verify:
local daemon reachable;
NapCat returns the logged-in QQ number;
QZone cookie exists;
p_skeyexists if NapCat exposes the required QZone cookie;daemon accepts the internal bind.
Only after that call qzone_publish.
Tools in v0.3
qzone_statusqzone_list_postsqzone_get_postqzone_publish(direct publish; text + multiple local images)qzone_prepare_publish(preview only; returns one-time confirmation token)qzone_confirm_publish(publishes a prepared preview)qzone_likeqzone_unlikeqzone_commentqzone_reply_commentqzone_deleteqzone_visitors
Video is intentionally left out of the first version.
v0.2 notes
Keeps the existing direct publish flow unchanged.
Adds an optional two-step preview/confirm publish flow to reduce accidental posts.
Retries once with a fresh NapCat QZone credential bind when the daemon reports an authentication/login failure.
Tightens local-only URL validation using parsed loopback hostnames (including
::1) instead of string prefixes.Multi-image input continues to use the existing
images: list[str]path and is validated againstQZONE_MEDIA_ROOT.QZONE_PUBLISH_PREVIEW_TTLcontrols preview-token lifetime in seconds (default600).
v0.3 notes
Keeps all v0.2 behavior and APIs unchanged.
Confirms feed listing, post detail, comments, replies, delete, and like flows are exposed as MCP tools.
Adds a dedicated
qzone_unliketool so agents do not need to rememberunlike=true.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/inzzou/qzone-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server