@mastra/mcp-docs-server 1.0.0-beta.3 → 1.0.0-beta.5

package/.docs/raw/agents/guardrails.mdx

@@ -22,8 +22,7 @@ Use processors for content moderation, prompt injection prevention, response san
 
 Import and instantiate the relevant processor class, and pass it to your agent’s configuration using either the `inputProcessors` or `outputProcessors` option:
 
-```typescript {3,9-17} title="src/mastra/agents/moderated-agent.ts" showLineNumbers copy
-import { openai } from "@ai-sdk/openai";
+```typescript {2,8-16} title="src/mastra/agents/moderated-agent.ts" showLineNumbers copy
 import { Agent } from "@mastra/core/agent";
 import { ModerationProcessor } from "@mastra/core/processors";
 
@@ -31,10 +30,10 @@ export const moderatedAgent = new Agent({
   id: "moderated-agent",
   name: "Moderated Agent",
   instructions: "You are a helpful assistant",
-  model: openai("gpt-4o-mini"),
+  model: "openai/gpt-5.1",
   inputProcessors: [
     new ModerationProcessor({
-      model: openai("gpt-4.1-nano"),
+      model: "openai/gpt-4.1-nano",
       categories: ["hate", "harassment", "violence"],
       threshold: 0.7,
       strategy: "block",
@@ -52,7 +51,7 @@ Input processors are applied before user messages reach the language model. They
 
 The `UnicodeNormalizer` is an input processor that cleans and normalizes user input by unifying Unicode characters, standardizing whitespace, and removing problematic symbols, allowing the LLM to better understand user messages.
 
-```typescript {6-9} title="src/mastra/agents/normalized-agent.ts" showLineNumbers copy
+```typescript {8-11} title="src/mastra/agents/normalized-agent.ts" showLineNumbers copy
 import { UnicodeNormalizer } from "@mastra/core/processors";
 
 export const normalizedAgent = new Agent({
@@ -74,7 +73,7 @@ export const normalizedAgent = new Agent({
 
 The `PromptInjectionDetector` is an input processor that scans user messages for prompt injection, jailbreak attempts, and system override patterns. It uses an LLM to classify risky input and can block or rewrite it before it reaches the model.
 
-```typescript {6-11} title="src/mastra/agents/secure-agent.ts" showLineNumbers copy
+```typescript {8-13} title="src/mastra/agents/secure-agent.ts" showLineNumbers copy
 import { PromptInjectionDetector } from "@mastra/core/processors";
 
 export const secureAgent = new Agent({
@@ -83,7 +82,7 @@ export const secureAgent = new Agent({
   // ...
   inputProcessors: [
     new PromptInjectionDetector({
-      model: openai("gpt-4.1-nano"),
+      model: "openai/gpt-4.1-nano",
       threshold: 0.8,
       strategy: "rewrite",
       detectionTypes: ["injection", "jailbreak", "system-override"],
@@ -98,7 +97,7 @@ export const secureAgent = new Agent({
 
 The `LanguageDetector` is an input processor that detects and translates user messages into a target language, enabling multilingual support while maintaining consistent interaction. It uses an LLM to identify the language and perform the translation.
 
-```typescript {6-11} title="src/mastra/agents/multilingual-agent.ts" showLineNumbers copy
+```typescript {8-13} title="src/mastra/agents/multilingual-agent.ts" showLineNumbers copy
 import { LanguageDetector } from "@mastra/core/processors";
 
 export const multilingualAgent = new Agent({
@@ -107,7 +106,7 @@ export const multilingualAgent = new Agent({
   // ...
   inputProcessors: [
     new LanguageDetector({
-      model: openai("gpt-4.1-nano"),
+      model: "openai/gpt-4.1-nano",
       targetLanguages: ["English", "en"],
       strategy: "translate",
       threshold: 0.8,
@@ -126,7 +125,7 @@ Output processors are applied after the language model generates a response, but
 
 The `BatchPartsProcessor` is an output processor that combines multiple stream parts before emitting them to the client. This reduces network overhead and improves the user experience by consolidating small chunks into larger batches.
 
-```typescript {6-10} title="src/mastra/agents/batched-agent.ts" showLineNumbers copy
+```typescript {8-12} title="src/mastra/agents/batched-agent.ts" showLineNumbers copy
 import { BatchPartsProcessor } from "@mastra/core/processors";
 
 export const batchedAgent = new Agent({
@@ -149,7 +148,7 @@ export const batchedAgent = new Agent({
 
 The `TokenLimiterProcessor` is an output processor that limits the number of tokens in model responses. It helps manage cost and performance by truncating or blocking messages when the limit is exceeded.
 
-```typescript {6-10, 13-15} title="src/mastra/agents/limited-agent.ts" showLineNumbers copy
+```typescript {8-12} title="src/mastra/agents/limited-agent.ts" showLineNumbers copy
 import { TokenLimiterProcessor } from "@mastra/core/processors";
 
 export const limitedAgent = new Agent({
@@ -172,7 +171,7 @@ export const limitedAgent = new Agent({
 
 The `SystemPromptScrubber` is an output processor that detects and redacts system prompts or other internal instructions from model responses. It helps prevent unintended disclosure of prompt content or configuration details that could introduce security risks. It uses an LLM to identify and redact sensitive content based on configured detection types.
 
-```typescript {5-13} title="src/mastra/agents/scrubbed-agent.ts" copy showLineNumbers
+```typescript {7-16} title="src/mastra/agents/scrubbed-agent.ts" copy showLineNumbers
 import { SystemPromptScrubber } from "@mastra/core/processors";
 
 const scrubbedAgent = new Agent({
@@ -180,7 +179,7 @@ const scrubbedAgent = new Agent({
   name: "Scrubbed Agent",
   outputProcessors: [
     new SystemPromptScrubber({
-      model: openai("gpt-4.1-nano"),
+      model: "openai/gpt-4.1-nano",
       strategy: "redact",
       customPatterns: ["system prompt", "internal instructions"],
       includeDetections: true,
@@ -203,7 +202,7 @@ Hybrid processors can be applied either before messages are sent to the language
 
 The `ModerationProcessor` is a hybrid processor that detects inappropriate or harmful content across categories like hate, harassment, and violence. It can be used to moderate either user input or model output, depending on where it's applied. It uses an LLM to classify the message and can block or rewrite it based on your configuration.
 
-```typescript {6-11, 14-16} title="src/mastra/agents/moderated-agent.ts" showLineNumbers copy
+```typescript {8-13,16-18} title="src/mastra/agents/moderated-agent.ts" showLineNumbers copy
 import { ModerationProcessor } from "@mastra/core/processors";
 
 export const moderatedAgent = new Agent({
@@ -212,7 +211,7 @@ export const moderatedAgent = new Agent({
   // ...
   inputProcessors: [
     new ModerationProcessor({
-      model: openai("gpt-4.1-nano"),
+      model: "openai/gpt-4.1-nano",
       threshold: 0.7,
       strategy: "block",
       categories: ["hate", "harassment", "violence"],
@@ -232,7 +231,7 @@ export const moderatedAgent = new Agent({
 
 The `PIIDetector` is a hybrid processor that detects and removes personally identifiable information such as emails, phone numbers, and credit cards. It can redact either user input or model output, depending on where it's applied. It uses an LLM to identify sensitive content based on configured detection types.
 
-```typescript {6-13, 16-18} title="src/mastra/agents/private-agent.ts" showLineNumbers copy
+```typescript {8-15,18-20} title="src/mastra/agents/private-agent.ts" showLineNumbers copy
 import { PIIDetector } from "@mastra/core/processors";
 
 export const privateAgent = new Agent({
@@ -241,7 +240,7 @@ export const privateAgent = new Agent({
   // ...
   inputProcessors: [
     new PIIDetector({
-      model: openai("gpt-4.1-nano"),
+      model: "openai/gpt-4.1-nano",
       threshold: 0.6,
       strategy: "redact",
       redactionMethod: "mask",
@@ -306,7 +305,7 @@ Many of the built-in processors support a `strategy` parameter that controls how
 
 Most strategies allow the request to continue without interruption. When `block` is used, the processor calls its internal `abort()` function, which immediately stops the request and prevents any subsequent processors from running.
 
-```typescript {8} title="src/mastra/agents/private-agent.ts" showLineNumbers copy
+```typescript {10} title="src/mastra/agents/private-agent.ts" showLineNumbers copy
 import { PIIDetector } from "@mastra/core/processors";
 
 export const privateAgent = new Agent({
@@ -330,7 +329,7 @@ For example, if an agent uses the `PIIDetector` with `strategy: "block"` and the
 
 #### `.generate()` example
 
-```typescript {3-4, } showLineNumbers
+```typescript showLineNumbers
 const result = await agent.generate(
   "Is this credit card number valid?: 4543 1374 5089 4332",
 );
@@ -341,7 +340,7 @@ console.error(result.tripwireReason);
 
 #### `.stream()` example
 
-```typescript {4-5} showLineNumbers
+```typescript showLineNumbers
 const stream = await agent.stream(
   "Is this credit card number valid?: 4543 1374 5089 4332",
 );

package/.docs/raw/agents/human-in-the-loop-with-tools.mdx

@@ -59,13 +59,13 @@ const findUserTool = createTool({
   resumeSchema: z.object({
     name: z.string(),
   }),
-  execute: async (inputData, { workflow }) => {
-    if (!workflow.resumeData) {
-      return workflow.suspend({ message: "Please provide the name of the user" });
+  execute: async (inputData, { agent }) => {
+    if (!agent.resumeData) {
+      return agent.suspend({ message: "Please provide the name of the user" });
     }
 
     return {
-      name: workflow?.resumeData?.name,
+      name: agent?.resumeData?.name,
       email: "test@test.com",
     };
   },
@@ -73,11 +73,12 @@ const findUserTool = createTool({
 ```
 
 To continue execution, call `resumeStream` with the run’s `runId` and the `resumeData` that satisfies the `resumeSchema`. The workflow resumes from the suspension point and the tool completes with the new data.
+When using `suspend` directly in the tool, you don't need to add `requireToolApproval: true` to the agent `stream`/`generate` call, nor `requireApproval: true` to the tool creation.
 
 ```typescript {1} title="Resume a suspended tool call" showLineNumbers copy
 const resumedStream = await myAgent.resumeStream(
   { name: "John Smith" },
-  { runId: stream.runId },
+  { runId: stream.runId }
 );
 ```
 

package/.docs/raw/agents/networks.mdx

@@ -24,7 +24,6 @@ Mastra agent networks operate using these principles:
 An agent network is built around a top-level routing agent that delegates tasks to agents, workflows, and tools defined in its configuration. Memory is configured on the routing agent using the `memory` option, and `instructions` define the agent's routing behavior.
 
 ```typescript {22-23,26,29} title="src/mastra/agents/routing-agent.ts" showLineNumbers copy
-import { openai } from "@ai-sdk/openai";
 import { Agent } from "@mastra/core/agent";
 import { Memory } from "@mastra/memory";
 import { LibSQLStore } from "@mastra/libsql";
@@ -44,7 +43,7 @@ export const routingAgent = new Agent({
       Always respond with a complete report—no bullet points.
       Write in full paragraphs, like a blog post.
       Do not answer with incomplete or uncertain information.`,
-  model: openai("gpt-4o-mini"),
+  model: "openai/gpt-5.1",
   agents: {
     researchAgent,
     writingAgent,

package/.docs/raw/agents/overview.mdx

@@ -63,7 +63,7 @@ export const testAgent = new Agent({
   id: "test-agent",
   name: "Test Agent",
   instructions: "You are a helpful assistant.",
-  model: "openai/gpt-4o-mini",
+  model: "openai/gpt-5.1",
 });
 ```
 
@@ -112,7 +112,7 @@ export const testAgent = new Agent({
   id: "test-agent",
   name: "Test Agent",
   instructions: "You are a helpful assistant.",
-  model: openai("gpt-4o-mini"),
+  model: openai("gpt-5.1"),
 });
 ```
 
@@ -320,7 +320,7 @@ const response = await testAgentWithTools.generate(
         summary: z.string(),
         keywords: z.array(z.string()),
       }),
-      model: "openai/gpt-4o",
+      model: "openai/gpt-5.1",
     },
   },
 );
@@ -444,8 +444,8 @@ export const testAgent = new Agent({
     const userTier = requestContext.get("user-tier") as UserTier["user-tier"];
 
     return userTier === "enterprise"
-      ? openai("gpt-4o-mini")
-      : openai("gpt-4.1-nano");
+      ? "openai/gpt-5"
+      : "openai/gpt-4.1-nano";
   },
 });
 ```

package/.docs/raw/agents/using-tools.mdx

@@ -47,8 +47,7 @@ To make a tool available to an agent, add it to `tools`. Mentioning available to
 
 An agent can use multiple tools to handle more complex tasks by delegating specific parts to individual tools. The agent decides which tools to use based on the user's message, the agent's instructions, and the tool descriptions and schemas.
 
-```typescript {9,11} title="src/mastra/agents/weather-agent.ts" showLineNumbers copy
-import { openai } from "@ai-sdk/openai";
+```typescript {8,10} title="src/mastra/agents/weather-agent.ts" showLineNumbers copy
 import { Agent } from "@mastra/core/agent";
 import { weatherTool } from "../tools/weather-tool";
 
@@ -58,7 +57,7 @@ export const weatherAgent = new Agent({
   instructions: `
       You are a helpful weather assistant.
       Use the weatherTool to fetch current weather data.`,
-  model: openai("gpt-4o-mini"),
+  model: "openai/gpt-5.1",
   tools: { weatherTool },
 });
 ```
@@ -67,7 +66,7 @@ export const weatherAgent = new Agent({
 
 The agent uses the tool's `inputSchema` to infer what data the tool expects. In this case, it extracts `London` as the `location` from the message and passes it to the tool's inputData parameter.
 
-```typescript {5} title="src/test-tool.ts" showLineNumbers copy
+```typescript title="src/test-tool.ts" showLineNumbers copy
 import { mastra } from "./mastra";
 
 const agent = mastra.getAgent("weatherAgent");
@@ -79,7 +78,7 @@ const result = await agent.generate("What's the weather in London?");
 
 When multiple tools are available, the agent may choose to use one, several, or none, depending on what's needed to answer the query.
 
-```typescript {6} title="src/mastra/agents/weather-agent.ts" showLineNumbers copy
+```typescript {8} title="src/mastra/agents/weather-agent.ts" showLineNumbers copy
 import { weatherTool } from "../tools/weather-tool";
 import { activitiesTool } from "../tools/activities-tool";
 

package/.docs/raw/course/01-first-agent/05-running-playground.md

@@ -1,14 +1,14 @@
-# Running the Playground
+# Running Mastra Studio
 
-To test your agent as you build it, you'll need to run the Mastra playground:
+To test your agent as you build it, you'll need to run the Mastra Studio:
 
 ```bash
 npm run dev
 ```
 
-This will start the playground at `http://localhost:4111/`, where you can interact with your agent and test its capabilities.
+This will start the studio at `http://localhost:4111`, where you can interact with your agent and test its capabilities.
 
-The playground provides a user-friendly interface for testing your agent, allowing you to:
+The studio provides a user-friendly interface for testing your agent, allowing you to:
 
 - Send messages to your agent
 - See the agent's responses
@@ -16,4 +16,4 @@ The playground provides a user-friendly interface for testing your agent, allowi
 - Test tools directly
 - Debug any issues that arise
 
-In the next step, we'll create our first agent with a simple system prompt and test it in the playground.
+In the next step, we'll create our first agent with a simple system prompt and test it in the studio.

package/.docs/raw/course/01-first-agent/09-testing-your-agent.md

@@ -1,12 +1,12 @@
 # Testing Your Agent
 
-Now let's test our agent in the playground:
+Now let's test our agent in Mastra Studio:
 
 1. Make sure your development server is running with `npm run dev`
-2. Open the playground at http://localhost:4111/
+2. Open the studio at http://localhost:4111/
 3. You should see your "Financial Assistant Agent" in the list of agents
 4. Try sending a message like "Hello, can you help me analyze my spending?"
 
 At this point, your agent can respond to basic questions but doesn't have access to any transaction data. In the next step, we'll create a custom tool to fetch transaction data from a Google Sheet.
 
-Testing your agent in the playground is an important step in the development process. It allows you to see how your agent responds to different inputs and identify any issues that need to be addressed before deploying it to production.
+Testing your agent in the studio is an important step in the development process. It allows you to see how your agent responds to different inputs and identify any issues that need to be addressed before deploying it to production.

package/.docs/raw/course/01-first-agent/13-testing-your-tool.md

@@ -1,9 +1,9 @@
 # Testing Your Tool
 
-Let's test our tool and agent in the playground:
+Let's test our tool and agent in Mastra Studio:
 
 1. Make sure your development server is running with `npm run dev`
-2. Open the playground at http://localhost:4111/
+2. Open the studio at http://localhost:4111/
 3. You can test the tool directly in the Tools tab to make sure it's working
 4. Then, try asking your agent questions like:
    - "Can you show me my recent transactions?"
@@ -12,4 +12,4 @@ Let's test our tool and agent in the playground:
 
 Your agent should now be able to fetch the transaction data and answer questions about it. However, it doesn't yet have memory, so it won't remember previous conversations. We'll add that in the next step.
 
-Testing your tool directly in the playground is a great way to verify that it's working correctly before integrating it with your agent. This helps you identify and fix any issues with the tool itself before troubleshooting potential issues with the agent's use of the tool.
+Testing your tool directly in the studio is a great way to verify that it's working correctly before integrating it with your agent. This helps you identify and fix any issues with the tool itself before troubleshooting potential issues with the agent's use of the tool.

package/.docs/raw/course/01-first-agent/17-testing-memory.md

@@ -1,9 +1,9 @@
 # Testing Your Agent with Memory
 
-Let's test our agent's memory capabilities in the playground:
+Let's test our agent's memory capabilities in Mastra Studio:
 
 1. Make sure your development server is running with `npm run dev`
-2. Open the playground at http://localhost:4111/
+2. Open the studio at http://localhost:4111/
 3. Start a conversation with your agent by asking about transactions
 4. Then, ask a follow-up question that references the previous conversation, like:
    - "What was that largest transaction again?"

package/.docs/raw/course/04-workflows/07-using-playground.md

@@ -14,7 +14,7 @@ You should see output like:
 
 ```bash
 🚀 Mastra Dev Server starting...
-📊 Playground available at: http://localhost:4111
+📊 Studio available at: http://localhost:4111
 ```
 
 ## Accessing Workflows in Playground

package/.docs/raw/deployment/building-mastra.mdx

@@ -9,7 +9,7 @@ Mastra runs as a standard Node.js server and can be deployed across a wide range
 
 ## Default project structure
 
-The [getting started guide](/guides/v1/quickstarts/standalone-server) scaffolds a project with sensible defaults to help you begin quickly. By default, the CLI organizes application files under the `src/mastra/` directory, resulting in a structure similar to the following:
+The [getting started guide](/guides/v1/getting-started/quickstart) scaffolds a project with sensible defaults to help you begin quickly. By default, the CLI organizes application files under the `src/mastra/` directory, resulting in a structure similar to the following:
 
 ```
 src/

package/.docs/raw/deployment/cloud-providers/amazon-ec2.mdx

@@ -16,7 +16,7 @@ Deploy your Mastra applications to Amazon EC2 (Elastic Cloud Compute).
 This guide assumes your Mastra application has been created using the default
 `npx create-mastra@beta` command.
 For more information on how to create a new Mastra application,
-refer to our [getting started guide](/guides/v1/quickstarts/standalone-server)
+refer to our [getting started guide](/guides/v1/getting-started/quickstart)
 :::
 
 ## Prerequisites

package/.docs/raw/deployment/cloud-providers/aws-lambda.mdx

@@ -15,7 +15,7 @@ This approach allows you to run your Mastra server as a containerized Lambda fun
 This guide assumes your Mastra application has been created using the default
 `npx create-mastra@beta` command.
 For more information on how to create a new Mastra application,
-refer to our [getting started guide](/guides/v1/quickstarts/standalone-server)
+refer to our [getting started guide](/guides/v1/getting-started/quickstart)
 :::
 
 ## Prerequisites

package/.docs/raw/deployment/cloud-providers/azure-app-services.mdx

@@ -14,7 +14,7 @@ Deploy your Mastra applications to Azure App Services.
 This guide assumes your Mastra application has been created using the default
 `npx create-mastra@beta` command.
 For more information on how to create a new Mastra application,
-refer to our [getting started guide](/guides/v1/quickstarts/standalone-server)
+refer to our [getting started guide](/guides/v1/getting-started/quickstart)
 :::
 
 ## Prerequisites

package/.docs/raw/deployment/cloud-providers/digital-ocean.mdx

@@ -16,7 +16,7 @@ Deploy your Mastra applications to Digital Ocean's App Platform and Droplets.
 This guide assumes your Mastra application has been created using the default
 `npx create-mastra@beta` command.
 For more information on how to create a new Mastra application,
-refer to our [getting started guide](/guides/v1/quickstarts/standalone-server)
+refer to our [getting started guide](/guides/v1/getting-started/quickstart)
 :::
 
 <Tabs>

package/.docs/raw/deployment/cloud-providers/index.mdx

@@ -22,7 +22,7 @@ For self-hosted Node.js server deployment, see the [Creating A Mastra Server](/d
 
 Before deploying to a cloud provider, ensure you have:
 
-- A [Mastra application](/guides/v1/quickstarts/standalone-server)
+- A [Mastra application](/guides/v1/getting-started/quickstart)
 - Node.js `v22.13.0` or later
 - A GitHub repository for your application (required for most CI/CD setups)
 - Domain name management access (for SSL and HTTPS)

package/.docs/raw/deployment/mastra-cloud/observability.mdx

@@ -7,45 +7,47 @@ import { MastraCloudCallout } from "@site/src/components/MastraCloudCallout";
 
 # Understanding Tracing and Logs
 
-Mastra Cloud captures execution data to help you monitor your application's behavior in the production environment.
+Mastra Cloud provides full observability for production applications, giving you insight into how your agents and workflows behave. Observability can be enabled whether your application is deployed to Mastra Cloud, running locally, or hosted on your own infrastructure. Any Mastra project can send traces and logs to the platform regardless of where it's running.
 
-<MastraCloudCallout />
-
-## Logs
+For details on configuring observability, see the [Cloud Exporter](/docs/v1/observability/tracing/exporters/cloud) docs.
 
-You can view detailed logs for debugging and monitoring your application's behavior on the [Logs](/docs/v1/deployment/mastra-cloud/dashboard#logs) page of the Dashboard.
-
-![Dashboard logs](/img/mastra-cloud/mastra-cloud-dashboard-logs.jpg)
-
-Key features:
-
-Each log entry includes its severity level and a detailed message showing agent, workflow, or storage activity.
+<MastraCloudCallout />
 
 ## Traces
 
-More detailed traces are available for both agents and workflows by using a [logger](/docs/v1/logging) or enabling [observability](/docs/v1/observability/tracing/overview) using one of our [supported providers](/docs/v1/observability/tracing/overview#exporters).
+More detailed traces are available for both agents and workflows by enabling [observability](/docs/v1/observability/tracing/overview) using one of our [supported providers](/docs/v1/observability/tracing/overview#exporters).
 
 ### Agents
 
-With a [logger](/docs/v1/logging) enabled, you can view detailed outputs from your agents in the **Traces** section in Studio.
+With observability enabled, you can view detailed outputs from your agents in the **Traces** section in Studio.
 
 ![observability agents](/img/mastra-cloud/mastra-cloud-observability-agents.jpg)
 
 Key features:
 
-Tools passed to the agent during generation are standardized using `convertTools`. This includes retrieving client-side tools, memory tools, and tools exposed from workflows.
+Agent traces break a run into clear steps, model calls, tool calls, and intermediate chunks, each with timing, inputs, outputs, and errors. You can drill into any span to inspect prompts, token usage, and results, making it easy to diagnose issues and understand how the agent produced its output.
 
 ### Workflows
 
-With a [logger](/docs/v1/logging) enabled, you can view detailed outputs from your workflows in the **Traces** section in Studio.
+With observability enabled, you can view detailed outputs from your workflows in the **Traces** section in Studio.
 
 ![observability workflows](/img/mastra-cloud/mastra-cloud-observability-workflows.jpg)
 
 Key features:
 
-Workflows are created using `createWorkflow`, which sets up steps, metadata, and tools. You can run them with `runWorkflow` by passing input and options.
+Workflow traces capture each step in the run, including transitions, branching, timing, and any tool calls inside the workflow. You can inspect inputs, outputs, and errors for every step, making it easy to debug long-running or multi-step processes and understand how data flows through the workflow.
+
+## Logs
+
+You can view detailed logs for debugging and monitoring your application's behavior on the [Logs](/docs/v1/deployment/mastra-cloud/dashboard#logs) page of the Dashboard.
+
+![Dashboard logs](/img/mastra-cloud/mastra-cloud-dashboard-logs.jpg)
+
+Key features:
+
+Each log entry includes its severity level and a detailed message showing agent, workflow, or storage activity.
 
 ## Next steps
 
-- [Logging](/docs/v1/logging)
+- [Logging](/docs/v1/observability/logging)
 - [Tracing](/docs/v1/observability/tracing/overview)

package/.docs/raw/deployment/mastra-cloud/setting-up.mdx

@@ -18,7 +18,7 @@ This page explains how to set up a project on [Mastra Cloud](https://mastra.ai/c
 - A [Mastra Cloud](https://mastra.ai/cloud) account
 - A GitHub account / repository containing a Mastra application
 
-> See our [Getting started](/guides/v1/quickstarts/standalone-server) guide to scaffold out a new Mastra project with sensible defaults.
+> See our [Getting started](/guides/v1/getting-started/quickstart) guide to scaffold out a new Mastra project with sensible defaults.
 
 ## Setup and Deploy process
 

package/.docs/raw/deployment/overview.mdx

@@ -41,8 +41,8 @@ Mastra Cloud is a deployment platform that connects to your GitHub repository, a
 
 Mastra can be integrated with a variety of web frameworks. For example, see one of the following for a detailed guide.
 
-- [With Next.js](../frameworks/web-frameworks/next-js)
-- [With Astro](../frameworks/web-frameworks/astro)
+- [With Next.js](/guides/v1/getting-started/next-js)
+- [With Astro](/guides/v1/getting-started/astro)
 
 When integrated with a framework, Mastra typically requires no additional configuration for deployment.
 

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

@@ -7,14 +7,14 @@ 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/v1/frameworks/web-frameworks/next-js)
-- [With Astro](/docs/v1/frameworks/web-frameworks/astro)
+- [With Next.js](/guides/v1/getting-started/next-js)
+- [With Astro](/guides/v1/getting-started/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/v1/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](/guides/v1/getting-started/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/v1/deployment/overview), which is not supported in serverless environments:
 
@@ -30,7 +30,7 @@ export default nextConfig;
 
 ## With Astro on Vercel
 
-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.
+If you've integrated Mastra with Astro [by following our guide](/guides/v1/getting-started/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/v1/deployment/overview), which is not supported in serverless environments:
 
@@ -47,7 +47,7 @@ export default defineConfig({
 
 ## With Astro on Netlify
 
-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.
+If you've integrated Mastra with Astro [by following our guide](/guides/v1/getting-started/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/v1/deployment/overview), which is not supported in serverless environments:
 

package/.docs/raw/evals/custom-scorers.mdx

@@ -41,13 +41,12 @@ Every scorer starts with the `createScorer` factory function, which requires a n
 
 ```typescript
 import { createScorer } from '@mastra/core/evals';
-import { openai } from '@ai-sdk/openai';
 
 const glutenCheckerScorer = createScorer({
   name: 'Gluten Checker',
   description: 'Check if recipes contain gluten ingredients',
   judge: {                    // Optional: for prompt object steps
-    model: openai('gpt-4o'),
+    model: 'openai/gpt-5.1',
     instructions: 'You are a Chef that identifies if recipes contain gluten.'
   }
 })
@@ -245,7 +244,6 @@ Together, these components allow you to define custom evaluation logic using LLM
 > 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/evals";
 import { z } from "zod";
 
@@ -303,7 +301,7 @@ export const glutenCheckerScorer = createScorer({
   name: "Gluten Checker",
   description: "Check if the output contains any gluten",
   judge: {
-    model: openai("gpt-4o"),
+    model: "openai/gpt-4.1-nano",
     instructions: GLUTEN_INSTRUCTIONS,
   },
 })
@@ -338,7 +336,7 @@ Sets up the LLM model and defines its role as a domain expert.
 
 ```typescript
 judge: {
-  model: openai('gpt-4o'),
+  model: 'openai/gpt-4.1-nano',
   instructions: GLUTEN_INSTRUCTIONS,
 }
 ```

package/.docs/raw/evals/overview.mdx

@@ -37,7 +37,6 @@ You can add built-in scorers to your agents to automatically evaluate their outp
 
 ```typescript title="src/mastra/agents/evaluated-agent.ts" showLineNumbers copy
 import { Agent } from "@mastra/core/agent";
-import { openai } from "@ai-sdk/openai";
 import {
   createAnswerRelevancyScorer,
   createToxicityScorer,
@@ -47,11 +46,11 @@ export const evaluatedAgent = new Agent({
   // ...
   scorers: {
     relevancy: {
-      scorer: createAnswerRelevancyScorer({ model: openai("gpt-4o-mini") }),
+      scorer: createAnswerRelevancyScorer({ model: "openai/gpt-4.1-nano" }),
       sampling: { type: "ratio", rate: 0.5 },
     },
     safety: {
-      scorer: createToxicityScorer({ model: openai("gpt-4o-mini") }),
+      scorer: createToxicityScorer({ model: "openai/gpt-4.1-nano" }),
       sampling: { type: "ratio", rate: 1 },
     },
   },

package/.docs/raw/getting-started/project-structure.mdx

@@ -62,6 +62,6 @@ Top-level files define how your Mastra project is configured, built, and connect
 ## Next steps
 
 - Read more about [Mastra's features](/docs/v1#why-mastra).
-- Integrate Mastra with your frontend framework: [Next.js](/docs/v1/frameworks/web-frameworks/next-js), [React](/docs/v1/frameworks/web-frameworks/vite-react), or [Astro](/docs/v1/frameworks/web-frameworks/astro).
+- Integrate Mastra with your frontend framework: [Next.js](/guides/v1/getting-started/next-js), [React](/guides/v1/getting-started/vite-react), or [Astro](/guides/v1/getting-started/astro).
 - Build an agent from scratch following one of our [guides](/guides/v1).
 - Watch conceptual guides on our [YouTube channel](https://www.youtube.com/@mastra-ai) and [subscribe](https://www.youtube.com/@mastra-ai?sub_confirmation=1)!