Pickclip can hand your AI assistant a private window into your clipboard — and hands to work with it. Ask Claude "pull that URL I copied yesterday, clean it, and put the result on my clipboard" — and it finds the clip, runs Pickclip's Clean Link on it, and hands the result back to your pastebuffer, over a local server that never leaves your Mac unless you point it at a cloud model.

The short version

Pickclip runs a local MCP server — off until you switch it on in Settings → AI Tools.
Your assistant can read your clipboard history, run your Pickclip actions on clips, put results on your clipboard, and create, edit, and delete custom actions.
It's localhost-only and token-protected. Password-manager and concealed clips are never shared.
One-click install as a Claude Desktop extension — no Node, no config files. Also works with Claude Code, Cursor, and Redeep. Free during your trial; needs a license afterward.

What your assistant can do

See and search your clipboard history — recent copies with previews, source app, and timestamps.
Read full clip contents — the complete text of any clip, or the image itself, plus whatever is on the clipboard right now.
Run your actions on clips — invoke any built-in action (Fix, Organize, Translate, Clean Link, Plain Text) or one of your custom actions on a history clip or the current copy, and get the result back — optionally straight onto your clipboard.
Put text on your clipboard — hand a finished result back to your pastebuffer, ready to paste wherever you're working. The previous copy stays in history.
Manage your custom actions — list them, and create, update, or delete them from plain-language instructions (Pickclip decides whether each becomes an AI prompt or a small script, exactly like building one by hand). And now the assistant can verify one by running it on a real clip.

Connect Claude Desktop — one click

Claude Desktop installs local MCP servers as extensions, and Pickclip builds one for you. No config files, no Node, nothing to copy.

Turn it on. In Pickclip, open Settings → AI Tools and switch on "Let AI tools use your clipboard and actions."
Install the extension. Click Install Extension. Pickclip builds a Pickclip.mcpb and hands it to Claude Desktop, which shows its one-click install dialog. Confirm, and you're connected.
Ask away. Try "Using Pickclip, what are the last few things I copied?", "Run Fix on my last copy and put it on my clipboard," or "Make me a Pickclip action that formats JSON."

There's no token or port to manage — the extension carries a tiny helper that reads those from Pickclip each time it connects, so it never goes stale and holds no secrets. If Pickclip isn't running when Claude connects, the helper launches it for you.

Connect Redeep — one click

Redeep is our own agent harness, and it installs MCP servers from the same .mcpb bundle format. In Pickclip, open Settings → AI Tools and click Install in Redeep. Pickclip builds the bundle and hands it to Redeep, which shows its native install sheet — review, confirm, and your Redeep agents can read your clipboard and manage your Pickclip actions. The same zero-secret, version-independent helper does the work.

Other clients (manual setup)

For Claude Code, one command connects it:

claude mcp add Pickclip -- /Applications/Pickclip.app/Contents/Helpers/pickclip-mcp-bridge

For Cursor, any other MCP client that launches a command, or to edit Claude Desktop's config by hand — use the Copy config button under Manual setup in Settings → AI Tools. It puts this on your clipboard, with the command path matching wherever Pickclip is installed:

{
  "mcpServers": {
    "Pickclip": {
      "command": "/Applications/Pickclip.app/Contents/Helpers/pickclip-mcp-bridge"
    }
  }
}

For Cursor, merge it into ~/.cursor/mcp.json (or a project's .cursor/mcp.json). For Claude Desktop, merge it into ~/Library/Application Support/Claude/claude_desktop_config.json (create it if needed; add "Pickclip" alongside any servers already there) and restart the app. Other clients: point their MCP configuration at the same command. There's nothing else to configure — no port, no token, no Node.

For AI agents

If you're an AI agent (or building one) and need the full picture — the security model, the discovery file, direct HTTP access, and all ten tools with exact argument and result shapes — read the machine-friendly reference: pickclip.pro/mcp/docs.md. It's plain Markdown, written to be fetched and read by agents evaluating Pickclip or setting up a connection. A site-wide index also lives at /llms.txt.

Privacy & security

Off by default. Nothing is exposed until you turn on AI Tools.
It can write, and says so. With AI Tools on, the assistant can put text on your clipboard and run your actions — not just read. A push replaces your current copy, but the previous copy stays in your Pickclip history.
Local and authenticated. The server binds to 127.0.0.1 only and requires a per-install access token, so other apps and websites can't reach it. You can regenerate the token anytime to disconnect existing clients.
Secrets stay secret. Clips from password managers and other concealed or transient copies never enter Pickclip's history, so they're never shared.
Your data, your choice of model. When your assistant runs in the cloud, the clipboard text it reads is sent to that service like any other prompt. If that matters to you, connect a local model.
Licensing. AI Tools is free to try during your Pickclip trial; once the trial ends it needs a license, like the rest of Pickclip.

↓ Download Pickclip · Read the blog