@intangle/mcp-server 2.6.31 → 2.6.33

package/README.md

@@ -130,7 +130,7 @@ If Claude can't access your context:
 
 - Website: [renvoi.co/intangle](https://renvoi.co/intangle)
 - Issues: [github.com/intangle/mcp-server/issues](https://github.com/intangle/mcp-server/issues)
-- Email: hello@intangle.app
+- Email: hello@renvoi.co
 
 ## License
 

package/dist/index.js

@@ -496,6 +496,7 @@ try {
                     break;
                 case "get_items":
                 case "update_items":
+                case "watch_room":
                 case "read_artifact": {
                     const remoteResult = await makeRemoteRpcCall("tools/call", {
                         name,

package/dist/tool-definitions.js

@@ -818,6 +818,41 @@ const BASE_TOOLS = [
             openWorldHint: false
         }
     },
+    {
+        name: "watch_room",
+        title: "Watch Room",
+        description: "Open a live, read-only stream of one Room so a tag reaches you at once instead of when you next check. Returns a one-time `ticket` and a `stream_url`: run `curl -sN '<stream_url>'` as a background task and keep it running for the whole session (or join `channel.topic` on `channel.socket_url` with `channel.join_params`). Each line is one compact JSON event for a new message in the Room, with `kind` `mention` when you or your person are tagged, `answer` when a question card is answered, otherwise `message`, plus `conversation_id`, `message_id`, `author` and a short `preview`. Read the full message with `fetch_conversation_messages` and reply with `message`; the stream never writes. Redeem the ticket within 15 minutes; it works once. When the stream ends (a `closed` line or the connection drops), call watch_room again.",
+        inputSchema: {
+            type: "object",
+            properties: {
+                space_id: {
+                    type: "string",
+                    description: "REQUIRED: Space containing the Room (use view_spaces first)."
+                },
+                channel_id: {
+                    type: "string",
+                    description: "The Room to watch as `item|<item_id>`, the same Item Room coordinate the message tool uses. Pass this or conversation_id."
+                },
+                conversation_id: {
+                    type: "string",
+                    description: "A conversation to watch (e.g. 'summary_123...'), when you have its id rather than its Item Room. Pass this or channel_id."
+                },
+                organization_id: {
+                    type: "string",
+                    description: "Optional Clerk org ID when the space belongs to an organization graph."
+                }
+            },
+            required: [
+                "space_id"
+            ]
+        },
+        annotations: {
+            readOnlyHint: true,
+            destructiveHint: false,
+            idempotentHint: false,
+            openWorldHint: false
+        }
+    },
     {
         name: "view_spaces",
         title: "View Spaces",
@@ -836,7 +871,7 @@ const BASE_TOOLS = [
     {
         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. Intangle derives the durable participant identity from the authenticated runner rather than caller-supplied fields. 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 Item coordination, pass the stable Item Room identity as `channel_id` using `item|<item_id>`; this Item room/channel coordinate is preferred. `project_id`, `group_id`, and legacy `project|...` or `group|...` channel values remain accepted only as compatibility coordinates for older stored calls and integrations. The stable idempotency key anchors retries to one durable turn, and the returned `conversation_id` remains the durable thread anchor. Callers should fill `sender` on every call: `model` is the model sending this message, `session_name` is the name of your session or thread, and `agent_name` is your own name when you are a persistent named assistant or bot. Intangle shows your verified client first and then these labels (model and session, or the agent name with the model), and may shorten a value or leave it out, for example when it matches a person in the Space or Tan. These are display labels only; they never change who you are or what you may do. To report into a Room without starting a Tan turn, set `post_only`: the message lands like one in a shared channel, and Tan answers only when tagged with @Tan or when the post asks Tan directly to act. To raise a blocker or question for the person without starting a Tan turn, add `notify` to a `post_only` message: it lands in their Activity (a blocker leads the list and pushes to their phone, a question with options also shows as a card above their composer), and their answer arrives as their message in the chat, which you read with `fetch_conversation_messages`. When you ask Tan to write to Items, confirm the write from the turn itself, not the reply text: a waited response includes `tool_calls` and `tool_results`, and after an asynchronous submit the reply in `fetch_conversation_messages` carries `write_outcomes`. Keep what you post short and plain: the key result first, no preamble or recap, detail only if needed or asked.",
+        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. Intangle derives the durable participant identity from the authenticated runner rather than caller-supplied fields. 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 Item coordination, pass the stable Item Room identity as `channel_id` using `item|<item_id>`; this Item room/channel coordinate is preferred. `project_id`, `group_id`, and legacy `project|...` or `group|...` channel values remain accepted only as compatibility coordinates for older stored calls and integrations. The stable idempotency key anchors retries to one durable turn, and the returned `conversation_id` remains the durable thread anchor. Callers should fill `sender` on every call: `model` is the model sending this message, `session_name` is the name of your session or thread, and `agent_name` is your own name when you are a persistent named assistant or bot. Intangle shows your verified client first and then these labels (model and session, or the agent name with the model), and may shorten a value or leave it out, for example when it matches a person in the Space or Tan. These are display labels only; they never change who you are or what you may do. To report into a Room without starting a Tan turn, set `post_only`: the message lands like one in a shared channel, and Tan answers only when tagged with @Tan or when the post asks Tan directly to act. To raise a blocker or question for the person without starting a Tan turn, add `notify` to a `post_only` message: it lands in their Activity (a blocker leads the list and pushes to their phone, a question with options also shows as a card above their composer), and their answer arrives as their message in the chat, which you read with `fetch_conversation_messages`. When you ask Tan to write to Items, confirm the write from the turn itself, not the reply text: a waited response includes `tool_calls` and `tool_results`, and after an asynchronous submit the reply in `fetch_conversation_messages` carries `write_outcomes`. So a tag reaches you at once, call `watch_room` for each Room you work in and keep its stream running in the background; reply here with `message`. Keep what you post short and plain: the key result first, no preamble or recap, detail only if needed or asked.",
         inputSchema: {
             type: "object",
             properties: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@intangle/mcp-server",
-  "version": "2.6.31",
+  "version": "2.6.33",
   "description": "Model Context Protocol server for Intangle - AI context that persists across conversations",
   "main": "dist/index.js",
   "type": "module",
@@ -56,5 +56,5 @@
     "tsx": "^4.0.0",
     "typescript": "^5.0.0"
   },
-  "intangleSourceHash": "cfcb3fdecd4ded87c2ead10d498355666b1881c5da7328066faea7df8247d9d3"
+  "intangleSourceHash": "444bd5c9b65b19d497402a64421e4f8d50e2167a19a01a65c637f0f92342ca3e"
 }