A
licenseNot graded
qualityA
maintenanceEnables AI agents to search and retrieve past chat transcripts from Cursor, Claude Code, and Kiro, providing a global, local memory for context-aware assistance.
129 npm
2
MIT
@clipy/mcp
Related Servers
Alternatives to @clipy/mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to store, search (keyword and semantic), retrieve, update, and delete personal browser clips from a Cloudflare-backed store, authenticated via per-user token.1-
- AlicenseNot gradedqualityDmaintenanceProvides AI agents with structured access to Zoom recorded meetings, enabling search, summarization, and action item extraction.4 npmBSD 2-Clause "Simplified"
- AlicenseAqualityBmaintenanceEnables AI agents to search videos, retrieve metadata and transcripts, pinpoint exact moments via hybrid semantic search, and conduct multi-video research with timestamp deep links—all without YouTube API keys.51MIT
- AlicenseNot gradedqualityBmaintenanceSearch within videos by dialogue, on-screen visuals, and recurring faces using natural language - connected with your favorite agent (like Claude, Codex, Hermes).52MIT
- AlicenseAqualityDmaintenanceEnables AI agents to search, watch, summarize, clip, and extract transcripts from YouTube videos, all without needing an API key or leaving the chat.911 npm53Apache 2.0
TDQS
A4.1/5.0
Scored across 21 tools
Disambiguation4/5
Each tool targets a distinct resource or action: recordings vs context documents, sessions vs one-shot capture, and the cross-library search_memory is explicitly differentiated from search_recordings. The main overlap is get_agent_context being a superset of get_summary/get_transcript/get_key_moments, but it is clearly documented as the one-call bundle, so agents can choose correctly.
Naming Consistency5/5
All tool names follow a consistent verb_noun snake_case pattern: get_, list_, search_, add_, stop_, abort_, record, wait_for_artifacts, download_recording, replace_transcript. There are no mixed conventions or vague verbs, making the set highly predictable.
Tool Count3/5
21 tools falls in the 16-25 borderline range and feels heavy for a single MCP server, even though the tools split into coherent subdomains (recording management, session recording, context documents, search). Each tool appears purposeful, but the overall surface is larger than typical well-scoped servers.
Completeness4/5
Core workflows are covered: creating recordings via record/start_recording, annotating via add_marker/add_chapter, retrieving via list/search/get/transcript/summary/key_moments/agent_context, and reading context documents. Minor gaps exist: uploaded recordings cannot be deleted or have metadata edited, and context-document import is CLI-only, but these do not break the main capture-and-retrieve loop.
Maintenance
ActivityMaintained
ResponsivenessNo issues