Maven Dependencies MCP Server
Check Maven dependency versions and look up the latest releases from Maven Central in real time.
Add to your client
Copy the config for your MCP client and paste it into its config file.
npm install -g mcp-maven-depsPaste into ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"maven-dependencies-mcp-server": {
"command": "npx",
"args": [
"mcp-maven-deps"
]
}
}
}Step-by-step guides: Add to Claude Desktop · Add to Cursor · Add to Windsurf
Before you start
- Node.js with npm/npx
- Internet access to Maven Central (repo1.maven.org)
About Maven Dependencies MCP Server
Maven Dependencies MCP Server gives AI assistants real-time access to Maven Central so they can verify dependency coordinates and find the latest stable (or pre-release) versions. It queries maven-metadata.xml directly, the same file Maven and Gradle use for resolution, ensuring fresh and accurate results. It handles full Maven coordinates and automatically distinguishes stable releases from pre-releases (alpha, beta, milestone, RC, snapshot). It supports stdio (default) and SSE transports, with optional remote access over HTTP.
Tools & capabilities (3)
get_latest_releaseRetrieves the latest stable release version of a Maven dependency. Excludes pre-release versions (alpha, beta, milestone, RC, snapshot) by default; set excludePreReleases=false to include them. Accepts a Maven coordinate string (groupId:artifactId[:version][:packaging][:classifier]).
check_maven_version_existsChecks if a specific version of a Maven dependency exists. The version can be provided either inside the dependency string or as a separate version parameter. Returns a boolean result.
list_maven_versionsLists Maven dependency versions in deploy order (most recent first), one per line, with optional pre-release filtering (excludePreReleases, default true) and depth control (depth, default 15, max 100).
When to use it
- Verify that a Maven dependency coordinate exists before adding it to a build file
- Find the latest stable release of a library to keep dependencies up to date
- Confirm whether a specific version of an artifact is published on Maven Central
- List recent versions of a dependency, optionally including pre-releases, when planning an upgrade
- Let an AI coding assistant resolve accurate Java/JVM dependency versions for Maven, Gradle, SBT, or Mill projects
Security notes
SSE transport can be bound to a remote host with --host=0.0.0.0, exposing the server over HTTP without authentication. Only do this on trusted networks.
Maven Dependencies MCP Server FAQ
Where does the version data come from?
The server queries maven-metadata.xml directly on Maven Central (https://repo1.maven.org/maven2/<g>/<a>/maven-metadata.xml), the authoritative file Maven and Gradle consult during dependency resolution. It updates within seconds of a deploy, so results are never stale.
Are pre-release versions included by default?
No. By default tools exclude pre-releases (alpha, beta, milestone, RC, snapshot) so you get production-ready versions. Set excludePreReleases=false to include them.
Does it support transports other than stdio?
Yes. In addition to stdio (the default), it supports SSE (Server-Sent Events) over HTTP. You can run it with --port and optionally --host=0.0.0.0 for remote access.
Can I install it via Smithery?
Yes. You can install it for Claude Desktop automatically with: npx -y @smithery/cli install maven-deps-server --client claude.
Alternatives to Maven Dependencies MCP Server
Compare all alternatives →
Microsoft's official browser-automation MCP using Playwright's accessibility tree (no vision model).
Up-to-date, version-specific library documentation injected into your coding agent.
Code intelligence engine that indexes repos into a persistent knowledge graph for AI coding agents.
Compare Maven Dependencies MCP Server with: