screenpipe-mcp 0.18.10 → 0.18.11

package/LICENSE.md

@@ -0,0 +1,90 @@
+# Screenpipe Commercial License
+
+Copyright (c) 2024-2026 Mediar, Inc. (dba Screenpipe). All rights reserved.
+
+## 1. Definitions
+
+"Licensed Work" means the Screenpipe software covered by this license,
+including its source code and documentation, and any binaries built from
+that source code.
+
+"Licensor" means Mediar, Inc. (dba Screenpipe).
+
+"You" means the individual or entity exercising rights under this license.
+
+"Commercial Use" means any use of the Licensed Work:
+  (a) in a business or production environment;
+  (b) to generate revenue or to support revenue-generating activity; or
+  (c) by or on behalf of a for-profit entity, after the Evaluation period.
+
+## 2. Free Use
+
+You may use, copy, modify, and run the Licensed Work at no charge for:
+  - Personal, non-commercial use;
+  - Non-profit, educational, or research use;
+  - Evaluation, development, and testing for up to seven (7) days,
+    at any organization size.
+
+## 3. Official Builds and Subscriptions
+
+This license governs the source code of the Licensed Work and any binaries
+built from it by you or by third parties. It does not govern official
+prebuilt builds of Screenpipe distributed by the Licensor. Use of official
+builds is governed by the Screenpipe Terms of Service at
+https://screenpi.pe/terms and by the terms of your subscription or other
+app license.
+
+For clarity: one subscription or lifetime license per person, covering
+that person's own devices, including that person's own work use. Up to
+four (4) individual licenses may be used within a single company; five
+(5) or more users at one company require a Screenpipe Team or Enterprise
+plan, regardless of who pays for the individual licenses. Machines not
+tied to an individual licensed user (servers, shared or unattended
+machines) require a commercial agreement with the Licensor.
+
+## 4. Commercial Use Requires a Paid License
+
+Any Commercial Use of the Licensed Work requires a separate paid commercial
+license from the Licensor. This applies regardless of company size,
+headcount, revenue, or funding. Contact louis@screenpi.pe or visit
+https://screenpi.pe/commercial-license.
+
+## 5. Prohibited Without a Commercial License
+
+Without a valid commercial license you may not:
+  - Sell, sublicense, or distribute the Licensed Work as part of a
+    commercial product or service;
+  - Provide the Licensed Work as a hosted or managed service to third parties;
+  - Embed or integrate the Licensed Work into a product offered to customers;
+  - Use the Licensed Work to build, offer, or operate a competing product
+    or service.
+
+## 6. Ownership
+
+The Licensor and its licensors retain all right, title, and interest in the
+Licensed Work, including any modifications or patches you make. No rights are
+granted except those expressly stated in this license.
+
+## 7. Termination
+
+Any use outside the terms of this license terminates your rights
+automatically. On termination you must cease all use and destroy all copies
+in your possession.
+
+## 8. Warranty Disclaimer
+
+THE LICENSED WORK IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
+OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+LICENSOR BE LIABLE FOR ANY CLAIM, DAMAGES, OR OTHER LIABILITY, WHETHER IN AN
+ACTION OF CONTRACT, TORT, OR OTHERWISE, ARISING FROM, OUT OF, OR IN
+CONNECTION WITH THE LICENSED WORK OR THE USE OR OTHER DEALINGS IN THE
+LICENSED WORK.
+
+---
+
+This license applies to all code in this repository.
+
+Versions of Screenpipe previously released under the MIT license remain
+available under the MIT license. This license applies to this version and
+all later versions of the Licensed Work.

package/README.md

@@ -179,6 +179,7 @@ Get accessibility text, parsed tree nodes, and extracted URLs for a specific fra
 - All timestamps are handled in UTC
 - Results are formatted for readability in Claude's interface
 - macOS automation features require accessibility permissions
