---
title: Web UI
slug: litmus-mcp-server/web-ui
docTags: 
createdAt: 2026-05-11T21:42:05.387Z
---

The Docker image includes a built-in chat interface that lets you interact with Litmus Edge using natural language. No MCP client configuration required.

## Start the server with the Web UI

```bash
docker run -d --name litmus-mcp-server \
  -p 8000:8000 -p 9000:9000 \
  -e ANTHROPIC_API_KEY=<key> \
  ghcr.io/litmusautomation/litmus-mcp-server:latest
```

- `:9000` Web UI. Open `http://localhost:9000` in your browser, add a Litmus Edge instance via the config page, and start chatting.
- `:8000` SSE endpoint for external MCP clients. Still available; using the Web UI does not disable it.

## First-run setup

If no LLM API key is configured, opening `http://localhost:9000` lands on a setup screen. Enter at least one of:

- `ANTHROPIC_API_KEY`
- `OPENAI_API_KEY`
- `GEMINI_API_KEY`

The Web UI saves the keys and immediately fetches the live model catalog from each provider so you can pick a specific model.

## Pages

| Path          | Purpose                                                                                                         |
| ------------- | --------------------------------------------------------------------------------------------------------------- |
| `/`           | Chat interface. Streams the model's response, renders markdown, shows tool-call badges, supports a stop button. |
| `/update-env` | Configuration: API keys, model selection, Litmus Edge instances, NATS, InfluxDB, LEM.                           |
| `/health`     | One status card per configured Litmus Edge instance. Shows reachability and active-instance state.              |
| `/setup`      | First-run API key entry (auto-redirected to when no key is set).                                                |

## LLM providers

Supported providers: Anthropic Claude, OpenAI, Google Gemini.

The active provider and model are switchable from `/update-env` at any time. See [LLM Providers](#) for details.

## Multiple Litmus Edge instances

The Web UI lets you register and switch between multiple Litmus Edges from a single MCP server. Each instance keeps its own URL and OAuth2 credentials; the active instance is mirrored into the canonical `EDGE_URL` / `EDGE_API_CLIENT_ID` / `EDGE_API_CLIENT_SECRET` so the rest of the system works unchanged.

Manage instances under **Config -> Litmus Edge Instances**, or check status per-instance from the **Health** page. See [Multi-Instance Edge](#).

## Splitting the Web UI and MCP server across hosts

If you deploy the MCP server and the Web UI on separate hosts, point the Web UI at the server with:

```bash
-e MCP_SSE_URL=http://<mcp-server-host>:8000/sse
```

## Live Litmus documentation as MCP Resources

The server exposes `litmus://docs/<section>` URIs that fetch live content from [docs.litmus.io](https://docs.litmus.io) on demand. MCP-aware clients can pull current reference material directly into the model's context. See [MCP Resources](#).