mcp-trmm

What is mcp-trmm?

A focused MCP server for TRMM-style remote management operations. It exposes a curated set of MCP tools for common IT operations tasks such as agent lookup, checks, scripts, software, services, Windows updates, reporting, alerts, automation, and tasks. Designed specifically for local or smaller models that struggle with constructing raw API paths, HTTP methods, or JSON payloads.

How to use mcp-trmm?

Run the FastAPI app with Uvicorn: uvicorn server:app --host 0.0.0.0 --port 8000. The server mounts the MCP ASGI app at /mcp and includes bearer token protection and a /healthz endpoint. Connect an MCP client to the server’s URL to use the tools.

Key features of mcp-trmm

• Small, curated tool surface for common IT operations.
• Model-friendly strongly-named tools with simple arguments.
• Read-first behavior encourages inspection before action.
• Backend-owned request formatting (no raw API paths).
• Safer operations with limited destructive tools.
• Consistent result handling and structured error reporting.

Use cases of mcp-trmm

• Reboot an agent by name (list agents, then call reboot).
• Investigate a service issue (find agent, get service status, control if needed).
• Check and manage Windows updates (get updates, scan, install).
• Run scripts or commands on agents without manual API requests.
• Automate alert updates and task management.

FAQ from mcp-trmm

What makes this server different from a generic “call any endpoint” tool?

Instead of exposing one generic tool, the server provides small, strongly-named tools with only a few arguments. The backend translates those arguments into valid API requests, reducing errors from smaller models.

What runtime dependencies does mcp-trmm require?

It runs as a FastAPI application served by Uvicorn. The server itself is an MCP server that connects to an upstream TRMM/PAI API via the api_client.py layer.

What data does mcp-trmm access?

The server sends HTTP requests to an upstream TRMM/PAI API. It does not store data locally; it only acts as a translation and proxy layer for the model’s tool calls.

Are there known limitations?

Yes. The server intentionally does not expose every endpoint from the upstream schema. It avoids generic CRUD, broad administrative mutation endpoints, highly ambiguous updates, raw pass-through tools, and configuration-heavy endpoints.

What transport and authentication does mcp-trmm use?

The server uses HTTP/ASGI with a FastAPI mount. It supports bearer token protection for the MCP route and includes a simple /healthz endpoint for health checks.