Skip to content

Conversation

@vish74
Copy link
Contributor

@vish74 vish74 commented May 15, 2025

Description

Adding official Litmus MCP server to the list of Third-Party Servers. Using MCP server Litmus Edge provides Industrial Data Collection, Edge Analytics & Industrial AI.

Server Details

Motivation and Context

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

How Has This Been Tested?

Extensively tested with:

  • Cursor IDE
  • Claude Desktop
  • VS Code / Copilot
  • Windsurf

Breaking Changes

N/A

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Protocol Documentation
  • My changes follows MCP security best practices
  • I have updated the server's README accordingly
  • I have tested this with an LLM client
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have documented all environment variables and configuration options

Additional context

@vish74
Copy link
Contributor Author

vish74 commented May 15, 2025

This PR is ready, please review it.
Thanks you team for maintaining this repo ! @cliffhall @tadasant @evalstate

Copy link
Member

@cliffhall cliffhall left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! 👍

@cliffhall cliffhall merged commit 97564f7 into modelcontextprotocol:main May 17, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants