Troubleshooting
Fix server URL, sign-in, organization, permission and missing-project problems with Autonomy MCP.
Most MCP problems come from one of three causes: the wrong server URL, the wrong signed-in account, or the wrong organization. Check those before changing the client's settings.
Wrong server URL
Check that the client uses https://app.autonomyqa.com/api/mcp, ending with /api/mcp.
API key rejected
MCP doesn't accept organization API keys (aut_…). Remove any Authorization header or key from the client's MCP settings and let it sign in through the browser. API keys are for the HTTP API.
Sign-in loop or expired link
The sign-in link from a client works once and only for a few minutes. If the page says "This link has expired", start the connection again from the client. If the loop continues, sign out of Autonomy QA in the browser, remove the connection in the client, and connect again.
Wrong or missing organization
Each connection reaches one organization: the one you chose when you authorized it. To reach another, connect the client again and choose that organization. If the page says your account isn't in an organization yet, create one in Autonomy QA or ask to be invited, then connect again.
Missing projects
A member's assistant reaches only the projects that member can open. If autonomy_project_list doesn't show a project, ask an organization admin to give you access to it, then try again. Owners and admins reach every project.
Permission errors
A tool that returns FORBIDDEN: This operation requires the <scope> scope. was called without that permission. When the client connects again, approve the permission it asks for. If the consent screen doesn't list it, the client didn't request it; check the client's settings.
Wrong project or environment
Runs use environments of the same project as the test case. If a run can't find its environment, list the project's environments with autonomy_environment_list and use one of their slugs.
Client cache
Some clients cache their sign-in. If the browser flow succeeds but tools still fail, remove the Autonomy server from the client, restart the client, and add the server again.
Didn’t find it?