get_appsLABSCO SUMMARY
Coverage numbers without opening the dashboard.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
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
USE CASES
01
Checking whether a build is covered enough to release
List the builds for the branch, take the session ID of the one you are shipping, and read its coverage.
02
Finding the build a CI run produced
Walk down from the application to its branches to its builds — three calls that replace navigating the same hierarchy by hand.
03
Understanding what a build actually contained
Read the metadata beside the coverage, so a coverage drop can be attributed to what changed rather than guessed at.
04
Confirming your agents are reporting
Check which agents are live before trusting a gap in the data — an absent agent looks exactly like untested code.
05
Answering who changed what
Read the audit log actions when a setting moved and nobody remembers moving it.
7 tools
Listed in project docs. Your client may show a different list.
get_audit_log_actionsget_branchesget_build_coverageget_build_metadataget_buildsget_live_agentsBEFORE YOU INSTALL
What to know first
Tools you get
7 tools named in the project's documentation.
Requires
- podman on PATH
- SEALIGHTS_API_TOKEN in your environment
- SEALIGHTS_AGENT_TOKEN in your environment
INSTALLATION
Connect your client
Server setup
TERMINAL
podman run -i --rm -e SEALIGHTS_DOMAIN -e SEALIGHTS_API_TOKEN -e SEALIGHTS_AGENT_TOKEN quay.io/maorfr/sealights-mcpMCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"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": "<YOUR_SEALIGHTS_API_TOKEN>",
"SEALIGHTS_AGENT_TOKEN": "<YOUR_SEALIGHTS_AGENT_TOKEN>"
}
}
}
}
