@intangle/mcp-server 2.6.5 → 2.6.7

package/.env.local

@@ -1,3 +1,4 @@
-MCP_API_KEY=mcp_placeholder_key_will_be_replaced_by_user_specific_key
+MCP_API_KEY=mcp_user_30H8yYW7mghw0Zb8aQLhT4AsyRq_9f26b9e53ea30765ee25d9745b670afb
 NEXT_APP_URL=https://intangle.app
 VERCEL_BYPASS_TOKEN=igXBygPO1T5dWLBaVyQiN9QB7IECZ50O
+INTANGLE_REMOTE_MCP_TOKEN=mcp_user_30H8yYW7mghw0Zb8aQLhT4AsyRq_9f26b9e53ea30765ee25d9745b670afb

package/README.md

@@ -17,7 +17,7 @@ Intangle is an AI context system that gives Claude and other AI assistants persi
 Claude code by running the command below (recommend "-s" user for global across projects):
 
 ```bash
-claude mcp add intangle -s user --env MCP_API_KEY=<your-api-key-here> --env NEXT_APP_URL=https://app.intangle.app -- npx -y @intangle/mcp-server
+claude mcp add intangle -s user --env MCP_API_KEY=<your-api-key-here> --env NEXT_APP_URL=https://renvoi.co/intangle -- npx -y @intangle/mcp-server
 ```
 
 If your deployment is behind Vercel Deployment Protection (for example staging), add:
@@ -36,7 +36,7 @@ Standard MCP (Claude desktop, Cursor): by adding to your `claude_desktop_config.
       "args": ["@intangle/mcp-server"],
       "env": {
         "MCP_API_KEY": "your-api-key-here",
-        "NEXT_APP_URL": "https://app.intangle.app",
+        "NEXT_APP_URL": "https://renvoi.co/intangle",
         "VERCEL_BYPASS_TOKEN": "optional-vercel-bypass-token-for-protected-deployments"
       }
     }

package/dist/index.js

@@ -30,7 +30,7 @@ try {
     config({ quiet: true });
     config({ path: ".env.local", quiet: true });
     // Base URL for API calls to Next.js app
-    const API_BASE_URL = process.env.NEXT_APP_URL || "https://app.intangle.app";
+    const API_BASE_URL = process.env.NEXT_APP_URL || "https://renvoi.co/intangle";
     const MCP_API_KEY = process.env.MCP_API_KEY;
     const VERCEL_BYPASS_TOKEN = process.env.VERCEL_BYPASS_TOKEN || process.env.VERCEL_PROTECTION_BYPASS;
     log(`CWD: ${process.cwd()}`);
@@ -158,7 +158,7 @@ try {
             if (contentType.includes("text/html") ||
                 /^\s*<!DOCTYPE\s+html/i.test(responseBody) ||
                 /^\s*<html\b/i.test(responseBody)) {
-                throw new Error(`API call to ${buildApiUrl(endpoint)} returned HTML instead of JSON. Check NEXT_APP_URL and point it at the app host, e.g. https://app.intangle.app.`);
+                throw new Error(`API call to ${buildApiUrl(endpoint)} returned HTML instead of JSON. Check NEXT_APP_URL and point it at the app host, e.g. https://renvoi.co/intangle.`);
             }
             return JSON.parse(responseBody);
         }

package/dist/tool-definitions.js

