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
Authorizationheader.
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. Sign in and approve
The client opens TestOptim in your browser. Sign in, then read the consent page. It names the client and lists what it can do:
- See your projects
- Start and stop test runs, and read their results
- Read the issues TestOptim found
- Start explorations of your app
Select Allow. Only the Owner or an Admin of the organization can approve.
3. The client connects
The browser returns to the client, and the server shows as connected. The client lists 8 tools: list_projects, start_test_run, get_test_run, stop_test_run, list_issues, get_issue, start_exploration and get_exploration.
4. Ask for results
We called three tools:
-
list_projectsreturned our 2 projects. -
list_issueson one project returned the open issues, with severity and status. -
get_issuereturned one issue in full: description, 5 steps to reproduce, expected and actual behaviour, the page URL and a screenshot link.
In a coding agent, the same calls look like this: "Run the QA tests on the checkout project and show me the critical issues." The agent calls start_test_run, waits with get_test_run, then reads the results with list_issues and get_issue. A test run uses your plan's test executions, the same as a run started in the app.
5. Remove access when you are done
Each OAuth connection appears in TestOptim under Settings → API keys, named after the client, for example "MCP Inspector (OAuth)". Disconnecting in the client does not remove it. To stop access, revoke it there.
API keys still work
If your client does not support OAuth sign-in, create an API key under Settings → API keys and send it as Authorization: Bearer topt_.... The setup for each client is in the TestOptim MCP README.
TestOptim plans start at $19 a month after a 7-day free trial that needs a card. testoptim.com



Top comments (0)