MCP server for Beaker lab automation — system provisioning, job management, distro discovery, and failure diagnosis
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-beaker","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# mcp-beaker  [](https://pepy.tech/projects/mcp-beaker) [](https://github.com/faizbawa/mcp-beaker/actions/workflows/ci.yml)   MCP server for [Beaker](https://beaker-project.org/) lab automation -- system provisioning, job management, distro discovery, and failure diagnosis. Works with any Beaker server instance. Built on [FastMCP v3](https://gofastmcp.com/) and designed for use with AI coding assistants (Cursor, Claude Desktop, etc.). ## Features - **27 tools** covering the full Beaker lifecycle: systems, jobs, distros, tasks - **Hostname filter**: list or search systems by FQDN substring (e.g. `ampere-mtsnow`), combined with availability presets (`free`/`available`/`all`) - **Beaker Py3 compatible**: works with both legacy and modernized Beaker REST APIs - **Flexible auth**: Kerberos (native GSSAPI/SPNEGO or `bkr` CLI fallback) and password (XML-RPC) - **Job XML validation**: auto-fills missing fields, infers distro families - **Failure diagnosis**: deep analysis with auto-retry on correctable failures - **10 documentation topics** exposed as MCP resources - **2 workflow prompts** for common tasks (reserve system, diagnose job) - **Generic**: works with any Beaker URL, configurable SSL/CA settings ## Installation ### Container (recommended) The container image bundles everything -- no host dependencies beyond `podman` (or `docker`). Kerberos authentication happens inside the container via `KRB5_PRINCIPAL` and `KRB5_PASSWORD` environment variables. ```bash # Pull the pre-built image from GHCR podman pull ghcr.io/faizbawa/mcp-beaker:latest # Or build locally from the repo podman build -t mcp-beaker:latest -f Containerfile . ``` ### Pip…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.