Track MCP LogoTrack MCP
Track MCP LogoTrack MCP

The world's largest repository of Model Context Protocol servers. Discover, explore, and submit MCP tools.

Product

  • Categories
  • Top MCP
  • New & Updated
  • Submit MCP

Company

  • About

Legal

  • Privacy Policy
  • Terms of Service
  • Cookie Policy

© 2026 TrackMCP. All rights reserved.

Built with ❤️ by Krishna Goyal

    Litmus Mcp Server

    Official MCP server for configuring Litmus instances.

    5 stars
    Python
    Updated Nov 3, 2025
    industrial
    mcp
    mcp-server

    Table of Contents

    • Table of Contents
    • Quick Launch
    • Start an HTTP SSE MCP Server using Docker
    • Web UI
    • Persistent Configuration
    • Claude Code CLI
    • Cursor IDE
    • VS Code / GitHub Copilot
    • Manual Configuration
    • Windsurf
    • STDIO with Claude Desktop
    • Clone
    • Set ENABLE_STDIO to 'true' in /src/config.py:
    • Run the server
    • Add json server definision to your Claude Desktop config file:
    • Tips
    • Available Tools
    • Tool Use Notes
    • Litmus Central
    • MCP server registries

    Table of Contents

    • Table of Contents
    • Quick Launch
    • Start an HTTP SSE MCP Server using Docker
    • Web UI
    • Persistent Configuration
    • Claude Code CLI
    • Cursor IDE
    • VS Code / GitHub Copilot
    • Manual Configuration
    • Windsurf
    • STDIO with Claude Desktop
    • Clone
    • Set ENABLE_STDIO to 'true' in /src/config.py:
    • Run the server
    • Add json server definision to your Claude Desktop config file:
    • Tips
    • Available Tools
    • Tool Use Notes
    • Litmus Central
    • MCP server registries

    Documentation

    Litmus MCP Server

    The official Litmus Automation Model Context Protocol (MCP) Server enables LLMs and intelligent systems to interact with Litmus Edge for device configuration, monitoring, and management. It is built on top of the MCP SDK and adheres to the Model Context Protocol spec.

    Table of Contents

    • Quick Launch
    • Web UI
    • Persistent Configuration
    • Claude Code CLI
    • Cursor IDE
    • VS Code / Copilot
    • Windsurf
    • STDIO - Claude Desktop
    • Tips
    • Tools
    • Litmus Central

    ---

    Quick Launch

    Start an HTTP SSE MCP Server using Docker

    Run the server in Docker (HTTP SSE only)

    bash
    docker run -d --name litmus-mcp-server -p 8000:8000 ghcr.io/litmusautomation/litmus-mcp-server:latest

    NOTE: The Litmus MCP Server is built for linux/AMD64 platforms. If running in Docker on ARM64, specify the AMD64 platform type by including the --platform argument:

    bash
    docker run -d --name litmus-mcp-server --platform linux/amd64 -p 8000:8000 ghcr.io/litmusautomation/litmus-mcp-server:main

    ---

    Web UI

    The Docker image includes a built-in chat interface that lets you interact with Litmus Edge using natural language — no MCP client configuration required.

    Start the server with both ports exposed:

    bash
    docker run -d --name litmus-mcp-server \
      -p 8000:8000 -p 9000:9000 \
      -e ANTHROPIC_API_KEY= \
      ghcr.io/litmusautomation/litmus-mcp-server:latest
    • **:9000** — Web UI (chat interface). Open http://localhost:9000 in your browser, add a Litmus Edge instance via the config page, and start chatting.
    • **:8000** — SSE endpoint for external MCP clients (Claude Desktop, Cursor, VS Code, etc.) — still available as normal.

    If you deploy the MCP server and web client on separate hosts, set MCP_SSE_URL to point the web client at the server:

    bash
    -e MCP_SSE_URL=http://:8000/sse

    Persistent Configuration

    By default, configuration saved through the Web UI (API keys, Litmus Edge instances, model preferences, connection settings) is written to .env inside the container and is lost when the container is removed.

    To retain configuration across container restarts and replacements, mount a host file over /app/.env:

    bash
    # One-time setup — the host file must exist before docker run
    mkdir -p /opt/litmus-mcp
    touch /opt/litmus-mcp/.env
    
    # Run with the volume mount
    docker run -d --name litmus-mcp-server \
      -p 8000:8000 -p 9000:9000 \
      -v /opt/litmus-mcp/.env:/app/.env \
      ghcr.io/litmusautomation/litmus-mcp-server:latest

    Any configuration you save in the UI is written to /opt/litmus-mcp/.env on the host. A new container started with the same -v flag will pick it up automatically on startup.

    Note: The host-side file must be created with touch before running the container. If it does not exist, Docker creates a directory at that path and the application will fail to write configuration.

    Docker Compose equivalent:

    yaml
    services:
      litmus-mcp-server:
        image: ghcr.io/litmusautomation/litmus-mcp-server:latest
        ports:
          - "8000:8000"
          - "9000:9000"
        volumes:
          - /opt/litmus-mcp/.env:/app/.env

    ---

    Claude Code CLI

    Run Claude from a directory that includes a configuration file at ~/.claude/mcp.json:

    json
    {
      "mcpServers": {
        "litmus-mcp-server": {
          "type": "sse",
          "url": "http://localhost:8000/sse",
          "headers": {
            "EDGE_URL": "${EDGE_URL}",
            "EDGE_API_CLIENT_ID": "${EDGE_API_CLIENT_ID}",
            "EDGE_API_CLIENT_SECRET": "${EDGE_API_CLIENT_SECRET}",
            "NATS_SOURCE": "${NATS_SOURCE}",
            "NATS_PORT": "${NATS_PORT:-4222}",
            "NATS_USER": "${NATS_USER}",
            "NATS_PASSWORD": "${NATS_PASSWORD}",
            "INFLUX_HOST": "${INFLUX_HOST}",
            "INFLUX_PORT": "${INFLUX_PORT:-8086}",
            "INFLUX_DB_NAME": "${INFLUX_DB_NAME:-tsdata}",
            "INFLUX_USERNAME": "${INFLUX_USERNAME}",
            "INFLUX_PASSWORD": "${INFLUX_PASSWORD}"
          }
        }
      }
    }

    Anthropic Docs

    ---

    Cursor IDE

    Add to ~/.cursor/mcp.json or .cursor/mcp.json:

    json
    {
      "mcpServers": {
        "litmus-mcp-server": {
          "url": "http://:8000/sse",
          "headers": {
            "EDGE_URL": "https://",
            "EDGE_API_CLIENT_ID": "",
            "EDGE_API_CLIENT_SECRET": "",
            "NATS_SOURCE": "",
            "NATS_PORT": "4222",
            "NATS_USER": "
    
    - [MCP.so](https://mcp.so/server/litmus-mcp-server/litmusautomation)
    
    ---
    
    © 2026 Litmus Automation, Inc. All rights reserved.

    Similar MCP

    Based on tags & features

    • AD

      Adls Mcp Server

      Python·
      4
    • KI

      Kill Process Mcp

      Python·
      9
    • DA

      Davinci Resolve Mcp

      Python·
      327
    • FH

      Fhir Mcp Server

      Python·
      55

    Trending MCP

    Most active this week

    • PL

      Playwright Mcp

      TypeScript·
      22.1k
    • SE

      Serena

      Python·
      14.5k
    • MC

      Mcp Playwright

      TypeScript·
      4.9k
    • MC

      Mcp Server Cloudflare

      TypeScript·
      3.0k
    View All MCP Servers

    Similar MCP

    Based on tags & features

    • AD

      Adls Mcp Server

      Python·
      4
    • KI

      Kill Process Mcp

      Python·
      9
    • DA

      Davinci Resolve Mcp

      Python·
      327
    • FH

      Fhir Mcp Server

      Python·
      55

    Trending MCP

    Most active this week

    • PL

      Playwright Mcp

      TypeScript·
      22.1k
    • SE

      Serena

      Python·
      14.5k
    • MC

      Mcp Playwright

      TypeScript·
      4.9k
    • MC

      Mcp Server Cloudflare

      TypeScript·
      3.0k