JVM Build Tools MCP Server¶
Run and inspect Maven, Gradle, and sbt builds through one Model Context Protocol server. The 2.0 release candidate exposes 24 public tools over local stdio or optional Streamable HTTP.
Download the published v2.0.0-rc.2 JAR or read its release notes. This prerelease includes the structured build-result contract, bounded Maven metadata checks, and privacy-safe aggregate dependency security results.
-
Start a build
Follow the 2.0 quickstart to set a project root, launch the packaged JAR, and detect your first build tool.
-
Keep results private
Read the configuration guide for project boundaries, HTTP scopes, and bounded, redacted diagnostics.
-
Upgrade from 1.x
Check the migration guide before changing an existing client or automation.
-
Understand the design
Browse the architecture, current tool catalog, and release gates.
flowchart LR
A["🟣 MCP client"] -->|stdio or scoped HTTP| B["🔵 Server + SDK"]
B --> C{"🟠 Project and command checks"}
C -->|allowed| D["🟢 Maven · Gradle · sbt"]
D --> E["🟢 Bounded, redacted diagnostics"]
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 Build scripts still run with the server process's operating-system permissions. A configured project root limits accepted paths; it does not sandbox untrusted code. See container isolation for a stronger boundary. The server keeps raw build logs and commands local; model-visible results contain bounded, redacted diagnostics. A client or user can still send private text in a prompt, so review what you share.
Looking for implementation details? Start with the 2.0 design review and developer workflow. Older 1.x examples and specs are labeled as historical reference.