Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
MCP server for Moodle plugin development: structural context of a Moodle install for AI agents.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account oito2, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.3.0) reached the registry 2 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, ScienceShot science reference
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
Sourced, citable answers in radiation and particle physics, photonics, electronics and quantum.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
🌐 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.