mvn-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_version_toolC | Check a Maven version and get all version update information in a single call |
| check_version_batch_toolC | Process multiple Maven dependency version checks in a single batch request |
| list_available_versions_toolC | List all available versions of a Maven artifact grouped by minor version tracks |
| scan_java_project_toolC | Java-specific tool for scanning Maven projects for vulnerabilities |
| analyze_pom_file_toolC | Analyze a single Maven POM file without scanning the entire workspace |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| list_mcp_assets_prompt | Return a comprehensive list of all MCP server capabilities. |
| triage | Analyze service dependencies and create vulnerability triage report. |
| plan | Create actionable update plan based on triage report. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_server_capabilities | Get dynamic list of server capabilities. |
TDQS
Scored across 5 tools
Tools are mostly distinct: analyze POM, check version (single and batch), list versions, and scan vulnerabilities. The two version check tools (single and batch) could cause minor confusion, but their purposes are clearly separated by batch vs single.
All tools follow a consistent verb_noun_tool pattern (e.g., analyze_pom_file_tool, check_version_tool). The naming is uniform and predictable, making it easy for an agent to understand the action and target.
5 tools is well-suited for a Maven analysis server. Each tool covers a distinct area (POM analysis, version checking, version listing, vulnerability scanning) without being too sparse or overwhelming.
The toolset covers core Maven analysis tasks, but lacks tools for modifying POM files or performing dependency updates. This is a minor gap for a server focused on analysis, as agents can work around missing actions.