OpenAPI to MCP
OpenAPI refresh & merge
How Agenetix non-destructively merges a new OpenAPI spec into your existing tool catalog.
When your API evolves, you can refresh the OpenAPI spec and Agenetix will merge the changes without destroying your work. New endpoints are added, changed endpoints are updated, and removed endpoints are disabled — your custom tool rules are always preserved.
How the merge works#
flowchart TD
Import["Import new OpenAPI spec"] --> Parse["Parse all operations"]
Parse --> Match["Match against existing tools"]
Match --> Existing["Existing match found"]
Match --> NoMatch["New endpoint"]
Match --> Missing["Endpoint removed"]
Existing --> Update["Update source description + schema\nPreserve your rules"]
NoMatch --> CreateNew["Add new tool\nenabled by default"]
Missing --> Disable["Disable tool\npreserve for history"]What gets updated vs. preserved#
| Category | During refresh |
|---|---|
| Source information (OpenAPI description, input schema, HTTP method/path) | Updated from the new spec |
| Your rule edits (description override, instructions, when to use, when not to use, examples) | Preserved, never overwritten |
| Enabled/disabled state | Preserved for existing tools |
Merge summary#
After a refresh, you see a summary of what changed:
| Category | Meaning |
|---|---|
| Added | New tools from endpoints that did not exist before |
| Updated | Existing tools where the OpenAPI description or schema changed |
| Unchanged | Tools with no differences from the new spec |
| Removed | Tools whose endpoint disappeared — disabled, not deleted |
| Reappeared | Previously removed tools that came back — re-enabled with your old rules intact |
Why removed tools are kept#
When an endpoint disappears from the spec, Agenetix disables the tool rather than deleting it. This preserves:
- Request log history for that tool
- Agent configurations that referenced the tool
- Your custom rules, in case the endpoint returns in a future spec version
- A clear audit trail of the tool's lifecycle
How to refresh#
In the dashboard: Open the server detail page and click Refresh OpenAPI.
You can provide a new spec URL or paste updated JSON directly. After the merge completes, review the summary to understand what changed before redeploying.