YAP — Claude Code MCP server: what it does, how to install
Compiles Linux packages across .deb, .rpm, .apk, and Arch formats using a shared PKGBUILD definition. Executes all tasks in disposable OCI containers via Docker or Podman.
claude mcp add --env YAP_VERBOSE=<YAP_VERBOSE> --transport stdio yap-yet-another-packager -- docker run -i --rm -e YAP_VERBOSE ghcr.io/m0rf30/yap-mcp:2.8.0What YAP — Yet Another Packager does
This MCP server links your coding agent to the YAP packaging tool, transforming an Arch-style PKGBUILD recipe into packages for Debian, Fedora, Alpine, and Arch distros. Distribution overrides use a double-underscore syntax such as depends__ubuntu to specify unique package names cleanly.
All builds execute inside isolated OCI containers, preventing build-time dependencies from altering your host environment. The system handles foreign CPU cross-compilation, produces SBOM sidecars in CycloneDX 1.5 or SPDX 2.3 formats, and signs packages without calling a local gpg binary.
Because every operation relies on container isolation, a functioning Docker or Podman daemon is required on your workstation.
What it helps with
- produce
.deb,.rpm,.apk, and Arch packages from one PKGBUILD - isolate compilation workloads inside Docker or Podman containers
- generate CycloneDX 1.5 and SPDX 2.3 SBOM sidecars alongside binaries
- cross-compile Linux packages for different target CPU architectures
Example prompts for the agent
- Build DEB and RPM packages defined in
yap.json - Run a build for Ubuntu Jammy using container isolation
- Generate CycloneDX SBOM sidecars for the current
PKGBUILD
How to install YAP — Yet Another Packager
Platform CLI
claude mcp add --env YAP_VERBOSE=<YAP_VERBOSE> --transport stdio yap-yet-another-packager -- docker run -i --rm -e YAP_VERBOSE ghcr.io/m0rf30/yap-mcp:2.8.0Replace <…> with your own values
Platform CLI
codex mcp add yap-yet-another-packager --env YAP_VERBOSE=<YAP_VERBOSE> -- docker run -i --rm -e YAP_VERBOSE ghcr.io/m0rf30/yap-mcp:2.8.0Replace <…> with your own values
Config file
{
"mcpServers": {
"yap-yet-another-packager": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"YAP_VERBOSE",
"ghcr.io/m0rf30/yap-mcp:2.8.0"
],
"env": {
"YAP_VERBOSE": "<YAP_VERBOSE>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"yap-yet-another-packager": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"YAP_VERBOSE",
"ghcr.io/m0rf30/yap-mcp:2.8.0"
],
"env": {
"YAP_VERBOSE": "<YAP_VERBOSE>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e YAP_VERBOSE=<YAP_VERBOSE> yap-yet-another-packager docker run -i --rm -e YAP_VERBOSE ghcr.io/m0rf30/yap-mcp:2.8.0Replace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about YAP — Yet Another Packager
How to install YAP — Yet Another Packager in Claude Code?
Run this terminal command: `claude mcp add --env YAP_VERBOSE=<YAP_VERBOSE> --transport stdio yap-yet-another-packager -- docker run -i --rm -e YAP_VERBOSE ghcr.io/m0rf30/yap-mcp:2.8.0`.
What does YAP — Yet Another Packager do?
It translates a single PKGBUILD manifest into distribution packages across DEB, RPM, APK, and Arch targets. Each build runs inside a temporary container.
What prerequisites are needed to run YAP?
You need an active Docker or Podman setup. The MCP server runs via ghcr.io/m0rf30/yap-mcp:2.8.0 and launches containerized environments for compilation.
