Best for
- JVM projects using Gradle or Maven.
- AI coding agents that need structured data directly.
- Reducing token consumption from build tools.
P
Pare Jvm
Community
Structured Gradle & Maven build tool operations as typed JSON for AI agents.
GitHub source repository ↗
43FMRS · D
The server provides a structured, token-efficient wrapper for JVM build tools within the Pare ecosystem. It is suitable as a general-purpose Gradle/Maven MCP server, but is not officially maintained by the upstream build tool vendors. Setup is straightforward via npx and it is compatible with multiple MCP clients.
Pare JVM is an MCP server within the Pare family that targets JVM build tools. It wraps Gradle and Maven command-line tools and returns clean, schema-validated JSON instead of raw terminal text, providing typed data that agents can act on directly without brittle string parsing. It leverages MCP's structuredContent and outputSchema features to deliver type-safe, validated data. The server is distributed as an npm package @paretools/jvm and communicates via stdio.
Tools
The tool list has not been reviewed yet.
Setup
Configure the server in your MCP client using the provided JSON config. Add an mcpServers entry with command 'npx', args ['-y', '@paretools/jvm']. Ensure Node.js 20 or higher is installed.
claude_desktop_config.json
{
"mcpServers": {
"pare-jvm": {
"command": "npx",
"args": [
"-y",
"@paretools/jvm"
]
}
}
}
Fit and risk
Not for
- Projects that do not use JVM build tools.
- Advanced build scenarios requiring non-standard CLI output.
- Build operations that require interactive terminal or TTY.
Required permissions
- Ability to execute Gradle and Maven commands.
- Read access to project files and build configurations.
- Network access to download dependencies if needed.
- Permissions to create, modify, and delete build artifacts and temporary files.
Risks and side effects
- Executing build commands may modify project files (e.g., generated files, clean target directories).
- Potential unintended build/test execution if commands are unrestricted.
- Potential loss of build cache or unsaved work.
- Risk from running in untrusted repositories; ensure project source is trusted.
Troubleshooting
- Check Node.js version is 20 or higher.
- Verify npx is in PATH, or use 'cmd /c npx' on Windows.
- Run `npx -y @paretools/jvm` to pre-cache the package.
- If connection times out, increase the client's initTimeout.
- Use environment variables to limit tools and reduce context usage.
Use cases
Reliable Gradle build, test, and dependency management for AI agents.
Reliable Maven build, test, and dependency management for AI agents.
Consuming structured build results in agent workflows without parsing terminal text.
Supported clients
Claude DesktopFull support
Claude CodeFull support
CursorFull support
VS CodeFull support
WindsurfFull support
ClineFull support
Roo CodeFull support
OpenAI CodexFull support
Gemini CLIFull support
ZedFull support