Available now: ReadyAPI MCP Server ReadyAPI MCP Plugin 1.0.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. Coming soon: Version 1.1.0 of the ReadyAPI MCP Plugin is due to release later in August 2026. 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.2.0 includes the following updates. See Version History for changes in previous releases. Before you upgrade
• H2 database migration: ReadyAPI 4.2.0 removes the H2 migrator. If you are upgrading from a version earlier than 3.51.0, complete the H2 database migration before upgrading to 4.2.0 by first upgrading to any version between 3.51.0 and 4.1.0. For more information, see H2 Migration. AI Enhancements
• AI Test Generation plugin now uses Gemini 3: The AI Test Generation plugin no longer supports Gemini 2.5 as the performance model. Gemini 3 replaces it as the default.
• ReadyAPI MCP plugin update notifications: ReadyAPI now notifies you when a newer version of the MCP plugin is available, so you can keep your plugin up to date. UI Enhancements
• Functional Test UI updates: The Coverage and History sections now share a consistent look and feel with the rest of ReadyAPI, making it easier to navigate between views.
• Security UI updates: The Security module, Security Tests creator, and Auth Manager now share a consistent look and feel with the rest of ReadyAPI, making security configuration easier to navigate.
• Virtualization UI updates: The JDBC Request dialog and Conditional Match configuration dialog now share a consistent look and feel with the rest of ReadyAPI, making virtualization setup easier to navigate. For more information, see JDBC Request, Conditional Match Overview, and How to Use Conditional Match. Security Enhancements
• New VM option to enforce Auth Repository encryption: IT administrators can now add -AuthProfileEncrypt=true to the ReadyAPI deployment package to ensure the Auth Repository is encrypted by default for all users, preventing OAuth tokens and credentials from being exposed in project files. For more information, see Auth Repository. Integrations
• Improved Zephyr Squad integration: Selecting a cycle in the Map to Zephyr dialog now filters the test case list to show only test cases for that cycle, making it easier to map the right test cases to the correct cycle. For more information, see 2. Map a ReadyAPI project to Zephyr Squad. Performance Enhancements
• Improved TPS performance in Load Tests: ReadyAPI now handles thread contention more efficiently during Load Test execution, resulting in higher transactions per second (TPS).
• Improved Load Test step performance: ReadyAPI now caches settings for the most commonly used Load Test steps, reducing overhead and improving overall Load Test performance. General Updates
• Reduced logging in Conditional Match: ReadyAPI now uses reduced logging frequency in Conditional Match, improving dispatching performance and throughput in the Virtualization module.
• Resolved macOS compatibility warning for x64 applications: ReadyAPI no longer displays a compatibility warning for x64 applications on macOS.
• Opening projects from older ReadyAPI versions: Projects created in versions prior to ReadyAPI 3.57.0 open normally in ReadyAPI 4.2.0 but are automatically saved with AES encryption. Once saved, these projects can no longer be opened in ReadyAPI versions that predate AES encryption support (pre-3.57.0). For more information, see Protecting Sensitive Data.
• Library Updates: ReadyAPI 4.2.0 uses newer versions of several libraries than 4.1.0. If your scripts reference any classes from the Libraries Updated in 4.2.0, review and update them as needed. See Bug Fixes in ReadyAPI 4.2.0 for the complete list of fixes included in this release.