YAP — Yet Another Packager
Drive reproducible .deb/.rpm/.apk/.pkg.tar.zst builds from one PKGBUILD definition through MCP tools and prompts.
Overview
YAP is a Ship-phase MCP server that builds native Linux packages across distros from a PKGBUILD using 19 packaging and CI-style tools.
What is this MCP server?
- 19 MCP tools including validate, parse_pkgbuild, graph, build, build_status, build_wait, build_logs, list_artifacts, ins
- 3 MCP prompts: build_single_pkg, cross_compile, sign_and_release
- 2 resources: yap://distros and yap://pkgbuild/{path}
- OCI image ghcr.io/m0rf30/yap-mcp:2.3.2 with stdio transport; multi-distro list_distros / resolve_distro
- Version 2.3.2
Community signal: 21 GitHub stars.
What problem does it solve?
You maintain one app but dread maintaining separate packaging scripts for Debian, RPM, Alpine, and Arch artifacts.
Who is it for?
Indie maintainers and small teams releasing CLI or server binaries who want agent-driven packaging with MCP observability.
Skip if: Pure SaaS deploys to Vercel only, mobile store builds, or developers unwilling to run OCI-based packaging tooling.
What do I get? / Deliverables
After wiring yap-mcp, your agent can validate, build, monitor, and collect multi-format packages from a unified PKGBUILD workflow.
- Built native packages per selected distro
- Build logs, status, and artifact listings via MCP
- Graph/inspect views of package dependencies
Recommended MCP Servers
Journey fit
How it compares
Multi-distro packager MCP, not a generic Dockerfile generator or unit-test skill.
Common Questions / FAQ
Who is YAP for?
Linux-focused builders who release .deb, .rpm, .apk, or .pkg.tar.zst artifacts and want MCP tools to drive YAP from Claude Code or similar hosts.
When should I use YAP?
Use it in Ship/Launch when you need validated builds, logs, artifact lists, or cross-compile/sign-release prompts before publishing packages.
How do I add YAP to my agent?
Register the stdio MCP server using OCI image ghcr.io/m0rf30/yap-mcp:2.3.2 in your MCP config and set YAP_VERBOSE=1 only when debugging.