@mastra/mcp-docs-server 0.13.32 → 0.13.34-alpha.0

package/.docs/raw/workflows/agents-and-tools.mdx

@@ -0,0 +1,131 @@
+---
+title: "Agents and Tools | Workflows | Mastra Docs"
+description: "Learn how to call agents and tools from workflow steps and choose between execute functions and step composition."
+---
+
+# Agents and Tools
+
+Workflow steps can call agents to leverage LLM reasoning or call tools for type-safe logic. You can either invoke them from within a step's `execute` function or compose them directly as steps using `createStep()`.
+
+## Using agents in workflows
+
+Use agents in workflow steps when you need reasoning, language generation, or other LLM-based tasks. Call from a step's `execute` function for more control over the agent call (e.g., track conversation history or return structured output). Compose agents as steps when you don't need to modify how the agent is invoked.
+
+### Calling agents
+
+Call agents inside a step's `execute` function using `.generate()` or `.stream()`. This lets you modify the agent call and handle the response before passing it to the next step.
+
+```typescript {7-12} filename="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
+const step1 = createStep({
+  // ...
+  execute: async ({ inputData, mastra }) => {
+    const { message } = inputData;
+
+    const testAgent = mastra.getAgent("testAgent");
+    const response = await testAgent.generate(`Convert this message into bullet points: ${message}`, {
+      memory: {
+        thread: "user-123",
+        resource: "test-123"
+      }
+    });
+
+    return {
+      list: response.text
+    };
+  }
+});
+```
+
+> See [Calling Agents](../../examples/agents/calling-agents.mdx) for more examples.
+
+### Agents as steps
+
+Compose an agent as a step using `createStep()` when you don't need to modify the agent call. Use `.map()` to transform the previous step's output into a `prompt` the agent can use.
+
+![Agent as step](/image/workflows/workflows-agent-tools-agent-step.jpg)
+
+```typescript {1,3,8-13} filename="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
+import { testAgent } from "../agents/test-agent";
+
+const step1 = createStep(testAgent);
+
+export const testWorkflow = createWorkflow({
+  // ...
+})
+  .map(async ({ inputData }) => {
+    const { message } = inputData;
+    return {
+      prompt: `Convert this message into bullet points: ${message}`
+    };
+  })
+  .then(step1)
+  .then(step2)
+  .commit();
+```
+
+> See [Input Data Mapping](./input-data-mapping.mdx) for more information.
+
+## Using tools in workflows
+
+Use tools in workflow steps to leverage existing tool logic. Call from a step's `execute` function when you need to prepare context or process responses. Compose tools as steps when you don't need to modify how the tool is used.
+
+### Calling tools
+
+Call tools inside a step's `execute` function using `.execute()`. This gives you more control over the tool's input context, or process its response before passing it to the next step.
+
+```typescript {8-13,16} filename="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
+import { testTool } from "../tools/test-tool";
+
+const step2 = createStep({
+  // ...
+  execute: async ({ inputData, runtimeContext }) => {
+    const { formatted } = inputData;
+
+    const response = await testTool.execute({
+      context: {
+        text: formatted
+      },
+      runtimeContext
+    });
+
+    return {
+      emphasized: response.emphasized
+    };
+  }
+});
+```
+
+> See [Calling Tools](../../examples/tools/calling-tools.mdx) for more examples.
+
+### Tools as steps
+
+Compose a tool as a step using `createStep()` when the previous step's output matches the tool's input context. You can use `.map()` to transform the previous step's output if they don't.
+
+![Tool as step](/image/workflows/workflows-agent-tools-tool-step.jpg)
+
+```typescript {1,3,9-14} filename="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
+import { testTool } from "../tools/test-tool";
+
+const step2 = createStep(testTool);
+
+export const testWorkflow = createWorkflow({
+  // ...
+})
+  .then(step1)
+  .map(async ({ inputData }) => {
+    const { formatted } = inputData;
+    return {
+      text: formatted
+    };
+  })
+  .then(step2)
+  .commit();
+```
+
+> See [Input Data Mapping](./input-data-mapping.mdx) for more information.
+
+## Related
+
+- [Using Agents](../agents/overview.mdx)
+- [Using Tools](../tools-mcp/overview.mdx)
+

package/.docs/raw/workflows/overview.mdx

@@ -31,7 +31,9 @@ Mastra workflows operate using these principles:
 
 Steps are the building blocks of workflows. Create a step using `createStep()` with `inputSchema` and `outputSchema` to define the data it accepts and returns.
 
