Online MCP

Name: Online MCP
Author: manovagyanik1

by manovagyanik1version 0.17.0i★ –iRuns on your computer

Registry nameonline.clipy/mcp

Install

Overview

Description from the maker (original English)

Read your Clipy screen recordings: search, transcripts, AI summaries, and key moments with frames.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiVery new↓ 87/wk · ★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Search & AI memory
You need to fill in: CLIPY_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: CLIPY_API_KEY, CLIPY_API_URL

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

claude mcp add clipy --env CLIPY_API_KEY=your-value --env CLIPY_API_URL=your-value -- npx -y @clipy/mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "clipy": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@clipy/mcp"
      ],
      "env": {
        "CLIPY_API_KEY": "your-value",
        "CLIPY_API_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

CLIPY_API_KEY secret env
Clipy API key. Optional — the server reads the credential `clipy login` stores at ~/.config/clipy/config.json. Set this to override it, or for CI where there is no login. Create a key free at https:/…
CLIPY_API_URL env
Override the Clipy API base URL (defaults to https://clipy.online)

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain clipy.online (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

More stars than 0% of the other 5714 servers in this category
Published to the registry more recently than 59% of the other 5714 servers in this category
Basic checks equal to or better than 100% of the other 5714 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Online MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: CLIPY_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.17.0) reached the registry 27 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

by upstashWidely used↓ 972.7K/wk★ 64.2KUpdated 2 days ago

Computer or cloud

Install

Codebase Memory

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

by DeusDataWidely used↓ 18K/wk★ 48.1KUpdated 22 days ago

Runs on your computer

Install

Exa

Connect AI agents to Exa for web search, content fetching, and multi-step research.

by exa-labsWidely used★ 5.2KUpdated 2 months ago

Runs in the cloud✓ exa.ai

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@clipy/mcp

Give your AI agent access to your Clipy screen recordings.

Developed in the Clipy monorepo. A public mirror for browsing the source and filing

issues lives at [github.com/clipy-recorder/clipy-mcp](https://github.com/clipy-recorder/clipy-mcp)

(MIT), kept in sync with each npm release.

This is a Model Context Protocol (MCP) server. It lets Claude, Cursor, Windsurf, and other MCP-capable agents search your recordings and your team library, and read their transcripts and AI summaries, so you can do things like _"turn this bug-report recording into a Linear ticket"_ without leaving your agent — and, with the record tool, record a web app headlessly and get it back as a Clipy recording (_"build the feature, then record the outcome"_).

The canonical cross-surface operating contract is [clipy.online/agents.md](https://clipy.online/agents.md). For the exact connected MCP version and schemas, use the standard tools/list request.

The read tools need the recordings:read scope, which every key gets by default. The write tools — record, the session tools (start_recording, add_marker, add_chapter, stop_recording, abort_recording), and replace_transcript — additionally need the key to carry the ingest scope ("Record & upload"), which the server enforces. get_edit_transcript and edit_recording need the recordings:write scope. A recordings:read-only key can read every recording you can open but cannot create, modify, or delete anything.

Setup

npx @clipy/cli@latest login

It opens your browser; click Approve once. The key is saved to ~/.config/clipy/config.json, and this server reads that file — so there is no key to copy anywhere, and no secret ends up in your shell history or your MCP config.

Then add the server to your MCP client.

Claude Code

The --scope user flag installs Clipy globally for every project. Without it, claude mcp add defaults to local scope (the current folder only):

claude mcp add --scope user clipy -- npx -y @clipy/mcp

Codex

This writes the server to your global ~/.codex/config.toml, so it's available in every Codex session:

codex mcp add clipy -- npx -y @clipy/mcp

Or add it to ~/.codex/config.toml by hand:

[mcp_servers.clipy]

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

Claude Desktop / Cursor / Windsurf

Edit the matching user-level config (claude_desktop_config.json, ~/.cursor/mcp.json, or the Windsurf MCP config) directly:

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

Add an "env": { "CLIPY_API_KEY": "clipy_sk_live_xxx" } block only if you are not using clipy login on this machine.

Setting the key explicitly

Use CLIPY_API_KEY when there is no clipy login to read from — CI, a container — or when you deliberately want a different key than the logged-in one. An explicit env var always wins over the config file. Mint keys at https://clipy.online/settings/api-keys (shown only once).

Never inline your key into the server's launch command — e.g.

"command": "sh", "args": ["-c", "CLIPY_API_KEY=… npx -y @clipy/mcp"]. Command-line

arguments are visible to every local process via the process table (ps, /proc),

so a key placed there is effectively world-readable on the machine. Put it in the env

block instead. (claude mcp add --env … / codex mcp add --env … write that env block

for you — they expose the key only in the argv of that single setup command, never in the

long-running server's.)

Hosted connector

You can also connect without installing anything. Clipy runs this server at https://clipy.online/api/mcp (Streamable HTTP).

Connector UIs such as Claude and ChatGPT sign in with OAuth. Discovery starts at https://clipy.online/.well-known/oauth-protected-resource.
Other clients send Authorization: Bearer .
A key with only the recordings:read scope sees only the read tools.

For MCP directories and reviewers

Clipy keeps a demo account with three sample recordings: a bug walkthrough, UI feedback and a product demo. Directories can get a read-only test key by emailing support@clipy.online.

Tools

Tool	What it does
`search_memory`	Search the whole Clipy memory at once — every screen recording the user made and every video they imported — returning the matching moments with timestamps and a URL that opens at that point. Matching is semantic as well as literal, so "login flow" finds a moment where someone said "the authentication screen". Reach for this first when the user refers to something they showed, recorded, or watched; the per-library tools below each see only half the picture. Each hit carries `kind` (`recording` or `context`) to tell you which tool to read next, a `resolution` saying whether its timestamp is an exact moment or a ~50s span, and a `semantic.status` to check before treating an empty result as "nothing recorded".
`search_recordings`	Search the recordings you can open by keyword (title + description). Optional `scope` (`mine`, `team`, `shared`, `all`) and `workspace`.
`list_recordings`	List the most recent recordings you can open, with each one's maker and workspace. Optional `scope` and `workspace`.
`get_recording`	Metadata for one recording (status, duration, transcript/summary status).
`get_transcript`	The full timestamped transcript + plaintext.
`get_summary`	The AI summary: TL;DR, key points, action items.
`get_edit_transcript`	The recording as an editable transcript (needs the `recordings:write` scope, since it includes the text of cut words): every word with its index, start/end in ms on the original timeline, a `filler` flag (um, uh, er, hmm) and `removed` on words the current version already cuts, plus the `revision` to pass to `edit_recording`. Paged by `fromWord`/`limit`.
`edit_recording`	Edit the video by its transcript (needs the `recordings:write` scope): cut word ranges or ms ranges, remove every filler word, bring cuts back, or turn on click auto zoom (`autoZoom`, Mac and Windows recordings). Clipy keeps the original, so a cut can be brought back until the owner deletes the original; the share link stays the same and switches to the new version when the render finishes. Supports `dryRun` and `expectedRevision`.
`get_browser_diagnostics`	Privacy-redacted visited routes, console warnings/errors, page exceptions, and failed fetch/XHR metadata. The evidence is explicitly labelled page-reported; headers, bodies, cookies, tokens, typed values, and raw query values are never captured.
`get_interactions`	Bounded pages of prepared routes, pointer samples, semantic clicks, derived drags, scroll bursts, pointer dwells, coarse typing (never values or exact key counts), and highlights. Filter by `fromMs`/`toMs`/`types`, set `limit` (1–250, default 100), and follow `pagination.nextCursor` with unchanged filters. Reports source coverage and preparation state; dwell is not proof of attention and coordinates belong to the capture viewport, not transformed playback frames.
`wait_for_artifacts`	Poll until a recording's transcript/summary finish processing.
`download_recording`	Download the MP4 locally so you can clip it or extract frames yourself (e.g. with ffmpeg).
`get_key_moments`	Key moments: timestamps, captions, and click coordinates.
`get_agent_context`	The full agent-context bundle (summary + interaction timeline + key moments + transcript + available browser diagnostics) as markdown.
`record`	Record a web app headlessly and upload it as a Clipy recording; returns its share + agent-context URLs. Accepts a `type` (recording kind), `viewports` (sweep several screen sizes into one video), `storageState` / `userDataDir`+`profileDirectory` / `initScript` (record behind a login), and timestamped `notes` that become the (silent) recording's transcript. Needs Playwright in this server's environment and an `ingest`-scoped key (see below).
`start_recording`	Start a recording session that keeps recording while you work (drive the page with your own browser tools, run commands, …). Accepts `type`, `storageState` / `userDataDir`+`profileDirectory` / `initScript`, and `exposeCdp` (get a CDP endpoint + in-page `window.__clipyMark`/`window.__clipyChapter` bridge to drive the recorded page). Auto-stops + uploads at `maxSeconds` (default 600) so it can never run away.
`add_marker`	Drop a narration marker into the active session (live clock, or backdate with `atSeconds`) — markers become the recording's transcript chapters. Can carry evidence in one of two provenances: clipy-verified (`assertSelector` / `assertText` / `assertUrl`) where Clipy checks the page itself, or driver-attested (`observed` + `verdict`) where you report what your own tooling saw. Clipy-verified outcomes render with a verdict glyph (✓ pass, ✗ failure that can abort via `failMode`, ⚠ unverified — never a silent pass); driver-attested ones render with a weaker-looking hedge glyph (`≈`) so the two are never mistaken at a glance, and they are tallied in separate segments. Navigations + console errors are added automatically as `[auto]` marks.
`add_chapter`	Drop a `=== CHAPTER: ===` boundary into the active session — split a recording into named sections (ideal for before/after demos).
`stop_recording`	Finish the session: close the browser, upload, return the share + agent-context URLs.
`abort_recording`	Discard the active session; nothing is uploaded.
`list_context_documents`	List the user's context documents — YouTube videos and local video files they imported with `clipy context import`, so agents can read them. A separate library from their own screen recordings.
`get_context_document`	One context document's metadata: source, duration, tags, the server's classification (video type, whether visual evidence is needed, planned moments), and which transcript/frames exist. Not the transcript itself.
`read_context_document`	Read a context document as compiled markdown — header, metadata, then the timestamped transcript with frame captions interleaved. Takes `startMs`/`endMs` so you can walk a two-hour video section by section instead of flooding your context.
`update_recording`	Rename a recording or edit its description (needs `recordings:write`).
`organize_recording`	File into a folder and add or remove tags (needs `recordings:write`).
`set_recording_privacy`	Switch the share link between public, restricted and private. Never invites or emails anyone (needs `recordings:write`).
`list_folders` / `create_folder`	Folders with ids; create is idempotent by name.
`list_comments`	The comment thread: timestamped comments, replies, resolved state. Author names only (needs `comments:read`).
`add_comment`	Comment at a moment or reply, as the key's owner. Everyone in the thread is notified (needs `comments:write`).
`get_analytics`	Views, unique viewers, completion and who watched (needs `analytics:read`). Free accounts get the totals only.
`upload_video`	Upload a WebM, MP4 or QuickTime `.mov` from this machine and get its share and agent-context links (needs `ingest`).
`delete_recording`	Permanently delete a recording. `confirm` must repeat the id (needs `recordings:delete`, from `clipy login --allow-delete`).

| replace_transcript | Replace a recording's transcript with text you author (needs the ingest scope). Call get_transcript first and pass its revision; stale replacements are rejected instead of overwriting a concurrent edit. The summary regenerates automatically. Marked as agent-edited, never passed off as spee

Only the beginning is shown; read the rest in the repo

Online MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

@clipy/mcp

Setup

Claude Code

Codex

Claude Desktop / Cursor / Windsurf

Setting the key explicitly

Hosted connector

For MCP directories and reviewers

Tools