@@ -39,7 +39,7 @@ const TOOL_DEFINITIONS = [
     {
         name: "fetch_items",
         title: "Fetch Items by ID",
-        description: "Retrieve full content for specific items by ID. Accepts single ID or array of IDs.",
+        description: "Retrieve full content for specific items by ID, including `file_*`, `artifact_*`, and `summary_*` ids. File fetches return extracted content, file metadata, chunk metadata, and decrypted `data.source_data_url` when available; use this before asking Tan to reason over a specific uploaded contract/file in detail. Artifact fetches return content plus render metadata and `config`/`state`/`data` when available.",
         inputSchema: {
             type: "object",
             properties: {
@@ -49,16 +49,17 @@ const TOOL_DEFINITIONS = [
                 },
                 id: {
                     type: "string",
-                    description: "Single ID to fetch (context or task ID like 'mem_123' or 'task_456' or 'skill_789')"
+                    description: "Single ID to fetch (e.g. `mem_123`, `task_456`, `skill_789`, `doc_321`, `file_654`, `artifact_654`, or `summary_987`)."
                 },
                 ids: {
                     type: "array",
                     items: { type: "string" },
-                    description: "Array of IDs to fetch (mix of context, task, and skill IDs). Use this to fetch multiple items in one call."
+                    description: "Array of IDs to fetch (mix of context, task, skill, document, file, artifact, insight, or conversation IDs). Use this to fetch multiple items in one call."
                 }
             }
         }
     },
+    { name: "read_artifact", title: "Read Artifact", description: "Read one existing artifact by `artifact_id` without asking Tan to restream it in chat. Returns content plus render metadata and `config`/`state`/`data` when available. Prefer this when an external agent already has the artifact id and needs the current artifact payload directly.", inputSchema: { type: "object", properties: { space_id: { type: "string", description: "Optional: Space containing the artifact. Provide this for shared/org spaces so access checks resolve against the correct graph." }, artifact_id: { type: "string", description: "REQUIRED: Existing artifact ID to read (e.g. `artifact_123`)." }, item_id: { type: "string", description: "Optional alias for `artifact_id`." }, organization_id: { type: "string", description: "Optional Clerk org ID when the space belongs to an organization graph." } }, required: ["artifact_id"] } },
     {
         name: "usage_status",
         title: "Usage Status",
@@ -750,7 +751,7 @@ const TOOL_DEFINITIONS = [
     {
         name: "message",
         title: "Message Assistant",
-        description: "Primary way to use Intangle for memory, communicating and collaborating with Tan agent in a shared thread. Send a request and either wait for one assistant turn to complete or submit asynchronously for later polling. External agents should include a stable participant_id, participant_type=`agent`, and participant_label so Tan can identify who is speaking and keep progress updates attached to the right caller. Returns assistant text plus continuity IDs (`session_id`, `conversation_id`) so callers can continue the same thread reliably across turns.",
+        description: "Primary way to use Intangle for memory, communicating and collaborating with Tan agent in a shared thread. Send a request and either wait for one assistant turn to complete or submit asynchronously for later polling. External agents should include a stable participant_id, participant_type=`agent`, and participant_label so Tan can identify who is speaking and keep progress updates attached to the right caller. Conversations are backed by `summary_*` IDs; reuse the returned `conversation_id` and reuse the returned `session_id` so callers can continue the same thread reliably across turns. For shared coordination channels, pass a stable `channel_id` and keep reusing the same `conversation_id`; `channel_id` scopes context, while `conversation_id` is the durable thread anchor.",
         inputSchema: {
             type: "object",
             properties: {
@@ -772,16 +773,24 @@ const TOOL_DEFINITIONS = [
                 },
                 new_conversation: {
                     type: "boolean",
-                    description: "Optional. When true, force a fresh conversation instead of reusing the current active thread."
+                    description: "Optional escape hatch. When true, force a fresh conversation instead of reusing the current active thread."
                 },
                 session_id: {
                     type: "string",
-                    description: "Optional runtime session ID to reuse across calls. Reuse the returned session_id for best continuity and lower warm-up overhead."
+                    description: "Optional runtime session ID to reuse across calls. For follow-up turns, reuse the exact session_id returned by the previous call for best continuity and lower warm-up overhead."
                 },
                 project_id: {
                     type: "string",
                     description: "Optional project scope for the assistant turn."
                 },
+                group_id: {
+                    type: "string",
+                    description: "Optional group scope for the assistant turn. Use this with channel_id for group-scoped coordination."
+                },
+                channel_id: {
+                    type: "string",
+                    description: "Optional route/channel scope for the assistant turn. Defaults to root when omitted. Examples: root, group|legal, project|work/launch."
+                },
                 organization_id: {
                     type: "string",
                     description: "Optional Clerk org ID when the space belongs to an organization graph."
@@ -841,6 +850,7 @@ const TOOL_DEFINITIONS = [
 const READ_ONLY_TOOLS = new Set([
     "search",
     "fetch_items",
+    "read_artifact",
     "usage_status",
     "fetch_conversation_messages",
     "list_conversation_inbox",
@@ -856,6 +866,7 @@ const DESTRUCTIVE_TOOLS = new Set([
 const IDEMPOTENT_TOOLS = new Set([
     "search",
     "fetch_items",
+    "read_artifact",
     "usage_status",
     "fetch_conversation_messages",
     "list_conversation_inbox",

package/index.ts

@@ -45,7 +45,7 @@ try {
   config({ path: ".env.local", quiet: true })
 
   // Base URL for API calls to Next.js app
-  const API_BASE_URL = process.env.NEXT_APP_URL || "https://app.intangle.app"
+  const API_BASE_URL = process.env.NEXT_APP_URL || "https://renvoi.co/intangle"
   const MCP_API_KEY = process.env.MCP_API_KEY
   const VERCEL_BYPASS_TOKEN =
     process.env.VERCEL_BYPASS_TOKEN || process.env.VERCEL_PROTECTION_BYPASS
@@ -215,7 +215,7 @@ try {
         /^\s*<html\b/i.test(responseBody)
       ) {
         throw new Error(
-          `API call to ${buildApiUrl(endpoint)} returned HTML instead of JSON. Check NEXT_APP_URL and point it at the app host, e.g. https://app.intangle.app.`
+          `API call to ${buildApiUrl(endpoint)} returned HTML instead of JSON. Check NEXT_APP_URL and point it at the app host, e.g. https://renvoi.co/intangle.`
         )
       }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@intangle/mcp-server",
-  "version": "2.6.5",
+  "version": "2.6.7",
   "description": "Model Context Protocol server for Intangle - AI context that persists across conversations",
   "main": "dist/index.js",
   "type": "module",

package/tool-definitions.ts

@@ -46,7 +46,7 @@ const TOOL_DEFINITIONS = [
     name: "fetch_items",
     title: "Fetch Items by ID",
     description:
-      "Retrieve full content for specific items by ID. Accepts single ID or array of IDs.",
+      "Retrieve full content for specific items by ID, including `file_*`, `artifact_*`, and `summary_*` ids. File fetches return extracted content, file metadata, chunk metadata, and decrypted `data.source_data_url` when available; use this before asking Tan to reason over a specific uploaded contract/file in detail. Artifact fetches return content plus render metadata and `config`/`state`/`data` when available.",
     inputSchema: {
       type: "object",
       properties: {
@@ -58,17 +58,18 @@ const TOOL_DEFINITIONS = [
         id: {
           type: "string",
           description:
-            "Single ID to fetch (context or task ID like 'mem_123' or 'task_456' or 'skill_789')"
+            "Single ID to fetch (e.g. `mem_123`, `task_456`, `skill_789`, `doc_321`, `file_654`, `artifact_654`, or `summary_987`)."
         },
         ids: {
           type: "array",
           items: { type: "string" },
           description:
-            "Array of IDs to fetch (mix of context, task, and skill IDs). Use this to fetch multiple items in one call."
+            "Array of IDs to fetch (mix of context, task, skill, document, file, artifact, insight, or conversation IDs). Use this to fetch multiple items in one call."
         }
       }
     }
   },
+  { name: "read_artifact", title: "Read Artifact", description: "Read one existing artifact by `artifact_id` without asking Tan to restream it in chat. Returns content plus render metadata and `config`/`state`/`data` when available. Prefer this when an external agent already has the artifact id and needs the current artifact payload directly.", inputSchema: { type: "object", properties: { space_id: { type: "string", description: "Optional: Space containing the artifact. Provide this for shared/org spaces so access checks resolve against the correct graph." }, artifact_id: { type: "string", description: "REQUIRED: Existing artifact ID to read (e.g. `artifact_123`)." }, item_id: { type: "string", description: "Optional alias for `artifact_id`." }, organization_id: { type: "string", description: "Optional Clerk org ID when the space belongs to an organization graph." } }, required: ["artifact_id"] } },
   {
     name: "usage_status",
     title: "Usage Status",
@@ -839,7 +840,7 @@ const TOOL_DEFINITIONS = [
     name: "message",
     title: "Message Assistant",
     description:
-      "Primary way to use Intangle for memory, communicating and collaborating with Tan agent in a shared thread. Send a request and either wait for one assistant turn to complete or submit asynchronously for later polling. External agents should include a stable participant_id, participant_type=`agent`, and participant_label so Tan can identify who is speaking and keep progress updates attached to the right caller. Returns assistant text plus continuity IDs (`session_id`, `conversation_id`) so callers can continue the same thread reliably across turns.",
+      "Primary way to use Intangle for memory, communicating and collaborating with Tan agent in a shared thread. Send a request and either wait for one assistant turn to complete or submit asynchronously for later polling. External agents should include a stable participant_id, participant_type=`agent`, and participant_label so Tan can identify who is speaking and keep progress updates attached to the right caller. Conversations are backed by `summary_*` IDs; reuse the returned `conversation_id` and reuse the returned `session_id` so callers can continue the same thread reliably across turns. For shared coordination channels, pass a stable `channel_id` and keep reusing the same `conversation_id`; `channel_id` scopes context, while `conversation_id` is the durable thread anchor.",
     inputSchema: {
       type: "object",
       properties: {
@@ -864,17 +865,27 @@ const TOOL_DEFINITIONS = [
         new_conversation: {
           type: "boolean",
           description:
-            "Optional. When true, force a fresh conversation instead of reusing the current active thread."
+            "Optional escape hatch. When true, force a fresh conversation instead of reusing the current active thread."
         },
         session_id: {
           type: "string",
           description:
-            "Optional runtime session ID to reuse across calls. Reuse the returned session_id for best continuity and lower warm-up overhead."
+            "Optional runtime session ID to reuse across calls. For follow-up turns, reuse the exact session_id returned by the previous call for best continuity and lower warm-up overhead."
         },
         project_id: {
           type: "string",
           description: "Optional project scope for the assistant turn."
         },
+        group_id: {
+          type: "string",
+          description:
+            "Optional group scope for the assistant turn. Use this with channel_id for group-scoped coordination."
+        },
+        channel_id: {
+          type: "string",
+          description:
+            "Optional route/channel scope for the assistant turn. Defaults to root when omitted. Examples: root, group|legal, project|work/launch."
+        },
         organization_id: {
           type: "string",
           description:
@@ -941,6 +952,7 @@ const TOOL_DEFINITIONS = [
 const READ_ONLY_TOOLS = new Set([
   "search",
   "fetch_items",
+  "read_artifact",
   "usage_status",
   "fetch_conversation_messages",
   "list_conversation_inbox",
@@ -958,6 +970,7 @@ const DESTRUCTIVE_TOOLS = new Set([
 const IDEMPOTENT_TOOLS = new Set([
   "search",
   "fetch_items",
+  "read_artifact",
   "usage_status",
   "fetch_conversation_messages",
   "list_conversation_inbox",