screenpipe-mcp 0.7.0 → 0.8.0

package/README.md

@@ -1,6 +1,6 @@
 # Screenpipe MCP Server
 
-<a href="https://www.pulsemcp.com/servers/mediar-ai-screenpipe"><img src="https://www.pulsemcp.com/badge/top-pick/mediar-ai-screenpipe" width="400" alt="PulseMCP Badge"></a>
+<a href="https://www.pulsemcp.com/servers/screenpipe-screenpipe"><img src="https://www.pulsemcp.com/badge/top-pick/screenpipe-screenpipe" width="400" alt="PulseMCP Badge"></a>
 
 <br/>
 
@@ -33,8 +33,8 @@ The easiest way to use screenpipe-mcp is with npx. Edit your Claude Desktop conf
 Clone and build from source:
 
 ```bash
-git clone https://github.com/mediar-ai/screenpipe
-cd screenpipe/screenpipe-integrations/screenpipe-mcp
+git clone https://github.com/screenpipe/screenpipe
+cd screenpipe/crates/screenpipe-integrations/screenpipe-mcp
 npm install
 npm run build
 ```

package/dist/index.js

@@ -81,7 +81,11 @@ const BASE_TOOLS = [
         description: "Search screenpipe's recorded content: screen text (OCR), audio transcriptions, and UI elements. " +
             "Returns timestamped results with app context. " +
             "Call with no parameters to get recent activity. " +
-            "Use the 'screenpipe://context' resource for current time when building time-based queries.",
+            "Use the 'screenpipe://context' resource for current time when building time-based queries.\n\n" +
+            "DEEP LINKS: When referencing specific moments in results, create clickable timeline links:\n" +
+            "Format: [readable time](screenpipe://timeline?timestamp=ISO8601_TIMESTAMP)\n" +
+            "Example: [10:30 AM](screenpipe://timeline?timestamp=2024-01-15T18:30:00Z)\n" +
+            "Users can click these links to jump directly to that moment in their timeline.",
         annotations: {
             title: "Search Content",
             readOnlyHint: true,
@@ -374,7 +378,19 @@ Screenpipe captures three types of data:
 1. Read screenpipe://context first to get current timestamps
 2. Use search-ui-events for "what did I type?" queries
 3. Use get-ui-event-stats to understand app usage patterns
-4. Combine search-content (what was on screen) with search-ui-events (what was done)`,
+4. Combine search-content (what was on screen) with search-ui-events (what was done)
+
+## Timeline Deep Links
+When showing search results to users, create clickable links to specific moments:
+
+**Format:** \`[readable time](screenpipe://timeline?timestamp=ISO8601_TIMESTAMP)\`
+
+**Examples:**
+- \`[10:30 AM](screenpipe://timeline?timestamp=2024-01-15T18:30:00Z)\`
+- \`[yesterday at 3pm](screenpipe://timeline?timestamp=2024-01-14T15:00:00Z)\`
+
+Users can click these links to jump directly to that moment in their screenpipe timeline.
+Always use the exact timestamp from search results when creating these links.`,
                     },
                 ],
             };

package/manifest.json

@@ -2,7 +2,7 @@
   "manifest_version": "0.3",
   "name": "screenpipe",
   "display_name": "Screenpipe",
-  "version": "0.5.0",
+  "version": "0.8.0",
   "description": "Search your screen recordings and audio transcriptions with AI",
   "long_description": "Screenpipe is a 24/7 screen and audio recorder that lets you search everything you've seen or heard. This extension connects Claude to your local screenpipe instance, enabling AI-powered search through your digital memory.",
   "author": {
@@ -11,11 +11,11 @@
   },
   "repository": {
     "type": "git",
-    "url": "https://github.com/mediar-ai/screenpipe"
+    "url": "https://github.com/screenpipe/screenpipe"
   },
   "homepage": "https://screenpi.pe",
-  "documentation": "https://github.com/mediar-ai/screenpipe/tree/main/screenpipe-integrations/screenpipe-mcp",
-  "support": "https://github.com/mediar-ai/screenpipe/issues",
+  "documentation": "https://github.com/screenpipe/screenpipe/tree/main/crates/screenpipe-integrations/screenpipe-mcp",
+  "support": "https://github.com/screenpipe/screenpipe/issues",
   "license": "MIT",
   "server": {
     "type": "node",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "screenpipe-mcp",
-  "version": "0.7.0",
+  "version": "0.8.0",
   "description": "MCP server for screenpipe - search your screen recordings and audio transcriptions",
   "main": "dist/index.js",
   "bin": {

package/src/index.ts

@@ -64,7 +64,11 @@ const BASE_TOOLS: Tool[] = [
       "Search screenpipe's recorded content: screen text (OCR), audio transcriptions, and UI elements. " +
       "Returns timestamped results with app context. " +
       "Call with no parameters to get recent activity. " +
-      "Use the 'screenpipe://context' resource for current time when building time-based queries.",
+      "Use the 'screenpipe://context' resource for current time when building time-based queries.\n\n" +
+      "DEEP LINKS: When referencing specific moments in results, create clickable timeline links:\n" +
+      "Format: [readable time](screenpipe://timeline?timestamp=ISO8601_TIMESTAMP)\n" +
+      "Example: [10:30 AM](screenpipe://timeline?timestamp=2024-01-15T18:30:00Z)\n" +
+      "Users can click these links to jump directly to that moment in their timeline.",
     annotations: {
       title: "Search Content",
       readOnlyHint: true,
@@ -369,7 +373,19 @@ Screenpipe captures three types of data:
 1. Read screenpipe://context first to get current timestamps
 2. Use search-ui-events for "what did I type?" queries
 3. Use get-ui-event-stats to understand app usage patterns
-4. Combine search-content (what was on screen) with search-ui-events (what was done)`,
+4. Combine search-content (what was on screen) with search-ui-events (what was done)
+
+## Timeline Deep Links
+When showing search results to users, create clickable links to specific moments:
+
+**Format:** \`[readable time](screenpipe://timeline?timestamp=ISO8601_TIMESTAMP)\`
+
+**Examples:**
+- \`[10:30 AM](screenpipe://timeline?timestamp=2024-01-15T18:30:00Z)\`
+- \`[yesterday at 3pm](screenpipe://timeline?timestamp=2024-01-14T15:00:00Z)\`
+
+Users can click these links to jump directly to that moment in their screenpipe timeline.
+Always use the exact timestamp from search results when creating these links.`,
           },
         ],
       };