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

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@latest` command.
 For more information on how to create a new Mastra application,
-refer to our [getting started guide](/docs/getting-started/installation)
+refer to our [getting started guide](/docs/v1/getting-started/installation)
 :::
 
 ## Prerequisites
@@ -44,6 +44,7 @@ Lambda functions have limitations with file system storage. Configure your Mastr
 import { LibSQLStore } from "@mastra/libsql";
 
 const storage = new LibSQLStore({
+  id: 'mastra-storage',
   url: ":memory:", // in-memory storage
 });
 ```
@@ -56,12 +57,13 @@ For persistent memory across Lambda invocations, use external storage providers
 import { LibSQLStore } from "@mastra/libsql";
 
 const storage = new LibSQLStore({
+  id: 'mastra-storage',
   url: "libsql://your-database.turso.io", // External Turso database
   authToken: process.env.TURSO_AUTH_TOKEN,
 });
 ```
 
-For more memory configuration options, see the [Memory documentation](/docs/memory/overview).
+For more memory configuration options, see the [Memory documentation](/docs/v1/memory/overview).
 
 ## Creating a Dockerfile
 
@@ -90,7 +92,7 @@ ENV READINESS_CHECK_PATH="/api"
 
 EXPOSE 8080
 
-CMD ["node", "--import=./.mastra/output/instrumentation.mjs", ".mastra/output/index.mjs"]
+CMD ["node", ".mastra/output/index.mjs"]
 ```
 
 ## Building and Deploying
@@ -214,7 +216,7 @@ Once deployed, test your Lambda function:
 2. Visit the URL in your browser to see your Mastra's server home screen
 3. Test your agents and workflows using the generated API endpoints
 
-For more information about available API endpoints, see the [Server documentation](/docs/deployment/server-deployment).
+For more information about available API endpoints, see the [Server documentation](/docs/v1/deployment/server-deployment).
 
 ## Connecting your client
 
@@ -287,6 +289,6 @@ For production deployments:
 
 ## Next steps
 
-- [Mastra Client SDK](/reference/client-js/mastra-client)
+- [Mastra Client SDK](/reference/v1/client-js/mastra-client)
 - [AWS Lambda documentation](https://docs.aws.amazon.com/lambda/)
 - [AWS Lambda Web Adapter](https://github.com/awslabs/aws-lambda-web-adapter)

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@latest` command.
 For more information on how to create a new Mastra application,
-refer to our [getting started guide](/docs/getting-started/installation)
+refer to our [getting started guide](/docs/v1/getting-started/installation)
 :::
 
 ## Prerequisites
@@ -141,7 +141,7 @@ Access your deployed application:
 
 You can now connect to your Mastra server from your client application using a `MastraClient` from the `@mastra/client-js` package.
 
-Refer to the [`MastraClient` documentation](/reference/client-js/mastra-client) for more information.
+Refer to the [`MastraClient` documentation](/reference/v1/client-js/mastra-client) for more information.
 
 ```typescript copy showLineNumbers
 import { MastraClient } from "@mastra/client-js";
@@ -159,7 +159,7 @@ such as `LibSQLStore` with a file URL. Consider using cloud-based storage soluti
 
 ## Next steps
 
-- [Mastra Client SDK](/reference/client-js/mastra-client)
+- [Mastra Client SDK](/reference/v1/client-js/mastra-client)
 - [Configure custom domains](https://docs.microsoft.com/en-us/azure/app-service/app-service-web-tutorial-custom-domain)
 - [Enable HTTPS](https://docs.microsoft.com/en-us/azure/app-service/configure-ssl-bindings)
 - [Azure App Service documentation](https://docs.microsoft.com/en-us/azure/app-service/)

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

@@ -119,7 +119,7 @@ Deploy your Mastra application to Digital Ocean's Droplets.
 - A domain name with an A record pointing to your droplet
 - A reverse proxy configured (e.g., using [nginx](https://nginx.org/))
 - SSL certificate configured (e.g., using [Let's Encrypt](https://letsencrypt.org/))
-- Node.js 18+ installed on your droplet
+- Node.js 22.13.0 or later installed on your droplet
 
 ### Deployment Steps
 
@@ -201,7 +201,7 @@ npm run build
 Run the application
 
 ```bash copy
-node --import=./.mastra/output/instrumentation.mjs --env-file=".env" .mastra/output/index.mjs
+node --env-file=".env" .mastra/output/index.mjs
 ```
 
 :::note
@@ -220,7 +220,7 @@ Your Mastra application will run on port 4111 by default. Ensure your reverse pr
 
 You can now connect to your Mastra server from your client application using a `MastraClient` from the `@mastra/client-js` package.
 
-Refer to the [`MastraClient` documentation](/docs/server-db/mastra-client) for more information.
+Refer to the [`MastraClient` documentation](/docs/v1/server-db/mastra-client) for more information.
 
 ```typescript copy showLineNumbers
 import { MastraClient } from "@mastra/client-js";
@@ -232,6 +232,6 @@ const mastraClient = new MastraClient({
 
 ## Next steps
 
-- [Mastra Client SDK](/reference/client-js/mastra-client)
+- [Mastra Client SDK](/reference/v1/client-js/mastra-client)
 - [Digital Ocean App Platform documentation](https://docs.digitalocean.com/products/app-platform/)
 - [Digital Ocean Droplets documentation](https://docs.digitalocean.com/products/droplets/)

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

@@ -7,19 +7,19 @@ description: "Deploy your Mastra applications to popular cloud providers."
 
 Standalone Mastra applications can be deployed to popular cloud providers, see one of the following guides for more information:
 
-- [Amazon EC2](/docs/deployment/cloud-providers/amazon-ec2)
-- [AWS Lambda](/docs/deployment/cloud-providers/aws-lambda)
-- [Digital Ocean](/docs/deployment/cloud-providers/digital-ocean)
-- [Azure App Services](/docs/deployment/cloud-providers/azure-app-services)
+- [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)
 
-For self-hosted Node.js server deployment, see the [Creating A Mastra Server](/docs/deployment/server-deployment) guide.
+For self-hosted Node.js server deployment, see the [Creating A Mastra Server](/docs/v1/deployment/server-deployment) guide.
 
 ## Prerequisites
 
 Before deploying to a cloud provider, ensure you have:
 
-- A [Mastra application](/docs/getting-started/installation)
-- Node.js `v20.0` or higher
+- A [Mastra application](/docs/v1/getting-started/installation)
+- 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)
 - Basic familiarity with server setup (e.g. Nginx, environment variables)
@@ -34,8 +34,9 @@ Specifically, ensure you've removed it from both `src/mastra/index.ts` and `src/
 export const mastra = new Mastra({
   // ...
   storage: new LibSQLStore({
+    id: 'mastra-storage',
     // [!code --]
-    // stores telemetry, evals, ... into memory storage, if it needs to persist, change to file:../mastra.db // [!code --]
+    // stores telemetry, scorer results, ... into memory storage, if it needs to persist, change to file:../mastra.db // [!code --]
     url: ":memory:", // [!code --]
   }), //[!code --]
 });
@@ -43,10 +44,12 @@ export const mastra = new Mastra({
 
 ```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 --]

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

@@ -66,7 +66,7 @@ Common issues to watch for when deploying Mastra in a monorepo:
 Use `transpilePackages` to compile TypeScript workspace packages or libraries. List package names exactly as they appear in each `package.json`. Use `externals` to exclude dependencies resolved at runtime, and `sourcemap` to emit readable stack traces.
 
 ```typescript title="src/mastra/index.ts" showLineNumbers copy
-import { Mastra } from "@mastra/core/mastra";
+import { Mastra } from "@mastra/core";
 
 export const mastra = new Mastra({
   // ...
@@ -78,7 +78,7 @@ export const mastra = new Mastra({
 });
 ```
 
-> See [Mastra Class](/reference/core/mastra-class) for more configuration options.
+> See [Mastra Class](/reference/v1/core/mastra-class) for more configuration options.
 
 ## Supported monorepos
 

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

@@ -20,7 +20,7 @@ Mastra offers multiple deployment options to suit your application's needs, from
 
 ### Runtime support
 
-- Node.js `v20.0` or higher
+- Node.js `v22.13.0` or later
 - Bun
 - Deno
 - [Cloudflare](../deployment/serverless-platforms/cloudflare-deployer)
@@ -79,4 +79,4 @@ Once your Mastra application is deployed, you'll need to configure your client t
 - Retries and error handling
 - Support for streaming responses
 
-[Client configuration guide →](/docs/server-db/mastra-client)
+[Client configuration guide →](/docs/v1/server-db/mastra-client)

package/.docs/raw/deployment/server-deployment.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](/docs/getting-started/installation) 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](/docs/v1/getting-started/installation) 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/
@@ -45,7 +45,7 @@ The build process follows these steps:
 1. **Locates entry file**: Finds `index.ts` or `index.js` in your specified directory (default: `src/mastra/`).
 2. **Creates build directory**: Generates a `.mastra/` directory containing:
    - **`.build`**: Contains dependency analysis, bundled dependencies, and build configuration files.
-   - **`output`**: Contains the production-ready application bundle with `index.mjs`, `instrumentation.mjs`, and project-specific files.
+   - **`output`**: Contains the production-ready application bundle with `index.mjs` and project-specific files.
 3. **Copies static assets**: Copies the `public/` folder contents to the `output` directory for serving static files.
 4. **Bundles code**: Uses Rollup with tree shaking and source maps for optimization.
 5. **Generates server**: Creates a [Hono](https://hono.dev) HTTP server ready for deployment.
@@ -71,11 +71,3 @@ Start the HTTP server:
 ```bash copy
 node .mastra/output/index.mjs
 ```
-
-## Enable Telemetry
-
-To enable telemetry and observability, load the instrumentation file:
-
-```bash copy
-node --import=./.mastra/output/instrumentation.mjs .mastra/output/index.mjs
-```

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

@@ -5,7 +5,7 @@ description: "Learn how to deploy a Mastra application to Cloudflare using the M
 
 # CloudflareDeployer
 
-The `CloudflareDeployer` class handles deployment of standalone Mastra applications to Cloudflare Workers. It manages configuration, deployment, and extends the base [Deployer](/reference/deployer/) class with Cloudflare specific functionality.
+The `CloudflareDeployer` class handles deployment of standalone Mastra applications to Cloudflare Workers. It manages configuration, deployment, and extends the base [Deployer](/reference/v1/deployer/) class with Cloudflare specific functionality.
 
 ## Installation
 
@@ -16,7 +16,7 @@ npm install @mastra/deployer-cloudflare@latest
 ## Usage example
 
 ```typescript title="src/mastra/index.ts" showLineNumbers copy
-import { Mastra } from "@mastra/core/mastra";
+import { Mastra } from "@mastra/core";
 import { CloudflareDeployer } from "@mastra/deployer-cloudflare";
 
 export const mastra = new Mastra({
@@ -30,7 +30,7 @@ export const mastra = new Mastra({
 });
 ```
 
-> See the [CloudflareDeployer](/reference/deployer/cloudflare) API reference for all available configuration options.
+> See the [CloudflareDeployer](/reference/v1/deployer/cloudflare) API reference for all available configuration options.
 
 ## Manual deployment
 
@@ -83,4 +83,4 @@ The `CloudflareDeployer` automatically generates a `wrangler.json` configuration
 
 ## Next steps
 
-- [Mastra Client SDK](/reference/client-js/mastra-client)
+- [Mastra Client SDK](/reference/v1/client-js/mastra-client)

package/.docs/raw/deployment/serverless-platforms/index.mdx

@@ -7,19 +7,19 @@ description: "Build and deploy Mastra applications using platform-specific deplo
 
 Standalone Mastra applications can be deployed to popular serverless platforms using one of our deployer packages:
 
-- [Cloudflare](/docs/deployment/serverless-platforms/cloudflare-deployer)
-- [Netlify](/docs/deployment/serverless-platforms/netlify-deployer)
-- [Vercel](/docs/deployment/serverless-platforms/vercel-deployer)
+- [Cloudflare](/docs/v1/deployment/serverless-platforms/cloudflare-deployer)
+- [Netlify](/docs/v1/deployment/serverless-platforms/netlify-deployer)
+- [Vercel](/docs/v1/deployment/serverless-platforms/vercel-deployer)
 
-Deployers **aren't** required when integrating Mastra with a framework. See [Web Framework Integration](/docs/deployment/web-framework) for more information.
+Deployers **aren't** required when integrating Mastra with a framework. See [Web Framework Integration](/docs/v1/deployment/web-framework) for more information.
 
-For self-hosted Node.js server deployment, see the [Creating A Mastra Server](/docs/deployment/server-deployment) guide.
+For self-hosted Node.js server deployment, see the [Creating A Mastra Server](/docs/v1/deployment/server-deployment) guide.
 
 ## Prerequisites
 
 Before you begin, ensure you have:
 
-- Node.js `v20.0` or higher
+- Node.js `v22.13.0` or later
 - If using a platform-specific deployer:
   - An account with your chosen platform
   - Required API keys or credentials
@@ -34,8 +34,9 @@ Specifically, ensure you've removed it from both `src/mastra/index.ts` and `src/
 export const mastra = new Mastra({
   // ...
   storage: new LibSQLStore({
+    id: 'mastra-storage',
     // [!code --]
-    // stores telemetry, evals, ... into memory storage, if it needs to persist, change to file:../mastra.db // [!code --]
+    // stores telemetry, scorer results, ... into memory storage, if it needs to persist, change to file:../mastra.db // [!code --]
     url: ":memory:", // [!code --]
   }), //[!code --]
 });
@@ -43,10 +44,12 @@ export const mastra = new Mastra({
 
 ```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 --]

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

@@ -5,7 +5,7 @@ description: "Learn how to deploy a Mastra application to Netlify using the Mast
 
 # NetlifyDeployer
 
-The `NetlifyDeployer` class handles deployment of standalone Mastra applications to Netlify. It manages configuration, deployment, and extends the base [Deployer](/reference/deployer/) class with Netlify specific functionality.
+The `NetlifyDeployer` class handles deployment of standalone Mastra applications to Netlify. It manages configuration, deployment, and extends the base [Deployer](/reference/v1/deployer/) class with Netlify specific functionality.
 
 ## Installation
 
@@ -16,7 +16,7 @@ npm install @mastra/deployer-netlify@latest
 ## Usage example
 
 ```typescript title="src/mastra/index.ts" showLineNumbers copy
-import { Mastra } from "@mastra/core/mastra";
+import { Mastra } from "@mastra/core";
 import { NetlifyDeployer } from "@mastra/deployer-netlify";
 
 export const mastra = new Mastra({
@@ -25,7 +25,7 @@ export const mastra = new Mastra({
 });
 ```
 
-> See the [NetlifyDeployer](/reference/deployer/netlify) API reference for all available configuration options.
+> See the [NetlifyDeployer](/reference/v1/deployer/netlify) API reference for all available configuration options.
 
 ## Continuous integration
 
@@ -82,4 +82,4 @@ The `NetlifyDeployer` 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/serverless-platforms/vercel-deployer.mdx

@@ -5,7 +5,7 @@ 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
 
@@ -16,7 +16,7 @@ npm install @mastra/deployer-vercel@latest
 ## 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.
 ---
 
@@ -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)