+- The MCP tools already return compact, readable text. If you instead call the underlying screenpipe REST API directly (e.g. via `curl`), the list endpoints (`/search`, `/elements`, `/frames/{id}/elements`) accept `?format=csv|tsv` for a columnar table (column names written once) and `?fields=a,b,c` to select only the columns you need (dotted paths like `content.text`). On list-shaped results that is roughly a 70% token cut versus the default JSON, which stays unchanged when neither param is set.
 
 ## Privacy Policy
 

package/dist/index.js

@@ -315,6 +315,10 @@ const TOOLS = [
                 },
                 speaker_ids: { type: "string", description: "Comma-separated speaker IDs to filter audio" },
                 speaker_name: { type: "string", description: "Filter audio by speaker name (case-insensitive partial match)" },
+                tags: {
+                    type: "string",
+                    description: "Comma-separated tags; returns only items carrying ALL of them (e.g. 'person:ada,project:atlas'). Works for screen + audio (content_type 'ocr'/'audio'/'all', tags written by add-tags) AND memories (content_type 'memory', tags written by update-memory). Same tag string links across all three, so two items sharing a tag are connected. Use namespaced tags (person:, project:, topic:) to link people/projects/topics. content_type 'input' and 'accessibility' have no tags and return nothing when this is set.",
+                },
                 max_content_length: {
                     type: "integer",
                     description: "Truncate each result's text via middle-truncation. Use 200-500 to keep responses compact.",
@@ -426,7 +430,7 @@ const TOOLS = [
             properties: {
                 id: { type: "integer", description: "Memory ID — omit to create new, provide to update/delete" },
                 content: { type: "string", description: "Memory text (required for creation)" },
-                tags: { type: "array", items: { type: "string" }, description: "Categorization tags (e.g. ['work', 'project-x'])" },
+                tags: { type: "array", items: { type: "string" }, description: "Tags. Prefer namespaced (person:ada, project:atlas, topic:pricing) so this memory links to the same people/projects you tag on frames/audio. Retrieve with search-content content_type='memory' tags='person:ada'." },
                 importance: { type: "number", description: "0.0 (trivial) to 1.0 (critical). Default 0.5." },
                 source_context: { type: "object", description: "Optional metadata linking to source (app, timestamp, etc.)" },
                 delete: { type: "boolean", description: "Set true to delete the memory identified by id" },
@@ -486,14 +490,18 @@ const TOOLS = [
     },
     {
         name: "add-tags",
-        description: "Add tags to a content item (vision frame or audio chunk) for organization and retrieval.",
+        description: "Tag a screen frame (vision) or audio chunk (audio) so it can be retrieved later. " +
+            "Tags are a shared linking layer: use namespaced tags (person:ada, project:atlas, topic:pricing) to connect a capture to a person, project, or topic. " +
+            "The SAME tag string also works on memories (via update-memory), so tagging a frame and a memory with person:ada links them. " +
+            "Retrieve later with search-content tags='person:ada' (add content_type+start_time/end_time to scope to a timeframe). " +
+            "Note: frames are pruned by retention, so for durable links prefer tagging a memory; tag frames/audio for shorter-term recall.",
         annotations: { title: "Add Tags", readOnlyHint: false, destructiveHint: false, openWorldHint: false },
         inputSchema: {
             type: "object",
             properties: {
-                content_type: { type: "string", enum: ["vision", "audio"], description: "Type of content to tag" },
-                id: { type: "integer", description: "Content item ID" },
-                tags: { type: "array", items: { type: "string" }, description: "Tags to add" },
+                content_type: { type: "string", enum: ["vision", "audio"], description: "vision = screen frame, audio = audio chunk. Get the id from search-content results (frame_id / chunk_id)." },
+                id: { type: "integer", description: "Content item ID (OCR result frame_id, or audio result chunk_id)" },
+                tags: { type: "array", items: { type: "string" }, description: "Tags to add. Prefer namespaced: person:<name>, project:<name>, topic:<name>." },
             },
             required: ["content_type", "id", "tags"],
         },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "screenpipe-mcp",
-  "version": "0.18.10",
+  "version": "0.18.11",
   "description": "MCP server for screenpipe - search your screen recordings and audio transcriptions",
   "main": "dist/index.js",
   "bin": {
@@ -28,7 +28,7 @@
     "audio-transcription"
   ],
   "author": "Screenpipe",
-  "license": "MIT",
+  "license": "SEE LICENSE IN LICENSE.md",
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.27.1"
   },

package/src/index.ts

@@ -302,6 +302,11 @@ const TOOLS: Tool[] = [
         },
         speaker_ids: { type: "string", description: "Comma-separated speaker IDs to filter audio" },
         speaker_name: { type: "string", description: "Filter audio by speaker name (case-insensitive partial match)" },
+        tags: {
+          type: "string",
+          description:
+            "Comma-separated tags; returns only items carrying ALL of them (e.g. 'person:ada,project:atlas'). Works for screen + audio (content_type 'ocr'/'audio'/'all', tags written by add-tags) AND memories (content_type 'memory', tags written by update-memory). Same tag string links across all three, so two items sharing a tag are connected. Use namespaced tags (person:, project:, topic:) to link people/projects/topics. content_type 'input' and 'accessibility' have no tags and return nothing when this is set.",
+        },
         max_content_length: {
           type: "integer",
           description: "Truncate each result's text via middle-truncation. Use 200-500 to keep responses compact.",
@@ -420,7 +425,7 @@ const TOOLS: Tool[] = [
       properties: {
         id: { type: "integer", description: "Memory ID — omit to create new, provide to update/delete" },
         content: { type: "string", description: "Memory text (required for creation)" },
-        tags: { type: "array", items: { type: "string" }, description: "Categorization tags (e.g. ['work', 'project-x'])" },
+        tags: { type: "array", items: { type: "string" }, description: "Tags. Prefer namespaced (person:ada, project:atlas, topic:pricing) so this memory links to the same people/projects you tag on frames/audio. Retrieve with search-content content_type='memory' tags='person:ada'." },
         importance: { type: "number", description: "0.0 (trivial) to 1.0 (critical). Default 0.5." },
         source_context: { type: "object", description: "Optional metadata linking to source (app, timestamp, etc.)" },
         delete: { type: "boolean", description: "Set true to delete the memory identified by id" },
@@ -483,14 +488,18 @@ const TOOLS: Tool[] = [
   {
     name: "add-tags",
     description:
-      "Add tags to a content item (vision frame or audio chunk) for organization and retrieval.",
+      "Tag a screen frame (vision) or audio chunk (audio) so it can be retrieved later. " +
+      "Tags are a shared linking layer: use namespaced tags (person:ada, project:atlas, topic:pricing) to connect a capture to a person, project, or topic. " +
+      "The SAME tag string also works on memories (via update-memory), so tagging a frame and a memory with person:ada links them. " +
+      "Retrieve later with search-content tags='person:ada' (add content_type+start_time/end_time to scope to a timeframe). " +
+      "Note: frames are pruned by retention, so for durable links prefer tagging a memory; tag frames/audio for shorter-term recall.",
     annotations: { title: "Add Tags", readOnlyHint: false, destructiveHint: false, openWorldHint: false },
     inputSchema: {
       type: "object",
       properties: {
-        content_type: { type: "string", enum: ["vision", "audio"], description: "Type of content to tag" },
-        id: { type: "integer", description: "Content item ID" },
-        tags: { type: "array", items: { type: "string" }, description: "Tags to add" },
+        content_type: { type: "string", enum: ["vision", "audio"], description: "vision = screen frame, audio = audio chunk. Get the id from search-content results (frame_id / chunk_id)." },
+        id: { type: "integer", description: "Content item ID (OCR result frame_id, or audio result chunk_id)" },
+        tags: { type: "array", items: { type: "string" }, description: "Tags to add. Prefer namespaced: person:<name>, project:<name>, topic:<name>." },
       },
       required: ["content_type", "id", "tags"],
     },