maven-mcp
# Maven MCP Server
[](https://opensource.org/licenses/MIT)
MCP server for Maven Central - search artifacts, check versions, and analyze dependencies.
## Installation
### Prerequisites
You need to authenticate with GitHub Packages. See [SETUP.md](SETUP.md) for detailed instructions.
### Quick Setup
Add to your MCP settings (`~/.cursor/mcp.json` or `~/Library/Application Support/Claude/claude_desktop_config.json`):
```json
{
"mcpServers": {
"maven-mcp": {
"command": "npx",
"args": ["-y", "@awin/maven-mcp"]
}
}
}
```
**Note**: Make sure you have configured GitHub Packages authentication before running this command.
## Tools
### `getLibraryVersions`
Get all available versions for a Maven artifact.
```json
{ "groupId": "org.springframework.boot", "artifactId": "spring-boot-starter" }
```
### `getLatestVersion`
Get only the latest version.
```json
{ "groupId": "org.springframework.boot", "artifactId": "spring-boot-starter" }
```
### `searchArtifacts`
Search Maven artifacts by keyword.
```json
{ "query": "spring-boot", "limit": 5 }
```
### `getDependencies`
Get dependencies for a specific version.
```json
{ "groupId": "org.springframework.boot", "artifactId": "spring-boot-starter", "version": "3.3.0" }
```
### `compareVersions`
Compare dependencies between versions.
```json
{ "groupId": "org.springframework.boot", "artifactId": "spring-boot-starter", "fromVersion": "3.2.0", "toVersion": "3.3.0" }
```
## Features
- Real-time data from Maven Central (no indexing delays)
- Direct queries to maven-metadata.xml
- Search, version lookup, and dependency analysis
## Development
```bash
npm install
npm run build
node dist/index.js
```
## Publishing
This package is automatically published to GitHub Packages when a new release is created. To publish manually:
```bash
npm run build
npm publish
```
Make sure you have the proper permissions in the `@awin` organization.
## License
MIT - see [LICENSE](LICENSE)
TDQS
Scored across 5 tools
Each tool has a clear, distinct purpose: search for artifacts, get latest version, get all versions, get dependencies for a specific version, and compare dependencies between two versions. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in camelCase (e.g., searchArtifacts, getLatestVersion). The naming is predictable and uniform across the set.
With 5 tools, the server is well-scoped for Maven artifact operations. It covers essential tasks without being too sparse or bloated, making it easy for an agent to navigate.
The tool set covers core Maven artifact workflows: search, version listing, dependency retrieval, and version comparison. Missing are artifact metadata details (e.g., description, licenses) and transitive dependency analysis, but the surface is mostly complete for common use cases.