Connect Cursor to AdaptOrch in mcp.json.

Create an account at /app/signup and an API key at /app/api-keys. Model execution also needs your provider, model and provider key; provider usage is billed by the provider separately from the AdaptOrch plan. Set these only in your local environment, never in a shared transcript or committed file.

export ADAPTORCH_API_KEY="ado_..."
export ADAPTORCH_PROVIDER="openai"
export ADAPTORCH_PROVIDER_MODEL="YOUR_SUPPORTED_MODEL"
export ADAPTORCH_PROVIDER_KEY="YOUR_PROVIDER_KEY"

Add the adaptorch entry inside the existing mcpServers object, then review it in Cursor's MCP settings.

{
  "mcpServers": {
    "adaptorch": {
      "url": "https://adaptorch.com/mcp",
      "headers": { "Authorization": "Bearer ${env:ADAPTORCH_API_KEY}" }
    }
  }
}

This block shows the authentication syntax only. Before model execution, add your X-Provider, X-Provider-Model and X-Provider-Key headers using the per-client guide in the signed-in dashboard.

This read-only tools/list request checks the endpoint and your AdaptOrch key. It does not submit a run or spend provider budget. A valid key returns a result.tools array that includes adaptorch_run. Without a key the endpoint answers HTTP 401 with Missing bearer token, which still proves it is reachable.

curl --fail --silent --show-error https://adaptorch.com/mcp \
  -H "Authorization: Bearer $ADAPTORCH_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Ask Cursor to call adaptorch_run once with the single-task payload below. This consumes plan allowance and provider budget, so do not resubmit it while polling.

{
  "payload": {"subtasks": [{"id": "ping", "description": "Reply exactly PONG", "estimated_tokens": 16}]},
  "synthesis_mode": "paper",
  "budget_policy": {"global_timeout_budget_seconds": 20}
}

Use the returned run_id with adaptorch_get_run and adaptorch_get_artifacts, or open /app/runs.

The run record shows the inputs, the selected model and outputs, recorded commands and check outcomes when an execution environment is configured, and open review items. A SUCCEEDED run is not a test pass: a repository code check needs a separately configured execution environment, and missing or skipped checks stay unverified.

AdaptOrch documents the Cursor configuration format above, but this connection has not been tested by AdaptOrch end to end in Cursor. Read the claim boundary before relying on run records in a review process, and see the AI PR review guide for what to inspect.

See all AdaptOrch integrations, or the full MCP documentation for Gemini CLI, VS Code and Windsurf configuration formats.