@mastra/mcp-docs-server 0.13.4 → 0.13.5

package/.docs/raw/workflows/control-flow.mdx

@@ -10,9 +10,9 @@ When you build a workflow, you typically break down operations into smaller task
 - If the schemas match, the `outputSchema` from each step is automatically passed to the `inputSchema` of the next step.
 - If the schemas don't match, use [Input data mapping](./input-data-mapping.mdx) to transform the `outputSchema` into the expected `inputSchema`.
 
-## Sequential
+## Chaining steps with `.then()`
 
-Chain steps to execute in sequence using `.then()`:
+Chain steps to execute sequentially using `.then()`:
 
 ```typescript {8-9} filename="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
 import { createWorkflow, createStep } from "@mastra/core/workflows";
@@ -27,7 +27,9 @@ export const testWorkflow = createWorkflow({...})
   .commit();
 ```
 
-## Parallel
+This does what you'd expect: it executes `step1`, then it executes `step2`.
+
+## Parallel steps with `.parallel()`:
 
 Execute steps in parallel using `.parallel()`:
 
@@ -37,17 +39,19 @@ import { z } from "zod";
 
 const step1 = createStep({...});
 const step2 = createStep({...});
+const step3 = createStep({...});
 
 export const testWorkflow = createWorkflow({...})
   .parallel([step1, step2])
+  .then(step3)
   .commit();
 ```
 
-This executes all steps in the array concurrently, then continues to the next step after all parallel steps complete.
+This executes `step1` and `step2` concurrently, then continues to `step3` after both complete.
 
 > See [Parallel Execution with Steps](/examples/workflows/parallel-steps) for more information.
 
-## Branch
+## Conditional branching (`.branch()`)
 
 Create conditional branches using `.branch()`:
 
@@ -60,8 +64,8 @@ const greaterThanStep = createStep({...});
 
 export const testWorkflow = createWorkflow({...})
   .branch([
-    [async ({ inputData: { some_value } }) => some_value <= 9, lessThanStep],
-    [async ({ inputData: { some_value } }) => some_value >= 10, greaterThanStep]
+    [async ({ inputData: { value } }) => (value < 9), lessThanStep],
+    [async ({ inputData: { value } }) => (value >= 9), greaterThanStep]
   ])
   .commit();
 ```
@@ -70,17 +74,13 @@ Branch conditions are evaluated sequentially, but steps with matching conditions
 
 > See [Workflow with Conditional Branching](/examples/workflows/conditional-branching) for more information.
 
-## Loops
+## Looping commands
 
 Workflows support two types of loops. When looping a step, or any step-compatible construct like a nested workflow, the initial `inputData` is sourced from the output of the previous step.
 
-To ensure compatibility, the loop’s initial input must either:
-
-- Match the shape of the previous step’s output, or
-- Be explicitly transformed using the `map` function.
+To ensure compatibility, the loop’s initial input must either match the shape of the previous step’s output, or be explicitly transformed using the `map` function.
 
-
-### Dowhile
+### `.dowhile()`
 
 Executes a step repeatedly while a condition is true.
 
@@ -95,7 +95,7 @@ export const testWorkflow = createWorkflow({...})
   .commit();
 ```
 
-### Dountil
+### `.dountil()`
 
 Executes a step repeatedly until a condition becomes true.
 
@@ -110,8 +110,7 @@ export const testWorkflow = createWorkflow({...})
   .commit();
 ```
 
-
-### Foreach
+### `.foreach()`
 
 Sequentially executes the same step for each item from the `inputSchema`.
 
@@ -126,7 +125,7 @@ export const testWorkflow = createWorkflow({...})
   .commit();
 ```
 
-### Early exit
+### Early exit with `.bail()`
 
 You can bail out of a workflow execution successfully by calling `bail()` in a step. This returns whatever payload is passed to the `bail()` function as the result of the workflow.
 
@@ -167,6 +166,7 @@ export const testWorkflow = createWorkflow({...})
   .then(step1)
   .commit();
 ```
