Litmus Mcp Server

Created By
litmusautomationa year ago
Official MCP server for configuring Litmus Edge instances. https://litmus.io
Overview

What is Litmus MCP Server?

Litmus MCP Server is the official Model Context Protocol (MCP) Server developed by Litmus Automation, designed to enable large language models (LLMs) and intelligent systems to interact with Litmus Edge for device configuration, monitoring, and management.

How to use Litmus MCP Server?

To use the Litmus MCP Server, you can quickly launch it using Docker with the command: docker run -d --name litmus-mcp-server -p 8000:8000 ghcr.io/litmusautomation/litmus-mcp-server:main. You can also configure it in various IDEs like Cursor IDE, Claude Desktop, and VS Code by adding the server URL to their respective configuration files.

Key features of Litmus MCP Server?

  • Supports real-time communication via Server-Sent Events (SSE).
  • Provides a comprehensive API for device management and configuration.
  • Integrates with multiple development environments and tools.
  • Allows for easy setup and configuration through Docker.

Use cases of Litmus MCP Server?

  1. Configuring and managing devices in an industrial IoT environment.
  2. Monitoring device status and configurations in real-time.
  3. Integrating with development tools for enhanced productivity in automation tasks.

FAQ from Litmus MCP Server?

  • What is the purpose of the Litmus MCP Server?

It facilitates communication between intelligent systems and Litmus Edge for device management.

  • Is there documentation available?

Yes, comprehensive documentation can be found at Litmus Docs.

  • Can I run it on my local machine?

Yes, it can be easily run locally using Docker.

Server Config

{
  "mcpServers": {
    "litmus-mcp-server": {
      "url": "http://<IP Address>:8000/sse"
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
litmusautomation
Star
0
Language
Python
License
Apache-2.0 license
Category

Recommend Servers

View All
Meteomatics

14 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago
GovQL
@Alex Stout

# govql-mcp-server An MCP (Model Context Protocol) server for [GovQL](https://govql.us) — gives AI clients like Claude Desktop, Claude Code, and Cursor direct access to the US Congressional GraphQL API at [api.govql.us/graphql](https://api.govql.us/graphql) without bespoke HTTP wiring. For the design rationale (why FastMCP-Python, the passthrough+curated philosophy, roadmap through v0.4), see [design.md](https://github.com/govql/govql/blob/main/mcp-server/docs/design.md). ## What you can do with it Ask an agent questions like: - *"How did Vermont's two senators vote on the most recent nomination?"* - *"Which legislators in the 118th Congress switched parties during their service?"* - *"Compare Senator Sanders' voting record to Senator Murkowski's on cloture votes in the most recent Congress."* The agent picks the right tool, writes the GraphQL query against the live schema, and parses the response — no manual API wrangling. ## Install The server runs as a per-client subprocess over stdio. Pick your client: ### Claude Desktop Edit `claude_desktop_config.json` (Settings → Developer → Edit Config): ```json { "mcpServers": { "govql": { "command": "uvx", "args": ["govql-mcp-server"] } } } ``` Restart Claude Desktop. The `govql` tools appear in the tools panel. ### Claude Code Add to `.mcp.json` in your project (or `~/.mcp.json` for global): ```json { "mcpServers": { "govql": { "command": "uvx", "args": ["govql-mcp-server"] } } } ``` ### Cursor Settings → MCP → Add Server. Use the same `command` / `args` as above. ### Other clients Any MCP-compatible client that supports stdio servers will work. The command is `uvx govql-mcp-server` with no required arguments. ## Tools | Tool | Purpose | |---|---| | `execute_graphql` | Run any GraphQL query against the GovQL endpoint. Returns the result plus an `last_ingest` timestamp so the agent can reason about data freshness. | | `list_types` | Returns the names and kinds of every type in the GovQL schema. Optional `kind` filter (`"OBJECT"`, `"INPUT_OBJECT"`, `"ENUM"`, etc.) to narrow further. Start here when you don't know what's queryable. | | `describe_type` | Returns one type's full details — fields, arg signatures, input fields, enum values. Call after `list_types` to learn the shape of a specific type before writing a query. | ## Configuration All env vars are optional — the package is zero-config for end users. | Env var | Default | Purpose | |---|---|---| | `GOVQL_ENDPOINT` | `https://api.govql.us/graphql` | Endpoint to query. Override to point at a local dev stack. | | `GOVQL_TIMEOUT_MS` | `30000` | Per-request HTTP timeout. | | `LOG_LEVEL` | `INFO` | Logging level. Logs go to stderr only (stdout is reserved for the MCP transport). | ## Limits (enforced by the upstream API) - Max query depth: 10 - Max query complexity: ~10 billion points (`first: N` multiplies child cost by N — keep page sizes reasonable on deeply nested queries) - Rate limit: 100 requests / 60 s per source IP A depth or complexity violation surfaces as a GraphQL `errors` entry in the tool response so the agent can adjust and retry. ## Data freshness Every `execute_graphql` response includes a `last_ingest` ISO timestamp. Vote data refreshes hourly; legislator data refreshes daily. ## Status Version 0.1.0 ships three foundational tools: a GraphQL passthrough (`execute_graphql`) and two narrow schema-discovery tools (`list_types`, `describe_type`). Curated higher-level tools (`find_legislator`, `get_voting_record`, `compare_voters`, etc.) are planned for subsequent releases — see [design.md](https://github.com/govql/govql/blob/main/mcp-server/docs/design.md) for the roadmap. ## Links - [GovQL project site](https://govql.us) - [GraphQL API](https://api.govql.us/graphql) - [Source / issues](https://github.com/govql/govql)

an hour ago
Tip Mcp Server
@tip

11 hours ago