Developers

How the integration works

The desktop app exposes its engine over MCP on standard input and output. Your assistant talks to that process; the process talks to the app that is already running. The app is where the browser, the credential vault and your files live, so that is where Recipes run.

Your assistant writes Recipe source: a recipe.yaml plus an orchestration.js or work.js script. You review that source like any other code. Before it can run, it goes through the same validation as a hand-written Recipe, including the requirement to have acceptance checks.

Setup

• Install and open the desktop app.
• Go to Integrations. The page shows a ready-to-paste stdio configuration for your machine and a Ready badge that reflects whether the MCP server is actually up.
• Copy the configuration into your assistant using the steps below.
• Restart the assistant. Ask it to list Recipes; if it can, you are connected.

Claude Code

Add the server to the project’s MCP file, or register it once with the CLI. The command and arguments come from the Integrations page.

// .mcp.json
{
  "mcpServers": {
    "anyrepeat": {
      "command": "<command from the Integrations page>",
      "args": ["<args from the Integrations page>"]
    }
  }
}

Codex

Register the stdio server with the Codex CLI, then restart Codex.

codex mcp add anyrepeat -- <command from the Integrations page>

Cursor

Add the server under mcpServers in the project’s Cursor MCP file.

// .cursor/mcp.json
{
  "mcpServers": {
    "anyrepeat": {
      "command": "<command from the Integrations page>",
      "args": ["<args from the Integrations page>"]
    }
  }
}

OpenCode

Add a local MCP entry to the OpenCode config.

// opencode.jsonc
{
  "mcp": {
    "anyrepeat": {
      "type": "local",
      "command": ["<command from the Integrations page>"],
      "enabled": true
    }
  }
}

What the tools do

The server describes itself. Ask for the authoring contract first; it returns the script API, the recipe.yaml schema and the validation rules, generated from the SDK, so nothing has to be guessed.

• workflow_contract: the authoring contract. Call it before writing any yaml or script.
• workflow_validate, workflow_save: check and store Recipe source.
• workflow_list, workflow_run, workflow_cancel: find and run Recipes.
• browser_navigate, page_elements: look at a site inside the desktop session, with the user’s logins, before writing against it.
• run_list, run_artifacts, run_stats: results, outputs and pass rates of past runs.

Where runs happen

A run started from an assistant happens in the desktop app’s visible browser window, using the person’s own logged-in session. It is never headless and never in the background, and it takes over the window while it runs.