@mastra/mcp-docs-server 0.13.2-alpha.0 → 0.13.2-alpha.2

package/.docs/raw/workflows/suspend-and-resume.mdx

@@ -27,29 +27,26 @@ When running a workflow, its `status` can be one of the following:
 
 ## Suspend
 
-When the state is `suspended`, you can identify any and all steps that have been suspended by looking at the `suspended` array of the workflow.
+When the state is `suspended`, you can identify any and all steps that have been suspended by looking at the `suspended` array of the workflow result output.
 
 ```typescript {17} filename="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
 const step1 = createStep({
   id: "step-1",
   description: "Test suspend",
   inputSchema: z.object({
-    input: z.array(z.string())
-  }),
-  resumeSchema: z.object({
-    city: z.string()
+    input: z.string()
   }),
   outputSchema: z.object({
     output: z.string()
   }),
+  suspendSchema: z.object({}),
+  resumeSchema: z.object({
+    city: z.string()
+  }),
   execute: async ({ resumeData, suspend }) => {
-    const { city } = resumeData ?? {};
-
-    if (!city) {
+    if (!(resumeData ?? {}).city) {
       await suspend({});
-      return {
-        outcome: ""
-      };
+      return { output: "" };
     }
 
     return {
@@ -65,17 +62,69 @@ export const testWorkflow = createWorkflow({})
 
 > See [Define Suspendable workflow](/examples/workflows/human-in-the-loop#define-suspendable-workflow) for more information.
 
+### Identifying Suspended steps
+
+To resume a suspended workflow, inspect the `suspended` array in the result to determine which step needs input:
+
+```typescript {15} filename="src/test-workflow.ts" showLineNumbers copy
+import { mastra } from "./mastra";
+
+const run = await mastra.getWorkflow("testWorkflow").createRunAsync();
+
+const result = await run.start({
+  inputData: {
+    city: "London"
+  }
+});
+
+console.log(JSON.stringify(result, null, 2));
+
+if (result.status === "suspended") {
+  const resumedResult = await run.resume({
+    step: result.suspended[0],
+    resumeData: {
+      city: "Berlin"
+    }
+  });
+}
+
+```
+
+In this case, the logic resumes the first step listed in the `suspended` array. A `step` can also be defined using it's `id`, for example: 'step-1'.
+
+```json
+{
+  "status": "suspended",
+  "steps": {
+    // ...
+    "step-1": {
+      // ...
+      "status": "suspended",
+    }
+  },
+  "suspended": [
+    [
+      "step-1"
+    ]
+  ]
+}
+```
+
+> See [Run Workflow Results](/workflows/overview#run-workflow-results) for more details.
+
 ## Resume
 
 A workflow can be resumed by calling `resume` and providing the required `resumeData`.
 
-```typescript {6,12,13,14} filename="src/test-workflow.ts" showLineNumbers copy
+```typescript {16-18} filename="src/test-workflow.ts" showLineNumbers copy
 import { mastra } from "./mastra";
 
-const run = mastra.getWorkflow("testWorkflow").createRun();
+const run = await mastra.getWorkflow("testWorkflow").createRunAsync();
 
 const result = await run.start({
-  inputData: { suggestions: ["London", "Paris", "New York"] }
+   inputData: {
+    city: "London"
+  }
 });
 
 console.log(JSON.stringify(result, null, 2));
@@ -83,19 +132,15 @@ console.log(JSON.stringify(result, null, 2));
 if (result.status === "suspended") {
   const resumedResult = await run.resume({
     step: 'step-1',
-    resumeData: { city: "New York" }
+    resumeData: {
+      city: "Berlin"
+    }
   });
 
   console.log(JSON.stringify(resumedResult, null, 2));
 }
 ```
 
-To execute this run from your terminal:
-
-```bash copy
-npx tsx src/test-workflow.ts
-```
-
 ### Nested Workflow
 
 To resume a suspended nested workflow pass the workflow instance to the `step` parameter of the `resume` function.
