Maven MCP Server

Name: Maven MCP Server
Author: danielscholl

@danielscholl

Repository

About Maven MCP Server

MCP Server to communicate with Maven Central Feed

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mvn-mcp-server": {
      "command": "uv",
      "args": [
        "sync"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Maven MCP Server?

Maven MCP Server is a Model Context Protocol (MCP) server that provides tools for working with Maven dependencies. It checks if specific versions of dependencies exist in the Maven Central repository, retrieves the latest versions, and finds the latest version based on semantic versioning components.

How to use Maven MCP Server?

Clone the repository, install dependencies with uv sync and uv pip install -e ., then run tests with uv run pytest. Add an MCP configuration to .mcp.json using uv run maven-mcp-server as the command. Tools are invoked through MCP clients such as Claude Code.

Key features of Maven MCP Server

Check if a specific Maven dependency version exists
Retrieve latest major, minor, and patch versions
Batch check multiple dependencies in a single request
List all available versions grouped by minor tracks
Support for optional packaging and classifier parameters

Use cases of Maven MCP Server

Verifying whether a specific version of a Maven dependency has been published
Identifying available updates for dependencies in a project
Batch checking version updates across multiple dependencies
Exploring all available versions of a dependency for upgrade planning

FAQ from Maven MCP Server

What tools does Maven MCP Server provide?

It provides three core tools: maven-mcp-server__check_version_tool for single‑dependency checks, maven-mcp-server__check_version_batch_tool for batch checks, and maven-mcp-server__list_available_versions_tool for listing all versions grouped by minor tracks.

How are dependencies specified?

Dependencies are specified in the format groupId:artifactId (e.g., org.springframework:spring-core). Optional parameters include packaging (defaults to jar) and classifier.

What happens on error?

All tools return a standardized error response with an error code. Common codes include INVALID_INPUT_FORMAT, DEPENDENCY_NOT_FOUND, VERSION_NOT_FOUND, MAVEN_API_ERROR, and INTERNAL_SERVER_ERROR.