Maven Tools MCP Server
JVM dependency intelligence for any build tool using Maven Central Repository. Includes Context7 integration for upgrade documentation and guidance.
10 Tools
Add to Docker Desktop
Version 4.43 or later needs to be installed to add the server automatically
Tools
| Name | Description |
|---|---|
analyze_dependency_age | Single dependency. Returns days since last release and freshness (fresh/current/aging/stale), with actionable insights. Use when asked about 'how old' or 'last release' of a library. |
analyze_project_health | Bulk project view. Summarizes health across many dependencies using age and maintenance patterns, with concise recommendations. Use for dependency health reports. |
analyze_release_patterns | Single dependency. Analyzes historical releases to infer cadence, consistency, and likely next-release timeframe. Useful for maintenance and planning. |
check_multiple_dependencies | Bulk. For many coordinates (no versions), returns per-dependency latest versions by type. Set stableOnly=true to filter to production-ready (stable) versions only. Use for audits of multiple dependencies. |
check_version_exists | Single dependency + version. Validates existence on Maven Central and classifies its stability (stable/rc/beta/alpha/milestone/snapshot). Use when asked: 'does X:Y exist?' or 'is version V stable?' |
compare_dependency_versions | Bulk compare. Input includes versions. Suggests upgrades and classifies update type (major/minor/patch). Set onlyStableTargets=true to restrict upgrade recommendations to stable releases. Never suggests downgrades. |
get_latest_version | Single dependency. Returns newest versions by type (stable/rc/beta/alpha/milestone). Set preferStable=true to prioritize stable as primary while still including other types. Use when asked: 'what's the latest version of X?' Works with all JVM build tools. |
get_library_docs | Fetches up-to-date documentation for a library. You must call 'resolve-library-id' first to obtain the exact Context7-compatible library ID required to use this tool, UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. |
get_version_timeline | Single dependency. Returns a timeline of recent versions with dates, gaps, and stability patterns. Use for quick release history snapshots. |
resolve_library_id | Resolves a package/product name to a Context7-compatible library ID and returns a list of matching libraries. You MUST call this function before 'get-library-docs' to obtain a valid Context7-compatible library ID UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. Selection Process: 1. Analyze the query to understand what library/package the user is looking for 2. Return the most relevant match based on: - Name similarity to the query (exact matches prioritized) - Description relevance to the query's intent - Documentation coverage (prioritize libraries with higher Code Snippet counts) - Trust score (consider libraries with scores of 7-10 more authoritative) Response Format: - Return the selected library ID in a clearly marked section - Provide a brief explanation for why this library was chosen - If multiple good matches exist, acknowledge this but proceed with the most relevant one - If no good matches exist, clearly state this and suggest query refinements For ambiguous queries, request clarification before proceeding with a best-guess match. |
Manual installation
You can install the MCP server using:
Installation for