Scope and Limitations
This page describes what the MCP integration currently supports, what it does not support, and important constraints to be aware of before use.
REST APIs only
The MCP integration currently supports only REST APIs. GraphQL, WSDL, AsyncAPI, gRPC, and other protocol types are not supported for AI test generation or impact analysis. While api_import accepts multiple definition formats, the generate_test_cases_for_api and test_impact_analyze tools are optimized for REST/OpenAPI specifications exclusively. Support for additional protocol types is planned for a future release.
Local access only
The MCP Server binds only to 127.0.0.1. It is not accessible from other machines on the network, and this cannot be changed. All interaction happens through an MCP client running on the same machine as ReadyAPI.
Single concurrent connection
The MCP Server currently supports one connected client at a time. If you need to connect a second client, disconnect the first. Multi-connection support is in development.
Bearer-token authentication only
The server uses bearer-token authentication only. The bearer-token model is appropriate for the local single-user context in which the server operates.
No in-app review UI
AI-suggested changes - including generated test cases and applied fixes - appear as output in your MCP client. There is no in-app accept or decline UI in this release. Every change is captured in the MCP logs in ReadyAPI, providing an audit trail. Review all proposed changes in your MCP client before they are applied.
For planned improvements to this, see What's Coming.
Tools write directly to your workspace
Every Create, Update, Delete, and Generate tool modifies project files on disk immediately. There is no staging or preview step. All updates are live and can be monitored and reviewed in the ReadyAPI UI. Review proposed changes carefully before applying them, especially against projects that are shared or under version control.
To maintain control over AI-generated changes, we recommend the following workflow:
Initialize Git (or your version control system of choice) on your ReadyAPI project.
Create and switch to a feature branch before making MCP-driven changes.
Apply changes through MCP tools.
Push the branch and review the diff before merging.
Note
Git branch management and diff review work best with ReadyAPI composite projects. For more information, see Git Integration.
Save before running
Any changes made directly in the ReadyAPI UI must be saved before triggering a test run through the MCP tools. MCP picks up the last saved version of the project - unsaved UI changes are not visible to the MCP Server.
Agent XML access
If an agent cannot complete a task using the available MCP tools, it may attempt to read the ReadyAPI project XML directly. This is not a supported or recommended approach. To prevent this, include the following instruction at the start of each session: "Never read ReadyAPI project XML files directly."