Products
OML MCP
OML MCP gives a coding assistant access to the monitoring context in your repository. Through the Model Context Protocol, the assistant can look up recorded route coverage, consult OML’s instrumentation rules, and check an edit against its plan.
Project connection
During interactive setup, npx oneminute init offers to register OML MCP with an installed Codex or Claude Code client. The client launches the server locally and exchanges tool requests and responses over standard input and output. The registered project root sets the boundary for file reads.
Reading route coverage
When you ask which checkout routes still need monitoring, the assistant can call oml_project_context. The tool reads application setup from oml.json and recorded routes from oml-report.json. It checks source fingerprints so changes to a file can invalidate an earlier coverage assessment.
The assistant can filter by application or route path. Results include the route status and unresolved operations. An empty route list means there are no matching records. The application may still have routes that have never been reviewed.
Instrumentation conventions
Before editing, the assistant can call oml_conventions with the framework and operation it is working on. For example, a worker that retries a request has several attempts and one final outcome. The guidance distinguishes a retry from a failure that prevents the work from completing.
The tool also covers operation timing with measureOperation and preserving existing transaction boundaries, retries, and exception handling.
Checking an edit
After an edit, oml_validate reads the current JavaScript or TypeScript file. The assistant supplies the original source, the target function or method, the instrumentation plan, and the logger identifier. The validator checks syntax, planned event counts, bindings, and structural preservation.
A passing result is labeled partial. It tells the assistant which source checks passed. Event severity, behavior under real traffic, and complete coverage still need separate evidence.
Report access
The preview exposes oml_update_report with writes disabled. It returns a disabled status and leaves the coverage record intact. Asking the assistant to validate an edit therefore cannot mark the route as verified in the shared report.