Online MCP

Name: Online MCP
Author: manovagyanik1

作者：manovagyanik1版本 0.17.0i★ –i在你的电脑上运行

注册名称online.clipy/mcp

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i非常新↓ 87/周 · ★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 搜索与 AI 记忆
你需要填写：CLIPY_API_KEY

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： CLIPY_API_KEY, CLIPY_API_URL

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

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

在终端中运行这条命令

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

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

CLIPY_API_KEY 机密 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)

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

✓ 通过
作者与仓库一致
注册名称已通过域名 clipy.online 验证（注册中心会核实域名所有权）
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“搜索与 AI 记忆”中的其他服务器比较i

星标数多于此分类中其他 5717 个服务器的 0%
发布到注册中心的时间比此分类中其他 5717 个服务器的 59% 更新
基础检查结果等于或优于此分类中其他 5717 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Online MCP 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：CLIPY_API_KEY

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.17.0）于27天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Context7, Codebase Memory, Exa

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Context7

Up-to-date docs for AI agents

作者：upstash广泛使用↓ 97.3万/周★ 6.4万前天更新

电脑或云端

安装

Codebase Memory

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

作者：DeusData广泛使用↓ 1.8万/周★ 4.8万22天前更新

在你的电脑上运行

安装

Exa

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

作者：exa-labs广泛使用★ 52132个月前更新

在云端运行✓ exa.ai

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

@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

只显示了开头部分；其余内容请在仓库中阅读