AI tools

Your own LLM, through MCP.

RAAD has no built-in assistant. It runs an MCP server on your Mac, and the AI you already use, Claude, Cursor, or another client, asks it for the clips it needs.

Setup

Connect it in three steps.

Turn it on.
In RAAD, open Settings, then Platform Surfaces, and switch on “Allow MCP clients”. It is off until you do, and read-only when you do.
Connect your client.
Click Configure next to Claude Desktop, Claude Code, Cursor, or VS Code. RAAD adds only its own entry and leaves your other MCP servers untouched.
Ask your LLM.
Your client calls RAAD’s tools when it needs something you copied, and RAAD answers from your history on your Mac.

What it can do

Read by default. Write only if you say so.

Each group of tools sits behind its own switch in Settings, and the two that change things are off until you turn them on.

Read

Switch: “Allow MCP clients”

Search, browse, and recall your history.

search_clips
Find clips by exact words: an error string, a URL, an identifier.
semantic_search
Find clips by meaning when you do not remember the wording.
recent_clips
Your latest clips, newest first.
get_clip
Fetch one clip by its id.
list_pinboards
List your pinboards. Sealed ones never appear, not even by name.
get_pinboard
The clips filed in one pinboard.
get_session_context
What you were working on recently, grouped by app or site and by time.

Write

Switch: “Allow saving and organizing clips”

Off by default. Lets a client add to your history and organize it.

save_clip
Save text as a new clip, optionally into a pinboard.
create_pinboard
Create a pinboard.
add_to_pinboard
File an existing clip into a pinboard.

Clipboard

Switch: “Allow changing what ⌘V pastes”

Off by default, and separate from write because it changes what you paste next.

set_clipboard
Put a clip on the clipboard so your next ⌘V pastes it. RAAD shows you a notification every time.

A few tools need RAAD to be running; the rest read your history file directly. The full list, with every argument, is in the tool reference. Tool reference

What it can see

Some clips are invisible to it.

These limits are enforced by RAAD, not requested of the client, so they hold whatever the client asks for.

Sensitive clips: A clip marked concealed, or copied from an excluded app, is never returned by any tool.
Deleted clips: Never returned.
Sealed pinboards: Invisible entirely. They are not shown with a hidden name, and asking for one by id fails exactly like asking for one that does not exist.
Every write is logged: To a local audit table you can read in Settings, under Recent MCP Activity. No MCP tool can read that table, so an agent cannot see its own trail.

Where your clips go

RAAD sends nothing. Your LLM decides the rest.

RAAD itself never sends a clip anywhere. But an MCP client hands what it reads to its model. If that model runs in the cloud, the clips it reads go there, the same as anything else you paste into that chat.

If that matters for what you copy, use a client that runs its model on your Mac. Either way, sensitive, deleted, and sealed clips are never returned, so they cannot reach any model through RAAD.

By hand

Or configure it yourself.

If your client is not listed, or one-click setup cannot read its config file, add RAAD to the client’s MCP config. Your client starts the helper over stdio when it needs it.

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

Add this to the client’s MCP config.

The MCP server is included in the 14-day free trial and in every plan. Without either, it stops. See pricing

Download for Mac Read the MCP docs

Security policy