+
 #### Example Run Instance
 
 The following example demonstrates how to start a run with multiple inputs. Each input will pass through the `mapStep` sequentially.
@@ -202,44 +202,44 @@ export const testWorkflow = createWorkflow({...})
   .commit();
 ```
 
-## Parallel Workflows
+## Using a workflow as a step
 
-Workflows themselves can also be executed in parallel.
+For greater composability, you can re-use a workflow as a step in another workflow.
 
-```typescript {4-5,8} filename="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
+In the example below, `nestedWorkflow` is used as a step within `testWorkflow`. The `testWorkflow` uses `step1` while the `nestedWorkflow` composes `step2` and `step3`:
+
+```typescript {4,7} filename="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
 import { createWorkflow, createStep } from "@mastra/core/workflows";
 import { z } from "zod";
 
-const workflow1 = createWorkflow({...});
-const workflow2 = createWorkflow({...});
+export const nestedWorkflow = createWorkflow({...})
 
 export const testWorkflow = createWorkflow({...})
-  .parallel([workflow1, workflow2])
+  .then(nestedWorkflow)
   .commit();
 ```
 
-Parallel steps receive previous step results as input. Their outputs are passed into the next step input as an object where the key is the step `id` and the value is the step `output`.
-
-## Nested Workflows
+When using `.branch()` or `.parallel()` to build more complex control flows, executing more than one step requires wrapping those steps in a nested workflow, along with a clear definition of how they should be executed.
 
-In the example below, `nestedWorkflow` is used as a step within `testWorkflow`. The `testWorkflow` uses `step1` whilst the `nestedWorkflow` composes `step2` and `step3`
+## Running nested workflows in parallel
 
+Workflows themselves can also be executed in parallel.
 
-```typescript {4,7} filename="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
+```typescript {4-5,8} filename="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
 import { createWorkflow, createStep } from "@mastra/core/workflows";
 import { z } from "zod";
 
-export const nestedWorkflow = createWorkflow({...})
+const workflow1 = createWorkflow({...});
+const workflow2 = createWorkflow({...});
 
 export const testWorkflow = createWorkflow({...})
-  .then(nestedWorkflow)
+  .parallel([workflow1, workflow2])
   .commit();
 ```
 
-When using `.branch()` or `.parallel()` to build more complex control flows, executing more than one step requires wrapping those steps in a nested workflow, along with a clear definition of how they should be executed.
-
+Parallel steps receive previous step results as input. Their outputs are passed into the next step input as an object where the key is the step `id` and the value is the step `output`.
 
-## Cloned Workflows
+## Cloning workflows
 
 In the example below, `clonedWorkflow` is a clone of `workflow1` and is used as a step within `testWorkflow`. The `clonedWorkflow` is run sequentially after `step1`.
 

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

@@ -176,7 +176,7 @@ console.log(JSON.stringify(result, null, 2));
 
 To trigger this workflow, run the following:
 
-```bash
+```bash copy
 npx tsx src/test-workflow.ts
 ```
 

package/.docs/raw/workflows/pausing-execution.mdx

@@ -5,56 +5,93 @@ description: "Pausing execution in Mastra workflows allows you to pause executio
 
 # Sleep & Events
 
-Pausing execution in Mastra workflows allows you to pause execution while waiting for external input or resources via `sleep()`, `sleepUntil()` and `waitForEvent()`.
+Mastra lets you pause workflow execution when waiting for external input or timing conditions. This can be useful for things like polling, delayed retries, or waiting on user actions.
 
-This sets the workflow status to `waiting`.
+You can pause execution using:
 
-## sleep()
+- `sleep()`: Pause for a set number of milliseconds
+- `sleepUntil()`: Pause until a specific timestamp
+- `waitForEvent()`: Pause until an external event is received
+- `sendEvent()`: Send an event to resume a waiting workflow
 
