@agent-native/dispatch 0.8.17 → 0.8.18

package/src/routes/pages/workspace.tsx

@@ -11,6 +11,7 @@ import {
   IconEdit,
   IconFileText,
   IconPlus,
+  IconPlugConnected,
   IconTrash,
   IconUser,
   IconX,
@@ -87,6 +88,13 @@ const KIND_CONFIG = {
     description:
       "Reference resources - brand, positioning, persona, and domain context",
   },
+  "mcp-server": {
+    label: "MCP Server",
+    icon: IconPlugConnected,
+    pathPrefix: "mcp-servers/",
+    description:
+      "HTTP MCP servers - external tools centrally granted to app agents",
+  },
 } as const;
 
 const STARTER_GLOBAL_CONTEXT = [
@@ -135,6 +143,7 @@ function defaultResourcePath(kind: string, name: string): string {
   if (kind === "instruction") return `instructions/${slug}.md`;
   if (kind === "agent") return `agents/${slug}.md`;
   if (kind === "knowledge") return `context/${slug}.md`;
+  if (kind === "mcp-server") return `mcp-servers/${slug}.json`;
   return `${slug}.md`;
 }
 
@@ -347,8 +356,8 @@ function AddResourceDialog() {
         <DialogHeader>
           <DialogTitle>Add workspace resource</DialogTitle>
           <DialogDescription>
-            Create a skill, instruction, agent profile, or reference resource
-            that can be shared across workspace apps.
+            Create a skill, instruction, agent profile, reference resource, or
+            MCP server that can be shared across workspace apps.
           </DialogDescription>
         </DialogHeader>
         <div className="space-y-4 py-2">
@@ -364,6 +373,7 @@ function AddResourceDialog() {
                   <SelectItem value="instruction">Instruction</SelectItem>
                   <SelectItem value="agent">Agent</SelectItem>
                   <SelectItem value="knowledge">Knowledge pack</SelectItem>
+                  <SelectItem value="mcp-server">MCP server</SelectItem>
                 </SelectContent>
               </Select>
             </div>
@@ -390,7 +400,9 @@ function AddResourceDialog() {
                     ? "Research Specialist"
                     : kind === "knowledge"
                       ? "Core GTM Messaging"
-                      : "Code Style Guide"
+                      : kind === "mcp-server"
+                        ? "Zapier MCP"
+                        : "Code Style Guide"
               }
               value={name}
               onChange={(e) => setName(e.target.value)}
@@ -407,7 +419,9 @@ function AddResourceDialog() {
             <p className="text-xs text-muted-foreground">
               Skills use skills/name/SKILL.md. Guardrails in AGENTS.md or
               instructions/ auto-load in app chat. Reference resources in
-              context/ are indexed so agents can read them when relevant.
+              context/ are indexed so agents can read them when relevant. MCP
+              server resources use mcp-servers/name.json and are loaded as HTTP
+              MCP tools.
             </p>
           </div>
           <div className="space-y-2">
@@ -428,7 +442,9 @@ function AddResourceDialog() {
                     ? "---\nname: Research Specialist\ndescription: Handles research tasks\n---\n\n# Instructions\n\n..."
                     : kind === "knowledge"
                       ? "# Core GTM Messaging\n\n## Positioning\n\n## ICP\n\n## Proof points\n\n## Source\n\n"
-                      : "# Instructions\n\nAlways-on guardrails for agents across apps..."
+                      : kind === "mcp-server"
+                        ? '{\n  "type": "http",\n  "url": "https://example.com/mcp",\n  "headers": {\n    "Authorization": "Bearer ${keys.MCP_SERVER_TOKEN}"\n  },\n  "description": "Shared MCP tools for workspace apps"\n}\n'
+                        : "# Instructions\n\nAlways-on guardrails for agents across apps..."
               }
               value={content}
               onChange={(e) => setContent(e.target.value)}
@@ -447,7 +463,12 @@ function AddResourceDialog() {
           <Button
             onClick={() =>
               create.mutate({
-                kind: kind as "skill" | "instruction" | "agent" | "knowledge",
+                kind: kind as
+                  | "skill"
+                  | "instruction"
+                  | "agent"
+                  | "knowledge"
+                  | "mcp-server",
                 name,
                 description: description || undefined,
                 path: path || defaultResourcePath(kind, name),
@@ -1010,6 +1031,9 @@ export default function WorkspaceRoute() {
   const knowledge = (resources || []).filter(
     (r: any) => r.kind === "knowledge",
   );
+  const mcpServers = (resources || []).filter(
+    (r: any) => r.kind === "mcp-server",
+  );
 
   function ResourceList({
     items,
@@ -1056,7 +1080,7 @@ export default function WorkspaceRoute() {
   return (
     <DispatchShell
       title="Workspace Resources"
-      description="Manage inherited workspace skills, guardrail instructions, agent profiles, and reference resources. All-app resources are available to every app without syncing."
+      description="Manage inherited workspace skills, guardrail instructions, agent profiles, reference resources, and MCP servers. All-app resources are available to every app without syncing."
     >
       <div className="flex items-center justify-between">
         <div className="text-sm text-muted-foreground">
@@ -1087,6 +1111,9 @@ export default function WorkspaceRoute() {
           <TabsTrigger value="knowledge">
             Knowledge {knowledge.length > 0 && `(${knowledge.length})`}
           </TabsTrigger>
+          <TabsTrigger value="mcp">
+            MCP {mcpServers.length > 0 && `(${mcpServers.length})`}
+          </TabsTrigger>
         </TabsList>
 
         <TabsContent value="skills" className="mt-4">
@@ -1116,6 +1143,13 @@ export default function WorkspaceRoute() {
             emptyText="No knowledge packs yet. Add GTM, product, or domain context that apps can reuse."
           />
         </TabsContent>
+
+        <TabsContent value="mcp" className="mt-4">
+          <ResourceList
+            items={mcpServers}
+            emptyText="No workspace MCP servers yet. Add an HTTP MCP server to share external tools across apps."
+          />
+        </TabsContent>
       </Tabs>
     </DispatchShell>
   );

package/src/server/lib/workspace-resources-store.spec.ts

@@ -703,6 +703,7 @@ describe("workspace resource materialization", () => {
     expect(mocks.resourceEffectiveContext).toHaveBeenCalledWith(
       "person@example.test",
       "context/brand.md",
+      { workspaceAppId: "analytics", orgId: "org_123" },
     );
     expect(mocks.resourcePut).toHaveBeenCalledWith(
       "__workspace__",
@@ -899,6 +900,7 @@ describe("workspace resource materialization", () => {
     expect(mocks.resourceEffectiveContext).toHaveBeenCalledWith(
       "owner@example.test",
       "context/analytics-launch.md",
+      { workspaceAppId: "analytics", orgId: "org_123" },
     );
   });
 

package/src/server/lib/workspace-resources-store.ts

@@ -186,7 +186,8 @@ export type WorkspaceResourceKind =
   | "skill"
   | "instruction"
   | "agent"
-  | "knowledge";
+  | "knowledge"
+  | "mcp-server";
 export type WorkspaceResourceScope = "all" | "selected";
 
 export interface WorkspaceResourceInput {
@@ -969,10 +970,6 @@ export async function getWorkspaceResourceEffectiveContext(input: {
     await materializeGlobalResource(row);
   }
 
-  const coreContext: EffectiveResourceContext = await resourceEffectiveContext(
-    userEmail,
-    path,
-  );
   const resource = row ? workspaceResourceOption(row) : null;
   const activeGrant =
     resource?.scope === "selected" && appId
@@ -985,6 +982,15 @@ export async function getWorkspaceResourceEffectiveContext(input: {
     appId,
     activeGrantId: activeGrant?.id ?? null,
   });
+  const resolveEffectiveContext = resourceEffectiveContext as (
+    userEmail: string,
+    path: string,
+    options?: { workspaceAppId?: string | null; orgId?: string | null },
+  ) => Promise<EffectiveResourceContext>;
+  const coreContext = await resolveEffectiveContext(userEmail, path, {
+    workspaceAppId: appId,
+    orgId: ctx.orgId,
+  });
 
   return {
     appId,
@@ -1373,6 +1379,7 @@ export async function listWorkspaceResourcesOverview() {
   const instructions = resources.filter((r) => r.kind === "instruction");
   const agents = resources.filter((r) => r.kind === "agent");
   const knowledge = resources.filter((r) => r.kind === "knowledge");
+  const mcpServers = resources.filter((r) => r.kind === "mcp-server");
   const activeGrants = grants.filter((g) => g.status === "active");
 
   return {
@@ -1380,6 +1387,7 @@ export async function listWorkspaceResourcesOverview() {
     instructionCount: instructions.length,
     agentCount: agents.length,
     knowledgeCount: knowledge.length,
+    mcpServerCount: mcpServers.length,
     totalResources: resources.length,
     activeGrantCount: activeGrants.length,
   };

package/src/server/plugins/integrations.ts

@@ -10,7 +10,7 @@ const DISPATCH_INTEGRATION_SYSTEM_PROMPT = `You are the central dispatch for thi
 
 Default posture:
 - Treat Slack, Telegram, and email as shared entrypoints into the workspace.
-- Heavily delegate domain work to specialized agents through A2A (call-agent) when another app owns the job. Apps you can delegate to include slides (decks/presentations), analytics (data/dashboards), content (docs/articles), videos (Remotion compositions), forms (form builder), clips (screen recordings), design (visual designs), and images (brand image libraries and generated raster imagery).
+- Heavily delegate domain work to specialized agents through A2A (call-agent) when another app owns the job. Apps you can delegate to include slides (decks/presentations), analytics (data/dashboards), content (docs/articles), videos (Remotion compositions), forms (form builder), clips (screen recordings), design (visual designs), and assets (brand libraries plus generated images/videos).
 - Use the available-apps prompt context first, then list-connected-agents when you need fresh details, to see what agents are available before assuming a request must be handled locally.
 - When asked whether workspace apps expose agent cards or A2A endpoints, call list-workspace-apps with includeAgentCards=true. Without that probe, missing agent-card fields mean unchecked, not unavailable.
 - Treat first-party apps such as Mail, Calendar, Analytics, Brain, and Dispatch as existing hosted/connected neighbors available through links and A2A/default connected agents. Do not create wrapper apps, child apps, nested routes, or cloned template copies just to give a new app access to them; build only the genuinely new workflow and delegate cross-app work to those existing apps.
@@ -18,7 +18,7 @@ Default posture:
 - Reply in the originating thread unless the user explicitly asks you to send to a saved destination.
 
 When a user asks for something:
-- If it belongs to analytics, content, slides, videos, images, etc., delegate via call-agent — do not re-implement the domain logic in dispatch.
+- If it belongs to analytics, content, slides, videos, assets, etc., delegate via call-agent — do not re-implement the domain logic in dispatch.
 - After call-agent returns an answer, RELAY IT DIRECTLY to the user with at most a one-line preface — do not rephrase, summarize, or add commentary. The downstream agent already crafted the answer; your job is delivery, not editing. This minimizes round-trips and keeps the user-visible reply fast.
 - Exception: if the downstream agent reports a missing model/provider credential, do not name exact env vars, Vault keys, tokens, or secrets. Say the target app needs an LLM connection and recommend connecting Builder/managed LLM for that app; keep bring-your-own provider keys as a secondary option only if the user asks.
 - If the user asks to create, build, make, scaffold, or generate an "agent" from Dispatch chat or by tagging @agent-native in Slack, email, or Telegram, first classify the ask. If it is a simple Dispatch-native behavior like a reminder, digest, monitor, routing rule, saved instruction, or recurring workflow, create or update the recurring job/resource/destination in Dispatch. If it is a robust unique product or teammate that needs its own UI, data model, actions, integrations, or domain workflow, treat it as a new workspace app and call start-workspace-app-creation.