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

package/.docs/raw/deployment/serverless-platforms/vercel-deployer.mdx

@@ -5,18 +5,18 @@ description: "Learn how to deploy a Mastra application to Vercel using the Mastr
 
 # VercelDeployer
 
-The `VercelDeployer` class handles deployment of standalone Mastra applications to Vercel. It manages configuration, deployment, and extends the base [Deployer](/reference/deployer/) class with Vercel specific functionality.
+The `VercelDeployer` class handles deployment of standalone Mastra applications to Vercel. It manages configuration, deployment, and extends the base [Deployer](/reference/v1/deployer/) class with Vercel specific functionality.
 
 ## Installation
 
 ```bash copy
-npm install @mastra/deployer-vercel@latest
+npm install @mastra/deployer-vercel@beta
 ```
 
 ## Usage example
 
 ```typescript title="src/mastra/index.ts" showLineNumbers copy
-import { Mastra } from "@mastra/core/mastra";
+import { Mastra } from "@mastra/core";
 import { VercelDeployer } from "@mastra/deployer-vercel";
 
 export const mastra = new Mastra({
@@ -25,7 +25,7 @@ export const mastra = new Mastra({
 });
 ```
 
-> See the [VercelDeployer](/reference/deployer/vercel) API reference for all available configuration options.
+> See the [VercelDeployer](/reference/v1/deployer/vercel) API reference for all available configuration options.
 
 ### Optional overrides
 
@@ -99,4 +99,4 @@ The `VercelDeployer` automatically generates a `config.json` configuration file
 
 ## Next steps
 
-- [Mastra Client SDK](/reference/client-js/mastra-client)
+- [Mastra Client SDK](/reference/v1/client-js/mastra-client)

package/.docs/raw/deployment/web-framework.mdx

@@ -7,16 +7,16 @@ description: "Learn how Mastra can be deployed when integrated with a Web Framew
 
 This guide covers deploying integrated Mastra applications. Mastra can be integrated with a variety of web frameworks, see one of the following for a detailed guide.
 
-- [With Next.js](/docs/frameworks/web-frameworks/next-js)
-- [With Astro](/docs/frameworks/web-frameworks/astro)
+- [With Next.js](/docs/v1/frameworks/web-frameworks/next-js)
+- [With Astro](/docs/v1/frameworks/web-frameworks/astro)
 
 When integrated with a framework, Mastra typically requires no additional configuration for deployment.
 
 ## With Next.js on Vercel
 
-If you've integrated Mastra with Next.js [by following our guide](/docs/frameworks/web-frameworks/next-js) and plan to deploy to Vercel, no additional setup is required.
+If you've integrated Mastra with Next.js [by following our guide](/docs/v1/frameworks/web-frameworks/next-js) and plan to deploy to Vercel, no additional setup is required.
 
-The only thing to verify is that you've added the following to your `next.config.ts` and removed any usage of [LibSQLStore](/docs/deployment/overview), which is not supported in serverless environments:
+The only thing to verify is that you've added the following to your `next.config.ts` and removed any usage of [LibSQLStore](/docs/v1/deployment/overview), which is not supported in serverless environments:
 
 ```typescript {4} title="next.config.ts" showLineNumbers copy
 import type { NextConfig } from "next";
@@ -30,9 +30,9 @@ export default nextConfig;
 
 ## With Astro on Vercel
 
-If you've integrated Mastra with Astro [by following our guide](/docs/frameworks/web-frameworks/astro) and plan to deploy to Vercel, no additional setup is required.
+If you've integrated Mastra with Astro [by following our guide](/docs/v1/frameworks/web-frameworks/astro) and plan to deploy to Vercel, no additional setup is required.
 
-The only thing to verify is that you've added the following to your `astro.config.mjs` and removed any usage of [LibSQLStore](/docs/deployment/overview), which is not supported in serverless environments:
+The only thing to verify is that you've added the following to your `astro.config.mjs` and removed any usage of [LibSQLStore](/docs/v1/deployment/overview), which is not supported in serverless environments:
 
 ```javascript {2,6,7} title="astro.config.mjs" showLineNumbers copy
 import { defineConfig } from "astro/config";
