Skip to content

Deployment

Deployment Options

lgtm-mcp supports local stdio, a loopback-only development listener, a least-privilege stdio container, and a remote authenticated HTTPS boundary. Provider endpoint, credential, selector, identity, and trust material are supplied at runtime through AgentConfig; none is stored in this repository.

Installed stdio process

{
  "mcpServers": {
    "lgtm": {
      "command": "lgtm-mcp",
      "args": [],
      "env": {"MCP_TOOL_MODE": "intent"}
    }
  }
}

Loopback development listener

lgtm-mcp --transport streamable-http --host 127.0.0.1 --port 8000

Do not expose this listener beyond loopback. Network deployments require direct TLS or an explicitly trusted TLS-terminating ingress, configured authentication, exact MCP_ALLOWED_HOSTS, and an exact trusted-proxy CIDR policy.

Least-privilege local container

docker run -i --rm \
  --read-only \
  --cap-drop=ALL \
  --security-opt=no-new-privileges \
  --pids-limit=256 \
  --tmpfs /tmp:rw,noexec,nosuid,nodev,size=64m \
  -e TRANSPORT=stdio \
  registry.example.invalid/lgtm-mcp@sha256:<digest> lgtm-mcp

The operator projects the selected AgentConfig profile into the process at runtime; the image remains immutable and contains no environment connection profile.

Remote authenticated HTTPS endpoint

{
  "mcpServers": {
    "lgtm": {"url": "https://service.example.invalid/mcp"}
  }
}

Store the real remote URL, outbound identity reference, and TLS-profile reference in AgentConfig, not in MCP client JSON or documentation.

This page covers running lgtm-mcp as a long-lived server: the transports, a Docker Compose stack, putting it behind a Caddy reverse proxy, and giving it a DNS name with Technitium. To provision the LGTM observability stack it connects to, see Backing Platform.

lgtm-mcp ships both an MCP server (console script lgtm-mcp) and a Pydantic-AI agent server (console script lgtm-agent). The MCP server is a typed, deterministic tool surface a policy router or agent calls; the agent server connects to that surface to deliver a conversational interface. The agent section is documented at the end of this page.

Run the MCP server

The transport is selected with --transport (or the TRANSPORT env var):

lgtm-mcp
For IDE / desktop MCP clients that start the server as a subprocess.

lgtm-mcp --transport streamable-http --host 0.0.0.0 --port 8000
A network server with a /health endpoint and /mcp route.

lgtm-mcp --transport sse --host 0.0.0.0 --port 8000

Health check (HTTP transports):

curl -s http://localhost:8000/health        # {"status":"OK"}

Configuration (environment)

lgtm-mcp is configured entirely from the environment. The required set:

Var Default Meaning
ALERTMANAGER_URL http://localhost:9093 Prometheus Alertmanager API URL
GRAFANA_URL http://localhost:3000 Grafana API endpoint
LGTM_TOKEN (none) Grafana admin API key or service token

Plus HOST / PORT / TRANSPORT for HTTP transports. The full set is documented in .env.example. Copy it to .env and fill in the operator's service endpoints before starting the server.

Docker Compose

The repo ships docker/mcp.compose.yml. It reads a sibling .env and publishes the HTTP server on :8000:

services:
  lgtm-mcp:
    image: example/lgtm-mcp@sha256:<digest>
    container_name: lgtm-mcp
    hostname: lgtm-mcp
    restart: always
    env_file:
      - .env
    environment:
      - PYTHONUNBUFFERED=1
      - HOST=0.0.0.0
      - PORT=8000
      - TRANSPORT=streamable-http
    ports:
      - "8000:8000"
    healthcheck:
      test: ["CMD", "python3", "-c", "import urllib.request; urllib.request.urlopen('http://localhost:8000/health')"]
      interval: 30s
      timeout: 10s
      retries: 3
cp .env.example .env          # then edit GRAFANA_URL / ALERTMANAGER_URL / LGTM_TOKEN
docker compose -f docker/mcp.compose.yml up -d
docker compose -f docker/mcp.compose.yml logs -f

Behind a Caddy reverse proxy

Expose the HTTP server on a hostname with automatic TLS. Add to the operator's Caddyfile:

# Internal (self-signed) — homelab .example.invalid zone
lgtm-mcp.example.invalid {
    tls internal
    reverse_proxy lgtm-mcp:8000
}
# Public — automatic Let's Encrypt
lgtm-mcp.example.com {
    reverse_proxy lgtm-mcp:8000
}

Reload Caddy:

docker compose -f services/caddy/compose.yml exec caddy caddy reload --config /etc/caddy/Caddyfile

DNS with Technitium

Point the hostname at the host running Caddy. Via the Technitium API:

curl -s "http://technitium.example.invalid:5380/api/zones/records/add" \
  --data-urlencode "token=$TECHNITIUM_DNS_TOKEN" \
  --data-urlencode "domain=lgtm-mcp.example.invalid" \
  --data-urlencode "zone=arpa" \
  --data-urlencode "type=A" \
  --data-urlencode "ipAddress=192.0.2.10" \
  --data-urlencode "ttl=3600"

…or add an A record lgtm-mcp.example.invalid → <caddy-host-ip> in the Technitium web console (http://technitium.example.invalid:5380). The ecosystem technitium-dns-mcp automates this as a tool.

Register with an MCP client

Add to the operator's client's mcp_config.json (multiplexer nickname lgtm):

{
  "mcpServers": {
    "lgtm-mcp": {
      "command": "uv",
      "args": ["run", "lgtm-mcp"],
      "env": {
        "GRAFANA_URL": "http://your-grafana:3000",
        "ALERTMANAGER_URL": "http://your-alertmanager:9093",
        "LGTM_TOKEN": "your_grafana_api_token"
      }
    }
  }
}

For a remote HTTP server, point the client at http://lgtm-mcp.example.invalid/mcp instead.

Agent server

lgtm-mcp also ships a Pydantic-AI agent server (console script lgtm-agent) that connects to the MCP tool surface and exposes a conversational endpoint. It is built on the scion-sdk agent runtime and is installed with the agent extra:

pip install "lgtm-mcp[agent]"

Run it, pointing it at a running MCP server with --mcp-url (or wire it to a local mcp_config.json with --mcp-config):

lgtm-agent --mcp-url http://lgtm-mcp.example.invalid/mcp --host 0.0.0.0 --port 8080
Flag / Var Meaning
--mcp-url URL of the running MCP server the agent attaches to
--mcp-config Path to an mcp_config.json (defaults to mcp_config.json)
--host / --port Bind address for the agent HTTP server
--provider / --model-id LLM provider and model identifier

To run the agent in Docker, build from the repository and start the lgtm-agent entrypoint, setting MCP_URL to the MCP server endpoint. Place both the MCP server and the agent on the same Docker network so the agent reaches the server by container name (for example http://lgtm-mcp:8000/mcp).