← Back to directory
M

Maven Tools MCP Server

Community
JVM dependency intelligence for AI assistants via Maven Central.
GitHub source repository ↗
★ 32 Stars Category · Dev Tools Popular Source revision 550c8ec70d59
69FMRS · C

Maven Tools MCP Server offers robust dependency intelligence for AI assistants, leveraging live Maven Central data. With 11 tools, it covers version checks, upgrade comparisons, and POM-level analysis, making it valuable for developers and agents. It supports multiple image variants (standard, no-Context7, HTTP) and Docker deployment. As a non-official but high-quality open-source project, it provides clear benefits for dependency maintenance and automation.

Reliability
11/20
Security and permissions
14/20
Maintenance
14/20
Documentation
16/20
Setup experience
14/20
Read the FMRS scoring method →

Maven Tools MCP Server provides MCP-capable clients with practical inspection of JVM dependencies using live Maven Central data. It offers stability filtering, upgrade comparisons, dependency health signals, license data, CVE checks, and optional documentation lookups through Context7. It supports POM-level analysis, resolving effective versions across parent chains, dependency management, and BOM imports without building the project, and produces deterministic upgrade plans. Works for any JVM build tool that relies on Maven Central, including Maven, Gradle, SBT, and Mill.

Tools

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 effective versions from raw pom.xml, classify dependencies as EXPLICIT/MANAGED/EXPLICIT_OVERRIDE, and surface multi-BOM conflicts.
recommend_pom_upgrades
Return deterministic and attention-needed upgrade actions for an agent to apply.
resolve-library-id
Find a documentation library identifier in Context7.
query-docs
Fetch docs by Context7 library ID.

Setup

Add to Claude Desktop config:
{
"mcpServers": {
"maven-tools": {
"command": "docker",
"args": ["run", "-i", "--rm", "arvindand/maven-tools-mcp:latest"]
}
}
}

Or create .vscode/mcp.json in VS Code:
{
"servers": {
"maven-tools": {
"type": "stdio",
"command": "docker",
"args": ["run", "-i", "--rm", "arvindand/maven-tools-mcp:latest"]
}
}
}

claude_desktop_config.json
{
  "mcpServers": {
    "maven-tools": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "arvindand/maven-tools-mcp:latest"]
    }
  }
}

Fit and risk

Best for

  • Developers needing quick access to Maven Central dependency data in IDE
  • JVM projects with complex parent/BOM dependency management
  • Automated dependency upgrade workflows with AI agents
  • CI pre-checks for dependency updates
  • Scenarios requiring health, CVE, and license signals

Not for

  • Fully offline use (uncached queries require Maven Central access)
  • Replacing build tools like Maven or Gradle
  • Dependencies not resolved via Maven Central (e.g., private repos)
  • Automatically creating pull requests (server does not open PRs directly)

Required permissions

  • Network access to Maven Central (required)
  • Optional CONTEXT7_API_KEY environment variable (optional, most setups work without)
  • Access to local pom.xml files to analyze if needed
  • Docker runtime permissions if running as container

Risks and side effects

  • Dependency on external network; functionality unavailable if Maven Central is unreachable
  • Context7 integration adds an external dependency; use :latest-noc7 variant if needed
  • Not an official Maven Central or Context7 product; third-party server
  • Analysis based on public metadata may not reflect local environment specifics
  • Docker image should be from trusted source to avoid supply-chain threats

Troubleshooting

  1. Check network connectivity and access to Maven Central
  2. If Context7 fails, try the latest-noc7 image variant
  3. For custom CA certificates in corporate networks, refer to documentation
  4. Ensure Docker run includes -i and --rm flags
  5. See docs/troubleshooting.md for common issues

Use cases

Check latest stable versions of libraries without leaving the editor
Compare current dependency set against available upgrades
Audit projects for stale, risky, or weakly maintained dependencies
Resolve entire pom.xml into effective versions for each dependency
Generate deterministic upgrade plans for agent-driven dependency maintenance

Supported clients

Claude DesktopFull support
VS Code + GitHub CopilotPartial support