Skip to main content
Glama
Java Project Runner MCP

Java Project Runner MCP

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
project_listA

List registered Java/Spring Boot projects from ~/.java-project-runner/projects.json

project_inspectA

Inspect a registered project: pom/wrapper/javaHome/jarPath resolvability, Maven version probe, and config summary

project_buildB

Run Maven build for a registered project (default goal package, -DskipTests by default)

project_startA

Start the configured JAR (detached process group). Builds with Maven unless the JAR is fresh or skipBuild is set; use rebuild to force package.

project_stopB

Stop the managed process group only (SIGTERM then SIGKILL). Never kills by port/main-class.

project_restartB

Stop (if running) then start under one project lock (same build skip / rebuild options as project_start)

project_statusB

Query runtime status for one project or all tracked projects

project_logsC

Tail project logs (stdout/stderr/both), max 200 lines

project_registerC

Add a project to ~/.java-project-runner/projects.json (path must contain pom.xml)

project_updateB

Patch an existing registry project (id cannot change). Re-validates the full entry.

project_unregisterA

Remove a project from the registry. Refuses if runtime status is running/starting/stopping/unknown.

project_reclaimC

Re-verify a persisted PID against the managed java -jar fingerprint and mark running if matched

project_force_stopB

Stop a managed process when cmdline fingerprint still matches. Requires confirm:true. Allowed for unknown status; never blind-kills.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 13 tools

Disambiguation4/5

Most tools target clearly distinct lifecycle operations (register/list/inspect/build/start/stop/restart/status/logs). The main possible confusion is between start and restart, and between stop and force_stop, but the descriptions make the distinctions explicit enough for an agent.

Naming Consistency5/5

Every tool follows the same project_<verb/action> snake_case convention, with predictable verb choices. There is no mixing of casing or naming styles.

Tool Count5/5

With 13 tools, the set is well-scoped for a Java project runner: registry management, build, runtime lifecycle, status, logs, and recovery operations each have a clear place. No tool appears redundant or excessive.

Completeness5/5

The surface covers the full lifecycle: register, list, inspect, update, unregister, build, start, stop, restart, status, logs, plus force-stop and PID reclaim recovery operations. No obvious operational dead ends remain for the stated purpose.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues