arvindand/maven-tools-mcp

Maven Tools MCP Server gives MCP-capable clients a practical way to inspect JVM dependencies using live Maven Central data.
It is built for developers and agents that need more than a plain version lookup: stability filtering, upgrade comparisons, dependency health signals, license data, CVE checks, and optional documentation lookups through Context7.
What It Helps With
- **Version checks:** find stable releases and compare upgrades with major/minor/patch context.
- **Dependency audits:** inspect age, release cadence, known vulnerabilities, and license data.
- **POM analysis:** resolve declared dependency versions through parents and BOMs without building the project.
- **Upgrade planning:** get structured edits an agent can validate and apply, with major upgrades, conflicts, and overrides flagged for review.
- **Documentation:** look up library docs through the optional Context7 tools.
Coordinate-based tools work with Maven, Gradle, SBT, and Mill projects. The POM analysis and upgrade-planning tools take Maven pom.xml files.
Quick Start
**Prerequisite:** Docker installed and running. No local Java installation is required. For a Docker-free setup, see building and running the JAR.
Claude Desktop
Add the maven-tools entry to your Claude Desktop config (see config file locations):
VS Code + GitHub Copilot
Add the following server to .vscode/mcp.json in your workspace:
Image Variants
| Tag | Transport | Context7 | Best For |
|-----|-----------|----------|----------|
| :latest | STDIO | Yes | Default desktop MCP usage |
| :latest-noc7 | STDIO | No | Networks where Context7 is blocked or not wanted |
| :latest-http | HTTP | Yes | Streamable HTTP clients and sidecar workflows |
The current release is v3.2.3. For version-pinned setups, use :3.2.3, :3.2.3-noc7 or :3.2.3-http; each supports Linux AMD64 and ARM64.
CONTEXT7_API_KEY is optional. Most setups can start without it. If your environment requires Context7 auth, or you want to avoid anonymous limits, pass it through Docker with -e CONTEXT7_API_KEY.
For fuller setup guidance, including JAR and native-container usage, Docker Compose, and environment notes, see docs/setup.md.
Available Tools
The default image exposes 11 MCP tools; -noc7 exposes the 9 core tools.
Maven intelligence tools
| Tool | What It Does |
|------|---------------|
| get_latest_version | Find the latest version with stability-aware selection |
| check_version_exists | Verify a specific version and classify its stability |
| check_multiple_dependencies | Bulk lookup for dependency coordinates |
| compare_dependency_versions | Compare current versions against available upgrades |
| analyze_dependency_age | Classify how old a dependency is |
| analyze_release_patterns | Look at release cadence and maintenance signals |
| analyze_project_health | Run a broader dependency health audit |
| analyze_pom_dependencies | Resolve declared dependency versions, identify their source, and surface BOM conflicts |
| recommend_pom_upgrades | Produce actionable POM upgrade recommendations and flag changes needing review |
Context7 documentation tools
| Tool | What It Does |
|------|---------------|
| resolve_library_id | Find a documentation library identifier |
| query_docs | Fetch docs by Context7 library ID |
For parameters, examples, and tool-by-tool notes, see docs/tools.md.
POM-aware dependency analysis
Both POM tools use **Apache Maven Model Builder** for parent inheritance, properties, and dependency management, including imported BOMs. They accept raw POM XML and an optional sideloadedPoms bundle for unreleased parents or sibling modules.