Docs
RAAD exposes your clipboard history two ways outside the app itself: an MCP server
for AI clients like Claude, and a raad CLI for the terminal. Both are read-only by
default, off until you turn them on, and never return a sensitive or deleted clip no matter what
they're asked — see the security policy for the full boundary.
Where to start
- MCP server — point Claude Desktop, Claude Code, Cursor, or VS Code at RAAD's clipboard history. Setup, consent scopes, and the full tool reference.
- CLI —
raad search,raad recent,raad copy, and local encrypted backup (raad export/raad import). - Troubleshooting — MCP client not connecting, CLI not found, search not finding something you know you copied.
- Support — how to reach a human, and what to include so it's fast.
The privacy boundary, in one place
Everything RAAD exposes outside the app goes through the same two gates:
- Off by default. MCP access, MCP writes, and clipboard-set access are three independent toggles in Settings → Platform Surfaces, none on until you turn them on.
- Sensitive, deleted, and sealed-pinboard clips are never returned, no matter what a client
asks for or how it asks. This is enforced in one place in the code
(
RAADMCPCore.ClipQueryBuilder), not per-tool, so there's no path that can forget it.
Read the security policy for the complete threat model, including what a compromised machine can and can't see regardless of any of these toggles.