@@ -47,9 +47,9 @@ export default defineConfig({
 
 ## With Astro on Netlify
 
-If you've integrated Mastra with Astro [by following our guide](/docs/frameworks/web-frameworks/astro) and plan to deploy to Netlify, no additional setup is required.
+If you've integrated Mastra with Astro [by following our guide](/docs/v1/frameworks/web-frameworks/astro) and plan to deploy to Netlify, no additional setup is required.
 
-The only thing to verify is that you've added the following to your `astro.config.mjs` and removed any usage of [LibSQLStore](/docs/deployment/overview), which is not supported in serverless environments:
+The only thing to verify is that you've added the following to your `astro.config.mjs` and removed any usage of [LibSQLStore](/docs/v1/deployment/overview), which is not supported in serverless environments:
 
 ```javascript {2,6,7} title="astro.config.mjs" showLineNumbers copy
 import { defineConfig } from "astro/config";

package/.docs/raw/{scorers → evals}/custom-scorers.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Custom Scorers | Scorers | Mastra Docs"
+title: "Custom Scorers | Evals | Mastra Docs"
 ---
 
 # Custom scorers
@@ -40,7 +40,7 @@ You can mix and match approaches within a single scorer - for example, use a fun
 Every scorer starts with the `createScorer` factory function, which requires a name and description, and optionally accepts a type specification and judge configuration.
 
 ```typescript
-import { createScorer } from '@mastra/core/scores';
+import { createScorer } from '@mastra/core/evals';
 import { openai } from '@ai-sdk/openai';
 
 const glutenCheckerScorer = createScorer({
@@ -187,7 +187,7 @@ const glutenCheckerScorer = createScorer({...})
 })
 ```
 
-**Prompt Objects:** See the [`createScorer`](/reference/scorers/create-scorer) API reference for details on using prompt objects with generateScore, including required `calculateScore` function.
+**Prompt Objects:** See the [`createScorer`](/reference/v1/evals/create-scorer) API reference for details on using prompt objects with generateScore, including required `calculateScore` function.
 
 **Data Flow:** The score is available to generateReason as the `score` parameter
 
@@ -242,11 +242,11 @@ A custom scorer in Mastra uses `createScorer` with four core components:
 
 Together, these components allow you to define custom evaluation logic using LLMs as judges.
 
-> See [createScorer](/reference/scorers/create-scorer) for the full API and configuration options.
+> See [createScorer](/reference/v1/evals/create-scorer) for the full API and configuration options.
 
 ```typescript title="src/mastra/scorers/gluten-checker.ts" showLineNumbers copy
 import { openai } from "@ai-sdk/openai";
-import { createScorer } from "@mastra/core/scores";
+import { createScorer } from "@mastra/core/evals";
 import { z } from "zod";
 
 export const GLUTEN_INSTRUCTIONS = `You are a Chef that identifies if recipes contain gluten.`;
@@ -479,5 +479,5 @@ console.log("Reason:", result.reason);
 
 **Examples and Resources:**
 
-- [createScorer API Reference](/reference/scorers/create-scorer) - Complete technical documentation
+- [createScorer API Reference](/reference/v1/evals/create-scorer) - Complete technical documentation
 - [Built-in Scorers Source Code](https://github.com/mastra-ai/mastra/tree/main/packages/evals/src/scorers) - Real implementations for reference

package/.docs/raw/evals/off-the-shelf-scorers.mdx

@@ -0,0 +1,50 @@
+---
+title: "Built-in Scorers | Evals | Mastra Docs"
+description: "Overview of Mastra's ready-to-use scorers for evaluating AI outputs across quality, safety, and performance dimensions."
+---
+
+# Built-in Scorers
+
+Mastra provides a comprehensive set of built-in scorers for evaluating AI outputs. These scorers are optimized for common evaluation scenarios and are ready to use in your agents and workflows.
+
+## Available Scorers
+
+### Accuracy and Reliability
+
+These scorers evaluate how correct, truthful, and complete your agent's answers are:
+
+- [`answer-relevancy`](/reference/v1/evals/answer-relevancy): Evaluates how well responses address the input query (`0-1`, higher is better)
+- [`answer-similarity`](/reference/v1/evals/answer-similarity): Compares agent outputs against ground truth answers for CI/CD testing using semantic analysis (`0-1`, higher is better)
+- [`faithfulness`](/reference/v1/evals/faithfulness): Measures how accurately responses represent provided context (`0-1`, higher is better)
+- [`hallucination`](/reference/v1/evals/hallucination): Detects factual contradictions and unsupported claims (`0-1`, lower is better)
+- [`completeness`](/reference/v1/evals/completeness): Checks if responses include all necessary information (`0-1`, higher is better)
+- [`content-similarity`](/reference/v1/evals/content-similarity): Measures textual similarity using character-level matching (`0-1`, higher is better)
+- [`textual-difference`](/reference/v1/evals/textual-difference): Measures textual differences between strings (`0-1`, higher means more similar)
+- [`tool-call-accuracy`](/reference/v1/evals/tool-call-accuracy): Evaluates whether the LLM selects the correct tool from available options (`0-1`, higher is better)
+- [`prompt-alignment`](/reference/v1/evals/prompt-alignment): Measures how well agent responses align with user prompt intent, requirements, completeness, and format (`0-1`, higher is better)
+
+### Context Quality
+
+These scorers evaluate the quality and relevance of context used in generating responses:
+
+- [`context-precision`](/reference/v1/evals/context-precision): Evaluates context relevance and ranking using Mean Average Precision, rewarding early placement of relevant context (`0-1`, higher is better)
+- [`context-relevance`](/reference/v1/evals/context-relevance): Measures context utility with nuanced relevance levels, usage tracking, and missing context detection (`0-1`, higher is better)
+
+> tip Context Scorer Selection
+
+- Use **Context Precision** when context ordering matters and you need standard IR metrics (ideal for RAG ranking evaluation)
+- Use **Context Relevance** when you need detailed relevance assessment and want to track context usage and identify gaps
+
+Both context scorers support:
+
+- **Static context**: Pre-defined context arrays
+- **Dynamic context extraction**: Extract context from runs using custom functions (ideal for RAG systems, vector databases, etc.)
+
+### Output Quality
+
+These scorers evaluate adherence to format, style, and safety requirements:
+
+- [`tone-consistency`](/reference/v1/evals/tone-consistency): Measures consistency in formality, complexity, and style (`0-1`, higher is better)
+- [`toxicity`](/reference/v1/evals/toxicity): Detects harmful or inappropriate content (`0-1`, lower is better)
+- [`bias`](/reference/v1/evals/bias): Detects potential biases in the output (`0-1`, lower is better)
+- [`keyword-coverage`](/reference/v1/evals/keyword-coverage): Assesses technical terminology usage (`0-1`, higher is better)

package/.docs/raw/{scorers → evals}/overview.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Scorers overview | Scorers | Mastra Docs"
+title: "Scorers overview | Evals | Mastra Docs"
 description: Overview of scorers in Mastra, detailing their capabilities for evaluating AI outputs and measuring performance.
 ---
 
@@ -24,7 +24,7 @@ There are different kinds of scorers, each serving a specific purpose. Here are
 To access Mastra's scorers feature install the `@mastra/evals` package.
 
 ```bash copy
-npm install @mastra/evals@latest
+npm install @mastra/evals@beta
 ```
 
 ## Live evaluations
@@ -33,7 +33,7 @@ npm install @mastra/evals@latest
 
 ### Adding scorers to agents
 
-You can add built-in scorers to your agents to automatically evaluate their outputs. See the [full list of built-in scorers](/docs/scorers/off-the-shelf-scorers) for all available options.
+You can add built-in scorers to your agents to automatically evaluate their outputs. See the [full list of built-in scorers](/docs/v1/evals/off-the-shelf-scorers) for all available options.
 
 ```typescript title="src/mastra/agents/evaluated-agent.ts" showLineNumbers copy
 import { Agent } from "@mastra/core/agent";
@@ -41,7 +41,7 @@ import { openai } from "@ai-sdk/openai";
 import {
   createAnswerRelevancyScorer,
   createToxicityScorer,
-} from "@mastra/evals/scorers/llm";
+} from "@mastra/evals/scorers/prebuilt";
 
 export const evaluatedAgent = new Agent({
   // ...
@@ -106,7 +106,7 @@ In addition to live evaluations, you can use scorers to evaluate historical trac
 
 **Observability Required**
 
-To score traces, you must first configure observability in your Mastra instance to collect trace data. See [AI Tracing documentation](../observability/ai-tracing/overview) for setup instructions.
+To score traces, you must first configure observability in your Mastra instance to collect trace data. See [Tracing documentation](../observability/tracing/overview) for setup instructions.
 
 :::
 
@@ -130,10 +130,10 @@ Once registered, you can score traces interactively within Studio under the Obse
 
 Mastra provides a CLI command `mastra dev` to test your scorers. Studio includes a scorers section where you can run individual scorers against test inputs and view detailed results.
 
-For more details, see [Studio](/docs/getting-started/studio) docs.
+For more details, see [Studio](/docs/v1/getting-started/studio) docs.
 
 ## Next steps
 
-- Learn how to create your own scorers in the [Creating Custom Scorers](/docs/scorers/custom-scorers) guide
-- Explore built-in scorers in the [Off-the-shelf Scorers](/docs/scorers/off-the-shelf-scorers) section
-- Test scorers with [Studio](/docs/getting-started/studio)
+- Learn how to create your own scorers in the [Creating Custom Scorers](/docs/v1/evals/custom-scorers) guide
+- Explore built-in scorers in the [Off-the-shelf Scorers](/docs/v1/evals/off-the-shelf-scorers) section
+- Test scorers with [Studio](/docs/v1/getting-started/studio)

package/.docs/raw/evals/running-in-ci.mdx

@@ -0,0 +1,113 @@
+---
+title: "Running Scorers in CI | Evals | Mastra Docs"
+description: "Learn how to run scorer experiments in your CI/CD pipeline using the runEvals function."
+---
+
+# Running Scorers in CI
+
+Running scorers in your CI pipeline provides quantifiable metrics for measuring agent quality over time. The `runEvals` function processes multiple test cases through your agent or workflow and returns aggregate scores.
+
+## Basic Setup
+
+You can use any testing framework that supports ESM modules, such as [Vitest](https://vitest.dev/), [Jest](https://jestjs.io/), or [Mocha](https://mochajs.org/).
+
+## Creating Test Cases
+
+Use `runEvals` to evaluate your agent against multiple test cases. The function accepts an array of data items, each containing an `input` and optional `groundTruth` for scorer validation.
+
+```typescript copy showLineNumbers title="src/mastra/agents/weather-agent.test.ts"
+import { describe, it, expect } from 'vitest';
+import { createScorer, runEvals } from "@mastra/core/evals";
+import { weatherAgent } from "./weather-agent";
+import { locationScorer } from "../scorers/location-scorer";
+
+describe('Weather Agent Tests', () => {
+  it('should correctly extract locations from queries', async () => {
+    const result = await runEvals({
+      data: [
+        {
+          input: 'weather in Berlin',
+          groundTruth: { expectedLocation: 'Berlin', expectedCountry: 'DE' }
+        },
+        {
+          input: 'weather in Berlin, Maryland',
+          groundTruth: { expectedLocation: 'Berlin', expectedCountry: 'US' }
+        },
+        {
+          input: 'weather in Berlin, Russia',
+          groundTruth: { expectedLocation: 'Berlin', expectedCountry: 'RU' }
+        },
+      ],
+      target: weatherAgent,
+      scorers: [locationScorer]
+    });
+
+    // Assert aggregate score meets threshold
+    expect(result.scores['location-accuracy']).toBe(1);
+    expect(result.summary.totalItems).toBe(3);
+  });
+});
+```
+
+View the full example [here](/examples/v1/evals/running-in-ci)
+
+## Understanding Results
+
+The `runEvals` function returns an object with:
+
+- `scores`: Average scores for each scorer across all test cases
+- `summary.totalItems`: Total number of test cases processed
+
+```typescript
+{
+  scores: {
+    'location-accuracy': 1.0,  // Average score across all items
+    'another-scorer': 0.85
+  },
+  summary: {
+    totalItems: 3
+  }
+}
+```
+
+## Multiple Test Scenarios
+
+Create separate test cases for different evaluation scenarios:
+
+```typescript copy showLineNumbers title="src/mastra/agents/weather-agent.test.ts"
+describe('Weather Agent Tests', () => {
+  const locationScorer = createScorer({ /* ... */ });
+
+  it('should handle location disambiguation', async () => {
+    const result = await runEvals({
+      data: [
+        { input: 'weather in Berlin', groundTruth: { /* ... */ } },
+        { input: 'weather in Berlin, Maryland', groundTruth: { /* ... */ } },
+      ],
+      target: weatherAgent,
+      scorers: [locationScorer]
+    });
+
+    expect(result.scores['location-accuracy']).toBe(1);
+  });
+
+  it('should handle typos and misspellings', async () => {
+    const result = await runEvals({
+      data: [
+        { input: 'weather in Berln', groundTruth: { expectedLocation: 'Berlin', expectedCountry: 'DE' } },
+        { input: 'weather in Parris', groundTruth: { expectedLocation: 'Paris', expectedCountry: 'FR' } },
+      ],
+      target: weatherAgent,
+      scorers: [locationScorer]
+    });
+
+    expect(result.scores['location-accuracy']).toBe(1);
+  });
+});
+```
+
+## Next Steps
+
+- Learn about [creating custom scorers](/docs/v1/evals/custom-scorers)
+- Explore [off-the-shelf scorers](/docs/v1/evals/off-the-shelf-scorers)
+- Read the [runEvals API reference](/reference/v1/evals/run-evals)

package/.docs/raw/frameworks/agentic-uis/ai-sdk.mdx

@@ -18,13 +18,14 @@ When creating agents in Mastra, you can specify any AI SDK-supported model.
 import { Agent } from "@mastra/core/agent";
 
 export const weatherAgent = new Agent({
+  id: "weather-agent",
   name: "Weather Agent",
   instructions: "Instructions for the agent...",
   model: "openai/gpt-4-turbo",
 });
 ```
 
-> See [Using AI SDK with Mastra](/models#use-ai-sdk-with-mastra) for more information.
+> See [Using AI SDK with Mastra](/models/v1#use-ai-sdk-with-mastra) for more information.
 
 ## Streaming
 
@@ -33,32 +34,32 @@ The recommended way of using Mastra and AI SDK together is by installing the `@m
 <Tabs>
   <TabItem value="npm" label="npm">
     ```bash copy
-    npm install @mastra/ai-sdk
+    npm install @mastra/ai-sdk@beta
     ```
   </TabItem>
   <TabItem value="pnpm" label="pnpm">
     ```bash copy
-    pnpm add @mastra/ai-sdk
+    pnpm add @mastra/ai-sdk@beta
     ```
   </TabItem>
   <TabItem value="yarn" label="yarn">
     ```bash copy
-    yarn add @mastra/ai-sdk
+    yarn add @mastra/ai-sdk@beta
     ```
   </TabItem>
   <TabItem value="bun" label="bun">
     ```bash copy
-    bun add @mastra/ai-sdk
+    bun add @mastra/ai-sdk@beta
     ```
   </TabItem>
 </Tabs>
 
 ### `chatRoute()`
 
-When setting up a [custom API route](/docs/server-db/custom-api-routes), use the `chatRoute()` utility to create a route handler that automatically formats the agent stream into an AI SDK-compatible format.
+When setting up a [custom API route](/docs/v1/server-db/custom-api-routes), use the `chatRoute()` utility to create a route handler that automatically formats the agent stream into an AI SDK-compatible format.
 
 ```typescript title="src/mastra/index.ts" copy
-import { Mastra } from "@mastra/core/mastra";
+import { Mastra } from "@mastra/core";
 import { chatRoute } from "@mastra/ai-sdk";
 
 export const mastra = new Mastra({
@@ -110,7 +111,7 @@ const { error, status, sendMessage, messages, regenerate, stop } = useChat({
 Use the `workflowRoute()` utility to create a route handler that automatically formats the workflow stream into an AI SDK-compatible format.
 
 ```typescript title="src/mastra/index.ts" copy
-import { Mastra } from "@mastra/core/mastra";
+import { Mastra } from "@mastra/core";
 import { workflowRoute } from "@mastra/ai-sdk";
 
 export const mastra = new Mastra({
@@ -149,7 +150,7 @@ const { error, status, sendMessage, messages, regenerate, stop } = useChat({
 Use the `networkRoute()` utility to create a route handler that automatically formats the agent network stream into an AI SDK-compatible format.
 
 ```typescript title="src/mastra/index.ts" copy
-import { Mastra } from "@mastra/core/mastra";
+import { Mastra } from "@mastra/core";
 import { networkRoute } from "@mastra/ai-sdk";
 
 export const mastra = new Mastra({
@@ -187,7 +188,7 @@ The `@mastra/ai-sdk` package transforms and emits Mastra streams (e.g workflow,
   - `data-tool-network`: Nested network emitted from within an tool stream.
   - `data-tool-agent`: Nested agent emitted from within an tool stream.
 
-Here's an example: For a [nested agent stream within a tool](/docs/streaming/tool-streaming#tool-using-an-agent), `data-tool-agent` UI message parts will be emitted and can be leveraged on the client as documented below:
+Here's an example: For a [nested agent stream within a tool](/docs/v1/streaming/tool-streaming#tool-using-an-agent), `data-tool-agent` UI message parts will be emitted and can be leveraged on the client as documented below:
 
 ```typescript title="app/page.tsx" copy
 "use client";
@@ -276,7 +277,7 @@ export const testTool = createTool({
 });
 ```
 
-For more information about tool streaming see [Tool streaming documentation](/docs/streaming/tool-streaming)
+For more information about tool streaming see [Tool streaming documentation](/docs/v1/streaming/tool-streaming)
 
 ### Stream Transformations
 
@@ -428,7 +429,7 @@ export async function POST(req: Request) {
 }
 ```
 
-> When using `useChat()` with agent memory, refer to the [Agent Memory section](/docs/agents/agent-memory) for key implementation details.
+> When using `useChat()` with agent memory, refer to the [Agent Memory section](/docs/v1/agents/agent-memory) for key implementation details.
 
 ### Using `useCompletion()`
 
@@ -473,7 +474,7 @@ export async function POST(req: Request) {
 
 ### Passing additional data
 
-`sendMessage()` allows you to pass additional data from the frontend to Mastra. This data can then be used on the server as `RuntimeContext`.
+`sendMessage()` allows you to pass additional data from the frontend to Mastra. This data can then be used on the server as `RequestContext`.
 
 ```typescript {16-26} title="app/test/chat-extra.tsx" copy
 "use client";
@@ -518,41 +519,41 @@ export function ChatExtra() {
 
 ```typescript {8,12} title="app/api/chat-extra/route.ts" copy
 import { mastra } from "../../../mastra";
-import { RuntimeContext } from "@mastra/core/runtime-context";
+import { RequestContext } from "@mastra/core/request-context";
 
 export async function POST(req: Request) {
   const { messages, data } = await req.json();
   const myAgent = mastra.getAgent("weatherAgent");
 
-  const runtimeContext = new RuntimeContext();
+  const requestContext = new RequestContext();
 
   if (data) {
     for (const [key, value] of Object.entries(data)) {
-      runtimeContext.set(key, value);
+      requestContext.set(key, value);
     }
   }
 
   const stream = await myAgent.stream(messages, {
-    runtimeContext,
+    requestContext,
     format: "aisdk",
   });
   return stream.toUIMessageStreamResponse();
 }
 ```
 
-### Handling `runtimeContext` with `server.middleware`
+### Handling `requestContext` with `server.middleware`
 
-You can also populate the `RuntimeContext` by reading custom data in a server middleware:
+You can also populate the `RequestContext` by reading custom data in a server middleware:
 
 ```typescript {8,17} title="mastra/index.ts" copy
-import { Mastra } from "@mastra/core/mastra";
+import { Mastra } from "@mastra/core";
 
 export const mastra = new Mastra({
   agents: { weatherAgent },
   server: {
     middleware: [
       async (c, next) => {
-        const runtimeContext = c.get("runtimeContext");
+        const requestContext = c.get("requestContext");
 
         if (c.req.method === "POST") {
           try {
@@ -561,7 +562,7 @@ export const mastra = new Mastra({
 
             if (body?.data) {
               for (const [key, value] of Object.entries(body.data)) {
-                runtimeContext.set(key, value);
+                requestContext.set(key, value);
               }
             }
           } catch {}
@@ -573,7 +574,7 @@ export const mastra = new Mastra({
 });
 ```
 
-> You can then access this data in your tools via the `runtimeContext` parameter. See the [Runtime Context documentation](/docs/server-db/runtime-context) for more details.
+> You can then access this data in your tools via the `requestContext` parameter. See the [Request Context documentation](/docs/v1/server-db/request-context) for more details.
 
 ## Migrating from AI SDK v4 to v5
 
@@ -629,7 +630,7 @@ const weatherTool = createTool({
     temperature: z.number(),
     conditions: z.string(),
   }),
-  execute: async ({ context }) => {
+  execute: async (inputData) => {
     return {
       temperature: 72,
       conditions: "sunny",
@@ -668,7 +669,7 @@ const tools = {
     outputSchema: z.object({
       result: z.number(),
     }),
-    execute: async ({ context }) => {
+    execute: async (inputData) => {
       // implementation...
       return { result: 0 };
     },

package/.docs/raw/frameworks/agentic-uis/assistant-ui.mdx

@@ -40,7 +40,7 @@ project-root
 Bootstrap your Mastra server:
 
 ```bash copy
-npx create-mastra@latest
+npx create-mastra@beta
 ```
 
 This command will launch an interactive wizard to help you scaffold a new Mastra project, including prompting you for a project name and setting up basic configurations.