Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
MCP server for Moodle plugin development: structural context of a Moodle install for AI agents.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
链接指向作者自己的文件;我们不托管也不重新打包它。打开文件后,Claude Desktop 会进行安装。
在终端中运行这条命令
浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 oito2 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(1.3.0)于前天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。
同一分类中有:Spec Driven Development, Remote Desktop Commander, arr-mcp
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
One server, 40 tools, the whole media stack: *arrs, Jellyfin, Plex, Seerr, Cleanuparr, downloaders
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
🌐 Language: English · Português
An MCP (Model Context Protocol) server that gives AI assistants structural understanding of a Moodle installation and its plugins, so they can answer questions about the codebase and build plugins that follow its real conventions. Distributed as a single static binary.
Point build82 at a Moodle installation and it scans the codebase (version.php, db/*.php, XMLDB schemas, PHPDoc, hooks, tasks, capabilities, web services...) and generates a set of Markdown context files describing the installation and any plugin you're developing. An AI assistant connected to it can then answer questions about the codebase, scaffold new plugins consistently with existing conventions, and keep the docs in sync as you work.
Main features:
doctor), check the Moodle coding style (with phpcs), package a plugin for release, create a new plugin skeleton, and bump a plugin's version with its upgrade step..build82/ (at the Moodle root and at each plugin's root), never loose in the Moodle or plugin root.Prerequisites:
universal-ctags on PATH, to also generate a .build82/tags file for editor navigation.phpcs with the Moodle coding standard (composer global require moodlehq/moodle-cs), for the check_coding_style tool.Download a release binary (no Go toolchain required). Every release ships a checksums.txt — verify it before trusting a downloaded binary. From v1.1.0 checksums.txt is also signed with Sigstore and every binary carries a GitHub build provenance attestation (how to verify). Full step-by-step guide with checksum verification and troubleshooting: Installation Guide.
🐧 Linux
# amd64
curl -LO https://github.com/oito2/mcp-build82/releases/latest/download/build82_linux_amd64 curl -LO https://github.com/oito2/mcp-build82/releases/latest/download/checksums.txt sha256sum -c checksums.txt --ignore-missing \ && chmod +x build82_linux_amd64 \ && sudo mv build82_linux_amd64 /usr/local/bin/build82
curl -LO https://github.com/oito2/mcp-build82/releases/latest/download/build82_linux_arm64 curl -LO https://github.com/oito2/mcp-build82/releases/latest/download/checksums.txt sha256sum -c checksums.txt --ignore-missing \ && chmod +x build82_linux_arm64 \ && sudo mv build82_linux_arm64 /usr/local/bin/build82
build82 --version
🍎 macOS
Check your chip with uname -m (arm64 = Apple Silicon, x86_64 = Intel):
# Apple Silicon (M1/M2/M3/M4)
curl -LO https://github.com/oito2/mcp-build82/releases/latest/download/build82_darwin_arm64 curl -LO https://github.com/oito2/mcp-build82/releases/latest/download/checksums.txt shasum -a 256 -c checksums.txt --ignore-missing \ && chmod +x build82_darwin_arm64 \ && sudo mv build82_darwin_arm64 /usr/local/bin/build82
curl -LO https://github.com/oito2/mcp-build82/releases/latest/download/build82_darwin_amd64 curl -LO https://github.com/oito2/mcp-build82/releases/latest/download/checksums.txt shasum -a 256 -c checksums.txt --ignore-missing \ && chmod +x build82_darwin_amd64 \ && sudo mv build82_darwin_amd64 /usr/local/bin/build82
The binary isn't notarized by Apple, so Gatekeeper will refuse to run it the first time — clear the quarantine flag: xattr -d com.apple.quarantine /usr/local/bin/build82.
🪟 Windows
On Windows on Arm, use build82_windows_arm64.exe in every command below.
Invoke-WebRequest -Uri "https://github.com/oito2/mcp-build82/releases/latest/download/build82_windows_amd64.exe" -OutFile "build82_windows_amd64.exe"
Invoke-WebRequest -Uri "https://github.com/oito2/mcp-build82/releases/latest/download/checksums.txt" -OutFile "checksums.txt" Get-FileHash .\build82_windows_amd64.exe -Algorithm SHA256
Compare the printed Hash with the build82_windows_amd64.exe line in checksums.txt; continue only if they match:
Unblock-File .\build82_windows_amd64.exe
New-Item -ItemType Directory -Force -Path "$env:LOCALAPPDATA\build82" Move-Item -Force .\build82_windows_amd64.exe "$env:LOCALAPPDATA\build82\build82.exe"
Restart your terminal and run build82 --version to confirm it's on your PATH. The binary isn't code-signed; Unblock-File above keeps SmartScreen from blocking the first run ("Windows protected your PC") — if it still appears, click More info → Run anyway.
Or build from source (requires Go 1.26+):
go install github.com/oito2/mcp-build82/cmd/build82@latest
Register build82 as an MCP server in your AI tool:
build82 install [target]
It detects which supported tools are installed and prompts for the Moodle path. Run it without a target to configure every tool found, or pass one explicitly: claude (Claude Code), claude-desktop, antigravity, codex, opencode, cursor, zed, cline. Close the client first: install edits a configuration file the client also writes.
For example, with Claude Code you can also register it manually:
claude mcp add --scope user build82 -e BUILD82_MOODLE_PATH=/path/to/moodle -- /usr/local/bin/build82
Claude Desktop can also install build82 as a desktop extension: every release ships a build82.mcpb bundle with the binaries included — see Claude Desktop. build82 is also listed in the official MCP Registry as io.github.oito2/mcp-build82.
Per-client guides, including manual configuration: MCP Clients. To remove it: build82 uninstall [target] — see Uninstallation.
build82 self-update --check # report whether a newer release exists (exit 10 if so), without installing it
build82 self-update # download, verify, and install the latest release build82 self-update --require-signature # refuse to update unless cosign can verify the release signature build82 self-update --rollback # restore the previous binary if the new version turns out to be broken
Downloads come only from this repository's release on GitHub. When cosign v3 or later is on PATH, the release's signature is verified first; without it, a warning is printed and only the checksum is checked. Every download is checksum-verified against the release's checksums.txt and smoke-tested before the running binary is replaced; the previous binary is kept as .bak, and --rollback swaps the two (so running it again undoes it). If no backup exists, or the backup does not run, it fails with a clear error and nothing is changed. Details: CLI reference.
The full documentation site lives in docs/en/index.md (also in Portuguese). Main entry points:
Contributing: see CONTRIBUTING.md for the development workflow and release process, and the Code of Conduct.
This project was developed with the assistance of generative AI tools:
GPL-3.0 — see LICENSE.