SEAR
Expose benchmark-oriented release metrics to your agent through a read-only HTTP MCP endpoint plus an operator CLI for release surfaces.
Overview
SEAR is a MCP server for the Ship phase that provides a read-only, benchmark-first MCP endpoint and operator CLI for release surfaces.
What is this MCP server?
- Streamable HTTP MCP remote at https://sear.genesisconductor.io/api/mcp
- Read-only MCP endpoint paired with an operator CLI for release operations
- Benchmark-first release surface (version 0.1.0) from the SEAR web app subfolder
- Public site https://sear.genesisconductor.io for context alongside MCP consumption
- Version 0.1.0 with remote MCP URL https://sear.genesisconductor.io/api/mcp
- MCP transport type streamable-http; endpoint documented as read-only
What problem does it solve?
You lack a single read-only place for your agent to see release and benchmark context, so ship decisions stay informal and hard to cite.
Who is it for?
Indie teams treating benchmarks as a release gate who want agent-friendly, read-only access to SEAR’s hosted surface.
Skip if: Builders who only need local pytest results with no shared release metric hub, or anyone requiring write/deploy actions solely through this MCP.
What do I get? / Deliverables
Your agent pulls benchmark-first release data over HTTP MCP while you use the CLI for operator workflows, tightening perf-aware ship checks.
- Read-only benchmark and release context available to the agent via MCP
- Operator CLI workflow aligned with the same SEAR release surface
Recommended MCP Servers
Journey fit
How it compares
Hosted benchmark release reader via MCP, not an in-repo test skill or generic observability dashboard.
Common Questions / FAQ
Who is SEAR for?
Solo builders and small teams shipping benchmark-sensitive releases who want agents to read SEAR release data without write access.
When should I use SEAR?
Use it in ship and perf review when you promote builds and want MCP-backed benchmark context alongside your operator CLI steps.
How do I add SEAR to my agent?
Add the streamable HTTP remote https://sear.genesisconductor.io/api/mcp to your MCP client configuration and install or use the operator CLI from the igor-holt/sear repository as documented.