---
title: MCP Resources
slug: litmus-mcp-server/mcp-resources
docTags: 
createdAt: 2026-05-11T21:37:38.039Z
---

The Litmus MCP server exposes a set of `litmus://docs/<section>` URIs as MCP **Resources**. MCP-aware clients can read these URIs on demand, fetching live content directly from [docs.litmus.io](https://docs.litmus.io).

This means an LLM client can pull current Litmus reference material into its context without you copying and pasting documentation.

## Why Resources

MCP tools are for actions the model takes. MCP resources are for static (or live-fetched) reference material the model reads. By exposing Litmus docs as resources, an MCP client can:

- Pull driver-specific documentation when configuring a new device.
- Read the DeviceHub or Digital Twins user guide when the model is unsure how a feature works.
- Confirm the current behavior of a Litmus Edge component before suggesting changes.

## Available resources

| URI                                     | Source page                                                                       |
| --------------------------------------- | --------------------------------------------------------------------------------- |
| `litmus://docs/overview`                | [docs.litmus.io](https://docs.litmus.io)                                          |
| `litmus://docs/edge`                    | `/litmusedge`                                                                     |
| `litmus://docs/edge/devicehub`          | `/litmusedge/product-features/devicehub`                                          |
| `litmus://docs/edge/digitaltwins`       | `/litmusedge/product-features/digital-twins`                                      |
| `litmus://docs/edge/datahub`            | `/litmusedge/product-features/datahub`                                            |
| `litmus://docs/edge/marketplace`        | `/litmusedge/product-features/applications`                                       |
| `litmus://docs/edgemanager`             | `/edgemanager`                                                                    |
| `litmus://docs/edgemanager/marketplace` | `/edgemanager/lem-user-ui/product-features/marketplace-catalogs-and-applications` |
| `litmus://docs/edgemanager/grafana`     | `/edgemanager/lem-user-ui/product-features/grafana-dashboards`                    |
| `litmus://docs/solutions`               | `/solutions`                                                                      |

The full list is defined in `src/tools/resource_tools.py`.

## How a client uses them

Standard MCP protocol:

1. Client calls `list_resources` -> server returns the URIs above.
2. Client calls `read_resource(uri)` with one of them -> server fetches the page via `httpx`, returns the rendered text.

Different MCP clients surface resources differently. Some expose them via a context menu ("attach resource"), some let the model autonomously call `read_resource` mid-conversation, some require manual selection.

## Live vs cached

Each `read_resource` call performs a fresh `httpx` GET against `docs.litmus.io`. No caching, no bundling. If the docs are updated, the next read picks up the changes.

## See also

- [Tools Reference](#) for the action-oriented half of the MCP surface.