Tomcat

io.github.sarath-451Published by GitHub account sarath-451v1.0.2Updated Oct 24, 2026

Local MCP server for AI-assisted Apache Tomcat management and diagnostics

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A local MCP server that lets an AI assistant start, stop, deploy to and diagnose an Apache Tomcat instance on the user's machine.

What you can do
Start and stop the local Tomcat server and diagnose startup failures, including detecting Windows service installations and deploying or rolling back WAR files. Read and analyze Tomcat logs and GC logs. Take thread dumps and heap dumps for runtime diagnostics. All operations run locally against the user's own Tomcat installation.
When to use it
Useful when you maintain an Apache Tomcat deployment on a Windows machine and want an assistant to help with routine operations, failed startups, log analysis, or JVM diagnostics without switching between consoles and log files.
Requirements
Runs as a local stdio process from the npm package @sarath-451/tomcat-mcp. Needs Node.js 18+, a Java JDK (for jcmd, thread dumps and heap dumps) and an Apache Tomcat installation (9, 10 and 10.1 tested). Windows only; Linux support is described as planned. No authentication, environment variables or headers are declared.
Before you install
The server can start and stop Tomcat and deploy or roll back WAR files, which changes a running application; use it against a test instance first. Thread and heap dumps and log analysis read local runtime data. It is tied to Kiro IDE and Windows, and the README asks you to clone the repository and install dependencies before the one-click install.

Installation

In SourceWeft

  1. Open Tomcat in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Tomcat MCP (Model Context Protocol Server)

[npm version] [MCP Registry]

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.

[Add to Kiro]

📦 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:

bat

node -v
java -version
jcmd -h

Source: README.md at commit 2063788

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts