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

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

@@ -1,5 +1,5 @@
 ---
-title: "Cloud Providers | Deployment | Mastra Docs"
+title: "Cloud Providers | Deployment"
 description: "Deploy your Mastra applications to popular cloud providers."
 ---
 
@@ -9,16 +9,19 @@ Standalone Mastra applications can be deployed to popular cloud providers, see o
 
 - [Amazon EC2](/docs/v1/deployment/cloud-providers/amazon-ec2)
 - [AWS Lambda](/docs/v1/deployment/cloud-providers/aws-lambda)
-- [Digital Ocean](/docs/v1/deployment/cloud-providers/digital-ocean)
 - [Azure App Services](/docs/v1/deployment/cloud-providers/azure-app-services)
+- [Cloudflare](/docs/v1/deployment/cloud-providers/cloudflare-deployer)
+- [Digital Ocean](/docs/v1/deployment/cloud-providers/digital-ocean)
+- [Netlify](/docs/v1/deployment/cloud-providers/netlify-deployer)
+- [Vercel](/docs/v1/deployment/cloud-providers/vercel-deployer)
 
-For self-hosted Node.js server deployment, see the [Creating A Mastra Server](/docs/v1/deployment/server-deployment) guide.
+For self-hosted Node.js server deployment, see the [Creating A Mastra Server](/docs/v1/deployment/building-mastra) guide.
 
 ## Prerequisites
 
 Before deploying to a cloud provider, ensure you have:
 
-- A [Mastra application](/docs/v1/getting-started/installation)
+- 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)
@@ -26,33 +29,27 @@ Before deploying to a cloud provider, ensure you have:
 
 ## LibSQLStore
 
-`LibSQLStore` writes to the local filesystem, which is not supported in cloud environments that use ephemeral file systems. If you're deploying to platforms like **AWS Lambda**, **Azure App Services**, or **Digital Ocean App Platform**, you **must remove** all usage of `LibSQLStore`.
+`LibSQLStore` writes to the local filesystem, which is not supported in cloud environments that use ephemeral file systems. If you're deploying to platforms like AWS Lambda, Netlify, Azure App Services, or Digital Ocean App Platform, you must remove all usage of `LibSQLStore`.
 
-Specifically, ensure you've removed it from both `src/mastra/index.ts` and `src/mastra/agents/weather-agent.ts`:
+Specifically, ensure you've removed it from all Mastra files, including configuration on the main Mastra instance and any agents using it, e.g. for memory storage.
 
-```typescript title="src/mastra/index.ts" showLineNumbers
-export const mastra = new Mastra({
-  // ...
-  storage: new LibSQLStore({
-    id: 'mastra-storage',
-    // [!code --]
-    // stores telemetry, scorer results, ... into memory storage, if it needs to persist, change to file:../mastra.db // [!code --]
-    url: ":memory:", // [!code --]
-  }), //[!code --]
-});
+```diff title="src/mastra/index.ts"
+ export const mastra = new Mastra({
+-  storage: new LibSQLStore({
+-    id: 'mastra-storage',
+-    url: ":memory:",
+-  }),
+ });
 ```
 
-```typescript title="src/mastra/agents/weather-agent.ts" showLineNumbers
-export const weatherAgent = new Agent({
-  id: "weather-agent",
-  // ..
-  memory: new Memory({
-    // [!code --]
-    storage: new LibSQLStore({
-      id: 'mastra-storage',
-      // [!code --]
-      url: "file:../mastra.db", // path is relative to the .mastra/output directory // [!code --]
-    }), // [!code --]
-  }), //  [!code --]
-});
+```diff
+ export const weatherAgent = new Agent({
+   id: "weather-agent",
+   memory: new Memory({
+-    storage: new LibSQLStore({
+-      id: 'mastra-storage',
+-      url: "file:../mastra.db",
+-    }),
+   }),
+ });
 ```

package/.docs/raw/deployment/{serverless-platforms → cloud-providers}/netlify-deployer.mdx

@@ -1,5 +1,5 @@
 ---
-title: "NetlifyDeployer | Deployment | Mastra Docs"
+title: "NetlifyDeployer | Deployment"
 description: "Learn how to deploy a Mastra application to Netlify using the Mastra NetlifyDeployer"
 ---
 
@@ -15,12 +15,11 @@ npm install @mastra/deployer-netlify@beta
 
 ## Usage example
 
-```typescript title="src/mastra/index.ts" showLineNumbers copy
+```typescript title="src/mastra/index.ts" copy
 import { Mastra } from "@mastra/core";
 import { NetlifyDeployer } from "@mastra/deployer-netlify";
 
 export const mastra = new Mastra({
-  // ...
   deployer: new NetlifyDeployer(),
 });
 ```
@@ -43,32 +42,64 @@ Your project is now configured with automatic deployments which occur whenever y
 
 ## Manual deployment
 
-Manual deployments are also possible using the [Netlify CLI](https://docs.netlify.com/cli/get-started/). With the Netlify CLI installed run the following from your project root to deploy your application.
+Manual deployments are also possible using the [Netlify CLI](https://docs.netlify.com/cli/get-started/). With the Netlify CLI installed run the following from your project root to deploy your application. You can also run `netlify dev` from your project root to test your Mastra application locally.
 
 ```bash copy
 netlify deploy --prod
 ```
 
-> You can also run `netlify dev` from your project root to test your Mastra application locally.
+:::warning
 
-## Build output
+When using `netlify deploy` instead of continuous deployment, you need to create a `netlify.toml` file with these contents:
+
+```toml
+[build]
+  command = "npm run build"
+  publish = ".netlify/v1/functions"
 
-The build output for Mastra applications using the `NetlifyDeployer` includes all agents, tools, and workflows in your project, along with Mastra specific files required to run your application on Netlify.
+[functions]
+  directory = ".netlify/v1/functions"
+  node_bundler = "none"
+  included_files = [".netlify/v1/functions/**"]
 
