@mastra/mcp-docs-server 0.13.37 → 0.13.38

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

@@ -1,5 +1,7 @@
 ---
-title: "Suspend & Resume Workflows (Legacy) | Human-in-the-Loop | Mastra Docs"
+title: "Suspend and Resume in Workflows (Legacy) | Workflows (Legacy) | Mastra Docs"
+sidebar_position: 9
+sidebar_label: "Suspend & Resume"
 description: "Suspend and resume in Mastra workflows allows you to pause execution while waiting for external input or resources."
 ---
 
@@ -392,13 +394,13 @@ await start({ triggerData: { requestId: "auto-123" } });
 
 For a deeper understanding of how suspend and resume works under the hood:
 
-- [Understanding Snapshots in Mastra Workflows](../../reference/legacyWorkflows/snapshots.mdx) - Learn about the snapshot mechanism that powers suspend and resume functionality
-- [Step Configuration Guide](./steps.mdx) - Learn more about configuring steps in your workflows
-- [Control Flow Guide](./control-flow.mdx) - Advanced workflow control patterns
-- [Event-Driven Workflows](../../reference/legacyWorkflows/events.mdx) - Detailed reference for event-based workflows
+- [Understanding Snapshots in Mastra Workflows](/reference/legacyWorkflows/snapshots) - Learn about the snapshot mechanism that powers suspend and resume functionality
+- [Step Configuration Guide](./steps) - Learn more about configuring steps in your workflows
+- [Control Flow Guide](./control-flow) - Advanced workflow control patterns
+- [Event-Driven Workflows](/reference/legacyWorkflows/events) - Detailed reference for event-based workflows
 
 ## Related Resources
 
-- See the [Suspend and Resume Example](../../examples/workflows_legacy/suspend-and-resume.mdx) for a complete working example
-- Check the [Step Class Reference](../../reference/legacyWorkflows/step-class.mdx) for suspend/resume API details
-- Review [Workflow Observability](../../reference/observability/otel-config.mdx) for monitoring suspended workflows
+- See the [Suspend and Resume Example](/examples/workflows_legacy/suspend-and-resume) for a complete working example
+- Check the [Step Class Reference](/reference/legacyWorkflows/step-class) for suspend/resume API details
+- Review [Workflow Observability](/docs/observability/otel-tracing) for monitoring suspended workflows

package/.docs/raw/workflows-legacy/variables.mdx

@@ -1,5 +1,7 @@
 ---
-title: "Data Mapping with Workflow (Legacy) Variables | Mastra Docs"
+title: "Data Mapping with Workflow Variables | Workflows (Legacy) | Mastra Docs"
+sidebar_position: 5
+sidebar_label: "Variables"
 description: "Learn how to use workflow variables to map data between steps and create dynamic data flows in your Mastra workflows."
 ---
 
@@ -22,7 +24,7 @@ In Mastra workflows, variables serve as a way to:
 
 You can map data between steps using the `variables` property when adding a step to your workflow:
 
