About tomcat
tomcat is a local MCP server for Kiro IDE users managing Apache Tomcat. It supports operational tasks and diagnostics, and runs without exposing Tomcat over the network.
Key features
- 01Start and stop Tomcat
- 02Diagnose startup failures
- 03Deploy and roll back WAR files
- 04Read and analyze logs
- 05Capture thread and heap dumps
- 06Analyze GC logs
Use cases
- 01Investigate Tomcat startup problems
- 02Deploy or roll back a WAR
- 03Inspect logs and runtime dumps
MCP support
The local MCP server exposes Tomcat management and diagnostic operations to Kiro IDE. It runs locally and does not expose Tomcat over the network.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMETomcat MCP (Model Context Protocol Server)
A local Tomcat management MCP server for Kiro IDE that enables AI-assisted operations such as:
- Start / stop Tomcat
- Diagnose startup failures
- Deploy and rollback WAR files
- Read and analyze logs
- Take thread dumps and heap dumps
- Analyze GC logs
- Detect Windows service installations
This MCP runs locally and never exposes Tomcat over the network.
🌍 Available in MCP Registry
Tomcat MCP is officially published to the MCP Registry and npm.
Registry name: io.github.sarath-451/tomcat-mcp
npm package: @sarath-451/tomcat-mcp
Search via Registry API: https://registry.modelcontextprotocol.io/v0.1/servers?search=tomcat
🚀 One-Click Install (Kiro IDE)
Make sure you have cloned this repository and installed dependencies first.
📦 Requirements
- **Node.js 18+**
- **Java JDK** (required for jcmd, thread dumps, heap dumps)
- Apache Tomcat (9 / 10 / 10.1 tested)
- Windows (Linux support planned)
Check:
node -v
java -version
jcmd -h
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.