Build Tools MCP Server

Exposes JVM build tools via the Model Context Protocol, enabling interaction using natural language.

Local serverstdio

What is the Build Tools MCP Server?

Exposes JVM build tools via the Model Context Protocol, enabling interaction using natural language.

The short version

📖 Website: https://thepragmatik.github.io/mcp-server-jvm-build-tools/ — full docs, 30 MCP tools, MCP-RC features, and protocol evidence

  • Multi build tool — — runs Maven, Gradle, and SBT builds through a single server and a single API
  • Auto-detection — — scans for pom.xml, build.gradle(.kts), settings.gradle(.kts), and build.sbt with no manual config
  • Unified API — — same execute_build_command call for every build tool, no context-switching
  • Dependency tools — — check_dependency_version for fast Maven Central lookups
  • Security hardening — — shell injection blocking, dangerous flag blocking, path canonicalization, input validation
  • Gradle wrapper support — — auto-detects and uses gradlew; falls back to system Gradle

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Maintainer setup documentation.

How to install the Build Tools MCP Server

{
  "mcpServers": {
    "jvm-build-tools": {
      "command": "java",
      "args": [
        "-Dbuildtools.projects.allowed-roots=/workspace/projects",
        "-jar",
        "/opt/jvm-build-tools/server.jar"
      ]
    }
  }
}

From the project documentation. Replace placeholders and example paths before connecting.

Example prompts to try

  • “Use Build Tools to Maven.”
  • “Use Build Tools to Gradle.”
  • “Use Build Tools to SBT.”

Frequently asked questions

You need to add the Build Tools MCP server configuration to your Claude's `claude_desktop_config.json` file, specifying the path to your Java and Maven installations, and the location of the Build Tools JAR file. Restart Claude after making the changes.