Overview
5 min
litmus mcp server the litmus mcp server is the official model context protocol (mcp) server for litmus automation it lets large language models (llms) and ai coding agents including claude, cursor, vs code copilot, windsurf, and claude code interact directly with litmus edge for device configuration, real time monitoring, and industrial automation management built on the mcp sdk and compliant with the model context protocol spec https //modelcontextprotocol io/ the server ships as a single docker image with two components mcp server (port 8000) sse transport endpoint for external mcp clients such as claude desktop, cursor, vs code, windsurf, and claude code web ui (port 9000) a built in chat interface for interacting with litmus edge directly in a browser, no mcp client required what you can do the litmus mcp server exposes 57 tools across 11 categories, giving ai agents the ability to inspect and configure devicehub devices and tags read live values from nats topics query historical time series data from influxdb manage docker containers on the litmus edge marketplace build, list, and inspect digital twin models and instances pull system events, network information, and packet captures drive a litmus edge manager (lem) tenant list devices, licenses, alerts, and project usage see the tools reference # for the full list supported ai clients claude desktop claude code cursor vs code copilot windsurf any mcp compatible llm client built in web ui (no client needed) how it works the server is stateless all credentials are supplied per connection via http headers in sse mode, or via environment variables in stdio mode an llm client connects to the mcp server over sse, which in turn communicates with litmus edge via rest api and the litmus sdk nats broker for live tag and event values influxdb for historical time series data this architecture means no credentials are ever stored on the server, and each session is independently authenticated architecture quick start getting started # run the server in docker in under a minute web ui # chat with litmus edge directly in your browser client configuration # wire it into claude desktop, cursor, vs code, windsurf, claude code tools reference # every tool the llm can call, grouped by category headers reference # the full set of connection headers and what each one does project links github litmusautomation/litmus mcp server https //github com/litmusautomation/litmus mcp server container image ghcr io/litmusautomation/litmus mcp server\ latest glama registry glama ai/mcp/servers/@litmusautomation/litmus mcp server mcp so registry mcp so/server/litmus mcp server/litmusautomation