Sealights MCP Server

You can run the sealights-mcp server in a container using Podman or Docker:

Local serverstdio

What is the Sealights MCP MCP server?

You can run the sealights-mcp server in a container using Podman or Docker:. That is what the sealights mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

What it needs from you

Configuration is passed through the environment: SEALIGHTS_DOMAIN, SEALIGHTS_API_TOKEN, SEALIGHTS_AGENT_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Among the cloud and infrastructure options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by redhat-ai-tools; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Sealights MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How to install the Sealights MCP MCP server

{
  "mcpServers": {
    "sealights": {
      "command": "podman",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e", "SEALIGHTS_DOMAIN",
        "-e", "SEALIGHTS_API_TOKEN",
        "-e", "SEALIGHTS_AGENT_TOKEN",
        "quay.io/maorfr/sealights-mcp"
      ],
      "env": {
        "SEALIGHTS_DOMAIN": "https://your-domain.sealights.co",
        "SEALIGHTS_API_TOKEN": "REDACTED",
        "SEALIGHTS_AGENT_TOKEN": "REDACTED"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
SEALIGHTS_DOMAINConfiguration value read at startup.Optional
SEALIGHTS_API_TOKENCredential the server authenticates with.Yes
SEALIGHTS_AGENT_TOKENCredential the server authenticates with.Yes

Frequently asked questions

It connects Sealights MCP to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with Sealights MCP directly.