-`sleep()` pauses execution for a specified number of milliseconds.
+When using any of these methods, the workflow status is set to `waiting` until execution resumes.
 
-```typescript
-workflow
-    .then(step1)
-    .sleep(1000)
-    .then(step2)
-    .commit();
+## sleep
+
+The `sleep()` method pauses execution between steps for a specified number of milliseconds.
+
+```typescript {9} filename="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
+import { createWorkflow, createStep } from "@mastra/core/workflows";
+import { z } from "zod";
+
+const step1 = createStep({...});
+const step2 = createStep({...});
+
+export const testWorkflow = createWorkflow({...})
+  .then(step1)
+  .sleep(1000)
+  .then(step2)
+  .commit();
 ```
 
-## sleepUntil()
+## sleepUntil
 
-`sleepUntil()` pauses execution until a specified date.
+The `sleepUntil()` method pauses execution between steps until a specified date.
 
-```typescript
-workflow
-    .then(step1)
-    .sleepUntil(new Date(Date.now() + 1000))
-    .then(step2)
-    .commit();
+```typescript {9} filename="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
+import { createWorkflow, createStep } from "@mastra/core/workflows";
+import { z } from "zod";
+
+const step1 = createStep({...});
+const step2 = createStep({...});
+
+export const testWorkflow = createWorkflow({...})
+  .then(step1)
+  .sleepUntil(new Date(Date.now() + 5000))
+  .then(step2)
+  .commit();
 ```
 
-## waitForEvent()
+> `Date.now()` is evaluated when the workflow starts, not at the moment the `sleepUntil()` method is called.
 
-`waitForEvent()` pauses execution until an event is received. Events can be sent to the workflow using `run.sendEvent()`. The event name and the step to resume after the event is received are provided as arguments to `waitForEvent()`.
+## waitForEvent
 
-`.sendEvent()` takes as arguments the event name and the event data. The event data is optional and can be any JSON-serializable value.
+The `waitForEvent()` method pauses execution until a specific event is received. Use `run.sendEvent()` to send the event. You must provide both the event name and the step to resume.
 
-```typescript
-workflow
-    .then(step1)
-    .waitForEvent('my-event-name', step2)
-    .then(step3)
-    .commit();
+```typescript {10} filename="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
+import { createWorkflow, createStep } from "@mastra/core/workflows";
+import { z } from "zod";
 
-const run = await workflow.createRunAsync()
-run.start({})
+const step1 = createStep({...});
+const step2 = createStep({...});
+const step3 = createStep({...});
+
+export const testWorkflow = createWorkflow({...})
+  .then(step1)
+  .waitForEvent("my-event-name", step2)
+  .then(step3)
+  .commit();
+```
+## sendEvent
+
+The `.sendEvent()` method sends an event to the workflow. It accepts the event name and optional event data, which can be any JSON-serializable value.
+
+```typescript {5,12,15} filename="src/test-workflow.ts" showLineNumbers copy
+import { mastra } from "./mastra";
+
+const run = await mastra.getWorkflow("testWorkflow").createRunAsync();
+
+const result = run.start({
+  inputData: {
+    value: "hello"
+  }
+});
 
 setTimeout(() => {
-    run.sendEvent('my-event-name', {
-        data1: 'hello',
-        data2: {
-            anyData: 12
-        }
-    })
-}, 2e3)
-```
+  run.sendEvent("my-event-name", { value: "from event" });
+}, 3000);
+
+console.log(JSON.stringify(await result, null, 2));
+```
+
+> In this example, avoid using `await run.start()` directly, it would block sending the event before the workflow reaches its waiting state.

package/LICENSE.md

@@ -1,46 +1,15 @@
-# Elastic License 2.0 (ELv2)
+# Apache License 2.0
 
-Copyright (c) 2025 Mastra AI, Inc.
+Copyright (c) 2025 Kepler Software, Inc.
 
-**Acceptance**
-By using the software, you agree to all of the terms and conditions below.
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
 
