Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
JVM dependency intelligence for AI assistants via Maven Central
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"maven-tools": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/arvindand/maven-tools-mcp:latest"
]
}
}
}Run this in your terminal
claude mcp add maven-tools -- docker run -i --rm docker.io/arvindand/maven-tools-mcp:latestPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"maven-tools": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/arvindand/maven-tools-mcp:latest"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"maven-tools": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/arvindand/maven-tools-mcp:latest"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account arvindand, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (3.2.4) reached the registry 7 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Signoff
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Five gates that make an agent's 'done' provable: run them, read the verdict, audit the record.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
Coordinate-based tools work with Maven, Gradle, SBT, and Mill projects. The POM analysis and upgrade-planning tools take Maven pom.xml files.
Prerequisite: Docker installed and running. No local Java installation is required. For a Docker-free setup, see building and running the JAR.
Add the maven-tools entry to your Claude Desktop config (see config file locations):
{
"mcpServers": { "maven-tools": { "command": "docker", "args": ["run", "-i", "--rm", "arvindand/maven-tools-mcp:latest"] } } }
Add the following server to .vscode/mcp.json in your workspace:
{
"servers": { "maven-tools": { "type": "stdio", "command": "docker", "args": ["run", "-i", "--rm", "arvindand/maven-tools-mcp:latest"] } } }
| Tag | Transport | Context7 | Best For |
|---|---|---|---|
:latest | STDIO | Yes | Default desktop MCP usage |
:latest-noc7 | STDIO | No | Networks where Context7 is blocked or not wanted |
:latest-http | HTTP | Yes | Streamable 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.
The default image exposes 11 MCP tools; -noc7 exposes the 9 core tools.
| Tool | What It Does |
|---|---|
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 declared dependency versions, identify their source, and surface BOM conflicts |
recommend_pom_upgrades | Produce actionable POM upgrade recommendations and flag changes needing review |
| Tool | What It Does |
|---|---|
resolve_library_id | Find a documentation library identifier |
query_docs | Fetch docs by Context7 library ID |
For parameters, examples, and tool-by-tool notes, see docs/tools.md.
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.
EXPLICIT, MANAGED, or EXPLICIT_OVERRIDE, and identifies managing BOMs and conflicts.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.
A common prompt in Copilot or Claude is:
Check all latest versions of the dependencies in my
pom.xmland call out anything risky.
The client can combine tool results to report:
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.
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.
For a few more usage notes, see the FAQ section in docs/examples.md.
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.
docs/setup.md - installation, client configuration, image variants, build-from-source optionsdocs/tools.md - full tool catalog, parameters, and response behaviordocs/examples.md - practical prompts, advanced use cases, reusable commands, and FAQ notesdocs/dogfooding.md - weekly self-update workflow and agent integrationdocs/troubleshooting.md - common environment issues and fixesdocs/architecture.md - design principles, transport/runtime options, and technical notesCORPORATE-CERTIFICATES.md - custom CA certificate support for locked-down networksIf 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.
This project is licensed under the MIT License. See LICENSE.
Arvind Menon