Docs

RAAD exposes your clipboard history two ways outside the app itself: an MCP server for AI clients, and a raad CLI for the terminal. Both are read-only, off by default, and never return a sensitive or deleted clip no matter what they’re asked — see the security policy for the full boundary.

MCP server

Turn it on in RAAD → Settings → Platform Surfaces → “Allow MCP clients”. Then point your MCP client at the helper binary inside the installed app — it’s launched by the client over stdio, never by RAAD itself:

{
  "mcpServers": {
    "raad": {
      "command": "/Applications/RAAD.app/Contents/Helpers/raad-mcp"
    }
  }
}

For Claude Desktop, this goes in claude_desktop_config.json. Cursor and other MCP clients use the same shape under their own config file. The server exposes search and recent-clips tools only — nothing that writes to your clipboard history.

CLI

Install from RAAD → Settings → Platform Surfaces → “Install ‘raad’ to /usr/local/bin”. It’s the same binary as the app, reached through a symlink — nothing separate to update.

$ raad search "api key rotation" --json
[{ "id": "3fa2…", "text": "…" }]

$ raad recent 10
3fa2…	2026-07-30T21:03:00Z	npm install @vercel/analytics

$ raad copy 3fa2
copied to clipboard

search and recent take an optional --json flag for scripting; without it, output is tab-separated and readable in a terminal.

Local backup

Independent of cloud sync — a password-protected snapshot of your clip history and media, for moving between Macs or keeping an offline copy.

$ raad export --out history.raadbackup
Exported 56 clips to history.raadbackup

$ raad import history.raadbackup
Restored 56 clips.

Both prompt for a password at the terminal (input is hidden). Pinboards don’t travel with a backup yet — clips and media only.

Questions or something not working as documented here? hello@raad.app