Integration

Clipper + OpenClaw

Let your OpenClaw agent search your Clipper notes, recap live meetings, and suggest follow-up actions — all locally on your Mac via MCP. No data leaves your machine.

Overview

Clipper exposes a local MCP server (Model Context Protocol) over a Unix socket on your Mac. OpenClaw connects to it through the offlyn-clipper skill — no internet required.

The integration gives your OpenClaw agent direct access to your Clipper notes and live meeting context, with granular permission controls you manage in Clipper → Settings → Integrations.

Local only

All communication happens over a Unix domain socket on your Mac. No API keys, no cloud relay, no data leaves your machine.

What you get

  • Search your notes — ask OpenClaw about past meetings, voice notes, prior thinking, or project context.
  • Live meeting catch-up — while Clipper is recording, ask "catch me up" and get a recap of the current call.
  • Chat suggestion presets — OpenClaw offers quick action chips (action items, follow-up emails, key decisions) matching your in-app experience.
  • Full note context — drill into a specific note by ID for summary or full body.
  • Health check — a ping tool confirms connectivity and live meeting status.

Requirements

You need

  • macOS 14 (Sonoma) or later
  • Clipper installed and running
  • OpenClaw CLI installed (openclaw on PATH)
  • Node.js 18+ (for the MCP bridge)

Setup

Setup runs entirely from OpenClaw. The offlyn-clipper skill handles MCP registration, pairing, and verification.

  1. Launch Clipper and leave it running.

  2. Install the skill (one time) — view on ClawHub:

    openclaw skills install offlyn-clipper
  3. Run setup:

    bash ~/.openclaw/skills/offlyn-clipper/scripts/setup.sh
  4. Approve pairing — when Clipper shows the "OpenClaw wants to connect" dialog, click Allow.

  5. Start a new OpenClaw chat (/new) so the skill loads.

  6. Test it:

    openclaw agent --message "Search my Clipper notes for pricing"

Important: /new after setup

OpenClaw snapshots MCP tools at session start. If you set up the skill in an existing chat, tools won't appear. Always start a new chat after setup or after running openclaw gateway restart.

Available tools

Once connected, OpenClaw can call these MCP tools. You control which ones are enabled in Clipper → Settings → Integrations → Shared with OpenClaw.

Tool What it does
clipper_search_notes Search saved meetings, voice notes, and text notes. Returns summaries with citations.
clipper_get_note_context Get details for one note by UUID — summary or full body (if permitted).
clipper_catch_me_up Recap the live meeting Clipper is recording right now.
clipper_list_chat_presets List quick-action presets (same chips as Clipper's in-app chat).
clipper_ping Health check — confirms socket is reachable and reports live meeting status.

Live meeting catch-up

While Clipper is recording, you can ask OpenClaw to catch you up. The agent calls clipper_catch_me_up and summarizes the transcript so far — decisions, topics, action items, open questions.

Example prompts:

  • "Catch me up on my live meeting"
  • "What did I miss in the last 10 minutes?"
  • "Recap the current call"

Not recording?

If Clipper isn't actively recording, the tool returns no_active_meeting. Start or resume a recording in Clipper, then ask again.

Permissions & privacy

Clipper uses a layered permission model. OpenClaw never gets more access than you explicitly grant.

Scopes

Scope Grants access to Default
notes:search:limited Search summaries and snippets On
notes:read:summary Per-note summary / snippet On
notes:read:raw Full note body text Off (opt-in)

Per-tool toggles

Each MCP tool can be individually disabled in Settings → Integrations → Shared with OpenClaw. Disabled tools return a tool_disabled error to the agent.

Security model

  • Unix socket with 0600 permissions — only your user can connect.
  • Ed25519 challenge-response pairing with cryptographic verification.
  • Session tokens expire after 15 minutes (auto-renewed).
  • Every request is logged in Clipper's audit trail (visible in Settings).
  • Revoke access instantly by toggling OpenClaw off in Integrations.

Troubleshooting

"bundle-mcp runtime disposed"

This means your current OpenClaw chat session started before the Clipper MCP bridge was ready. Tools are frozen per-session.

Fix:

  1. Run openclaw gateway restart in Terminal.
  2. Start a new OpenClaw chat (/new).

There is no mcp reload command — you must start a fresh session.

Tools missing after setup

The skill wasn't loaded when the session started. Run openclaw gateway restart and open a /new chat.

connect ECONNREFUSED

Clipper isn't running or the socket doesn't exist yet. Launch Clipper, wait a few seconds, then retry. If the issue persists, re-run:

bash ~/.openclaw/skills/offlyn-clipper/scripts/setup.sh
Pairing denied

You clicked Deny on Clipper's pairing dialog. Re-run:

node ~/.openclaw/skills/offlyn-clipper/mcp-bridge/pair.mjs

Switch to Clipper and click Allow when the dialog appears.

permission_blocked

The requested scope isn't granted. Open Clipper → Settings → Integrations and enable the relevant toggle (e.g. "Share full note bodies" for raw access).

no_active_meeting

clipper_catch_me_up requires an active recording. Start recording in Clipper (Quick Note or the meeting banner), then ask again.

Updating the skill after an upgrade

After pulling a new Clipper version:

openclaw skills update offlyn-clipper
openclaw gateway restart

Then start a /new chat.

Ready to connect

Install the skill, approve pairing, and start asking OpenClaw about your notes and live meetings — all without leaving your terminal.

Download Clipper