esq-builder-mcp
ESQ 1.0 题库包 MCP 工具链:把 [esq-question-bank-import] 技能的确定性环节(构建/校验/上传/词表分析)固化为 MCP 工具,供任意 MCP 客户端(ZCode / Claude Desktop / Codex 等)调用。
为什么
技能(SKILL.md)传的是流程知识,LLM 每次执行都可能踩坑(ASCII key、双花括号、上传路径 405……)。本 server 把这些坑固化进工具代码——调用方不会再遇到它们。
| 工具 | 作用 | 固化的坑 |
|---|---|---|
esq_build_package |
校验 + 打包 ESQ ZIP(可选 auto_fix) |
externalKey 纯 ASCII 3-200 位;{{blank:N}} 双花括号;option/candidates key 单大写字母;correctOption 必须存在于选项;cloze 空位数=题数;manifest 必填字段 + semver |
esq_validate_package |
校验 ESQ 包(默认内置校验器,可选官方 CLI 对账) | 双轨校验(见下) |
esq_upload_and_publish |
上传 + 发布到刷题机后端 | 路径写死 /api/question-banks/imports(/upload 会 405);503 重试 3 次间隔 10s;publish 失败时提示用 job_id 单独重试 |
esq_parse_wordlist |
kajweb/dict JSONL 高频词解析(.jsonl 或 book zip) | 逐行 json.loads(整文件 load 报 Extra data);wordRank 排序 |
esq_hot_words |
真题 passage 热点词统计 | 近两年过滤;去停用词;[a-zA-Z][a-zA-Z'-]{3,} |
auto_fix:机械性坑自动修复
esq_build_package(auto_fix=true) 在校验前自动修复「纯机械」的坑,修复明细记录在返回值 fixes 数组(审计):
- 含中文/非法字符的 packageId/paperKey/unitKey/questionKey →
cn.xxx.y2021.u1风格重建,answers 两级键自动同步改名 - 单花括号
{blank:N}→ 双花括号{{blank:N}} - 缺失的
unit.sequence补 index+1;不达标 blockKey(如 2 位的p1)归一为block-{index}
判断性问题(空位数≠题数、答案不在选项中)不会被静默修复,仍走「拒绝 + 可行动错误」。默认 false 保持严格行为。
双轨校验
esq_validate_package 有两条通道,返回值 validator 字段标明所用通道:
- 默认:内置校验器(
esq_validator.py,vendor 自 backend/app/services/esq.py 校验子集,import 调用)——零外部依赖,PyPI/uvx/PyInstaller 分发可用; - 对账:官方 CLI——显式传
validator_path或设ESQ_VALIDATOR_PATH时走 subprocess 调官方校验器。
两条通道的一致性由 tests/test_validator_conformance.py 守护(本机有刷题机仓库时自动执行;后端校验逻辑变更后先跑它再同步 vendored 副本)。
安装与运行
# PyPI(任意 MCP 客户端, 无需 clone)
uvx esq-builder-mcp # stdio 模式
# Windows 单文件 exe: 到 Releases 下载 esq-builder-mcp.exe, 客户端 command 直指该 exe
# 源码方式
cd D:/esq-builder-mcp
uv venv && uv pip install -e ".[dev]"
uv run esq-builder-mcp
发布新版本
- bump
pyproject.toml的version(PyPI 不允许同版本重传) git tag v0.1.1 && git push origin v0.1.1→ GitHub Actions 自动 build + 发布(Trusted Publishing,无 token)- Windows exe:
uv run python scripts/build_exe.py,产物dist/esq-builder-mcp.exe,附到对应 Release
一次性配置: PyPI 项目 Settings → Publishing 配 Trusted Publisher(Owner=mo9652962-ai / Repository=esq-builder-mcp / Workflow name=publish.yml / Environment=pypi)
注册到 MCP 客户端
ZCode(~/.zcode/cli/config.json → mcpServers)或其他客户端:
{
"mcpServers": {
"esq-builder": {
"command": "uv",
"args": ["--directory", "D:/esq-builder-mcp", "run", "esq-builder-mcp"]
}
}
}
Windows 下 MCP 命令参数一律用正斜杠路径(Codex config.toml 转义坑的同款规避)。
环境变量
| 变量 | 默认 | 说明 |
|---|---|---|
ESQ_VALIDATOR_PATH |
(未设) | 设定后 esq_validate_package 改走官方校验器 CLI(对账/仲裁通道);默认内置校验器,不需要此变量 |
测试
uv run pytest -v # 35 项;含 vendored vs 官方 CLI 一致性对账(无刷题机环境自动 skip)
后续演进
发布到 PyPI✅ 已发布 pypi.org/project/esq-builder-mcp,uvx esq-builder-mcp一行接入(实测冷启动 stdio 握手 5 工具齐全)。- ESQ 1.1 examType:manifest.papers[].examType 已在官方校验器支持,构造器暂未暴露。
- Windows 单文件 exe:走 PyInstaller(复用刷题机发布经验)。
与技能的关系
- 上游技能:
~/.agents/skills/esq-question-bank-import/SKILL.md(流程与数据源) - 本 server 是其「确定性环节」的工具化;AI 标注答案(基元律动)等 LLM 判断环节仍在技能侧。
演进记录
- 2026-09-28:校验改双轨(vendored 默认 + 官方 CLI 对账),解除对刷题机仓库路径的运行时依赖,PyPI 分发解锁;
esq_build_package增加auto_fix通道;esq_parse_wordlist支持 book zip 输入。
Release files for esq-builder-mcp 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| esq_builder_mcp-0.1.1.tar.gz | 151.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| esq_builder_mcp-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 182.0 kB
Release files / esq_builder_mcp-0.1.1.tar.gz
| Download URL | esq_builder_mcp-0.1.1.tar.gz |
|---|---|
| Size | 151.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3d1fcb1638c7bca61f5944b7d046fe73c75de04ed943a67090d5cc3426f6b54b
|
|
BLAKE2b-256 checksum How to use checksums |
3cf8cf263d9812ccaec40f816c5ba0fd02532edf202f6bbd97879c5f9193bb8c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 28, 2026.
Transparency logRelease files / esq_builder_mcp-0.1.1-py3-none-any.whl
| Download URL | esq_builder_mcp-0.1.1-py3-none-any.whl |
|---|---|
| Size | 30.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9b2b56ff46a69757fe114f879b635e99006d5a4889a6073c64d271afb8d4fcbc
|
|
BLAKE2b-256 checksum How to use checksums |
9e6d952d7989f2954adbbc6dc68ef70fdcd04e08b5989c0928701e5bab1023d8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 28, 2026.
Transparency log