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 is the full flow, step by step.
What we tested
We ran this flow with the MCP Inspector (v2.15.0, MCP protocol 2025-11-25). Other clients that support OAuth sign-in for remote servers use the same flow, but we did not test them for this post.
1. Add the server with only its URL
Transport: Streamable HTTP
URL: https://api.testoptim.com/api/mcp
No Authorization header.
The server answers the first request with 401 and a WWW-Authenticate header that points to its OAuth metadata. The client finds the sign-in page from there and registers itself. You do not enter a client ID.
2.…