Maven Tools MCP Server

Community

JVM dependency intelligence for AI assistants via Maven Central.

How to install ↓ Compare GitHub source repository ↗

Category: Dev Tools #16 of 438
Stars: ★ 34 Popular
Transport: stdio (local process)
Runtime: Docker
Credentials: Optional API key
License: MIT
Last commit: 20 days ago
Tools: 11

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.

Strongest · Documentation 16/20 Weakest · Reliability 11/20

Reliability

11/20

Security and permissions

14/20

Maintenance

14/20

Documentation

16/20

Setup experience

14/20

Why each score

Reliability 11/20: README declares 11 tools, multiple image variants, and layered docs; tool catalog is internally consistent, but the supplied material contains no committed tests, CI workflows, or executable evidence verifying the init handshake and tool behavior. Cannot award above 12 under static calibration; deducted for missing verifiable test/CI evidence.
Security and permissions 14/20: Read-only dependency-intelligence server whose side effects are outbound calls to Maven Central and optional Context7; CONTEXT7_API_KEY is optional and passed via env, no hardcoded tokens, no delete/pay/deploy defaults, no red-line risks observed. Deducted for incomplete disclosure of outbound data-flow boundaries (Context7 doc queries) and confirmation/scoping details.
Maintenance 14/20: Version 3.2.2, explicit MIT license, NOTICE attribution, CHANGELOG, and documented weekly dogfooding workflow suggest sustained care; 0 open issues. Deducted because actual release cadence, commit activity, and a security-response channel cannot be verified from static material alone.
Documentation 16/20: Well-layered docs (setup/tools/examples/troubleshooting/architecture/dogfooding) with client config examples, disclosed limitations (not fully offline), parameter references, and license info. Deducted because linked docs' contents are unverifiable in static review and cost/quota details are only partially disclosed.
Setup experience 14/20: Copy-paste JSON configs for Claude Desktop and VS Code, multi-arch Docker images, clear variant guidance, and a short quick-start path. Deducted because files lack verifiable CI/install validation evidence per calibration rules, and variant/network choices add mild fragility.

Static review · not runListed 2026-09-08

Read the FMRS scoring method →

Fit and risk

What it can accessUses the network

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

Setup

Before you start

Runtime：Docker

CONTEXT7_API_KEY optionalsecret Optional Context7 API key for the documentation tools; pass with -e CONTEXT7_API_KEY if your environment requires Context7 auth or you want to avoid anonymous limits. Obtain it from Context7.

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"]
    }
  }
}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json

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

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal

claude mcp add maven-tools -- docker run -i --rm arvindand/maven-tools-mcp:latest

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

After adding the Docker-based maven-tools config to your client, confirm 11 tools appear in the tool list, including get_latest_version and analyze_pom_dependencies; then ask for the latest version of a concrete dependency and check a structured version answer comes back.

Troubleshooting

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

Things to try

Once connected, you can ask your AI assistant things like:

Check all latest versions of the dependencies in my pom.xml and call out anything risky.
Compare the current version of org.springframework:spring-core with the latest on Maven Central and tell me if the upgrade is major, minor, or patch.
Analyze my pom.xml and show the effective version and classification (EXPLICIT/MANAGED/EXPLICIT_OVERRIDE) of every dependency.
Use resolve-library-id to find the Spring Boot docs library ID, then fetch relevant docs with query-docs.

Tools 11

get_latest_version read-only

Find the latest version with stability-aware selection.

check_version_exists read-only

Verify a specific version and classify its stability.

check_multiple_dependencies read-only

Bulk lookup for dependency coordinates.

compare_dependency_versions read-only

Compare current versions against available upgrades.

analyze_dependency_age read-only

Classify how old a dependency is.

analyze_release_patterns read-only

Look at release cadence and maintenance signals.

analyze_project_health read-only

Run a broader dependency health audit.

analyze_pom_dependencies read-only

Resolve effective versions from raw pom.xml, classify dependencies as EXPLICIT/MANAGED/EXPLICIT_OVERRIDE, and surface multi-BOM conflicts.

Show 3 more tools

recommend_pom_upgrades read-only

Return deterministic and attention-needed upgrade actions for an agent to apply.

resolve-library-id read-only

Find a documentation library identifier in Context7.

query-docs read-only

Fetch docs by Context7 library ID.

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 Desktop

VS Code + GitHub CopilotPartial support

Listed from the project's documentation, not tested by this site.

Overview

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.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 63.3k · Tools 2 Compare with this →

NPM Sentinel MCP Server 79 · B

AI-powered NPM package analysis MCP server

★ 18 · Tools 19 Compare with this →

MartinLoop MCP Server 79 · B

An independent control layer that gives AI coding agents budgets, brakes, and receipts

★ 413 Compare with this →

GitHub MCP Server 76 · B

GitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language

★ 33.7k · Tools 15 Compare with this →

Compare with other MCP servers

Source revision 41c786b6a744 Data synced 2026-10-19 Read the FMRS scoring method