@clipy/mcp - npm Package Compare versions

Comparing version

0.10.0

0.11.0

+1

-1

package.json

		{
		"name": "@clipy/mcp",
		"version": "0.10.0",
		"version": "0.11.0",
		"mcpName": "online.clipy/mcp",
		@@ -5,0 +5,0 @@ "description": "Model Context Protocol (MCP) server for Clipy — give Claude, Cursor, and other AI agents read access to your screen recordings' transcripts, AI summaries, and key moments with frames.",

+5

-1

README.md

		@@ -16,2 +16,6 @@ # @clipy/mcp

		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
		@@ -100,2 +104,3 @@ write tools — `record`, the session tools (`start_recording`, `add_marker`, `add_chapter`,
		\| --- \| --- \|
		\| `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 your recordings by keyword (title + description). \|
		@@ -116,3 +121,2 @@ \| `list_recordings` \| List your most recent recordings. \|
		\| `abort_recording` \| Discard the active session; nothing is uploaded. \|
		\| `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". \|
		\| `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. \|
		@@ -119,0 +123,0 @@ \| `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. \|

dist/index.js

Sorry, the diff of this file is too big to display

		@@ -16,2 +16,6 @@ # @clipy/mcp

		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
		@@ -100,2 +104,3 @@ write tools — `record`, the session tools (`start_recording`, `add_marker`, `add_chapter`,
		\| --- \| --- \|
		\| `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 your recordings by keyword (title + description). \|
		@@ -116,3 +121,2 @@ \| `list_recordings` \| List your most recent recordings. \|
		\| `abort_recording` \| Discard the active session; nothing is uploaded. \|
		\| `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". \|
		\| `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. \|
		@@ -119,0 +123,0 @@ \| `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. \|

@clipy/mcp - npm Package Compare versions

Improved metrics