Connect a client
Configure Claude Code, Cursor, VS Code, Windsurf, Codex, and other MCP clients to use the Autonomy MCP server.
Autonomy runs one remote MCP server over Streamable HTTP. Every client uses the same server URL and signs in through the browser. The first time a client connects, Autonomy opens a browser window where you sign in and pick the organization whose projects the assistant should reach.
https://app.autonomyqa.com/api/mcpAdd the server to your client
Run this command, then complete the browser authorization when prompted. See the Claude Code MCP docs for more.
claude mcp add --transport http autonomy https://app.autonomyqa.com/api/mcpAdd Autonomy to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project). Cursor opens the browser authorization the first time it connects.
1{2 "mcpServers": {3 "autonomy": {4 "url": "https://app.autonomyqa.com/api/mcp"5 }6 }7}Add Autonomy to .vscode/mcp.json in your workspace. VS Code uses the servers key and an explicit http type.
1{2 "servers": {3 "autonomy": {4 "type": "http",5 "url": "https://app.autonomyqa.com/api/mcp"6 }7 }8}Add Autonomy to ~/.codeium/windsurf/mcp_config.json. Windsurf uses the serverUrl key for remote servers.
1{2 "mcpServers": {3 "autonomy": {4 "serverUrl": "https://app.autonomyqa.com/api/mcp"5 }6 }7}Add Autonomy to ~/.codex/config.toml. Codex reaches remote MCP servers through its streamable-HTTP client.
[mcp_servers.autonomy]
url = "https://app.autonomyqa.com/api/mcp"Any client that supports remote (Streamable HTTP) MCP servers and OAuth sign-in can connect. Use this URL:
1{2 "mcpServers": {3 "autonomy": {4 "url": "https://app.autonomyqa.com/api/mcp"5 }6 }7}Authorize an organization
Autonomy MCP uses OAuth only. There is no API key to paste, and organization API keys (aut_…) don't work on MCP. On first connection, the client opens your browser:
- Sign in to Autonomy QA, if you aren't already.
- Choose the organization. Each connection reaches one organization.
- Review what the client asks to do, then click Authorize.
See Organization access for what each permission means and how to reach another organization.
Verify the connection
After authorizing, ask the client to list your projects and a few recent runs. If nothing comes back, check that you authorized the organization that owns the project and that the URL ends with /api/mcp. See Troubleshooting if the connection fails.
Use Autonomy MCP to list my projects.
For the first project, list the five most recently updated test cases and the five most recent runs.
Return the test case names, their platforms, and each run's status.Once that works, follow the first MCP run with a small test case before asking the assistant to diagnose or fix product code.
Didn’t find it?