Back to Browse
Free
Server data from the Official MCP Registry
Read your Clipy screen recordings: search, transcripts, AI summaries, and key moments with frames.
About
Read your Clipy screen recordings: search, transcripts, AI summaries, and key moments with frames.
Security Report
5.2
Moderate5.2Moderate RiskThis is a well-architected MCP server for read-only access to Clipy screen recordings. Authentication is properly enforced via API key (with clear error messages when missing), credentials are handled securely via environment variables, and input validation is thorough using Zod schemas. The codebase exhibits good security practices including URL normalization, protocol validation for downloads, and timeout protections. One minor concern is that image frame fetches lack authentication, but this is intentional for CDN-hosted public content. No malicious patterns, exfiltration, or dangerous operations detected. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.
3 files analyzed · 7 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
What You'll Need
Set these up before or after installing:
Clipy API key — create one free at https://clipy.online/settings/api-keysRequired
Environment variable: CLIPY_API_KEY
Override the Clipy API base URL (defaults to https://clipy.online)
Environment variable: CLIPY_API_URL
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"online-clipy-mcp": {
"env": {
"CLIPY_API_KEY": "your-clipy-api-key-here",
"CLIPY_API_URL": "your-clipy-api-url-here"
},
"args": [
"-y",
"@clipy/mcp"
],
"command": "npx"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
@clipy/mcp
Give your AI agent access to your Clipy screen recordings.
This is a Model Context Protocol (MCP) server. It lets Claude, Cursor, Windsurf, and other MCP-capable agents search your recordings and read their transcripts, AI summaries, and key moments — including the video frames of exactly what the speaker pointed at, delivered as inline images your agent can see. So you can do things like "read this bug-report recording and ship the fix" without leaving your agent.
Zero-setup alternative: every public Clipy share link is also agent-readable without this server — append
.md(e.g.clipy.online/video/<id>.md) and any agent that can fetch a URL gets the summary, key moments with frames, and timestamped transcript. The MCP server adds private-library search, inline frame images, and one-call context bundles. More at clipy.online/for-agents.
It is read-only: it can never create, edit, or delete your recordings.
Setup
- Create a free API key at https://clipy.online/settings/api-keys (it looks like
clipy_sk_live_…). Copy it — it's shown only once. - 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 --env CLIPY_API_KEY=clipy_sk_live_xxx -- 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 --env CLIPY_API_KEY=clipy_sk_live_xxx -- npx -y @clipy/mcp
Or add it to ~/.codex/config.toml by hand:
[mcp_servers.clipy]
command = "npx"
args = ["-y", "@clipy/mcp"]
env = { CLIPY_API_KEY = "clipy_sk_live_xxx" }
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"],
"env": { "CLIPY_API_KEY": "clipy_sk_live_xxx" }
}
}
}
Tools
| Tool | What it does |
|---|---|
search_recordings | Search your recordings by keyword (title + description). |
list_recordings | List your most recent recordings. |
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. |
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). |
All tools accept a recording's public id (the slug in its share URL) or the full
https://clipy.online/video/<id> URL.
Config
| Env var | Required | Default | Notes |
|---|---|---|---|
CLIPY_API_KEY | yes | — | Your personal key from /settings/api-keys. |
CLIPY_API_URL | no | https://clipy.online | Override for self-hosted/staging. |
Privacy
Your key only ever reads your own recordings. Revoke it any time at
/settings/api-keys. The server runs locally on your machine; your key is never sent
anywhere except to the Clipy API over HTTPS.
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Fetch
Freeby Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
80.0K
Stars
7
Installs
5.3
Security
No ratings yet
Local
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
80.0K
Stars
6
Installs
6.5
Security
No ratings yet
Local
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
137
Stars
535
Installs
8.0
Security
4.8
Local