@@ -128,7 +173,7 @@ const dowhileWorkflow = createWorkflow({
   )
   .commit();
 
-const run = dowhileWorkflow.createRun();
+const run = await dowhileWorkflow.createRunAsync();
 const result = await run.start({ inputData: { value: 0 } });
 
 if (result.status === "suspended") {
@@ -151,7 +196,7 @@ import { RuntimeContext } from "@mastra/core/di";
 import { mastra } from "./mastra";
 
 const runtimeContext = new RuntimeContext();
-const run = mastra.getWorkflow("testWorkflow").createRun();
+const run = await mastra.getWorkflow("testWorkflow").createRunAsync();
 
 const result = await run.start({
   inputData: { suggestions: ["London", "Paris", "New York"] },

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

@@ -238,7 +238,7 @@ export const cityCoordinatesTool = createTool({
 
     const workflow = mastra?.getWorkflow("cityStringWorkflow");
 
-    const run = workflow?.createRun();
+    const run = await workflow?.createRunAsync();
 
     const { result } = await run?.start({
       inputData: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mastra/mcp-docs-server",
-  "version": "0.13.2-alpha.0",
+  "version": "0.13.2-alpha.2",
   "description": "MCP server for accessing Mastra.ai documentation, changelogs, and news.",
   "type": "module",
   "main": "dist/index.js",
@@ -24,15 +24,15 @@
   "author": "",
   "license": "Elastic-2.0",
   "dependencies": {
-    "@modelcontextprotocol/sdk": "^1.12.1",
+    "@modelcontextprotocol/sdk": "^1.13.0",
     "date-fns": "^4.1.0",
     "exit-hook": "^4.0.0",
     "jsdom": "^26.1.0",
     "turndown": "^7.2.0",
     "uuid": "^11.1.0",
-    "zod": "^3.25.57",
+    "zod": "^3.25.67",
     "zod-to-json-schema": "^3.24.5",
-    "@mastra/mcp": "^0.10.5-alpha.0"
+    "@mastra/mcp": "^0.10.5-alpha.2"
   },
   "devDependencies": {
     "@hono/node-server": "^1.14.4",
@@ -41,14 +41,14 @@
     "@types/turndown": "^5.0.5",
     "@wong2/mcp-cli": "^1.10.0",
     "cross-env": "^7.0.3",
-    "eslint": "^9.28.0",
+    "eslint": "^9.29.0",
     "hono": "^4.7.11",
     "tsup": "^8.5.0",
     "tsx": "^4.19.4",
     "typescript": "^5.8.3",
     "vitest": "^3.2.3",
     "@internal/lint": "0.0.13",
-    "@mastra/core": "0.10.7-alpha.1"
+    "@mastra/core": "0.10.7-alpha.4"
   },
   "peerDependencies": {
     "@mastra/core": "^0.10.0-alpha.0"

package/.docs/raw/mastra-cloud/deploying.mdx

@@ -1,142 +0,0 @@
----
-title: Deploying to Mastra Cloud
-description: GitHub-based deployment process for Mastra applications
----
-
-# Deploying to Mastra Cloud
-
-> **Beta Notice**
-> Mastra Cloud is currently in **public beta**.
-
-This page describes the deployment process for Mastra applications to Mastra Cloud using GitHub integration.
-
-## Prerequisites
-
-- A GitHub account
-- A GitHub repository containing a Mastra application
-- Access to Mastra Cloud
-
-## Deployment Process
-
-Mastra Cloud uses a Git-based deployment workflow similar to platforms like Vercel and Netlify:
-
-1. **Import GitHub Repository**
-
-   - From the Projects dashboard, click "Add new"
-   - Select the repository containing your Mastra application
-   - Click "Import" next to the desired repository
-
-2. **Configure Deployment Settings**
-
-   - Set the project name (defaults to repository name)
-   - Select branch to deploy (typically `main`)
-   - Configure the Mastra directory path (defaults to `src/mastra`)
-   - Add necessary environment variables (like API keys)
-
-3. **Deploy from Git**
-   - After initial configuration, deployments are triggered by pushes to the selected branch
-   - Mastra Cloud automatically builds and deploys your application
-   - Each deployment creates an atomic snapshot of your agents and workflows
-
-## Automatic Deployments
-
-Mastra Cloud follows a Git-driven workflow:
-
-1. Make changes to your Mastra application locally
-2. Commit changes to the `main` branch
-3. Push to GitHub
-4. Mastra Cloud automatically detects the push and creates a new deployment
-5. Once the build completes, your application is live
-
-## Deployment Domains
-
-Each project receives two URLs:
-
-1. **Project-specific domain**: `https://[project-name].mastra.cloud`
-
-   - Example: `https://gray-acoustic-helicopter.mastra.cloud`
-
-2. **Deployment-specific domain**: `https://[deployment-id].mastra.cloud`
-   - Example: `https://young-loud-caravan-6156280f-ad56-4ec8-9701-6bb5271fd73d.mastra.cloud`
-
-These URLs provide direct access to your deployed agents and workflows.
-
-## Viewing Deployments
-
-![Deployments List](../../../../../public/image/cloud-agents.png)
-
-The deployments section in the dashboard shows:
-
-- **Title**: Deployment identifier (based on commit hash)
-- **Status**: Current state (success or archived)
-- **Branch**: The branch used (typically `main`)
-- **Commit**: The Git commit hash
-- **Updated At**: Timestamp of the deployment
-
-Each deployment represents an atomic snapshot of your Mastra application at a specific point in time.
-
-## Interacting with Agents
-
-![Agent Interface](../../../../../public/image/cloud-agent.png)
-
-After deployment, interact with your agents:
-
-1. Navigate to your project in the dashboard
-2. Go to the Agents section
-3. Select an agent to view its details and interface
-4. Use the Chat tab to communicate with your agent
-5. View the agent's configuration in the right panel:
-   - Model information (e.g., OpenAI)
-   - Available tools (e.g., getWeather)
-   - Complete system prompt
-6. Use suggested prompts (like "What capabilities do you have?") or enter custom messages
-
-The interface shows the agent's branch (typically "main") and indicates whether conversation memory is enabled.
-
-## Monitoring Logs
-
-The Logs section provides detailed information about your application:
-
-- **Time**: When the log entry was created
-- **Level**: Log level (info, debug)
-- **Hostname**: Server identification
-- **Message**: Detailed log information, including:
-  - API initialization
-  - Storage connections
-  - Agent and workflow activity
-
-These logs help debug and monitor your application's behavior in the production environment.
-
-## Workflows
-
-![Workflows Interface](../../../../../public/image/cloud-workflows.png)
-
-The Workflows section allows you to view and interact with your deployed workflows:
-
-1. View all workflows in your project
-2. Examine workflow structure and steps
-3. Access execution history and performance data
-
-## Database Usage
-
-Mastra Cloud tracks database utilization metrics:
-
-- Number of reads
-- Number of writes
-- Storage used (MB)
-
-These metrics appear in the project overview, helping you monitor resource consumption.
-
-## Deployment Configuration
-
-Configure your deployment through the dashboard:
-
-1. Navigate to your project settings
-2. Set environment variables (like `OPENAI_API_KEY`)
-3. Configure project-specific settings
-
-Changes to configuration require a new deployment to take effect.
-
-## Next Steps
-
-After deployment, [trace and monitor execution](./observability.mdx) using the observability tools.