01
Bring the manifests.
Import two tools/list JSON snapshots: the version you know and the version you’re considering.
PLANNED · JSON IMPORT
A review layer for MCP tool manifests
Review what changed
in your agent’s tools.
A tool update can change more than a version number. Omnix is being built to put manifest changes in view—before you update an integration.
MCP tools/list in. A focused review out.
01 / The review, in focus
Small diff. Important context.
Explore three changes in a sample manifest.
Choose a change to see what’s different.
Beforebaseline.json
Aftercandidate.json
What to review
Visible changes, with the original context beside them. This preview uses sample data; it doesn’t assess whether an update is safe.
02 / A deliberate update
From two snapshots
to one clear decision.
The first version is planned around a simple loop:
compare, review, then keep a baseline.
02
Look at the changes.
Review added or removed tools, edited descriptions, and changes to input schemas in one focused comparison.
PLANNED · MANIFEST DIFF
03
Keep your baseline.
After your team’s review, export an approved baseline to use as the starting point for the next update.
PLANNED · BASELINE EXPORT
Currently in development
Less hunting through JSON.
More considered updates.
We’re shaping Omnix for developers who connect AI agents to tools through MCP. The goal is a small, useful review step that fits between a manifest update and an integration change.
BUILD NOTES / 001Back to the sample
Explore the concept
The interactive sample is ready to try.
Next: your own manifests
JSON imports, saved baselines and exports are planned for the first version.