-**Copyright License**
-The licensor grants you a non-exclusive, royalty-free, worldwide, non-sublicensable, non-transferable license to use, copy, distribute, make available, and prepare derivative works of the software, in each case subject to the limitations and conditions below
+    http://www.apache.org/licenses/LICENSE-2.0
 
-**Limitations**
-You may not provide the software to third parties as a hosted or managed service, where the service provides users with access to any substantial set of the features or functionality of the software.
-
-You may not move, change, disable, or circumvent the license key functionality in the software, and you may not remove or obscure any functionality in the software that is protected by the license key.
-
-You may not alter, remove, or obscure any licensing, copyright, or other notices of the licensor in the software. Any use of the licensor’s trademarks is subject to applicable law.
-
-**Patents**
-The licensor grants you a license, under any patent claims the licensor can license, or becomes able to license, to make, have made, use, sell, offer for sale, import and have imported the software, in each case subject to the limitations and conditions in this license. This license does not cover any patent claims that you cause to be infringed by modifications or additions to the software. If you or your company make any written claim that the software infringes or contributes to infringement of any patent, your patent license for the software granted under these terms ends immediately. If your company makes such a claim, your patent license ends immediately for work on behalf of your company.
-
-**Notices**
-You must ensure that anyone who gets a copy of any part of the software from you also gets a copy of these terms.
-
-If you modify the software, you must include in any modified copies of the software prominent notices stating that you have modified the software.
-
-**No Other Rights**
-These terms do not imply any licenses other than those expressly granted in these terms.
-
-**Termination**
-If you use the software in violation of these terms, such use is not licensed, and your licenses will automatically terminate. If the licensor provides you with a notice of your violation, and you cease all violation of this license no later than 30 days after you receive that notice, your licenses will be reinstated retroactively. However, if you violate these terms after such reinstatement, any additional violation of these terms will cause your licenses to terminate automatically and permanently.
-
-**No Liability**
-As far as the law allows, the software comes as is, without any warranty or condition, and the licensor will not be liable to you for any damages arising out of these terms or the use or nature of the software, under any kind of legal claim.
-
-**Definitions**
-The _licensor_ is the entity offering these terms, and the _software_ is the software the licensor makes available under these terms, including any portion of it.
-
-_you_ refers to the individual or entity agreeing to these terms.
-
-_your company_ is any legal entity, sole proprietorship, or other kind of organization that you work for, plus all organizations that have control over, are under the control of, or are under common control with that organization. _control_ means ownership of substantially all the assets of an entity, or the power to direct its management and policies by vote, contract, or otherwise. Control can be direct or indirect.
-
-_your licenses_ are all the licenses granted to you for the software under these terms.
-
-_use_ means anything you do with the software requiring one of your licenses.
-
-_trademark_ means trademarks, service marks, and similar rights.
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mastra/mcp-docs-server",
-  "version": "0.13.4",
+  "version": "0.13.5",
   "description": "MCP server for accessing Mastra.ai documentation, changelogs, and news.",
   "type": "module",
   "main": "dist/index.js",
@@ -22,7 +22,7 @@
   },
   "keywords": [],
   "author": "",
-  "license": "Elastic-2.0",
+  "license": "Apache-2.0",
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.13.0",
     "date-fns": "^4.1.0",
@@ -32,7 +32,7 @@
     "uuid": "^11.1.0",
     "zod": "^3.25.67",
     "zod-to-json-schema": "^3.24.5",
