Skip to content
Théophile Diot
fren
Navigation menu
fren
All work

2025-presentOpen source authoringAuthor and maintainer

BunkerWeb MCP

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

BunkerWeb MCPDecision 1 of 4

Decision
Map API operations to typed tools with strict input validation.
Consequence
Each API change has to be mirrored in a tool definition before any client can use it.

BunkerWeb MCPDecision 2 of 4

Decision
Use the existing authenticated API instead of adding a second privilege model.
Consequence
The server can never offer more than that API already allows, including where its limits are inconvenient.

BunkerWeb MCPDecision 3 of 4

Decision
Return structured resources that remain useful without a custom visual client.
Consequence
Responses carry structure a purpose-built interface would have supplied, so they are more verbose to read.

BunkerWeb MCPDecision 4 of 4

Decision
Keep optional semantic search separate from the built-in tool surface.
Consequence
Two 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