Advanced agent access

Use MCP when your agent needs private recording access

For a public Clipy video, install the skill and paste the normal link. Add MCP when Claude, Cursor, Codex, or another agent needs to search your library, read private recordings, and pull transcripts, summaries, and key moments through authenticated tools.

Install the Clipy skill first Set up MCP for private access

Connect in one line

claude mcp add --scope user clipy --env CLIPY_API_KEY=clipy_sk_live_xxx -- npx -y @clipy/mcp

The hero workflow

The normal flow is skill-first; MCP is for the private library

Record the bug with Clipy. Paste the public video link to an agent that has the Clipy skill installed. The skill knows to read the recording document automatically. If the agent needs private recordings, recent library search, or inline frame tool results, connect MCP with your API key.

1Install the Clipy skill for public link handoff.
2Paste a normal Clipy video link into the agent.
3Add MCP only when the agent needs authenticated library access.
4The agent drafts the issue, spec, or fix from grounded recording context.

MCP tools for authenticated recordings

By default the server only reads — it searches and reads your recordings, never changing or deleting them. Recording tools that capture a web app or run a live session require a key you explicitly grant the ingest scope.

search_recordings

Find a recording by keyword across titles and descriptions.

get_transcript

Read the full timestamped transcript and plaintext of any recording.

get_summary

Pull the AI summary — TL;DR, key points, and action items.

list_recordings

Browse the user's most recent recordings, newest first.

wait_for_artifacts

Poll until a fresh recording's transcript and summary finish processing.

get_recording

Get one recording's metadata and processing status.

download_recording

Download the MP4 locally so your agent can clip it or extract frames itself.

Connect MCP in under 3 minutes

1. Get your key with the browser login
If the skill is enough for public links, you can stop there. For private/library access, run npx @clipy/cli@latest login, click Approve once in the browser, and copy the stored apiKey from ~/.config/clipy/config.json into CLIPY_API_KEY below. Login keys can read your recordings and record new ones. Prefer minting by hand? Create one at clipy.online/settings/api-keys — it looks like clipy_sk_live_…, is shown once, and defaults to read-only: tick Record & upload if the agent should record.

2. Add the server to your agent

Claude Code — the --scope user flag installs Clipy globally for every project (the default scope is local, i.e. the current folder only):

claude mcp add --scope user clipy --env CLIPY_API_KEY=clipy_sk_live_xxx -- npx -y @clipy/mcp

Codex — this writes to your global ~/.codex/config.toml, so Clipy is available in every Codex session:

codex mcp add clipy --env CLIPY_API_KEY=clipy_sk_live_xxx -- npx -y @clipy/mcp

Or paste the block into the matching user-level config — claude_desktop_config.json, ~/.cursor/mcp.json, or your Windsurf config:

{
  "mcpServers": {
    "clipy": {
      "command": "npx",
      "args": ["-y", "@clipy/mcp"],
      "env": { "CLIPY_API_KEY": "clipy_sk_live_xxx" }
    }
  }
}

…or for Codex, into ~/.codex/config.toml:

[mcp_servers.clipy]
command = "npx"
args = ["-y", "@clipy/mcp"]
env = { CLIPY_API_KEY = "clipy_sk_live_xxx" }

3. Ask your agent about a recording
"Summarize my latest Clipy recording" or "read this Clipy link and draft a bug report." Full reference in the MCP docs.

Already left Loom? Your recordings should work for your agent too

Loom keeps your videos in a closed product. Clipy gives you the same record-and-share flow, free and with no signup wall — plus a skill so your AI tools can read what you recorded from the normal link. MCP is there when private library access is needed. Switching is easy: the free Loom downloader exports your library, and the Loom alternative page covers the rest. Built for engineers — see Clipy for developers.

How Clipy's agent handoff is different

vs. always-on screen capture

Tools that stream your whole screen to an agent 24/7 are powerful but invasive. Clipy is for the recordings you deliberately make and already share — intentional, scoped, and free.

vs. closed video-to-ticket integrations

Loom's AI can make a Jira ticket, but only through Loom's own closed integration. Clipy gives the recording context to your agent through a skill-first link handoff, then MCP when authenticated tools are needed.

FAQ

How do I give Claude a screen recording?: Install the Clipy skill first, then paste a normal public Clipy video link. Claude will fetch the recording document automatically. Add MCP only when Claude needs private recordings, library search, or authenticated tool calls.
Is it safe? What can the agent see?: Public links work through the skill without an API key. Your key only ever touches your own recordings, and a standard read key can't create, edit, or delete anything — the recording tools work only if you deliberately give a key the ingest scope. Revoke a key any time at /settings/api-keys.
Which agents work?: The skill path works with Claude and Codex-style skill folders. MCP works with Claude Desktop, Claude Code, Codex, Cursor, Windsurf, and other MCP clients.
Does it cost anything?: No. Clipy is free, and so is the MCP server and API key.

Ready? Install the skill for public links, or follow the MCP setup guide when your agent needs private library access.