@dudamel/mcp-agents 2026.924.1 → 2026.929.1

package/dist/index.js

@@ -137,13 +137,7 @@ function createSurfaceServer(opts) {
   const ctx = {
     role: config.role,
     readOnly: config.readOnly ?? false,
-    agentName: config.agentName,
-    callChain: config.callChain,
-    turnId: config.turnId,
-    rootTurnId: config.rootTurnId,
-    conversationId: config.conversationId,
-    requesterUserId: config.requesterUserId,
-    responseTarget: config.responseTarget
+    agentName: config.agentName
   };
   const host = withReadOnlyFilter(server, ctx.readOnly);
   for (const register of opts.registrars)
@@ -263,104 +257,6 @@ function registerAgentTools(server, client, ctx) {
       return jsonResult(result);
     }
   );
-  server.registerTool(
-    "send-message-to-agent",
-    {
-      description: "Send a message to a PEER Dudamel agent and get their response. Peers are the agents listed in the Peer Agents section of your system prompt: separate agents with their own tools, memory and history, running in their own process. This is the ONLY way to reach them \u2014 your coding tool's own agent-messaging tool (e.g. SendMessage) sees only subagents spawned inside your session and cannot reach a peer. Use this to delegate tasks to or ask questions of another Dudamel agent.",
-      inputSchema: {
-        agentName: z.string().describe("Target agent name (as shown in the peer agents list)"),
-        message: z.string().describe("Message to send to the target agent")
-      },
-      annotations: { readOnlyHint: false, destructiveHint: false }
-    },
-    async ({ agentName, message }) => {
-      const result = await client.post(
-        `/api/agents/by-name/${encodeURIComponent(agentName)}/message`,
-        // The chain this turn arrived with, plus ourselves (Plan 43 C1). This used to send a
-        // hardcoded `depth: 0`, which made the server's depth guard decorative: nothing ever
-        // reported being deeper than zero, so A→B→C→D was unbounded and A→B→A unnoticed.
-        {
-          message,
-          callChain: [...ctx.callChain ?? [], ...ctx.agentName ? [ctx.agentName] : []],
-          fromAgent: ctx.agentName,
-          // Plan 43 C3: the callee's turn records WHICH turn asked, so a multi-agent
-          // interaction can be reconstructed as a tree instead of guessed from timestamps.
-          parentTurnId: ctx.turnId,
-          rootTurnId: ctx.rootTurnId ?? ctx.turnId
-        }
-      );
-      return jsonResult(result);
-    }
-  );
-  server.registerTool(
-    "notify-agent",
-    {
-      description: "Hand control back to the conversation that launched THIS workflow run. Use it to report an outcome or to ask the user something through the agent, from a workflow step. Only works from inside a workflow execution, and only for the conversation that launched it \u2014 pass the ids from `{{ trigger.callback }}`. Nobody is blocked waiting: the message is delivered and the agent answers in its own channel.",
-      inputSchema: {
-        conversationId: z.string().describe("From `{{ trigger.callback.conversationId }}` \u2014 the conversation to resume"),
-        message: z.string().describe("What to tell the agent (it will act on it, not echo it)")
-      },
-      annotations: { readOnlyHint: false, destructiveHint: false }
-    },
-    async ({ conversationId, message }) => {
-      const executionWorkflowId = process.env["DUDAMEL_WORKFLOW_ID"];
-      if (!executionWorkflowId) {
-        throw new Error(
-          "notify-agent requires a workflow execution context (DUDAMEL_WORKFLOW_ID) \u2014 it only works from a workflow step, not from an agent conversation."
-        );
-      }
-      const result = await client.post("/api/agents/notify", {
-        conversationId,
-        executionWorkflowId,
-        message,
-        callChain: ctx.callChain
-      });
-      return jsonResult(result);
-    }
-  );
-  server.registerTool(
-    "ask-agent",
-    {
-      description: 'Ask the human a question THROUGH the agent, from a workflow step, and park this run until they answer. Pair it with a `waitForSignal` step on the same `signalName`. Unlike a fixed approval prompt, the agent turns a free-form answer ("s\xED dale, pero solo staging") into the structured payload your signal expects. Only works inside a workflow execution, and only for the conversation that launched it \u2014 pass the id from `{{ trigger.callback.conversationId }}`.',
-      inputSchema: {
-        conversationId: z.string().describe("From `{{ trigger.callback.conversationId }}` \u2014 where to ask"),
-        question: z.string().describe("What to ask the human, in their language"),
-        signalName: z.string().optional().describe("Signal your waitForSignal step listens on (default: humanApproval)")
-      },
-      annotations: { readOnlyHint: false, destructiveHint: false }
-    },
-    async ({ conversationId, question, signalName }) => {
-      const executionWorkflowId = process.env["DUDAMEL_WORKFLOW_ID"];
-      if (!executionWorkflowId) {
-        throw new Error(
-          "ask-agent requires a workflow execution context (DUDAMEL_WORKFLOW_ID) \u2014 it only works from a workflow step, not from an agent conversation."
-        );
-      }
-      const result = await client.post("/api/conversation-waits", {
-        conversationId,
-        executionWorkflowId,
-        question,
-        signalName: signalName ?? "humanApproval",
-        callChain: ctx.callChain
-      });
-      return jsonResult(result);
-    }
-  );
-  server.registerTool(
-    "answer-workflow",
-    {
-      description: "Unblock a workflow that is waiting on the human, with the answer turned into the payload it expects. Call it once you actually have the answer \u2014 translating what the person said into structured fields is your job here, and the reason a workflow asks through you instead of posting a fixed form.",
-      inputSchema: {
-        waitId: z.string().describe("The waitId the workflow gave you when it asked"),
-        payload: z.record(z.unknown()).optional().describe('Structured answer for the signal, e.g. {"approved": true, "env": "staging"}')
-      },
-      annotations: { readOnlyHint: false, destructiveHint: false }
-    },
-    async ({ waitId, payload }) => {
-      const result = await client.post("/api/conversation-waits/answer", { waitId, payload });
-      return jsonResult(result);
-    }
-  );
   server.registerTool(
     "update-agent",
     {

package/dist/stdio-server.js

@@ -168,13 +168,7 @@ function createSurfaceServer(opts) {
   const ctx2 = {
     role: config.role,
     readOnly: config.readOnly ?? false,
-    agentName: config.agentName,
-    callChain: config.callChain,
-    turnId: config.turnId,
-    rootTurnId: config.rootTurnId,
-    conversationId: config.conversationId,
-    requesterUserId: config.requesterUserId,
-    responseTarget: config.responseTarget
+    agentName: config.agentName
   };
   const host = withReadOnlyFilter(server2, ctx2.readOnly);
   for (const register of opts.registrars)
@@ -184,28 +178,13 @@ function createSurfaceServer(opts) {
 
 // ../common/dist/stdio.js
 function resolveStdioContext() {
-  let responseTarget;
-  const rawTarget = process.env["DUDAMEL_RESPONSE_TARGET"];
-  if (rawTarget) {
-    try {
-      responseTarget = JSON.parse(rawTarget);
-    } catch {
-      process.stderr.write("Warning: DUDAMEL_RESPONSE_TARGET is not valid JSON \u2014 ignoring.\n");
-    }
-  }
   return {
     apiUrl: process.env["DUDAMEL_API_URL"] ?? "http://localhost:3000",
     apiKey: process.env["DUDAMEL_API_KEY"],
     envRole: process.env["DUDAMEL_USER_ROLE"],
     // read/write access is per agent-assignment (Plan 52); the spawner injects the mode.
     readOnly: process.env["DUDAMEL_MCP_MODE"] === "readonly",
-    agentName: process.env["DUDAMEL_AGENT_NAME"],
-    callChain: (process.env["DUDAMEL_CALL_CHAIN"] ?? "").split(",").map((s) => s.trim()).filter(Boolean),
-    turnId: process.env["DUDAMEL_TURN_ID"],
-    rootTurnId: process.env["DUDAMEL_ROOT_TURN_ID"],
-    conversationId: process.env["DUDAMEL_CONVERSATION_ID"],
-    requesterUserId: process.env["DUDAMEL_REQUESTER_USER_ID"],
-    responseTarget
+    agentName: process.env["DUDAMEL_AGENT_NAME"]
   };
 }
 
@@ -321,104 +300,6 @@ function registerAgentTools(server2, client, ctx2) {
       return jsonResult(result);
     }
   );
-  server2.registerTool(
-    "send-message-to-agent",
-    {
-      description: "Send a message to a PEER Dudamel agent and get their response. Peers are the agents listed in the Peer Agents section of your system prompt: separate agents with their own tools, memory and history, running in their own process. This is the ONLY way to reach them \u2014 your coding tool's own agent-messaging tool (e.g. SendMessage) sees only subagents spawned inside your session and cannot reach a peer. Use this to delegate tasks to or ask questions of another Dudamel agent.",
-      inputSchema: {
-        agentName: z.string().describe("Target agent name (as shown in the peer agents list)"),
-        message: z.string().describe("Message to send to the target agent")
-      },
-      annotations: { readOnlyHint: false, destructiveHint: false }
-    },
-    async ({ agentName, message }) => {
-      const result = await client.post(
-        `/api/agents/by-name/${encodeURIComponent(agentName)}/message`,
-        // The chain this turn arrived with, plus ourselves (Plan 43 C1). This used to send a
-        // hardcoded `depth: 0`, which made the server's depth guard decorative: nothing ever
-        // reported being deeper than zero, so A→B→C→D was unbounded and A→B→A unnoticed.
-        {
-          message,
-          callChain: [...ctx2.callChain ?? [], ...ctx2.agentName ? [ctx2.agentName] : []],
-          fromAgent: ctx2.agentName,
-          // Plan 43 C3: the callee's turn records WHICH turn asked, so a multi-agent
-          // interaction can be reconstructed as a tree instead of guessed from timestamps.
-          parentTurnId: ctx2.turnId,
-          rootTurnId: ctx2.rootTurnId ?? ctx2.turnId
-        }
-      );
-      return jsonResult(result);
-    }
-  );
-  server2.registerTool(
-    "notify-agent",
-    {
-      description: "Hand control back to the conversation that launched THIS workflow run. Use it to report an outcome or to ask the user something through the agent, from a workflow step. Only works from inside a workflow execution, and only for the conversation that launched it \u2014 pass the ids from `{{ trigger.callback }}`. Nobody is blocked waiting: the message is delivered and the agent answers in its own channel.",
-      inputSchema: {
-        conversationId: z.string().describe("From `{{ trigger.callback.conversationId }}` \u2014 the conversation to resume"),
-        message: z.string().describe("What to tell the agent (it will act on it, not echo it)")
-      },
-      annotations: { readOnlyHint: false, destructiveHint: false }
-    },
-    async ({ conversationId, message }) => {
-      const executionWorkflowId = process.env["DUDAMEL_WORKFLOW_ID"];
-      if (!executionWorkflowId) {
-        throw new Error(
-          "notify-agent requires a workflow execution context (DUDAMEL_WORKFLOW_ID) \u2014 it only works from a workflow step, not from an agent conversation."
-        );
-      }
-      const result = await client.post("/api/agents/notify", {
-        conversationId,
-        executionWorkflowId,
-        message,
-        callChain: ctx2.callChain
-      });
-      return jsonResult(result);
-    }
-  );
-  server2.registerTool(
-    "ask-agent",
-    {
-      description: 'Ask the human a question THROUGH the agent, from a workflow step, and park this run until they answer. Pair it with a `waitForSignal` step on the same `signalName`. Unlike a fixed approval prompt, the agent turns a free-form answer ("s\xED dale, pero solo staging") into the structured payload your signal expects. Only works inside a workflow execution, and only for the conversation that launched it \u2014 pass the id from `{{ trigger.callback.conversationId }}`.',
-      inputSchema: {
-        conversationId: z.string().describe("From `{{ trigger.callback.conversationId }}` \u2014 where to ask"),
-        question: z.string().describe("What to ask the human, in their language"),
-        signalName: z.string().optional().describe("Signal your waitForSignal step listens on (default: humanApproval)")
-      },
-      annotations: { readOnlyHint: false, destructiveHint: false }
-    },
-    async ({ conversationId, question, signalName }) => {
-      const executionWorkflowId = process.env["DUDAMEL_WORKFLOW_ID"];
-      if (!executionWorkflowId) {
-        throw new Error(
-          "ask-agent requires a workflow execution context (DUDAMEL_WORKFLOW_ID) \u2014 it only works from a workflow step, not from an agent conversation."
-        );
-      }
-      const result = await client.post("/api/conversation-waits", {
-        conversationId,
-        executionWorkflowId,
-        question,
-        signalName: signalName ?? "humanApproval",
-        callChain: ctx2.callChain
-      });
-      return jsonResult(result);
-    }
-  );
-  server2.registerTool(
-    "answer-workflow",
-    {
-      description: "Unblock a workflow that is waiting on the human, with the answer turned into the payload it expects. Call it once you actually have the answer \u2014 translating what the person said into structured fields is your job here, and the reason a workflow asks through you instead of posting a fixed form.",
-      inputSchema: {
-        waitId: z.string().describe("The waitId the workflow gave you when it asked"),
-        payload: z.record(z.unknown()).optional().describe('Structured answer for the signal, e.g. {"approved": true, "env": "staging"}')
-      },
-      annotations: { readOnlyHint: false, destructiveHint: false }
-    },
-    async ({ waitId, payload }) => {
-      const result = await client.post("/api/conversation-waits/answer", { waitId, payload });
-      return jsonResult(result);
-    }
-  );
   server2.registerTool(
     "update-agent",
     {

package/dist/tools/agents.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"agents.d.ts","sourceRoot":"","sources":["../../src/tools/agents.ts"],"names":[],"mappings":"AACA,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,yCAAyC,CAAC;AAEzE,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,qBAAqB,CAAC;AAC5D,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,qBAAqB,CAAC;AAGvD,wBAAgB,kBAAkB,CAChC,MAAM,EAAE,SAAS,EACjB,MAAM,EAAE,gBAAgB,EACxB,GAAG,EAAE,WAAW,GACf,IAAI,CAiaN"}
+{"version":3,"file":"agents.d.ts","sourceRoot":"","sources":["../../src/tools/agents.ts"],"names":[],"mappings":"AACA,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,yCAAyC,CAAC;AAEzE,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,qBAAqB,CAAC;AAC5D,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,qBAAqB,CAAC;AAGvD,wBAAgB,kBAAkB,CAChC,MAAM,EAAE,SAAS,EACjB,MAAM,EAAE,gBAAgB,EACxB,GAAG,EAAE,WAAW,GACf,IAAI,CAmRN"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dudamel/mcp-agents",
-  "version": "2026.924.1",
+  "version": "2026.929.1",
   "description": "Dudamel agents MCP — stdio client for Dudamel's agents management surface over its REST API.",
   "license": "SEE LICENSE IN LICENSE.md",
   "type": "module",
@@ -32,8 +32,8 @@
   },
   "devDependencies": {
     "esbuild": "^0.25.0",
-    "@dudamel/mcp-common": "0.1.0",
     "@dudamel/contracts": "0.1.0",
+    "@dudamel/mcp-common": "0.1.0",
     "@dudamel/mcp-tool-contract": "0.1.0"
   },
   "scripts": {