BunkerWeb MCP
Open source authoring / 2025-present
A Python Model Context Protocol (MCP) server that exposes the BunkerWeb API through constrained tools and resources.
The problem
An AI client needs a narrow, reviewable interface to infrastructure. Giving it raw configuration access would make ordinary operator questions harder to validate and easier to overreach.
Decisions
Map API operations to typed tools with strict input validation.
CostEach API change has to be mirrored in a tool definition before any client can use it.
Use the existing authenticated API instead of adding a second privilege model.
CostThe server can never offer more than that API already allows, including where its limits are inconvenient.
Return structured resources that remain useful without a custom visual client.
CostResponses carry structure a purpose-built interface would have supplied, so they are more verbose to read.
Keep optional semantic search separate from the built-in tool surface.
CostTwo surfaces to document and reason about, and search improvements do not reach a default install.
Outcome
Operators and compatible AI clients can inspect and manage BunkerWeb through an explicit protocol surface rather than editing configuration blindly.
Evidence and scope
Looking for a collaborator?
Share the work and its constraints. I reply by email.