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.

Connect ChatGPT or ClaudeFull connector setup guide

Prefer public links only? Install the Clipy skill once, then paste a normal video URL. No OAuth or API key required for public recordings.

Hosted connector

Connect ChatGPT or Claude without a local server

Clipy's hosted MCP endpoint is https://clipy.online/api/mcp. Sign in with OAuth, approve access, and let the agent search your library. No API key and no npx process on your laptop. A public ChatGPT directory listing is not confirmed; use a custom app where your account allows it.

ChatGPT (custom app)

  1. 1Open ChatGPT Settings → Apps → Advanced settings and enable Developer mode when your plan or workspace allows it.
  2. 2Choose Apps → Create (workspace admins may also use Workspace settings → Apps → Create).
  3. 3Paste https://clipy.online/api/mcp as the MCP server URL and select OAuth.
  4. 4Sign in to Clipy, review the consent screen, finish the tool scan, and create the app.
  5. 5Enable the Clipy app in the conversation, then ask ChatGPT to search or summarize a recording.

If Create or Developer mode is missing, check plan and admin permissions. OpenAI documents current availability in its developer-mode help article. Revoke access anytime from Settings → Connected apps.

Claude Code (HTTP + OAuth)

Add the hosted connector at user scope, then complete browser sign-in:

claude mcp add --scope user --transport http clipy https://clipy.online/api/mcp
claude mcp login clipy

Default consent is read-only. If you also grant organize/write, the agent can rename recordings, edit descriptions, change tags or folders, and switch share modes. It cannot delete recordings, start a new capture, or invite people to a private link.

Full reference, limits, and the local API-key path: /docs/mcp. Internal checklist: docs/connectors-guide.md.

The hero workflow

Skill-first for public links; connectors for private libraries

Record the bug with Clipy. Paste the public video link to an agent that has the Clipy skill installed. The skill fetches agent context automatically. When the agent needs private recordings, library search, or authenticated edits, connect hosted MCP with OAuth (or local MCP with an API key).

  1. 1Install the Clipy skill for public link handoff.
  2. 2Paste a normal Clipy video link into the agent.
  3. 3Add the ChatGPT/Claude connector or local MCP when the agent needs authenticated library access.
  4. 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. 1. Log in once

    If the skill is enough for public links, you can stop there. For private/library access, run npx @clipy/cli@latest login and click Approve once in the browser. The key is saved to ~/.config/clipy/config.json and the MCP server reads it from there, so there is nothing to copy into the commands below. Login keys can read your recordings and record new ones. Prefer minting by hand? Create one at clipy.online/settings/api-keys and it looks like clipy_sk_live_…, is shown once, and defaults to read-only: tick Record & upload if the agent should record. Pass a hand-minted key as --env CLIPY_API_KEY=… and it overrides the logged-in one.

  2. 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 -- 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 -- 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"]
    }
  }
}

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

    [mcp_servers.clipy]
command = "npx"
args = ["-y", "@clipy/mcp"]

    Prefer a cloud connector with browser sign-in and no local API key? ChatGPT and Claude Code can use Clipy's hosted MCP endpoint. For Claude Code:

    claude mcp add --scope user --transport http clipy https://clipy.online/api/mcp
claude mcp login clipy

    In ChatGPT Developer mode, add https://clipy.online/api/mcp as a custom MCP app where your account and workspace permit it, then sign in with OAuth. A public ChatGPT directory listing is not confirmed; directory search is separate from connecting this endpoint. See the connector setup guide for the hosted-versus-local tool differences.

  3. 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 agent context 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 ChatGPT, 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.