maven-artifacts-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@maven-artifacts-mcp get latest version of org.springframework:spring-core"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Maven Version Resolver MCP Server
A TypeScript-based Model Context Protocol (MCP) server that provides Maven2 module version resolution capabilities with caching and logging.
Features
Latest stable version resolution from Maven Central
Pre-release filtering (excludes preview, RC, alpha, beta, snapshot, milestone versions)
5-minute in-memory cache with automatic cleanup
Request/response logging
Error handling and input validation
Related MCP server: Maven Version Server
Installation from Source
npm install
npm run buildUsage
Stdio Mode (Default)
For MCP clients like Cursor:
npm startRemote HTTP Server Mode
Run as a standalone network service:
# Start HTTP server on port 3001
npm run start:http
# Or with custom port
npm run dev:http -- --port 8080Development Mode
# Stdio mode
npm run dev
# HTTP mode
npm run dev:httpSetup
Stdio Mode (Recommended for Cursor)
Add to your .cursor-settings.json:
{
"mcp": {
"mcpServers": {
"maven-resolver": {
"command": "npx",
"args": ["maven-artifacts-mcp", "--stdio"],
"env": {
"CACHE_TTL_MINUTES": "5",
"MAVEN_API_TIMEOUT": "10000"
}
}
}
}
}Remote HTTP Mode
Start the server: npm run start:http, then configure:
{
"mcp": {
"mcpServers": {
"maven-resolver-remote": {
"command": "http",
"args": ["http://localhost:3001/sse"],
"env": {
"CACHE_TTL_MINUTES": "5",
"MAVEN_API_TIMEOUT": "10000"
}
}
}
}
}HTTP Endpoints:
GET /sse- MCP Server-Sent Events endpointGET /health- Health check endpointGET /tools- List available MCP tools and capabilities
Example /tools response:
curl http://localhost:3001/tools{
"service": "maven-mcp-server",
"tools": [{"name": "latest_version", "description": "Get the latest stable version of a Maven artifact"}],
"features": ["Filters out pre-release versions", "In-memory caching with 5-minute TTL"],
"endpoints": {"health": "/health", "sse": "/sse", "tools": "/tools"}
}Other environment variables like
"HTTPS_PROXY": "http://myorg.proxy:8080",
"HTTP_PROXY": "http://myorg.proxy:8080",
"NO_PROXY": "localhost,127.0.0.1,.local"
"LOG_LEVEL": "debug",
"NODE_ENV": "development" can also be provided.
MCP Tool: latest_version
Retrieves the latest version information for a Maven artifact.
Parameters
Parameter | Type | Required | Description |
| string | Yes | Maven group ID (e.g., "org.springframework") |
| string | Yes | Maven artifact ID (e.g., "spring-core") |
Example Usage
{
"tool": "latest_version",
"arguments": {
"groupId": "org.springframework",
"artifactId": "spring-core"
}
}Response includes latest version, last updated timestamp, repository, cache status, and excluded pre-release versions.
Version Filtering
Automatically filters out pre-release versions:
Preview versions (e.g.,
6.1.0-preview)Release candidates (e.g.,
6.1.0-RC1)Alpha/Beta versions (e.g.,
6.1.0-alpha)Snapshots (e.g.,
6.1.0-SNAPSHOT)Milestones (e.g.,
7.0.0-M1)
Configuration
Environment Variables
Variable | Default | Description |
| 10000 | API request timeout in milliseconds |
| 5 | Cache TTL in minutes |
| info | Logging verbosity level |
Npm Tasks
npm run build- Compile TypeScriptnpm start- Start the servernpm run dev- Build and start in development modenpm test- Run test suitenpm run test:coverage- Run tests with coverage
License
Apache 2.0 License
Available Tools
1 toollatest_versionA
Get the latest version of a Maven artifact from Maven Central repository
Inputs: groupId (required), artifactId (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or misselection. The single tool's purpose is clear and distinct.
With only one tool, the naming is trivially consistent. There are no mixed conventions or conflicting patterns to evaluate.
A single tool for a Maven artifacts server is far too few. The domain typically requires operations like listing versions, resolving metadata, or searching artifacts, making the count inadequate for the apparent scope.
The tool surface is severely incomplete, only offering the latest version lookup. Other essential operations for a Maven artifacts server are entirely absent, leaving obvious gaps that would prevent agents from performing common tasks.
Maintenance
Related MCP Connectors
Package versions, licences and known vulnerabilities for npm, PyPI, crates, Go, Maven, NuGet
CVEs, affected versions and fix versions for your dependencies, from an affected-version ledger.
Verify PyPI and npm packages, symbols, and version diffs against real artifacts. Free, no account.
Related MCP Servers
- AlicenseBqualityDmaintenanceAn MCP (Model Context Protocol) server that provides tools for checking Maven dependency versions. This server enables LLMs to verify Maven dependencies and retrieve their latest versions from Maven Central Repository.3173 npm34MIT
- AlicenseAqualityDmaintenanceAn MCP server for managing Maven dependency versions using direct metadata parsing from Maven Central. It provides tools to fetch latest stable versions, list version history, and compare versions with upgrade recommendations.4MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to query Maven artifacts in JFrog Artifactory by reusing credentials from ~/.m2/settings.xml and providing tools like getting latest stable versions, listing artifacts, and checking dependency updates.-
- AlicenseBqualityDmaintenanceEnables searching Maven Central artifacts, retrieving versions, and analyzing dependencies via natural language.5MIT