Gradle Tomcat MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_DIR | No | Directory for log files | ./logs |
| TOMCAT_PORT | No | Expected Tomcat port | 8080 |
| GRADLE_COMMAND | No | Gradle command to run | appRun |
| GRADLE_WORKING_DIR | No | Working directory for Gradle commands | current directory |
| MAX_LOG_BUFFER_SIZE | No | Maximum log entries in memory | 1000 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_tomcatC | Launch Tomcat via Gradle |
| stop_tomcatC | Terminate Tomcat process |
| restart_tomcatC | Stop and start Tomcat |
| get_tomcat_statusB | Check Tomcat process status |
| get_logsC | Retrieve log entries |
| clear_logsC | Clear log buffer and files |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose targeting specific Tomcat management tasks: clearing logs, retrieving logs, checking status, restarting, starting, and stopping. No overlap exists between these functions, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., clear_logs, get_logs, restart_tomcat). The verbs are action-oriented and predictable, with no deviations in naming style across the set.
With 6 tools, the server is well-scoped for managing Tomcat via Gradle, covering essential lifecycle operations (start, stop, restart, status) and log handling. Each tool earns its place without being excessive or insufficient for the domain.
The tool set provides complete coverage for Tomcat management: it includes lifecycle control (start, stop, restart), status monitoring, and log operations (retrieve and clear). No obvious gaps exist for the stated purpose, enabling agents to handle typical workflows without dead ends.