-```typescript showLineNumbers filename="src/mastra/workflows/index.ts" copy
+```typescript showLineNumbers title="src/mastra/workflows/index.ts" copy
 import { LegacyStep, LegacyWorkflow } from "@mastra/core/workflows/legacy";
 
 const workflow = new LegacyWorkflow({
@@ -57,7 +59,7 @@ export const mastra = new Mastra({
 
 You can access nested properties using dot notation in the `path` field:
 
-```typescript showLineNumbers filename="src/mastra/workflows/index.ts" copy
+```typescript showLineNumbers title="src/mastra/workflows/index.ts" copy
 workflow
   .step(step1)
   .then(step2, {
@@ -73,7 +75,7 @@ workflow
 
 You can map an entire object by using `.` as the path:
 
-```typescript showLineNumbers filename="src/mastra/workflows/index.ts" copy
+```typescript showLineNumbers title="src/mastra/workflows/index.ts" copy
 workflow
   .step(step1, {
     variables: {
@@ -88,7 +90,7 @@ workflow
 
 Variables can also be passed to `while` and `until` loops. This is useful for passing data between iterations or from outside steps:
 
-```typescript showLineNumbers filename="src/mastra/workflows/loop-variables.ts" copy
+```typescript showLineNumbers title="src/mastra/workflows/loop-variables.ts" copy
 // Step that increments a counter
 const incrementStep = new LegacyStep({
   id: "increment",
@@ -142,7 +144,7 @@ When a workflow executes, Mastra resolves variables at runtime by:
 
 This example shows how to map data from the workflow trigger to a step:
 
-```typescript showLineNumbers filename="src/mastra/workflows/trigger-mapping.ts" copy
+```typescript showLineNumbers title="src/mastra/workflows/trigger-mapping.ts" copy
 import { Mastra } from "@mastra/core";
 import { LegacyStep, LegacyWorkflow } from "@mastra/core/workflows/legacy";
 import { z } from "zod";
@@ -187,7 +189,7 @@ export const mastra = new Mastra({
 
 This example demonstrates mapping data from one step to another:
 
-```typescript showLineNumbers filename="src/mastra/workflows/step-mapping.ts" copy
+```typescript showLineNumbers title="src/mastra/workflows/step-mapping.ts" copy
 import { Mastra } from "@mastra/core";
 import { LegacyStep, LegacyWorkflow } from "@mastra/core/workflows/legacy";
 import { z } from "zod";
@@ -251,7 +253,7 @@ export const mastra = new Mastra({
 
 Mastra provides type safety for variable mappings when using TypeScript:
 
-```typescript showLineNumbers filename="src/mastra/workflows/type-safe.ts" copy
+```typescript showLineNumbers title="src/mastra/workflows/type-safe.ts" copy
 import { Mastra } from "@mastra/core";
 import { LegacyStep, LegacyWorkflow } from "@mastra/core/workflows/legacy";
 import { z } from "zod";

package/CHANGELOG.md

@@ -1,5 +1,19 @@
 # @mastra/mcp-docs-server
 
+## 0.13.38
+
+### Patch Changes
+
+- Updated dependencies [[`d6cb18e`](https://github.com/mastra-ai/mastra/commit/d6cb18e189fd0ac95d4934cf0d6f2866876d1a2e), [`d0ecff7`](https://github.com/mastra-ai/mastra/commit/d0ecff793d5cd50408cd8d1d113f02e28d897a3d), [`e84a959`](https://github.com/mastra-ai/mastra/commit/e84a9592bfdec4f1c9fdf108c9d4ea4e2ee8f7e3)]:
+  - @mastra/core@0.23.3
+
+## 0.13.38-alpha.0
+
+### Patch Changes
+
+- Updated dependencies [[`d6cb18e`](https://github.com/mastra-ai/mastra/commit/d6cb18e189fd0ac95d4934cf0d6f2866876d1a2e), [`d0ecff7`](https://github.com/mastra-ai/mastra/commit/d0ecff793d5cd50408cd8d1d113f02e28d897a3d), [`e84a959`](https://github.com/mastra-ai/mastra/commit/e84a9592bfdec4f1c9fdf108c9d4ea4e2ee8f7e3)]:
+  - @mastra/core@0.23.3-alpha.0
+
 ## 0.13.37
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mastra/mcp-docs-server",
-  "version": "0.13.37",
+  "version": "0.13.38",
   "description": "MCP server for accessing Mastra.ai documentation, changelogs, and news.",
   "type": "module",
   "main": "dist/index.js",
@@ -33,8 +33,8 @@
     "uuid": "^11.1.0",
     "zod": "^3.25.76",
     "zod-to-json-schema": "^3.24.6",
-    "@mastra/core": "0.23.2",
-    "@mastra/mcp": "^0.14.1"
+    "@mastra/mcp": "^0.14.1",
+    "@mastra/core": "0.23.3"
   },
   "devDependencies": {
     "@hono/node-server": "^1.19.5",
@@ -49,8 +49,8 @@
     "tsx": "^4.19.4",
     "typescript": "^5.8.3",
     "vitest": "^3.2.4",
-    "@internal/lint": "0.0.56",
-    "@mastra/core": "0.23.2"
+    "@internal/lint": "0.0.57",
+    "@mastra/core": "0.23.3"
   },
   "homepage": "https://mastra.ai",
   "repository": {

package/.docs/raw/memory/storage/memory-with-mongodb.mdx

@@ -1,148 +0,0 @@
----
-title: "Example: Memory with MongoDB | Memory | Mastra Docs"
-description: Example for how to use Mastra's memory system with MongoDB storage and vector capabilities.
----
-
-# Memory with MongoDB
-
-This example demonstrates how to use Mastra's memory system with MongoDB as the storage backend.
-
-## Prerequisites
-
-This example uses the `openai` model and requires a MongoDB database. Make sure to add the following to your `.env` file:
-
-```bash filename=".env" copy
-OPENAI_API_KEY=<your-api-key>
-MONGODB_URI=<your-connection-string>
-MONGODB_DB_NAME=<your-db-name>
-```
-
-And install the following package:
-
-```bash copy
-npm install @mastra/mongodb
-```
-
-## Adding memory to an agent
-
-To add MongoDB memory to an agent use the `Memory` class and create a new `storage` key using `MongoDBStore`. The configuration supports both local and remote MongoDB instances.
-
-```typescript filename="src/mastra/agents/example-mongodb-agent.ts" showLineNumbers copy
-import { Memory } from "@mastra/memory";
-import { Agent } from "@mastra/core/agent";
-import { openai } from "@ai-sdk/openai";
-import { MongoDBStore } from "@mastra/mongodb";
-
-export const mongodbAgent = new Agent({
-  name: "mongodb-agent",
-  instructions: "You are an AI agent with the ability to automatically recall memories from previous interactions.",
-  model: openai("gpt-4o"),
-  memory: new Memory({
-    storage: new MongoDBStore({
-      url: process.env.MONGODB_URI!,
-      dbName: process.env.MONGODB_DB_NAME!
-    }),
-    options: {
-      threads: {
-        generateTitle: true
-      }
-    }
-  })
-});
-```
-
-## Vector embeddings with MongoDB
-
-Embeddings are numeric vectors used by memory's `semanticRecall` to retrieve related messages by meaning (not keywords).
-
-> Note: You must use a deployment hosted on MongoDB Atlas to successfully use the MongoDB Vector database.
-
-This setup uses FastEmbed, a local embedding model, to generate vector embeddings.
-To use this, install `@mastra/fastembed`:
-
-```bash copy
-npm install @mastra/fastembed
-```
-
-Add the following to your agent:
-
-```typescript filename="src/mastra/agents/example-mongodb-agent.ts" showLineNumbers copy
-import { Memory } from "@mastra/memory";
-import { Agent } from "@mastra/core/agent";
-import { openai } from "@ai-sdk/openai";
-import { MongoDBStore, MongoDBVector } from "@mastra/mongodb";
-import { fastembed } from "@mastra/fastembed";
-
-export const mongodbAgent = new Agent({
-  name: "mongodb-agent",
-  instructions: "You are an AI agent with the ability to automatically recall memories from previous interactions.",
-  model: openai("gpt-4o"),
-  memory: new Memory({
-    storage: new MongoDBStore({
-      url: process.env.MONGODB_URI!,
-      dbName: process.env.MONGODB_DB_NAME!
-    }),
-    vector: new MongoDBVector({
-      uri: process.env.MONGODB_URI!,
-      dbName: process.env.MONGODB_DB_NAME!
-    }),
-    embedder: fastembed,
-    options: {
-      lastMessages: 10,
-      semanticRecall: {
-        topK: 3,
-        messageRange: 2
-      },
-      threads: {
-        generateTitle: true // generates descriptive thread titles automatically
-      }
-    }
-  })
-});
-```
-
-## Usage example
-
-Use `memoryOptions` to scope recall for this request. Set `lastMessages: 5` to limit recency-based recall, and use `semanticRecall` to fetch the `topK: 3` most relevant messages, including `messageRange: 2` neighboring messages for context around each match.
-
-```typescript filename="src/test-mongodb-agent.ts" showLineNumbers copy
-import "dotenv/config";
-
-import { mastra } from "./mastra";
-
-const threadId = "123";
-const resourceId = "user-456";
-
-const agent = mastra.getAgent("mongodbAgent");
-
-const message = await agent.stream("My name is Mastra", {
-  memory: {
-    thread: threadId,
-    resource: resourceId
-  }
-});
-
-await message.textStream.pipeTo(new WritableStream());
-
-const stream = await agent.stream("What's my name?", {
-  memory: {
-    thread: threadId,
-    resource: resourceId
-  },
-  memoryOptions: {
-    lastMessages: 5,
-    semanticRecall: {
-      topK: 3,
-      messageRange: 2
-    }
-  }
-});
-
-for await (const chunk of stream.textStream) {
-  process.stdout.write(chunk);
-}
-```
-
-## Related
-
-- [Calling Agents](../agents/calling-agents.mdx)