Maven Tools Mcp

io.github.arvindand由 GitHub 账号 arvindand 发布v3.2.4更新于 Nov 1, 2026

JVM dependency intelligence for AI assistants via Maven Central

概览

AI 生成的概览

该 MCP 服务器为助手提供 Maven Central 实时数据,用于检查 JVM 依赖版本、健康状况、许可证、CVE 与 POM 升级。

可以做什么
  • 查询 Maven 坐标的最新版本或指定版本,判定稳定性,并批量检查多个依赖
  • 对比当前版本与可用升级,区分主版本、次版本与补丁级变更
  • 审计依赖的年龄、发布节奏、维护信号、已知漏洞与许可证信息
  • 解析 pom.xml 中声明的版本,追溯父 POM、属性与导入的 BOM,并标出冲突
  • 生成结构化的 POM 升级建议,区分可直接执行的修改与需人工复核的变更
  • 通过可选的 Context7 工具查询库文档
适用场景
适合助手参与 JVM 项目时使用:检查依赖版本、规划升级,或在不构建项目的情况下审计 Maven POM 的陈旧程度、CVE 与许可证问题。
运行要求
以 stdio 在本地运行;文档中的安装方式需要已安装并运行 Docker(无需本地 Java),也可改用 JAR 方式。未缓存的元数据查询需要访问 Maven Central 或你配置的仓库,漏洞检查与 Context7 文档还依赖外部服务。CONTEXT7_API_KEY 为可选项。
安装前请注意
查询会发往 Maven Central、漏洞服务与 Context7,依赖坐标会离开本机;noc7 镜像变体可避开 Context7。服务器只返回建议,不会修改文件,是否应用由客户端或助手决定。分析仅覆盖声明的依赖,不含完整传递依赖图,且只处理默认激活的 profile。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Maven Tools Mcp,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

Maven Tools MCP Server

[Java] [Spring Boot] [Spring AI] [MCP Protocol] [License] [GitHub release (latest by date)] [Docker] [Docker Pulls] [GitHub stars]

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.

[Demo]

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):

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

VS Code + GitHub Copilot

Add the following server to .vscode/mcp.json in your workspace:

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

Image Variants

TagTransportContext7Best For
:latestSTDIOYesDefault desktop MCP usage
:latest-noc7STDIONoNetworks where Context7 is blocked or not wanted
:latest-httpHTTPYesStreamable HTTP clients and sidecar workflows

The current release is v3.2.4. For version-pinned setups, use :3.2.4, :3.2.4-noc7 or :3.2.4-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

ToolWhat It Does
get_latest_versionFind the latest version with stability-aware selection
check_version_existsVerify a specific version and classify its stability
check_multiple_dependenciesBulk lookup for dependency coordinates
compare_dependency_versionsCompare current versions against available upgrades
analyze_dependency_ageClassify how old a dependency is
analyze_release_patternsLook at release cadence and maintenance signals
analyze_project_healthRun a broader dependency health audit
analyze_pom_dependenciesResolve declared dependency versions, identify their source, and surface BOM conflicts
recommend_pom_upgradesProduce actionable POM upgrade recommendations and flag changes needing review

Context7 documentation tools

ToolWhat It Does
resolve_library_idFind a documentation library identifier
query_docsFetch 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.

  • analyze_pom_dependencies returns effective versions, classifies declarations as EXPLICIT, MANAGED, or EXPLICIT_OVERRIDE, and identifies managing BOMs and conflicts.
  • recommend_pom_upgrades returns deterministicActions for mechanical edits and needsAttention for major upgrades, BOM conflicts, and explicit overrides. Actions identify the version field or property to edit in the input POM.

Recommendations cover editable parent/BOM versions, explicit dependencies, root dependency-management entries, and direct build/plugin dependencies. Declarations without an unambiguous edit location in the input POM are skipped. The server returns recommendations; the client or agent validates and applies them.

Analysis covers declared dependencies, not the full transitive dependency graph. Profile activation is limited to active-by-default profiles. See POM analysis details and limits.

Example

A common prompt in Copilot or Claude is:

Check all latest versions of the dependencies in my pom.xml and call out anything risky.

The client can combine tool results to report:

  • current version vs latest version
  • whether the upgrade is major, minor, or patch
  • whether the newest release is stable
  • whether the dependency looks fresh, aging, or stale
  • whether there are known CVEs or license concerns worth noticing

For broader questions like "which library should I choose?", combine Maven metadata with Context7 documentation and client-side web search for ecosystem context.

See more prompt examples or the maven-tools agent skill for guidance on choosing and combining tools.

Dogfooding

This repository uses its own tools in a weekly dependency-update workflow. A Python agent sends the POM to recommend_pom_upgrades, validates and applies minor/patch actions, and opens a PR for review. Its XML editor checks current versions and preserves formatting. Manual major-upgrade reviews use the GitHub Copilot SDK; routine updates do not require an LLM.

See the dogfooding guide for the agent, GitHub Actions workflow, credentials, and manual triggers.

FAQ

  • Does this replace Renovate or Dependabot? The server provides dependency analysis and upgrade recommendations. File edits, testing, scheduling, and PR creation require a separate agent or workflow. The included agent demonstrates this for Maven POM updates.
  • Does it work offline? Not fully. Uncached metadata queries need access to Maven Central or your configured repository. Vulnerability checks and Context7 documentation also use external services.
  • Does it parse Gradle, SBT, or Mill build files? No. Use their dependencies' Maven coordinates with the coordinate-based tools; whole-file analysis accepts Maven POM XML.

For a few more usage notes, see the FAQ section in docs/examples.md.

Acknowledgements

The effective POM resolver under com.arvindand.mcp.maven.pom follows the resolution shape of maxxq-org/maxxq-maven (MIT, Guy Chauliac), scoped here to declared-dep resolution. See NOTICE.

More Docs

Further Reading

Contributing

If you want to build or test locally, start with docs/setup.md and the helper scripts in build/.

Check out v3.2.4 to build this release from source; main may contain unreleased changes.

Project history and release notes live in CHANGELOG.md.

License

This project is licensed under the MIT License. See LICENSE.

Author

Arvind Menon

来源:README.md,提交 54e55c0

工具

0
SourceWeft 曾在隔离沙箱中以无凭据方式启动该软件包一次,以列出其工具,但未能完成:该软件包类型无法在沙箱中运行。

版本历史

3
  1. v3.2.4最新Nov 1, 2026
  2. v3.2.3Oct 4, 2026
  3. v3.2.2Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分