mermate-opseeq-connect
Use when configuring, troubleshooting, or verifying the connection between Mermate and the Opseeq runtime gateway, including stage event reporting and pipeline orchestration.
SKILL.md.agents/skills/mermate-opseeq-connect/SKILL.md
GitHubMermate-Opseeq Connection
Required Configuration
.env
OPENAI_BASE_URL=http://localhost:9090/v1
OPSEEQ_URL=http://localhost:9090
Do NOT include /v1 in OPSEEQ_URL — each module appends path segments as needed.
.mcp.json
{
"mcpServers": {
"opseeq": { "url": "http://localhost:9090/mcp", "transport": "sse" },
"synth": { "command": "synthesis-mcp", "transport": "stdio" }
}
}
Pipeline Stage Reporting
Mermate reports stage events to Opseeq via opseeq-bridge.js:
reportStage(runId, stageEvent)— POST toOPSEEQ_URL/api/mermate/stagegetTrace(runId)— GET fromOPSEEQ_URL/api/mermate/trace/:run_id
Stage flow: render -> tla -> ts -> rust -> desktop
Opseeq MCP Tools for Mermate
Available via Opseeq MCP at http://localhost:9090/mcp:
mermate_status— copilot health, TLA+, TS, agent availabilitymermate_agent_modes— list agent modesmermate_render— send source for compilationmermate_generate_tla— generate TLA+ from runmermate_generate_ts— generate TypeScript from runpipeline_orchestrate— full multi-stage pipeline with reviewartifact_verify— verify pipeline artifacts
Docker
Image tag: mermate:v5
Build: docker build -t mermate:v5 .
Opseeq rebuild from Mermate: npm run opseeq:docker:build
Health Verification
- Mermate:
curl http://localhost:3333/api/copilot/health - Opseeq:
curl http://localhost:9090/health - Cross-check:
curl http://localhost:9090/api/status— verifymermate.running = true