QMYZ MCP Server

QMYZ MCP MCP server exists for a simple reason — assistants are far more useful when they can act on QMYZ MCP directly instead of describing what you should do. 1. 克隆仓库： bash git clone https://github.com/shibig666/QMYZ-MCP.git cd QMYZ-MCP .

What the assistant can call

Once QMYZ MCP is connected, these are the calls the assistant has available:

• sub_descript — 题目描述
• sub_type — 题目类型
• options — 选项内容（A、B、C、D等）
• option_count — 选项数量
• uuid — 题目唯一标识符
• JSESSIONID — YOUR_JSESSIONID
• get_courses — The get_courses tool exposed by this server
• get_question — The get_question tool exposed by this server
• submit_question — The submit_question tool exposed by this server

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. QMYZ MCP's toolset — sub_descript, sub_type, options and 6 more — is a fair guide to whether it matches your workflow. It is maintained by shibig666; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against QMYZ MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch QMYZ MCP.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the qmyz mcp mcp server does with a few real requests.