Add Tomcat MCP server

[sarath-451]

Summary

This PR adds Tomcat MCP, a local Model Context Protocol server for Kiro IDE.

It enables AI-assisted management and diagnostics of Apache Tomcat, including:

• Startup troubleshooting
• WAR deployment and rollback
• Log inspection
• JVM thread dumps and heap dumps
• GC log analysis
• Windows service detection

The MCP runs locally and does not expose any remote network access.

---

Motivation and Context

Apache Tomcat is widely used in local and on-prem environments, but diagnosing
startup failures, JVM issues, and deployment problems is often manual and time-consuming.

This MCP allows Kiro IDE to interact with Tomcat through a safe, local MCP server,
providing AI-assisted diagnostics and operational workflows without exposing
production systems remotely.

---

How Has This Been Tested?

• Tested locally on Windows with Apache Tomcat 10.1.x
• Verified startup and shutdown via MCP tools
• Tested WAR deployment and rollback
• Verified log reading and startup diagnostics
• Verified thread dump, heap dump, and GC log analysis using JDK tools
• Verified Windows service detection

---

Breaking Changes

• None. This is a new MCP server addition and does not modify existing functionality.

---

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

---

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

---

Additional context

This MCP is designed to be local-first and production-safe.
It intentionally avoids any remote network access and relies on explicit user actions
within Kiro IDE for operational tasks.

[jonathanhefner]

Hi, @sarath-451! 👋 Thanks for submitting a PR, but this is not the correct way to publish an MCP server to the MCP Registry. Please use the publisher CLI or the Registry API itself. See the quickstart guide for an example.