Yutori MCP

MCP tools and workflow skills for building agents that operate computers as well as browse, research, and monitor the web with Yutori.

You can use it with Claude Code, Codex, Cursor, VS Code, ChatGPT, OpenClaw, and other MCP hosts.

Features

Capabilities:

• Computer use — Operate apps on your Mac (macOS 15+)
• Browsing — Automate websites with an AI navigator
• Research — Run one-time deep web research tasks
• Scouting — Monitor the web continuously for anything you care about at a desired frequency

Workflow skills (for clients that support slash commands):

• /yutori-computer-use — Local Mac desktop automation
• /yutori-browse — Browser automation
• /yutori-research — Deep web research (async, 5–10 min)
• /yutori-scout — Set up continuous web monitoring
• /yutori-competitor-watch — Competitor monitoring template
• /yutori-api-monitor — API/changelog monitoring template

Installation

curl -LsSf https://astral.sh/uv/install.sh | sh

brew install uv

AI agent install (recommended)

Paste this into Claude Code, Codex, Cursor, Windsurf, or another coding agent:

Use https://yutori.com/api/llms.txt and set up Yutori for me.

Manual quick install

1. Run in terminal:

   uvx yutori-mcp login
   

   This will open Yutori Platform in your browser and save your API key locally.

   Or, manually add your API key

   Go to (https://platform.yutori.com) and add your key to the config file:

   mkdir -p ~/.yutori
   cat > ~/.yutori/config.json << 'EOF'
   {"api_key": "yt-your-api-key"}
   EOF
   

2. Install MCP using add-mcp (requires Node.js):

   npx add-mcp "uvx yutori-mcp"
   

   Pick the clients you want to configure.

3. Install workflow skills using skills.sh (requires Node.js):

   npx skills add yutori-ai/yutori-mcp -g
   

   Adds slash-command shortcuts like /yutori-scout, /yutori-research, and more.

   -g installs them at user scope. Omit -g if you want a project-local install instead.

   To list or remove skills later:

   npx skills ls -g
   npx skills remove -g yutori-login
   

4. Restart the tool you are using.

Manual per-client install

{
  "mcpServers": {
    "yutori": {
      "command": "uvx",
      "args": ["yutori-mcp"]
    }
  }
}

{
  "mcpServers": {
    "yutori": {
      "command": "uvx",
      "args": ["yutori-mcp"]
    }
  }
}

code --add-mcp '{"name":"yutori","command":"uvx","args":["yutori-mcp"]}'

{
  "mcpServers": {
    "yutori": {
      "command": "uvx",
      "args": ["yutori-mcp"]
    }
  }
}

{
  "mcp": {
    "allowed": ["yutori"]
  },
  "mcpServers": {
    "yutori": {
      "command": "uvx",
      "args": ["yutori-mcp"]
    }
  }
}

pip install yutori-mcp

macOS computer use

Optional, macOS 15+ only. Computer use operates the visible desktop, or a single app window in the background while you keep working, so it needs a local driver and system permissions on top of the install above:

uvx yutori-mcp computer-use setup    # installs CuaDriver.app, requests Screen Recording + Accessibility

setup finishes by running the readiness checks and reports anything still missing. Re-run those checks any time with uvx yutori-mcp computer-use doctor.

Prompting a task from the terminal

The task is one quoted positional argument — plain English, in the imperative, as if you were handing the Mac to someone else:

uvx yutori-mcp computer-use run "<what to do, and what to report back>"

Everything else is optional. The three that matter most:

# Name the app you want driven, so the run starts in the right place
uvx yutori-mcp computer-use run "Compute 17 * 23 and report the result." --app Calculator

# Start a browser task on a specific page (--start-url requires --app)
uvx yutori-mcp computer-use run "List every person on the team page and save them to ~/Desktop/team.txt." \
  --app Safari --start-url https://yutori.com/company

# Drive one window in the background and keep working (--mode background requires --app)
uvx yutori-mcp computer-use run "Add a note titled Standup with today's three agenda items." \
  --app Notes --mode background

Write the prompt so the run has a finish line:

• Say what "done" looks like. "…and report the list" or "…and save it to ~/Desktop/team.txt" gives the model something to stop at; "look at the team page" does not.
• Name the app and the starting page with --app / --start-url instead of describing them in the prompt. The runner opens them before the model's first screenshot, which saves turns and avoids the model guessing at which window to use.
• Spell out the constraints you care about — which account to use, which folder to write to, what to do when something is ambiguous ("if the page asks to log in, stop and say so").
• Keep it one task. One run holds a machine-wide lock; chain separate runs rather than packing five errands into one prompt.
• Don't put secrets in the prompt. Have the model use an already-signed-in app or an entry in Keychain; typed text shows up (scrubbed and truncated) in the action log.

Foreground (the default) drives the whole visible desktop — don't touch the Mac while it runs. Background drives one app's window and captures only that window, so you can keep working; leave that window alone. Some apps accept background clicks but not typed keys (Calculator, for one), and the run reports the refusal rather than typing blind — add --allow-foreground-fallback for typing-heavy background tasks.

uvx yutori-mcp computer-use stop ends the active run from another terminal (background runs have no on-screen Stop button). uvx yutori-mcp computer-use smoke is an end-to-end check: it types into Calculator to confirm the permissions took effect, then has the agent compute 9 * 9.

While a task runs, run prints each action as the agent takes it — including the individual clicks, keystrokes, and scrolls inside each computer_batch — and closes with the model's answer in a labeled FINAL OUTPUT block. Output is colorized when stdout is a terminal; set NO_COLOR=1 to turn that off, or FORCE_COLOR=1 to keep it through a pipe.

The harness in this repository is minimal: one task at a time (a machine-wide lock), either on the visible desktop or targeting one app window in the background, with no multiplexing. For scalable sandbox runs, see n2 on Daytona.

Tools

See TOOLS.md for the full tool reference — computer use, Browsing, Research, and Scout tools with parameters, examples, and response formats.

Development

Setup

git clone https://github.com/yutori-ai/yutori-mcp
cd yutori-mcp
pip install -e ".[dev]"

Testing

pytest

Running locally

yutori-mcp login    # authenticate (one-time)
yutori-mcp          # run the server (or: python -m yutori_mcp.server)

Computer-use runtime

computer-use doctor verifies the pinned yutori SDK install against the published wheel. SDK contributors testing an editable checkout can override that with YUTORI_MCP_ALLOW_EDITABLE_SDK=1.

Debugging with MCP Inspector

npx @modelcontextprotocol/inspector yutori-mcp

API Documentation

For full API documentation, visit docs.yutori.com.

License

Apache 2.0