MCP Maven Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_JAVA_HOME | No | Override JDK path | |
| MCP_MAVEN_TIMEOUT_MS | No | Build timeout in milliseconds | 300000 |
| MCP_MAVEN_CACHE_ENABLED | No | Enable/disable build caching | true |
| MCP_MAVEN_MAX_LOG_LINES | No | Max stdout lines to keep | 500 |
| MCP_MAVEN_DEFAULT_PROFILE | No | Default Maven profile | |
| MCP_MAVEN_SPRING_RING_BUFFER | No | Spring Boot log ring buffer size | 500 |
| MCP_MAVEN_SPRING_STARTUP_TIMEOUT | No | Max wait for Spring Boot startup | 120000 |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| compileProjectB | Compile the Maven project and return structured compilation errors |
| getCompilationErrorsC | Run compile and return only the structured error list (no success noise) |
| runTestsA | Run all tests (mvn test) and return structured results |
| runSingleTestB | Run a single test class and return structured results |
| runSingleMethodB | Run a single test method and return structured results |
| getFailedTestsA | Read test reports and return only failed/errored tests without re-running |
| getTestReportsA | Read test reports from disk without running tests again |
| verifyProjectB | Run mvn verify — compile, test, and integration-check the project |
| packageProjectC | Package the project as JAR/WAR (skip tests by default) |
| cleanProjectC | Clean the project (mvn clean) |
| executeMavenCommandB | Execute an arbitrary Maven command with custom arguments. Output is parsed for errors. |
| getProjectInfoA | Detect the current Maven project structure: root, modules, Java version |
| getJavaInfoA | Detect which JDK is being used — from JAVA_HOME, mvn --version, or PATH |
| getMavenInfoA | Get Maven version and path from mvn --version |
| pingA | Health check — verify the MCP server is alive and responding |
| springBootRunB | Start the Spring Boot application. Captures logs and detects port/startup. |
| springBootStopA | Stop the Spring Boot application gracefully (actuator shutdown first, SIGTERM fallback) |
| springBootStatusB | Get the current status of the Spring Boot application (port, PID, uptime, health) |
| springBootRestartC | Restart the Spring Boot application (stop then start) |
| springBootLogsC | Get the most recent log lines from the running Spring Boot application |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Christian-Carminati/mcp-maven-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server