+[[redirects]]
+  from = "/*"
+  to = "/.netlify/functions/api/:splat"
+  status = 200
+
+[build.environment]
+  NODE_VERSION = "22.13.0"
 ```
-.netlify/
-└── v1/
-    ├── functions/
-    │   └── api/
-    │       └── index.mjs
-    └── config.json
-package.json
+
+Adjust the `build.command` to your project.
+
+:::
+
+## Build output
+
+The build output for Mastra applications using the `NetlifyDeployer` includes all agents, tools, and workflows in your project, along with Mastra-specific files required to run your application on Netlify.
+
+```bash
+your-project/
+└── .netlify/
+    └── v1/
+        ├── config.json
+        └── functions/
+            └── api/
+                ├── index.js
+                ├── package.json
+                └── node_modules/
 ```
 
 The `NetlifyDeployer` automatically generates a `config.json` configuration file in `.netlify/v1` with the following settings:
 
 ```json
 {
+  "functions": {
+    "directory": ".netlify/v1/functions",
+    "node_bundler": "none",
+    "included_files": [".netlify/v1/functions/**"]
+  },
   "redirects": [
     {
       "force": true,

package/.docs/raw/deployment/{serverless-platforms → cloud-providers}/vercel-deployer.mdx

@@ -1,5 +1,5 @@
 ---
-title: "VercelDeployer | Deployment | Mastra Docs"
+title: "VercelDeployer | Deployment"
 description: "Learn how to deploy a Mastra application to Vercel using the Mastra VercelDeployer"
 ---
 

package/.docs/raw/{mastra-cloud → deployment/mastra-cloud}/dashboard.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Navigating the Dashboard | Mastra Cloud | Mastra Docs"
+title: "Navigating the Dashboard | Mastra Cloud"
 description: Details of each feature available in Mastra Cloud
 ---
 
@@ -7,7 +7,7 @@ import { MastraCloudCallout } from "@site/src/components/MastraCloudCallout";
 
 # Navigating the Dashboard
 
-This page explains how to navigate the Mastra Cloud dashboard, where you can configure your project, view deployment details, and interact with agents and workflows using the built-in [Studio](/docs/v1/mastra-cloud/dashboard#studio).
+This page explains how to navigate the Mastra Cloud dashboard, where you can configure your project, view deployment details, and interact with agents and workflows using the built-in [Studio](/docs/v1/deployment/mastra-cloud/dashboard#studio).
 
 <MastraCloudCallout />
 
@@ -97,4 +97,4 @@ Each MCP Server includes API endpoints for HTTP and SSE, along with IDE configur
 
 ## Next steps
 
-- [Understanding Tracing and Logs](/docs/v1/mastra-cloud/observability)
+- [Understanding Tracing and Logs](/docs/v1/deployment/mastra-cloud/observability)

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

@@ -0,0 +1,53 @@
+---
+title: "Understanding Tracing and Logs | Mastra Cloud"
+description: Monitoring and debugging tools for Mastra Cloud deployments
+---
+
+import { MastraCloudCallout } from "@site/src/components/MastraCloudCallout";
+
+# Understanding Tracing and Logs
+
+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.
+
+For details on configuring observability, see the [Cloud Exporter](/docs/v1/observability/tracing/exporters/cloud) docs.
+
+<MastraCloudCallout />
+
+## Traces
+
+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 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:
+
+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 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:
+
+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/observability/logging)
+- [Tracing](/docs/v1/observability/tracing/overview)

package/.docs/raw/{mastra-cloud → deployment/mastra-cloud}/overview.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Mastra Cloud | Mastra Cloud | Mastra Docs"
+title: "Mastra Cloud | Mastra Cloud"
 description: Deployment and monitoring service for Mastra applications
 ---
 
@@ -7,7 +7,7 @@ import { MastraCloudCallout } from "@site/src/components/MastraCloudCallout";
 
 # Mastra Cloud
 
-[Mastra Cloud](https://mastra.ai/cloud) is a platform for deploying, managing, monitoring, and debugging Mastra applications. When you [deploy](/docs/v1/mastra-cloud/setting-up) your application, Mastra Cloud exposes your agents, tools, and workflows as REST API endpoints.
+[Mastra Cloud](https://mastra.ai/cloud) is a platform for deploying, managing, monitoring, and debugging Mastra applications. When you [deploy](/docs/v1/deployment/mastra-cloud/setting-up) your application, Mastra Cloud exposes your agents, tools, and workflows as REST API endpoints.
 
 <MastraCloudCallout />
 
@@ -62,4 +62,4 @@ Mastra Cloud is purpose-built for Mastra agents, tools, and workflows. It handle
 
 ## Next steps
 
-- [Setting Up and Deploying](/docs/v1/mastra-cloud/setting-up)
+- [Setting Up and Deploying](/docs/v1/deployment/mastra-cloud/setting-up)

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

@@ -1,5 +1,5 @@
 ---
-title: "Setting Up and Deploying | Mastra Cloud | Mastra Docs"
+title: "Setting Up and Deploying | Mastra Cloud"
 description: Configuration steps for Mastra Cloud projects
 ---
 
@@ -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](/docs/v1/getting-started/installation) 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
 
@@ -98,8 +98,8 @@ Your project is now configured with automatic deployments which occur whenever y
 
 ## Testing your application
 
-After a successful deployment you can test your agents and workflows [Studio](/docs/v1/mastra-cloud/dashboard#studio) in Mastra Cloud, or interact with them using our [Client SDK](/docs/v1/server-db/mastra-client).
+After a successful deployment you can test your agents and workflows [Studio](/docs/v1/deployment/mastra-cloud/dashboard#studio) in Mastra Cloud, or interact with them using our [Client SDK](/docs/v1/server-db/mastra-client).
 
 ## Next steps
 
-- [Navigating the Dashboard](/docs/v1/mastra-cloud/dashboard)
+- [Navigating the Dashboard](/docs/v1/deployment/mastra-cloud/dashboard)

package/.docs/raw/deployment/monorepo.mdx

@@ -1,11 +1,11 @@
 ---
-title: "Monorepo Deployment | Deployment | Mastra Docs"
+title: "Monorepo Deployment | Deployment"
 description: Learn how to deploy Mastra applications that are part of a monorepo setup
 ---
 
 # Monorepo Deployment
 
-Deploying Mastra in a monorepo follows the same approach as deploying a standalone application. While some [Cloud](./cloud-providers/) or [Serverless Platform](./serverless-platforms/) providers may introduce extra requirements, the core setup is the same.
+Deploying Mastra in a monorepo follows the same approach as deploying a standalone application. While some [Cloud](./cloud-providers/) or [Serverless Platform](./cloud-providers/) providers may introduce extra requirements, the core setup is the same.
 
 ## Example monorepo
 
@@ -44,7 +44,7 @@ api/
 
 ## Deployment configuration
 
-The image below shows how to select `apps/api` as the project root when deploying to [Mastra Cloud](../mastra-cloud/overview). While the interface may differ between providers, the configuration remains the same.
+The image below shows how to select `apps/api` as the project root when deploying to [Mastra Cloud](./mastra-cloud/overview). While the interface may differ between providers, the configuration remains the same.
 
 ![Deployment configuration](/img/monorepo/monorepo-mastra-cloud.jpg)
 

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

@@ -1,5 +1,5 @@
 ---
-title: "Deployment Overview | Deployment | Mastra Docs"
+title: "Deployment Overview | Deployment"
 description: Learn about different deployment options for your Mastra applications
 ---
 
@@ -23,7 +23,7 @@ Mastra offers multiple deployment options to suit your application's needs, from
 - Node.js `v22.13.0` or later
 - Bun
 - Deno
-- [Cloudflare](../deployment/serverless-platforms/cloudflare-deployer)
+- [Cloudflare](../deployment/cloud-providers/cloudflare-deployer)
 
 ### Mastra Cloud
 
@@ -35,14 +35,14 @@ Mastra Cloud is a deployment platform that connects to your GitHub repository, a
 - Comprehensive logs and traces
 - Custom domains for each project
 
-[View Mastra Cloud documentation →](../mastra-cloud/overview)
+[View Mastra Cloud documentation →](./mastra-cloud/overview)
 
 ### With a Web Framework
 
 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.
 
@@ -57,7 +57,7 @@ You can deploy Mastra as a standard Node.js HTTP server, which gives you full co
 - Deploy to VMs, containers, or PaaS platforms
 - Ideal for integrating with existing Node.js applications
 
-[Server deployment guide →](./server-deployment)
+[Building Mastra →](./building-mastra)
 
 ### Serverless Platforms
 
@@ -68,7 +68,7 @@ Mastra provides platform-specific deployers for popular serverless platforms, en
 - Simplified deployment process
 - Automatic scaling through the platform
 
-[Serverless deployment guide →](./server-deployment)
+[Building Mastra →](./building-mastra)
 
 ## Client Configuration
 

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

@@ -1,5 +1,5 @@
 ---
-title: "Web Framework Integration | Deployment | Mastra Docs"
+title: "Web Framework Integration | Deployment"
 description: "Learn how Mastra can be deployed when integrated with a Web Framework"
 ---
 
@@ -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/{off-the-shelf-scorers.mdx → built-in-scorers.mdx}

@@ -1,5 +1,5 @@
 ---
-title: "Built-in Scorers | Evals | Mastra Docs"
+title: "Built-in Scorers | Evals"
 description: "Overview of Mastra's ready-to-use scorers for evaluating AI outputs across quality, safety, and performance dimensions."
 ---
 
@@ -7,14 +7,16 @@ description: "Overview of Mastra's ready-to-use scorers for evaluating AI output
 
 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
+To create your own scorers, see the [Custom Scorers](/docs/v1/evals/custom-scorers) guide.
 
-### Accuracy and Reliability
+## 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)
+- [`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)
@@ -23,7 +25,7 @@ These scorers evaluate how correct, truthful, and complete your agent's answers
 - [`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
+### Context quality
 
 These scorers evaluate the quality and relevance of context used in generating responses:
 
@@ -31,16 +33,16 @@ These scorers evaluate the quality and relevance of context used in generating r
 - [`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
+>
+>- 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:
 

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

@@ -1,5 +1,5 @@
 ---
-title: "Custom Scorers | Evals | Mastra Docs"
+title: "Custom Scorers | Evals"
 ---
 
 # Custom scorers
@@ -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

@@ -1,5 +1,5 @@
 ---
-title: "Scorers overview | Evals | Mastra Docs"
+title: "Scorers overview | Evals"
 description: Overview of scorers in Mastra, detailing their capabilities for evaluating AI outputs and measuring performance.
 ---
 
@@ -33,11 +33,10 @@ npm install @mastra/evals@beta
 
 ### 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/v1/evals/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/built-in-scorers) for all available options.
 
 ```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 },
     },
   },
@@ -135,5 +134,5 @@ 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/v1/evals/custom-scorers) guide
-- Explore built-in scorers in the [Off-the-shelf Scorers](/docs/v1/evals/off-the-shelf-scorers) section
+- Explore built-in scorers in the [Built-in Scorers](/docs/v1/evals/built-in-scorers) section
 - Test scorers with [Studio](/docs/v1/getting-started/studio)

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

@@ -1,5 +1,5 @@
 ---
-title: "Running Scorers in CI | Evals | Mastra Docs"
+title: "Running Scorers in CI | Evals"
 description: "Learn how to run scorer experiments in your CI/CD pipeline using the runEvals function."
 ---
 
@@ -49,8 +49,6 @@ describe('Weather Agent Tests', () => {
 });
 ```
 
-View the full example [here](/examples/v1/evals/running-in-ci)
-
 ## Understanding Results
 
 The `runEvals` function returns an object with:
@@ -109,5 +107,5 @@ describe('Weather Agent Tests', () => {
 ## Next Steps
 
 - Learn about [creating custom scorers](/docs/v1/evals/custom-scorers)
-- Explore [off-the-shelf scorers](/docs/v1/evals/off-the-shelf-scorers)
+- Explore [built-in scorers](/docs/v1/evals/built-in-scorers)
 - Read the [runEvals API reference](/reference/v1/evals/run-evals)