Log inSubmit server
Clipy MCP logo

Clipy MCP

by manovagyanik1

Searches, reads, records, and annotates Clipy videos through MCP tools for AI agents.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Clipy MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "manovagyanik1-clipy-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@clipy/cli@latest"
      ],
      "env": {
        "CLIPY_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @clipy/cli@latest

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

The manovagyanik1/clipy-mcp MCP server connects MCP-capable agents to Clipy recordings, imported videos, transcripts, summaries, browser diagnostics, and timestamped visual evidence. Agents can search recordings and context documents, inspect metadata, read compiled transcripts, download MP4 files, and retrieve key moments or agent-context bundles. With an ingest-scoped key, it can also record headless web applications, manage live recording sessions, add markers and chapters, and replace transcripts. Use it when an agent needs to investigate recorded browser activity, extract evidence from videos, or capture a web workflow for later analysis.

Use cases

  • Search recordings for a demonstrated bug or workflow
  • Read timestamped transcripts and summaries into an agent task
  • Capture a headless web app flow and upload it to Clipy
  • Inspect browser errors associated with a recorded page
  • Extract selected sections from imported videos

Key features

  • Semantic and literal video-memory search
  • Timestamped transcripts, summaries, and key moments
  • Privacy-redacted browser diagnostics
  • Headless browser recording and session controls
  • Context-document reading with time ranges
  • Revision-safe transcript replacement

Tools33

What Clipy MCP lets your agent do. Expand a tool for its parameters.

Self-reported~1.4k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

18/18 checks healthy over the last 76d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · @clipy/cli@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars5Stargazers on the source repository.
npm downloads1.1kPackage downloads in the last 30 days.
Last commit15d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed33Callable tools this server registers over MCP.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Clipy MCP works

What manovagyanik1/clipy-mcp MCP server does

The manovagyanik1/clipy-mcp MCP server exposes Clipy’s video library to MCP-compatible clients. It supports two main collections: the user’s own screen recordings and imported context videos, such as YouTube videos or local files imported through Clipy. Agents can search across both collections, locate timestamped moments, open matching points through Clipy URLs, and read the surrounding evidence.

For recordings, the server provides metadata, full timestamped transcripts, AI-generated summaries, key moments, browser diagnostics, downloadable MP4 files, and a combined markdown context bundle. Video frames can accompany relevant moments, including click markers rendered into the evidence. Browser diagnostics are privacy-redacted and identify routes, console messages, page exceptions, and failed requests without exposing headers, bodies, cookies, tokens, typed values, or raw query values.

How it works

Read operations use a Clipy recording’s public ID or its full share URL. A broad search can return hits from either the recordings library or the imported-video library, with a result type indicating which follow-up tools to use. Context documents can be read in time ranges, allowing an agent to process a section of a long video rather than loading the entire transcript at once.

The write path has two modes. The record tool launches a headless browser, captures a web application, and uploads the result to Clipy. The session tools provide a longer-lived workflow: start a session, operate the page with other browser tools, add markers or chapters, then stop and upload it. Sessions have an automatic maximum duration, and an active session can instead be discarded with abort_recording.

Markers may include page assertions or driver-reported observations. Chapters divide a recording into named sections. Transcript replacement uses a revision value from a prior read, which prevents a stale edit from overwriting a newer change.

Setup and configuration

The package is started with npx -y @clipy/mcp and uses the MCP client’s standard stdio configuration. Before launching it, authenticate with the Clipy CLI using npx @clipy/cli@latest login. The login stores credentials in the local Clipy configuration file, which the server can read without requiring the key to be copied into an MCP configuration.

For CI, containers, or a deliberately different credential, set CLIPY_API_KEY in the server process environment. The environment variable takes precedence over the local configuration file. Do not place the key in command-line arguments, where local processes may be able to inspect it.

Read tools require the recordings:read scope, which is included by default. Recording, session management, and transcript replacement additionally require the ingest scope. Headless recording also requires Playwright to be available in the server environment. Capturing the actual Mac screen is outside this MCP server’s scope and is handled by the Clipy CLI instead.

Tools and capabilities

The manovagyanik1/clipy-mcp MCP server includes tools for:

  • Searching all Clipy memory or only recording titles and descriptions.
  • Listing recordings and imported context documents.
  • Reading recording metadata, transcripts, summaries, key moments, and compiled agent context.
  • Inspecting privacy-redacted browser diagnostics.
  • Waiting for transcript and summary processing to finish.
  • Downloading recordings as MP4 files for local clipping or frame extraction.
  • Recording headless browser sessions with viewport sweeps and login-related browser state options.
  • Adding timestamped markers, named chapters, and verification evidence.
  • Stopping or discarding active recording sessions.
  • Reading imported videos in bounded time ranges.
  • Replacing a transcript while preserving revision safety and marking the result as agent-edited.

Limitations and notes

The server does not capture the physical Mac display or a native window; its recording tools use a headless Chromium page. Write operations are unavailable to keys limited to recordings:read. Transcript and summary data may require polling before it is ready. Browser diagnostics describe page-reported evidence and intentionally omit sensitive request and input contents. Imported context videos are maintained separately from the user’s screen recordings, although the broad memory search can search both.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Clipy MCP

Run it through the MCP client with `npx -y @clipy/mcp`. Authenticate first with `npx @clipy/cli@latest login`.

Yes. The provided setup includes a Claude Desktop stdio configuration using `npx` and `@clipy/mcp`.

It can read the key saved by `clipy login`, or use the `CLIPY_API_KEY` environment variable. Read access uses `recordings:read`; write operations also require `ingest`.

No. Its recording tools capture headless Chromium pages. Actual Mac screen capture is handled by the Clipy CLI.

Related MCP servers

All in Multimedia Process All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewClipy MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/manovagyanik1-clipy-mcp?style=directory)](https://allmcps.com/mcp/manovagyanik1-clipy-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/manovagyanik1-clipy-mcp"><img src="https://allmcps.com/api/badge/manovagyanik1-clipy-mcp?style=directory" alt="Clipy MCP on AllMCPs" /></a>