Model Context Protocol

Give your AI agent access to your screen recordings

Clipy's MCP server lets Claude, Cursor, and ChatGPT read your recordings' transcripts and AI summaries — and turn a 2-minute bug video into a ticket.

Create your API key Read the setup docs

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

Turn a bug-report video into a ticket — without leaving your agent

Record the bug with Clipy. Paste the link to your agent. It calls get_transcript and get_summary, reads exactly what happened — steps, errors, what you narrated — and drafts the Linear, Jira, or GitHub issue for you. No re-typing, no "wall of text" bug reports.

1Record the bug in Clipy (web, Chrome extension, or Mac app).
2Tell your agent: "Read this Clipy recording and open a bug ticket."
3The agent reads the transcript + AI summary through MCP.
4It drafts the issue with real repro steps. You review and ship.

Seven tools your agent gets

The server is read-only — it can search and read your recordings, never change or delete them.

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 in under 3 minutes

1. Create an API key
Mint a free key at clipy.online/settings/api-keys. It looks like clipy_sk_live_… and is shown once.

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 an MCP server so your AI tools can actually read what you recorded. 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 MCP 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 hands the transcript + summary to your agent, which can act in any tool it's connected to.

FAQ

How do I give Claude a screen recording?: Install the Clipy MCP server (one command above), create an API key, and ask Claude to read or summarize your recording. Claude calls the Clipy tools to fetch the transcript and summary.
Is it safe? What can the agent see?: The server is read-only and your key only ever reads your own recordings. It can't create, edit, or delete anything. Revoke a key any time at /settings/api-keys.
Which agents work?: Any MCP client — Claude Desktop, Claude Code, Codex, Cursor, Windsurf, and others. The server runs locally over stdio.
Does it cost anything?: No. Clipy is free, and so is the MCP server and API key.

Ready? Create an API key and follow the setup guide.