ReadyAPI 4.3.0

What's new in 4.3.0

Available now: ReadyAPI MCP Server
ReadyAPI MCP Plugin 1.1.0 is now available. From ReadyAPI 4.1.0 onwards, you can now build human and agentic workflows through MCP tools, keeping you in control of your data and workspace. MCP support is opt-in and becomes active only after you install the ReadyAPI MCP Plugin. See MCP Integration to learn more.
Once installed, you can connect Claude, GitHub Copilot, Cursor, and other AI assistants directly to your ReadyAPI workspace and describe what you need in plain English - the MCP Server handles the rest:
- Generate tests - Scaffold test cases from any OpenAPI spec in seconds.
- Detect spec changes - Surface-breaking changes and the exact tests they affect.
- Heal failing tests - Apply AI-recommended fixes directly to your project.
- Run and inspect - Trigger test runs and fetch per-step results without leaving your AI assistant.
Works with Claude Desktop, VS Code + Copilot, Cursor, and any MCP-compatible client. Requires ReadyAPI 4.1.0 or later.
UI Update Notice
ReadyAPI 4.0.0 introduced a refreshed user interface.
During the documentation update process, some screenshots and videos may display the previous UI. Functionality and workflows remain unchanged.
ReadyAPI 4.3.0 introduces the following enhancements and updates. See Version History for changes in previous releases.
AsyncAPI Enhancements
- AsyncAPI 3.0 support: ReadyAPI now supports AsyncAPI 3.0 imports alongside existing 2.x definitions. Key changes include:
- Operation names from your definitions now appear in the Navigator exactly as defined - for both 2.x and 3.0.
- In AsyncAPI 3.0, publish/subscribe is replaced with send/receive.
- The Endpoints tab has been renamed to Servers.
- A read-only Specification tab and version badges are now available.
For more information, see AsyncAPI Support.
Virtualization Enhancements
- Support for Send as Text mode in REST attachments: The Attachments table for multipart/form-data requests now includes a Send as column, letting you choose whether each part is sent as a file attachment or as plain form-data text. Existing requests default to File. For more information, see the REST Attachments section.
- New script object for Virtual Service responses: The Groovy script context for Virtual Services now includes mockResponseLite, a high-performance alternative to mockResponse for high-concurrency scenarios. It is available only in the Edit Response script context. …

Full release notes »