-```typescript {6,9,14} filename="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
+The `execute` function defines what the step does. Use it to call functions in your codebase, external APIs, agents, or tools.
+
+```typescript {6,9,15} filename="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
 import { createStep } from "@mastra/core/workflows";
 
 const step1 = createStep({
@@ -44,6 +46,7 @@ const step1 = createStep({
   }),
   execute: async ({ inputData }) => {
     const { message } = inputData;
+
     return {
       formatted: message.toUpperCase()
     };
@@ -53,6 +56,10 @@ const step1 = createStep({
 
 > See the [Step Class](../../reference/workflows/step.mdx) for a full list of configuration options.
 
+### Using agents and tools
+
+Workflow steps can also call registered agents or import and execute tools directly, visit the [Agents and Tools](./agents-and-tools.mdx) page for more information.
+
 ## Creating a workflow
 
 Create a workflow using `createWorkflow()` with `inputSchema` and `outputSchema` to define the data it accepts and returns. Add steps using `.then()` and complete the workflow with `.commit()`.
@@ -81,13 +88,11 @@ export const testWorkflow = createWorkflow({
 
 ### Understanding control flow
 
-Workflows can be composed using a number of different methods. The method you choose determines how each step's schema should be structured.
+Workflows can be composed using a number of different methods. The method you choose determines how each step's schema should be structured. Visit the [Control Flow](./control-flow.mdx) page for more information.
 
-> See [Control Flow](./control-flow.mdx) for more information.
+#### Composing workflow steps
 
-#### Composing steps
-
-When using `.then()`, steps run sequentially. The `inputSchema` of each step must match the `outputSchema` of the step before it. The final step’s `outputSchema` doesn’t need to match the workflow’s `outputSchema`, which can be defined independently.
+When using `.then()`, steps run sequentially. Each step’s `inputSchema` must match the `outputSchema` of the previous step. The final step’s `outputSchema` should match the workflow’s `outputSchema` to ensure end-to-end type safety.
 
 ```typescript {4,7,14,17,24,27} filename="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
 const step1 = createStep({
@@ -116,7 +121,7 @@ export const testWorkflow = createWorkflow({
     message: z.string()
   }),
   outputSchema: z.object({
-    output: z.string()
+    emphasized: z.string()
   })
 })
   .then(step1)
@@ -200,23 +205,21 @@ The workflow output includes the full execution lifecycle, showing the input and
 {
   "status": "success",
   "steps": {
-    "input": {
-      "message": "Hello world"
-    },
+    // ...
     "step-1": {
+      "status": "success",
       "payload": {
         "message": "Hello world"
       },
-      "status": "success",
       "output": {
         "formatted": "HELLO WORLD"
       },
     },
     "step-2": {
+      "status": "success",
       "payload": {
         "formatted": "HELLO WORLD"
       },
-      "status": "success",
       "output": {
         "emphasized": "HELLO WORLD!!!"
       },
@@ -260,7 +263,6 @@ const step1 = createStep({
 
 Use the Mastra [Playground](../server-db/local-dev-playground.mdx) to easily run workflows with different inputs, visualize the execution lifecycle, see the inputs and outputs for each step, and inspect each part of the workflow in more detail.
 
-
 ## Related
 
 For a closer look at workflows, see our [Workflow Guide](../../guides/guide/ai-recruiter.mdx), which walks through the core concepts with a practical example.

package/CHANGELOG.md

@@ -1,5 +1,26 @@
 # @mastra/mcp-docs-server
 
+## 0.13.34-alpha.0
+
+### Patch Changes
+
+- Updated dependencies [[`2b031e2`](https://github.com/mastra-ai/mastra/commit/2b031e25ca10cd3e4d63e6a27f909cba26d91405)]:
+  - @mastra/core@0.22.2-alpha.0
+
+## 0.13.33
+
+### Patch Changes
+
+- Updated dependencies []:
+  - @mastra/core@0.22.1
+
+## 0.13.33-alpha.0
+
+### Patch Changes
+
+- Updated dependencies []:
+  - @mastra/core@0.22.1-alpha.0
+
 ## 0.13.32
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mastra/mcp-docs-server",
-  "version": "0.13.32",
+  "version": "0.13.34-alpha.0",
   "description": "MCP server for accessing Mastra.ai documentation, changelogs, and news.",
   "type": "module",
   "main": "dist/index.js",
@@ -33,7 +33,7 @@
     "uuid": "^11.1.0",
     "zod": "^3.25.76",
     "zod-to-json-schema": "^3.24.6",
-    "@mastra/core": "0.22.0",
+    "@mastra/core": "0.22.2-alpha.0",
     "@mastra/mcp": "^0.14.0"
   },
   "devDependencies": {
@@ -49,8 +49,8 @@
     "tsx": "^4.19.4",
     "typescript": "^5.8.3",
     "vitest": "^3.2.4",
-    "@internal/lint": "0.0.51",
-    "@mastra/core": "0.22.0"
+    "@internal/lint": "0.0.52",
+    "@mastra/core": "0.22.2-alpha.0"
   },
   "homepage": "https://mastra.ai",
   "repository": {