Connect a Client
Configure Claude Code, Cursor, VS Code, Windsurf, Codex, and other MCP clients to use the Autonomy MCP server.
Autonomy exposes one remote MCP server over Streamable HTTP. Every client uses the same server URL and the same browser-based authorization — the first time a client connects, Autonomy opens a browser window to sign in and pick the organization that owns your plans and runs.
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 can connect. Use the production URL below, or replace the host if your organization is on a staging or dedicated deployment.
1{2 "mcpServers": {3 "autonomy": {4 "url": "https://app.autonomyqa.com/api/mcp"5 }6 }7}Authorize an organization
Autonomy MCP uses OAuth — there is no static API key to paste. On first connection the client opens a browser to sign in and authorize access. Choose the organization that owns the plans and runs you want to work with. See Organization Access for switching organizations and revoking access.
Verify the connection
After authorization, ask the client to list plans or recent runs. If nothing comes back, confirm 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 the test plans and the five most recent runs for this organization.
Return the plan names, platforms, run statuses, and any evidence links.Once that works, run the First MCP Run workflow against a small smoke plan before asking the agent to diagnose or fix product code.