Overview¶
mcp-server-jvm-build-tools lets an MCP client detect, run, and inspect Maven, Gradle, and sbt builds. The current 2.0 release-candidate contract exposes 24 public tools through stdio or optional Streamable HTTP using MCP 2025-11-25.
A client can discover a project's build tool, validate supported build files, run allowed commands, inspect bounded test and compiler diagnostics, and query dependency versions. Call tools/list for the exact input schemas in the installed JAR.
A first useful session¶
- Follow the quickstart: configure an existing allowed project root and launch the packaged server.
- Ask the client to call
detect_build_toolwith{"projectDir":"."}. The alias selects the first configured root without placing an absolute host path in a model-visible argument. - Ask for
list_build_toolsor run a supported test command withexecute_build_command. The server returns a bounded result with structured, redacted diagnostics. Raw build logs and process commands remain local.
For existing clients, read migration to 2.0 before upgrading. For each tool's scope and schema, use the current catalog.
Where the boundaries are¶
flowchart LR
A["🟣 Agent / MCP client"] -->|stdio or HTTP| B["🔵 SDK transport"]
B --> C{"🟠 Scope, root, command checks"}
C -->|allowed| D["🟢 Child build process"]
D --> E["🟢 Bounded output + redaction"]
E --> A
C -->|denied| F["🔴 Safe error"]
F --> A
classDef client fill:#eee5ff,stroke:#7c3aed,color:#24114b
classDef server fill:#dbeafe,stroke:#2563eb,color:#102a56
classDef boundary fill:#ffedd5,stroke:#ea580c,color:#512600
classDef safe fill:#dcfce7,stroke:#16a34a,color:#073b1e
classDef deny fill:#fee2e2,stroke:#dc2626,color:#4c1111
class A client
class B server
class C boundary
class D,E safe
class F deny Project roots and command checks constrain requests; they do not sandbox a build script. A build process inherits the server's OS permissions and may run other programs, access files, or use the network. Use container isolation for untrusted projects. The default stdio transport opens no listening port, but dependency lookups and build scripts may use network access. HTTP is opt-in and requires a configured bearer key and per-tool scopes.
See the architecture reference for component details and the configuration guide for local and HTTP setup.