The path is short and always the same: find the application, find the branch, find the build, read its coverage. Because the Build Session ID is the key throughout, a question about one specific CI run is two calls rather than a hunt through the UI.
An MCP server for SeaLights. Seven read tools cover applications, branches, builds, per-build coverage and metadata, the agents currently reporting, and the audit log.
- Every application SeaLights holds
- The branches for an application, visible ones by default
- Builds for an application, a branch, or both
- Coverage for one build, by its Build Session ID
- Detailed metadata for that same build
- The agents currently live
- Every action recorded in the audit log
Your SeaLights domain plus an API token and an agent token, passed to a Podman or Docker container. It can also run over SSE against a hosted URL, with the same tokens sent as headers.
One command plus a key — podman run -i --rm -e SEALIGHTS_DOMAIN -e SEALIGHTS_API_TOKEN -e SEALIGHTS_AGENT_TOKEN quay.io/maorfr/sealights-mcp, then supply credentials