Litmus MCP
Gives Claude access to your Litmus Edge deployment: browse DeviceHub devices and tags, read real-time and historical process data, manage Digital Twins, inspect system health, and reach the full Litmus SDK surface. This extension bridges Claude Desktop to a Litmus MCP Server you run on your own network (see https://github.com/litmusautomation/litmus-mcp-server); your credentials are stored in the operating system keychain and sent only to that server.
- Integration type
- Connector
- Verification status
Verified connector- Platform
- Claude
- Primary Subcategory
- Pending
- Secondary Subcategories
- None listed
- Brand
- Litmus Automation
- Access
- Unknown
- First tracked
- 2026-08-04
- Tool count
- 0
- Geography
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is visible.
Claude Discoverability Score
Your public score is being prepared
Litmus MCP is tracked in the public registry. Its Discoverability Score will appear as soon as the public benchmark is ready - never as an estimate.
Competitive lineup
How the Discoverability Score works
The Claude Discoverability Score will be the percentage of contested conversations where Litmus MCP appears in the connector picker or Claude invokes it directly. Found and Positioned will be shown as diagnostics, not score inputs.
Organic discovery scoring is pending. Your Connector score will appear on this scale when measurement goes live.
FoundDiagnostic
Whether Claude found your Connector in connector search. It must be Found before it can reach the picker, but the score counts picker appearances—not search results.
PickedMain score
How often your Connector appeared in the picker, or Claude invoked it directly, across contested conversations. This percentage is the Discoverability Score; the headline number is rounded.
PositionedDiagnostic
What position your Connector appeared in when it was shown in the picker. This shows prominence, but it does not affect the score.
0 tools agents can invoke
No tools are exposed by this Claude Connector in the latest snapshot.
How do I improve a Verified connector's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.