@mastra/mcp-docs-server 0.13.39 → 1.0.0-beta.1

package/.docs/raw/voice/speech-to-speech.mdx

@@ -35,7 +35,8 @@ import { OpenAIRealtimeVoice } from "@mastra/voice-openai-realtime";
 import { playAudio, getMicrophoneStream } from "@mastra/node-audio";
 
 const agent = new Agent({
-  name: "Agent",
+  id: "agent",
+  name: "OpenAI Realtime Agent",
   instructions: `You are a helpful assistant with real-time voice capabilities.`,
   model: openai("gpt-4o"),
   voice: new OpenAIRealtimeVoice(),
@@ -57,7 +58,7 @@ const micStream = getMicrophoneStream();
 await agent.voice.send(micStream);
 ```
 
-For integrating Speech-to-Speech capabilities with agents, refer to the [Adding Voice to Agents](/docs/agents/adding-voice) documentation.
+For integrating Speech-to-Speech capabilities with agents, refer to the [Adding Voice to Agents](/docs/v1/agents/adding-voice) documentation.
 
 ## Google Gemini Live (Realtime)
 
@@ -67,7 +68,8 @@ import { GeminiLiveVoice } from "@mastra/voice-google-gemini-live";
 import { playAudio, getMicrophoneStream } from "@mastra/node-audio";
 
 const agent = new Agent({
-  name: "Agent",
+  id: "agent",
+  name: "Gemini Live Agent",
   instructions:
     "You are a helpful assistant with real-time voice capabilities.",
   // Model used for text generation; voice provider handles realtime audio

package/.docs/raw/voice/speech-to-text.mdx

@@ -34,18 +34,18 @@ const voice = new OpenAIVoice();
 
 Mastra supports several Speech-to-Text providers, each with their own capabilities and strengths:
 
-- [**OpenAI**](/reference/voice/openai/) - High-accuracy transcription with Whisper models
-- [**Azure**](/reference/voice/azure/) - Microsoft's speech recognition with enterprise-grade reliability
-- [**ElevenLabs**](/reference/voice/elevenlabs/) - Advanced speech recognition with support for multiple languages
-- [**Google**](/reference/voice/google/) - Google's speech recognition with extensive language support
-- [**Cloudflare**](/reference/voice/cloudflare/) - Edge-optimized speech recognition for low-latency applications
-- [**Deepgram**](/reference/voice/deepgram/) - AI-powered speech recognition with high accuracy for various accents
-- [**Sarvam**](/reference/voice/sarvam/) - Specialized in Indic languages and accents
+- [**OpenAI**](/reference/v1/voice/openai/) - High-accuracy transcription with Whisper models
+- [**Azure**](/reference/v1/voice/azure/) - Microsoft's speech recognition with enterprise-grade reliability
+- [**ElevenLabs**](/reference/v1/voice/elevenlabs/) - Advanced speech recognition with support for multiple languages
+- [**Google**](/reference/v1/voice/google/) - Google's speech recognition with extensive language support
+- [**Cloudflare**](/reference/v1/voice/cloudflare/) - Edge-optimized speech recognition for low-latency applications
+- [**Deepgram**](/reference/v1/voice/deepgram/) - AI-powered speech recognition with high accuracy for various accents
+- [**Sarvam**](/reference/v1/voice/sarvam/) - Specialized in Indic languages and accents
 
 Each provider is implemented as a separate package that you can install as needed:
 
 ```bash
-pnpm add @mastra/voice-openai  # Example for OpenAI
+pnpm add @mastra/voice-openai@beta  # Example for OpenAI
 ```
 
 ## Using the Listen Method
@@ -61,6 +61,7 @@ import { getMicrophoneStream } from "@mastra/node-audio";
 const voice = new OpenAIVoice();
 
 const agent = new Agent({
+  id: "voice-agent",
   name: "Voice Agent",
   instructions:
     "You are a voice assistant that provides recommendations based on user input.",
@@ -83,4 +84,4 @@ const { text } = await agent.generate(
 console.log(`Recommendation: ${text}`);
 ```
 
-Check out the [Adding Voice to Agents](/docs/agents/adding-voice) documentation to learn how to use STT in an agent.
+Check out the [Adding Voice to Agents](/docs/v1/agents/adding-voice) documentation to learn how to use STT in an agent.

package/.docs/raw/voice/text-to-speech.mdx

@@ -39,21 +39,21 @@ const voice = new OpenAIVoice();
 
 Mastra supports a wide range of Text-to-Speech providers, each with their own unique capabilities and voice options. You can choose the provider that best suits your application's needs:
 
-- [**OpenAI**](/reference/voice/openai/) - High-quality voices with natural intonation and expression
-- [**Azure**](/reference/voice/azure/) - Microsoft's speech service with a wide range of voices and languages
-- [**ElevenLabs**](/reference/voice/elevenlabs/) - Ultra-realistic voices with emotion and fine-grained control
-- [**PlayAI**](/reference/voice/playai/) - Specialized in natural-sounding voices with various styles
-- [**Google**](/reference/voice/google/) - Google's speech synthesis with multilingual support
-- [**Cloudflare**](/reference/voice/cloudflare/) - Edge-optimized speech synthesis for low-latency applications
-- [**Deepgram**](/reference/voice/deepgram/) - AI-powered speech technology with high accuracy
-- [**Speechify**](/reference/voice/speechify/) - Text-to-speech optimized for readability and accessibility
-- [**Sarvam**](/reference/voice/sarvam/) - Specialized in Indic languages and accents
-- [**Murf**](/reference/voice/murf/) - Studio-quality voice overs with customizable parameters
+- [**OpenAI**](/reference/v1/voice/openai/) - High-quality voices with natural intonation and expression
+- [**Azure**](/reference/v1/voice/azure/) - Microsoft's speech service with a wide range of voices and languages
+- [**ElevenLabs**](/reference/v1/voice/elevenlabs/) - Ultra-realistic voices with emotion and fine-grained control
+- [**PlayAI**](/reference/v1/voice/playai/) - Specialized in natural-sounding voices with various styles
+- [**Google**](/reference/v1/voice/google/) - Google's speech synthesis with multilingual support
+- [**Cloudflare**](/reference/v1/voice/cloudflare/) - Edge-optimized speech synthesis for low-latency applications
+- [**Deepgram**](/reference/v1/voice/deepgram/) - AI-powered speech technology with high accuracy
+- [**Speechify**](/reference/v1/voice/speechify/) - Text-to-speech optimized for readability and accessibility
+- [**Sarvam**](/reference/v1/voice/sarvam/) - Specialized in Indic languages and accents
+- [**Murf**](/reference/v1/voice/murf/) - Studio-quality voice overs with customizable parameters
 
 Each provider is implemented as a separate package that you can install as needed:
 
 ```bash
-pnpm add @mastra/voice-openai  # Example for OpenAI
+pnpm add @mastra/voice-openai@beta  # Example for OpenAI
 ```
 
 ## Using the Speak Method
@@ -68,6 +68,7 @@ import { OpenAIVoice } from "@mastra/voice-openai";
 const voice = new OpenAIVoice();
 
 const agent = new Agent({
+  id: "voice-agent",
   name: "Voice Agent",
   instructions:
     "You are a voice assistant that can help users with their tasks.",
@@ -87,4 +88,4 @@ const readableStream = await voice.speak(text, {
 });
 ```
 
-Check out the [Adding Voice to Agents](/docs/agents/adding-voice) documentation to learn how to use TTS in an agent.
+Check out the [Adding Voice to Agents](/docs/v1/agents/adding-voice) documentation to learn how to use TTS in an agent.

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

@@ -39,6 +39,8 @@ const step1 = createStep({
 });
 ```
 
+> See [Calling Agents](/examples/v1/agents/calling-agents) 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.
@@ -64,7 +66,7 @@ export const testWorkflow = createWorkflow({
   .commit();
 ```
 
-> See [.map()](/reference/workflows/workflow-methods/map) for more information.
+> See [Input Data Mapping](./input-data-mapping) for more information.
 
 Mastra agents use a default schema that expects a `prompt` string as input and returns a `text` string as output:
 
@@ -92,14 +94,14 @@ import { testTool } from "../tools/test-tool";
 
 const step2 = createStep({
   // ...
-  execute: async ({ inputData, runtimeContext }) => {
+  execute: async ({ inputData, requestContext }) => {
     const { formatted } = inputData;
 
     const response = await testTool.execute({
       context: {
         text: formatted,
       },
-      runtimeContext,
+      requestContext,
     });
 
     return {
@@ -109,6 +111,8 @@ const step2 = createStep({
 });
 ```
 
+> See [Calling Tools](/docs/v1/workflows/agents-and-tools#calling-tools) 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.
@@ -134,9 +138,9 @@ export const testWorkflow = createWorkflow({
   .commit();
 ```
 
-> See [.map()](/reference/workflows/workflow-methods/map) for more information.
+> See [Input Data Mapping](./input-data-mapping) for more information.
 
 ## Related
 
-- [Using Agents](/docs/agents/overview)
+- [Using Agents](/docs/v1/agents/overview)
 - [Using Tools](../tools-mcp/overview)

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

@@ -184,9 +184,9 @@ The `.map()` method provides additional helper functions for more complex mappin
 
 **Available helper functions:**
 
-- [`getStepResult()`](/reference/workflows/workflow-methods/map#using-getstepresult): Access a specific step's full output
-- [`getInitData()`](/reference/workflows/workflow-methods/map#using-getinitdata): Access the workflow's initial input data
-- [`mapVariable()`](/reference/workflows/workflow-methods/map#using-mapvariable): Use declarative object syntax to extract and rename fields
+- [`getStepResult()`](/reference/v1/workflows/workflow-methods/map#using-getstepresult): Access a specific step's full output
+- [`getInitData()`](/reference/v1/workflows/workflow-methods/map#using-getinitdata): Access the workflow's initial input data
+- [`mapVariable()`](/reference/v1/workflows/workflow-methods/map#using-mapvariable): Use declarative object syntax to extract and rename fields
 
 ## Looping steps
 

package/.docs/raw/workflows/error-handling.mdx

@@ -163,25 +163,6 @@ export const testWorkflow = createWorkflow({...})
   .commit();
 ```
 
-## Monitor errors with `watch()`
-
-You can monitor workflows for errors using the `watch` method:
-
-```typescript {11} title="src/test-workflow.ts" showLineNumbers copy
-import { mastra } from "../src/mastra";
-
-const workflow = mastra.getWorkflow("testWorkflow");
-const run = await workflow.createRunAsync();
-
-run.watch((event) => {
-  const {
-    payload: { currentStep },
-  } = event;
-
-  console.log(currentStep?.payload?.status);
-});
-```
-
 ## Monitor errors with `stream()`
 
 You can monitor workflows for errors using `stream`:
@@ -191,7 +172,7 @@ import { mastra } from "../src/mastra";
 
 const workflow = mastra.getWorkflow("testWorkflow");
 
-const run = await workflow.createRunAsync();
+const run = await workflow.createRun();
 
 const stream = await run.stream({
   inputData: {
@@ -208,4 +189,4 @@ for await (const chunk of stream.stream) {
 
 - [Control Flow](./control-flow)
 - [Conditional Branching](./control-flow#conditional-logic-with-branch)
-- [Running Workflows](/examples/workflows_legacy/creating-a-workflow)
+- [Running Workflows](/docs/v1/workflows/overview)

package/.docs/raw/workflows/human-in-the-loop.mdx

@@ -36,6 +36,7 @@ import { Memory } from "@mastra/memory";
 import { LibSQLVector } from "@mastra/libsql";
 
 export const famousPersonAgent = new Agent({
+  id: "famous-person-generator",
   name: "Famous Person Generator",
   instructions: `You are a famous person generator for a "Heads Up" guessing game.
 
@@ -53,6 +54,7 @@ Return only the person's name, nothing else.`,
   model: openai("gpt-4o"),
   memory: new Memory({
     vector: new LibSQLVector({
+      id: 'workflow-vector',
       connectionUrl: "file:../mastra.db",
     }),
     embedder: openai.embedding("text-embedding-3-small"),
@@ -67,7 +69,7 @@ Return only the person's name, nothing else.`,
 });
 ```
 
-> See [Agent](/reference/agents/agent) for a full list of configuration options.
+> See [Agent](/reference/v1/agents/agent) for a full list of configuration options.
 
 ## Game agent
 
@@ -78,6 +80,7 @@ import { openai } from "@ai-sdk/openai";
 import { Agent } from "@mastra/core/agent";
 
 export const gameAgent = new Agent({
+  id: "game-agent",
   name: "Game Agent",
   instructions: `You are a helpful game assistant for a "Heads Up" guessing game.
 
@@ -238,14 +241,14 @@ export const headsUpWorkflow = createWorkflow({
   .commit();
 ```
 
-> See [Workflow](/reference/workflows/workflow) for a full list of configuration options.
+> See [Workflow](/reference/v1/workflows/workflow) for a full list of configuration options.
 
 ## Registering the agents and workflow
 
 To use a workflow or an agent, register them in your main Mastra instance.
 
 ```typescript title="src/mastra/index.ts" showLineNumbers copy
-import { Mastra } from "@mastra/core/mastra";
+import { Mastra } from "@mastra/core";
 
 import { headsUpWorkflow } from "./workflows/example-heads-up-workflow";
 import { famousPersonAgent } from "./agents/example-famous-person-agent";
@@ -265,4 +268,4 @@ export const mastra = new Mastra({
 ## Related
 
 - [Running Workflows](./overview#running-workflows)
-- [Control Flow](/docs/workflows/control-flow)
+- [Control Flow](/docs/v1/workflows/control-flow)

package/.docs/raw/workflows/inngest-workflow.mdx

@@ -20,7 +20,7 @@ Real-time monitoring, suspend/resume, and step-level observability are enabled v
 ## Setup
 
 ```sh
-npm install @mastra/inngest @mastra/core @mastra/deployer
+npm install @mastra/inngest@beta @mastra/core@beta @mastra/deployer@beta
 ```
 
 ## Building an Inngest Workflow
@@ -110,7 +110,7 @@ export { workflow as incrementWorkflow };
 Register the workflow with Mastra and configure the Inngest API endpoint:
 
 ```ts showLineNumbers copy title="src/mastra/index.ts"
-import { Mastra } from "@mastra/core/mastra";
+import { Mastra } from "@mastra/core";
 import { serve as inngestServe } from "@mastra/inngest";
 import { incrementWorkflow } from "./workflows";
 import { inngest } from "./inngest";
@@ -321,7 +321,7 @@ export const customWebhookFunction = inngest.createFunction(
 Update your Mastra configuration to include the custom functions:
 
 ```ts showLineNumbers copy title="src/mastra/index.ts"
-import { Mastra } from "@mastra/core/mastra";
+import { Mastra } from "@mastra/core";
 import { serve as inngestServe } from "@mastra/inngest";
 import { incrementWorkflow } from "./workflows";
 import { inngest } from "./inngest";

package/.docs/raw/workflows/input-data-mapping.mdx

@@ -0,0 +1,107 @@
+---
+title: "Input Data Mapping | Workflows | Mastra Docs"
+description: "Learn how to use workflow input mapping to create more dynamic data flows in your Mastra workflows."
+---
+
+# Input Data Mapping
+
+Input data mapping allows explicit mapping of values for the inputs of the next step. These values can come from a number of sources:
+
+- The outputs of a previous step
+- The request context
+- A constant value
+- The initial input of the workflow
+
+## Mapping with `.map()`
+
+In this example the `output` from `step1` is transformed to match the `inputSchema` required for the `step2`. The value from `step1` is available using the `inputData` parameter of the `.map` function.
+
+![Mapping with .map()](/img/workflows/workflows-data-mapping-map.jpg)
+
+```typescript {9} title="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
+const step1 = createStep({...});
+const step2 = createStep({...});
+
+export const testWorkflow = createWorkflow({...})
+  .then(step1)
+  .map(async ({ inputData }) => {
+    const { value } = inputData;
+    return {
+      output: `new ${value}`
+    };
+  })
+  .then(step2)
+  .commit();
+```
+
+## Using `inputData`
+
+Use `inputData` to access the full output of the previous step:
+
+```typescript {3} title="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
+  .then(step1)
+  .map(({ inputData }) => {
+    console.log(inputData);
+  })
+```
+
+## Using `getStepResult()`
+
+Use `getStepResult` to access the full output of a specific step by referencing the step's instance:
+
+```typescript {3} title="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
+  .then(step1)
+  .map(async ({ getStepResult }) => {
+    console.log(getStepResult(step1));
+  })
+```
+
+## Using `getInitData()`
+
+Use `getInitData` to access the initial input data provided to the workflow:
+
+```typescript {3} title="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
+  .then(step1)
+  .map(async ({ getInitData }) => {
+      console.log(getInitData());
+  })
+```
+
+## Using `mapVariable()`
+
+To use `mapVariable` import the necessary function from the workflows module:
+
+```typescript title="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
+import { mapVariable } from "@mastra/core/workflows";
+```
+
+### Renaming step with `mapVariable()`
+
+You can rename step outputs using the object syntax in `.map()`. In the example below, the `value` output from `step1` is renamed to `details`:
+
+```typescript {3-6} title="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
+  .then(step1)
+  .map({
+    details: mapVariable({
+      step: step,
+      path: "value"
+    })
+  })
+```
+
+### Renaming workflows with `mapVariable()`
+
+You can rename workflow outputs by using **referential composition**. This involves passing the workflow instance as the `initData`.
+
+```typescript {6-9} title="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
+export const testWorkflow = createWorkflow({...});
+
+testWorkflow
+  .then(step1)
+  .map({
+    details: mapVariable({
+      initData: testWorkflow,
+      path: "value"
+    })
+  })
+```

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

@@ -53,11 +53,11 @@ const step1 = createStep({
 });
 ```
 
-> See the [Step Class](/reference/workflows/step) for a full list of configuration options.
+> See the [Step Class](/reference/v1/workflows/step) 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 [Using Tools](/docs/agents/using-tools) page for more information.
+Workflow steps can also call registered agents or import and execute tools directly, visit the [Using Tools](/docs/v1/agents/using-tools) page for more information.
 
 ## Creating a workflow
 
@@ -82,11 +82,11 @@ export const testWorkflow = createWorkflow({
   .commit();
 ```
 
-> See the [Workflow Class](/reference/workflows/workflow) for a full list of configuration options.
+> See the [Workflow Class](/reference/v1/workflows/workflow) for a full list of configuration options.
 
 ### 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. Visit the [Control Flow](/docs/workflows/control-flow) page for more information.
+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](/docs/v1/workflows/control-flow) page for more information.
 
 ## Workflow state
 
@@ -146,7 +146,7 @@ export const testWorkflow = createWorkflow({
 
 ## Workflows as steps
 
-Use a workflow as a step to reuse its logic within a larger composition. Input and output follow the same schema rules described in [Core principles](/docs/workflows/control-flow).
+Use a workflow as a step to reuse its logic within a larger composition. Input and output follow the same schema rules described in [Core principles](/docs/v1/workflows/control-flow).
 
 ```typescript {26} title="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
 const step1 = createStep({...});
@@ -227,10 +227,10 @@ Workflows can be run in two modes: start waits for all steps to complete before
 
 <Tabs>
   <TabItem value="start" label="Start">
-Create a workflow run instance using `createRunAsync()`, then call `.start()` with `inputData` matching the workflow's `inputSchema`. The workflow executes all steps and returns the final result.
+Create a workflow run instance using `createRun()`, then call `.start()` with `inputData` matching the workflow's `inputSchema`. The workflow executes all steps and returns the final result.
 
 ```typescript showLineNumbers copy
-const run = await testWorkflow.createRunAsync();
+const run = await testWorkflow.createRun();
 
 const result = await run.start({
   inputData: {
@@ -242,10 +242,10 @@ console.log(result);
 ```
   </TabItem>
   <TabItem value="stream" label="Stream">
-Create a workflow run instance using `.createRunAsync()`, then call `.stream()` with `inputData` matching the workflow's `inputSchema`. The workflow emits events as each step executes, which you can iterate over to track progress.
+Create a workflow run instance using `.createRun()`, then call `.stream()` with `inputData` matching the workflow's `inputSchema`. The workflow emits events as each step executes, which you can iterate over to track progress.
 
 ```typescript showLineNumbers copy
-const run = await testWorkflow.createRunAsync();
+const run = await testWorkflow.createRun();
 
 const result = await run.stream({
   inputData: {
@@ -297,9 +297,9 @@ The workflow output includes the full execution lifecycle, showing the input and
 }
 ```
 
-## Using `RuntimeContext`
+## Using `RequestContext`
 
-Use [RuntimeContext](/docs/server-db/runtime-context) to access request-specific values. This lets you conditionally adjust behavior based on the context of the request.
+Use [RequestContext](/docs/v1/server-db/request-context) to access request-specific values. This lets you conditionally adjust behavior based on the context of the request.
 
 ```typescript title="src/mastra/workflows/test-workflow.ts" showLineNumbers
 export type UserTier = {
@@ -308,8 +308,8 @@ export type UserTier = {
 
 const step1 = createStep({
   // ...
-  execute: async ({ runtimeContext }) => {
-    const userTier = runtimeContext.get("user-tier") as UserTier["user-tier"];
+  execute: async ({ requestContext }) => {
+    const userTier = requestContext.get("user-tier") as UserTier["user-tier"];
 
     const maxResults = userTier === "enterprise"
       ? 1000
@@ -320,12 +320,13 @@ const step1 = createStep({
 });
 ```
 
-> See [Runtime Context](/docs/server-db/runtime-context) for more information.
+> See [Request Context](/docs/v1/server-db/request-context) for more information.
 
 ## Testing with Studio
 
-Use [Studio](/docs/getting-started/studio) 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.
+Use [Studio](/docs/v1/getting-started/studio) 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), which walks through the core concepts with a practical example.
+For a closer look at workflows, see our [Workflow Guide](/guides/v1/guide/ai-recruiter), which walks through the core concepts with a practical example.
+

package/.docs/raw/workflows/snapshots.mdx

@@ -77,7 +77,7 @@ Each snapshot includes the `runId`, input, step status (`success`, `suspended`,
   "suspendedPaths": {},
   "waitingPaths": {},
   "result": { "value": 100, "approved": true },
-  "runtimeContext": {},
+  "requestContext": {},
   "timestamp": 1758027578740
 }
 ```
@@ -88,9 +88,9 @@ Snapshots are saved to the configured storage system. By default, they use LibSQ
 
 Read more about:
 
-- [LibSQL Storage](/reference/storage/libsql)
-- [Upstash Storage](/reference/storage/upstash)
-- [PostgreSQL Storage](/reference/storage/postgresql)
+- [LibSQL Storage](/reference/v1/storage/libsql)
+- [Upstash Storage](/reference/v1/storage/upstash)
+- [PostgreSQL Storage](/reference/v1/storage/postgresql)
 
 ### Saving snapshots
 
@@ -132,12 +132,13 @@ Snapshots are persisted using a `storage` instance configured on the `Mastra` cl
 This example demonstrates how to use snapshots with LibSQL.
 
 ```typescript title="src/mastra/index.ts" showLineNumbers copy
-import { Mastra } from "@mastra/core/mastra";
+import { Mastra } from "@mastra/core";
 import { LibSQLStore } from "@mastra/libsql";
 
 export const mastra = new Mastra({
   // ...
   storage: new LibSQLStore({
+    id: 'mastra-storage',
     url: ":memory:",
   }),
 });
@@ -148,12 +149,13 @@ export const mastra = new Mastra({
 This example demonstrates how to use snapshots with Upstash.
 
 ```typescript title="src/mastra/index.ts" showLineNumbers copy
-import { Mastra } from "@mastra/core/mastra";
+import { Mastra } from "@mastra/core";
 import { UpstashStore } from "@mastra/upstash";
 
 export const mastra = new Mastra({
   // ...
   storage: new UpstashStore({
+  id: 'upstash-storage',
     url: "<upstash-redis-rest-url>",
     token: "<upstash-redis-rest-token>",
   }),
@@ -165,12 +167,13 @@ export const mastra = new Mastra({
 This example demonstrates how to use snapshots with PostgreSQL.
 
 ```typescript title="src/mastra/index.ts" showLineNumbers copy
-import { Mastra } from "@mastra/core/mastra";
+import { Mastra } from "@mastra/core";
 import { PostgresStore } from "@mastra/pg";
 
 export const mastra = new Mastra({
   // ...
   storage: new PostgresStore({
+    id: 'mastra-storage',
     connectionString: "<database-url>",
   }),
 });
@@ -240,7 +243,7 @@ Use `resumeData` to pass structured input when resuming a suspended step. It mus
 ```typescript {14-20} showLineNumbers copy
 const workflow = mastra.getWorkflow("approvalWorkflow");
 
-const run = await workflow.createRunAsync();
+const run = await workflow.createRun();
 
 const result = await run.start({
   inputData: {
@@ -263,6 +266,5 @@ if (result.status === "suspended") {
 
 ## Related
 
-- [Suspend and resume](/docs/workflows/suspend-and-resume)
-- [Human in the loop example](/examples/workflows_legacy/human-in-the-loop)
-- [WorkflowRun.watch()](/reference/workflows/run-methods/watch)
+- [Suspend and resume](/docs/v1/workflows/suspend-and-resume)
+- [Human in the loop example](/docs/v1/workflows/human-in-the-loop)