-    "@mastra/mcp": "^0.10.5"
+    "@mastra/mcp": "^0.10.6"
   },
   "devDependencies": {
     "@hono/node-server": "^1.14.4",
@@ -42,13 +42,13 @@
     "@wong2/mcp-cli": "^1.10.0",
     "cross-env": "^7.0.3",
     "eslint": "^9.29.0",
-    "hono": "^4.8.3",
+    "hono": "^4.8.4",
     "tsup": "^8.5.0",
     "tsx": "^4.19.4",
     "typescript": "^5.8.3",
     "vitest": "^3.2.4",
-    "@internal/lint": "0.0.17",
-    "@mastra/core": "0.10.10"
+    "@internal/lint": "0.0.18",
+    "@mastra/core": "0.10.11"
   },
   "peerDependencies": {
     "@mastra/core": "^0.10.0-alpha.0"

package/.docs/raw/deployment/server.mdx

@@ -1,116 +0,0 @@
----
-title: "Creating A Mastra Server"
-description: "Configure and customize the Mastra server with middleware and other options"
----
-
-# Creating A Mastra Server
-
-While developing or when you deploy a Mastra application, it runs as an HTTP server that exposes your agents, workflows, and other functionality as API endpoints. This page explains how to configure and customize the server behavior.
-
-## Server Architecture
-
-Mastra uses [Hono](https://hono.dev) as its underlying HTTP server framework. When you build a Mastra application using `mastra build`, it generates a Hono-based HTTP server in the `.mastra` directory.
-
-The server provides:
-
-- API endpoints for all registered agents
-- API endpoints for all registered workflows
-- Custom api route supports
-- Custom middleware support
-- Configuration of timeout
-- Configuration of port
-- Configuration of body limit
-
-See the [Middleware](/docs/deployment/middleware) and
-[Custom API Routes](/docs/deployment/custom-api-routes) pages for details on
-adding additional server behaviour.
-
-## Server configuration
-
-You can configure server `port` and `timeout` in the Mastra instance.
-
-```typescript copy showLineNumbers
-import { Mastra } from "@mastra/core";
-
-export const mastra = new Mastra({
-  server: {
-    port: 3000, // Defaults to 4111
-    timeout: 10000, // Defaults to 30000 (30s)
-  },
-});
-```
-
-The `method` option can be one of `"GET"`, `"POST"`, `"PUT"`,
-`"DELETE"` or `"ALL"`. Using `"ALL"` will cause the handler to be
-invoked for any HTTP method that matches the path.
-
-## Custom CORS Config
-
-Mastra allows you to configure CORS (Cross-Origin Resource Sharing) settings for your server.
-
-```typescript copy showLineNumbers
-import { Mastra } from "@mastra/core";
-
-export const mastra = new Mastra({
-  server: {
-    cors: {
-      origin: ["https://example.com"], // Allow specific origins or '*' for all
-      allowMethods: ["GET", "POST", "PUT", "DELETE", "OPTIONS"],
-      allowHeaders: ["Content-Type", "Authorization"],
-      credentials: false,
-    },
-  },
-});
-```
-
-## Deployment
-
-Since Mastra builds to a standard Node.js server, you can deploy to any platform that runs Node.js applications:
-
-- Cloud VMs (AWS EC2, DigitalOcean Droplets, GCP Compute Engine)
-- Container platforms (Docker, Kubernetes)
-- Platform as a Service (Heroku, Railway)
-- Self-hosted servers
-
-### Building
-
-Build the application:
-
-```bash copy
-# Build from current directory
-mastra build
-
-# Or specify a directory
-mastra build --dir ./my-project
-```
-
-The build process:
-
-1. Locates entry file (`src/mastra/index.ts` or `src/mastra/index.js`)
-2. Creates `.mastra` output directory
-3. Bundles code using Rollup with tree shaking and source maps
-4. Generates [Hono](https://hono.dev) HTTP server
-
-See [`mastra build`](/reference/cli/build) for all options.
-
-### Running the Server
-
-Start the HTTP server:
-
-```bash copy
-node .mastra/output/index.mjs
-```
-
-### Enable Telemetry for build output
-
-Load instrumentation for the build output like so:
-
-```bash copy
-node --import=./.mastra/output/instrumentation.mjs  .mastra/output/index.mjs
-```
-
-## Serverless Deployment
-
-Mastra also supports serverless deployment on Cloudflare Workers, Vercel, and Netlify.
-
-See our [Serverless Deployment](/docs/deployment/deployment) guide for setup instructions.