OfficialVerified

Litmus MCP Server

Litmus Edge device data, configuration, and management interface for AI systems.

Data last scanned today · Reviewed today

36 5 dangerous tools62 tools★ 12PythonMIT

Overview

The Litmus MCP Server provides a bridge between LLMs and Litmus Edge environments. It facilitates device configuration, monitoring, and overall system management by adhering to the Model Context Protocol, allowing AI models to interact directly with industrial edge hardware and data streams.

Our verdict

With a security score of 43/100, this server is classified as high-risk. The assessment highlights critical areas that remain unverified, specifically that the authentication methods and the read-only mode status have not yet undergone security review. Due to these significant unknowns regarding data access and protection, this tool should be treated with caution and is currently recommended only for development environments rather than production or sensitive industrial deployments.

Zero direct dependencies minimize the software supply-chain surface area.
Active maintenance with a commit nine days ago.
Comprehensive README documentation for deployment configurations.
Seven contributors involved in the repository development.

Authentication methods have not yet been editorially reviewed.
Read-only mode status remains unconfirmed by security audit.
Community-maintained project rather than an official vendor release.

Tools

Tool	Description	Risk
get_litmusedge_driver_list	List supported Litmus Edge drivers (e.g., ModbusTCP, OPCUA, BACnet).	low
get_devicehub_devices	List all configured DeviceHub devices with connection settings and status.	low
create_devicehub_device	Create a new device with specified driver and default configuration.	medium
get_device_connection_status	Check whether devices are actively publishing data via InfluxDB heartbeat (connected/stale/no_data).	low
get_devicehub_device_tags	Retrieve tags (data points/registers) for a specific device or all devices, paginated via limit/offset so any tag count can be paged through.	low
get_current_value_of_devicehub_tag	Read the current real-time value of a specific device tag.	low
create_devicehub_tag	Create a new tag (register) on a device.	medium
update_devicehub_tag	Update mutable fields of an existing tag (display name, description, properties).	medium
delete_devicehub_tag	Delete a tag from a device.	high
get_tag_status	Return runtime state (OK/Failed/Unknown) for tags on a specific device.	low

Compatibility

Client	Local	Docker	Remote	Read-only
ChatGPT
Claude Desktop
Cursor
VS Code
Windsurf

Frequently asked questions

›What architecture is required to run the Litmus MCP Server?

The server is built for linux/AMD64 platforms. Users on ARM64 systems must specify the --platform linux/amd64 flag when running the Docker container.

›How can I deploy the server with HTTPS support?

You can use a TLS-terminating reverse proxy like Caddy for automatic certificates, or provide your own certificate and key files via SSL_CERTFILE and SSL_KEYFILE environment variables for native TLS.

›Are self-signed certificates supported for native TLS?

No, self-signed certificates are rejected by Claude Desktop and claude.ai. You must use a certificate issued by a CA that your client machines already trust.

›Can I interact with the server without configuring an external MCP client?

Yes, the Docker image includes a built-in web-based chat interface accessible on port 9000, which allows you to connect to Litmus Edge instances directly through your browser.

›Which MCP transport protocols does the HTTP server support?

The server exposes two endpoints: /mcp for current streamable HTTP and /sse for legacy HTTP+SSE transport.