Let your coding agent ask a QA agent: connect TestOptim over MCP with one sign-in
Your coding agent says the change is done. A QA agent can check that. TestOptim runs AI tests on your web app and logs each failure as an issue with steps to reproduce. Its remote MCP server lets an MCP client list your projects, start test runs and read those issues. Until now you had to create an API key and paste it into the client config. Since Nov 10 you can sign in with OAuth instead. Here…
Your coding agent can now request QA agent assistance by connecting TestOptim over MCP with a single sign-in. QA tests run on your web app and log failures as issues with reproduction steps. TestOptim connects via its remote MCP server, which allows an MCP client to list projects, start test runs and read issues.
The configuration process now relies on OAuth sign-in instead of manually entering an API key into the client config. You simply add the server's URL in the browser, sign in, approve the consent page, and the client connects to the server. The client lists the available tools, such as listing projects, starting test runs, fetching issue details, and running explorations.
Using the coding agent's commands, you can ask TestOptim to execute QA tests, for example, "Run the QA tests on the checkout project and show me the critical issues." The agent will then call the necessary functions like start_test_run, get_test_run, list_issues, and get_issue to retrieve the desired test results.
If you no longer need access, you can remove the OAuth connection from TestOptim's Settings → API keys, under the client's named entry. Note that API keys still function for clients that do not support OAuth sign-in, and the setup details are provided in the TestOptim MCP README. TestOptim plans start at $19 a month after a 7-day free trial requiring a card.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.