@mastra/mcp-docs-server 1.0.0-beta.13 → 1.0.0-beta.14

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

@@ -39,7 +39,7 @@ npm install @mastra/core@beta
 
 Mastra's model router auto-detects environment variables for your chosen provider. For OpenAI, set `OPENAI_API_KEY`:
 
-```bash title=".env" copy
+```bash title=".env"
 OPENAI_API_KEY=<your-api-key>
 ```
 
@@ -55,7 +55,7 @@ Mastra supports more than 600 models. Choose from the [full list](/models/v1).
 
 Create an agent by instantiating the `Agent` class with system `instructions` and a `model`:
 
-```typescript title="src/mastra/agents/test-agent.ts" copy
+```typescript title="src/mastra/agents/test-agent.ts"
 import { Agent } from "@mastra/core/agent";
 
 export const testAgent = new Agent({
@@ -77,7 +77,7 @@ They are system-level prompts that establish the agent's core identity and exper
 
 Instructions can be provided in multiple formats for greater flexibility. The examples below illustrate the supported shapes:
 
-```typescript copy
+```typescript
 // String (most common)
 instructions: "You are a helpful assistant.";
 
@@ -99,7 +99,7 @@ instructions: [
 
 Each model provider also enables a few different options, including prompt caching and configuring reasoning. We provide a `providerOptions` flag to manage these. You can set `providerOptions` on the instruction level to set different caching strategy per system instruction/prompt.
 
-```typescript copy
+```typescript
 // With provider-specific options (e.g., caching, reasoning)
 instructions: {
   role: "system",
@@ -112,18 +112,21 @@ instructions: {
 }
 ```
 
-> See the [Agent reference doc](/reference/v1/agents/agent) for more information.
+:::info
+
+Visit [Agent reference](/reference/v1/agents/agent) for more information.
+
+:::
 
 ### Registering an agent
 
 Register your agent in the Mastra instance to make it available throughout your application. Once registered, it can be called from workflows, tools, or other agents, and has access to shared resources such as memory, logging, and observability features:
 
-```typescript {6} showLineNumbers title="src/mastra/index.ts" copy
+```typescript {5} title="src/mastra/index.ts"
 import { Mastra } from "@mastra/core";
 import { testAgent } from "./agents/test-agent";
 
 export const mastra = new Mastra({
-  // ...
   agents: { testAgent },
 });
 ```
@@ -132,7 +135,7 @@ export const mastra = new Mastra({
 
 You can call agents from workflow steps, tools, the Mastra Client, or the command line. Get a reference by calling `.getAgent()` on your `mastra` or `mastraClient` instance, depending on your setup:
 
-```typescript showLineNumbers copy
+```typescript
 const testAgent = mastra.getAgent("testAgent");
 ```
 
@@ -152,7 +155,7 @@ Pass a single string for simple prompts, an array of strings when providing mult
 
 (The `role` defines the speaker for each message. Typical roles are `user` for human input, `assistant` for agent responses, and `system` for instructions.)
 
-```typescript showLineNumbers copy
+```typescript
 const response = await testAgent.generate([
   { role: "user", content: "Help me organize my day" },
   { role: "user", content: "My day starts at 9am and finishes at 5.30pm" },
@@ -172,7 +175,7 @@ Pass a single string for simple prompts, an array of strings when providing mult
 
 (The `role` defines the speaker for each message. Typical roles are `user` for human input, `assistant` for agent responses, and `system` for instructions.)
 
-```typescript showLineNumbers copy
+```typescript
 const stream = await testAgent.stream([
   { role: "user", content: "Help me organize my day" },
   { role: "user", content: "My day starts at 9am and finishes at 5.30pm" },
@@ -193,7 +196,7 @@ for await (const chunk of stream.textStream) {
 When streaming responses, the `onFinish()` callback runs after the LLM finishes generating its response and all tool executions are complete.
 It provides the final `text`, execution `steps`, `finishReason`, token `usage` statistics, and other metadata useful for monitoring or logging.
 
-```typescript showLineNumbers copy
+```typescript
 const stream = await testAgent.stream("Help me organize my day", {
   onFinish: ({ steps, text, finishReason, usage }) => {
     console.log({ steps, text, finishReason, usage });
@@ -208,19 +211,27 @@ for await (const chunk of stream.textStream) {
   </TabItem>
 </Tabs>
 
-> See [.generate()](/reference/v1/agents/generate) or [.stream()](/reference/v1/streaming/agents/stream) for more information.
+:::info
+
+Visit [.generate()](/reference/v1/agents/generate) or [.stream()](/reference/v1/streaming/agents/stream) for more information.
+
+:::
 
 ## Structured output
 
 Agents can return structured, type-safe data using Zod or JSON Schema. The parsed result is available on `response.object`.
 
-> See [Structured Output](/docs/v1/agents/structured-output) for more information.
+:::info
+
+Visit [Structured Output](/docs/v1/agents/structured-output) for more information.
+
+:::
 
 ## Analyzing images
 
 Agents can analyze and describe images by processing both the visual content and any text within them. To enable image analysis, pass an object with `type: 'image'` and the image URL in the `content` array. You can combine image content with text prompts to guide the agent's analysis.
 
-```typescript showLineNumbers copy
+```typescript
 const response = await testAgent.generate([
   {
     role: "user",
@@ -241,12 +252,11 @@ const response = await testAgent.generate([
 console.log(response.text);
 ```
 
-
 ## Using `maxSteps`
 
 The `maxSteps` parameter controls the maximum number of sequential LLM calls an agent can make. Each step includes generating a response, executing any tool calls, and processing the result. Limiting steps helps prevent infinite loops, reduce latency, and control token usage for agents that use tools. The default is 1, but can be increased:
 
-```typescript showLineNumbers copy
+```typescript
 const response = await testAgent.generate("Help me organize my day", {
   maxSteps: 10,
 });
@@ -260,7 +270,7 @@ You can monitor the progress of multi-step operations using the `onStepFinish` c
 
 `onStepFinish` is only available when streaming or generating text without structured output.
 
-```typescript showLineNumbers copy
+```typescript
 const response = await testAgent.generate("Help me organize my day", {
   onStepFinish: ({ text, toolCalls, toolResults, finishReason, usage }) => {
     console.log({ text, toolCalls, toolResults, finishReason, usage });
@@ -272,22 +282,25 @@ const response = await testAgent.generate("Help me organize my day", {
 
 Agents can use tools to go beyond language generation, enabling structured interactions with external APIs and services. Tools allow agents to access data and perform clearly defined operations in a reliable, repeatable way.
 
-```typescript title="src/mastra/agents/test-agent.ts" showLineNumbers
+```typescript title="src/mastra/agents/test-agent.ts"
 export const testAgent = new Agent({
   id: "test-agent",
   name: "Test Agent",
-  // ...
   tools: { testTool },
 });
 ```
 
-> See [Using Tools](/docs/v1/agents/using-tools) for more information.
+:::info
+
+Visit [Using Tools](/docs/v1/agents/using-tools) for more information.
+
+:::
 
 ## Using `RequestContext`
 
 Use `RequestContext` to access request-specific values. This lets you conditionally adjust behavior based on the context of the request.
 
-```typescript title="src/mastra/agents/test-agent.ts" showLineNumbers
+```typescript title="src/mastra/agents/test-agent.ts"
 export type UserTier = {
   "user-tier": "enterprise" | "pro";
 };
@@ -295,7 +308,6 @@ export type UserTier = {
 export const testAgent = new Agent({
   id: "test-agent",
   name: "Test Agent",
-  // ...
   model: ({ requestContext }) => {
     const userTier = requestContext.get("user-tier") as UserTier["user-tier"];
 
@@ -306,7 +318,11 @@ export const testAgent = new Agent({
 });
 ```
 
-> See [Request Context](/docs/v1/server/request-context) for more information.
+:::info
+
+See [Request Context](/docs/v1/server/request-context) for more information.
+
+:::
 
 ## Testing with Studio
 

package/.docs/raw/agents/processors.mdx

@@ -35,18 +35,17 @@ Mastra includes several processors for common use cases. You can also create cus
 
 Import and instantiate the processor, then pass it to the agent's `inputProcessors` or `outputProcessors` array:
 
-```typescript {3,9-15} title="src/mastra/agents/moderated-agent.ts" showLineNumbers copy
-import { openai } from "@ai-sdk/openai";
+```typescript {2,8-14} title="src/mastra/agents/moderated-agent.ts"
 import { Agent } from "@mastra/core/agent";
 import { ModerationProcessor } from "@mastra/core/processors";
 
 export const moderatedAgent = new Agent({
   name: "moderated-agent",
   instructions: "You are a helpful assistant",
-  model: openai("gpt-4o-mini"),
+  model: "openai/gpt-4o-mini",
   inputProcessors: [
     new ModerationProcessor({
-      model: openai("gpt-4.1-nano"),
+      model: "openai/gpt-4.1-nano",
       categories: ["hate", "harassment", "violence"],
       threshold: 0.7,
       strategy: "block",
@@ -77,7 +76,7 @@ When memory is enabled on an agent, memory processors are automatically added to
 ```
 [Memory Processors] → [Your inputProcessors]
 ```
-Memory loads conversation history first, then your processors run.
+Memory loads message history first, then your processors run.
 
 **Output processors:**
 ```
@@ -93,7 +92,7 @@ Custom processors implement the `Processor` interface:
 
 ### Custom input processor
 
-```typescript title="src/mastra/processors/custom-input.ts" showLineNumbers copy
+```typescript title="src/mastra/processors/custom-input.ts"
 import type {
   Processor,
   MastraDBMessage,
@@ -141,7 +140,7 @@ The framework handles both return formats, so modifying system messages is optio
 
 To modify system messages (e.g., trim verbose prompts for smaller models), return an object with both `messages` and `systemMessages`:
 
-```typescript title="src/mastra/processors/system-trimmer.ts" showLineNumbers copy
+```typescript title="src/mastra/processors/system-trimmer.ts"
 import type { Processor, CoreMessage, MastraDBMessage } from "@mastra/core";
 
 export class SystemTrimmer implements Processor {
@@ -174,7 +173,7 @@ This is useful for:
 
 While `processInput` runs once at the start of agent execution, `processInputStep` runs at **each step** of the agentic loop (including tool call continuations). This enables per-step configuration changes like dynamic model switching or tool choice modifications.
 
-```typescript title="src/mastra/processors/step-processor.ts" showLineNumbers copy
+```typescript title="src/mastra/processors/step-processor.ts"
 import type { Processor, ProcessInputStepArgs, ProcessInputStepResult } from "@mastra/core";
 
 export class DynamicModelProcessor implements Processor {
@@ -247,7 +246,7 @@ await agent.generate({
 
 ### Custom output processor
 
-```typescript title="src/mastra/processors/custom-output.ts" showLineNumbers copy
+```typescript title="src/mastra/processors/custom-output.ts"
 import type {
   Processor,
   MastraDBMessage,
@@ -292,14 +291,13 @@ Mastra provides utility processors for common tasks:
 
 Prevents context window overflow by removing older messages when the total token count exceeds a specified limit.
 
-```typescript copy showLineNumbers {9-12}
+```typescript {7-10}
 import { Agent } from "@mastra/core/agent";
 import { TokenLimiter } from "@mastra/core/processors";
-import { openai } from "@ai-sdk/openai";
 
 const agent = new Agent({
   name: "my-agent",
-  model: openai("gpt-4o"),
+  model: "openai/gpt-4o",
   inputProcessors: [
     // Ensure the total tokens don't exceed ~127k
     new TokenLimiter(127000),
@@ -309,7 +307,7 @@ const agent = new Agent({
 
 The `TokenLimiter` uses the `o200k_base` encoding by default (suitable for GPT-4o). You can specify other encodings for different models:
 
-```typescript copy showLineNumbers {6-9}
+```typescript {6-9}
 import cl100k_base from "js-tiktoken/ranks/cl100k_base";
 
 const agent = new Agent({
@@ -327,14 +325,13 @@ const agent = new Agent({
 
 Removes tool calls from messages sent to the LLM, saving tokens by excluding potentially verbose tool interactions.
 
-```typescript copy showLineNumbers {5-14}
+```typescript {7-16}
 import { Agent } from "@mastra/core/agent";
 import { ToolCallFilter, TokenLimiter } from "@mastra/core/processors";
-import { openai } from "@ai-sdk/openai";
 
 const agent = new Agent({
   name: "my-agent",
-  model: openai("gpt-4o"),
+  model: "openai/gpt-4o",
   inputProcessors: [
     // Example 1: Remove all tool calls/results
     new ToolCallFilter(),
@@ -348,13 +345,17 @@ const agent = new Agent({
 });
 ```
 
-> **Note:** The example above filters tool calls and limits tokens for the LLM, but these filtered messages will still be saved to memory. To also filter messages before they're saved to memory, manually add memory processors before utility processors. See [Memory Processors](/docs/v1/memory/memory-processors#manual-control-and-deduplication) for details.
+:::note
+
+The example above filters tool calls and limits tokens for the LLM, but these filtered messages will still be saved to memory. To also filter messages before they're saved to memory, manually add memory processors before utility processors. See [Memory Processors](/docs/v1/memory/memory-processors#manual-control-and-deduplication) for details.
+
+:::
 
 ## Using workflows as processors
 
 You can use Mastra workflows as processors to create complex processing pipelines with parallel execution, conditional branching, and error handling:
 
-```typescript title="src/mastra/processors/moderation-workflow.ts" showLineNumbers copy
+```typescript title="src/mastra/processors/moderation-workflow.ts"
 import { createWorkflow, createStep } from "@mastra/core/workflows";
 import { ProcessorStepSchema } from "@mastra/core/processors";
 import { Agent } from "@mastra/core/agent";
@@ -387,7 +388,7 @@ When an agent is registered with Mastra, processor workflows are automatically r
 
 Processors can request that the LLM retry its response with feedback. This is useful for implementing quality checks, output validation, or iterative refinement:
 
-```typescript title="src/mastra/processors/quality-checker.ts" showLineNumbers copy
+```typescript title="src/mastra/processors/quality-checker.ts"
 import type { Processor } from "@mastra/core";
 
 export class QualityChecker implements Processor {

package/.docs/raw/agents/structured-output.mdx

@@ -23,7 +23,7 @@ Agents can return structured data by defining the expected output with either [Z
 
 Define the `output` shape using [Zod](https://zod.dev/):
 
-```typescript showLineNumbers copy
+```typescript
 import { z } from "zod";
 
 const response = await testAgent.generate("Help me plan my day.", {
@@ -45,7 +45,7 @@ console.log(response.object);
 
 You can also use JSON Schema to define your output structure:
 
-```typescript showLineNumbers copy
+```typescript
 const response = await testAgent.generate("Help me plan my day.", {
   structuredOutput: {
     schema: {
@@ -72,7 +72,11 @@ console.log(response.object);
 </Tabs>
 
 
-> See [.generate()](/reference/v1/agents/generate#structuredoutput) for a full list of configuration options.
+:::info
+
+Visit [.generate()](/reference/v1/agents/generate#structuredoutput) for a full list of configuration options.
+
+:::
 
 ### Example output
 
@@ -99,7 +103,7 @@ The `response.object` will contain the structured data as defined by the schema.
 
 Streaming also supports structured output. The final structured object is available on `stream.fullStream` and after the stream completes on `stream.object`. Text stream chunks are still emitted, but they contain natural language text rather than structured data.
 
-```typescript showLineNumbers copy
+```typescript
 import { z } from "zod";
 
 const stream = await testAgent.stream("Help me plan my day.", {
@@ -131,7 +135,7 @@ for await (const chunk of stream.textStream) {
 
 When your main agent isn't proficient at creating structured output you can provide a `model` to `structuredOutput`. In this case, Mastra uses a second agent under the hood to extract structured data from the main agent's natural language response. This makes two LLM calls, one to generate the response and another to turn that response into the structured object, which adds some latency and cost but can improve accuracy for complex structuring tasks.
 
-```typescript showLineNumbers copy
+```typescript
 import { z } from "zod";
 
 const response = await testAgent.generate("Analyze the TypeScript programming language.", {
@@ -162,7 +166,7 @@ By default, Mastra passes the schema to the model provider using the `response_f
 
 If your model provider doesn't support `response_format`, you'll get an error from the API. When this happens, set `jsonPromptInjection: true`. This adds the schema to the system prompt instead, instructing the model to output JSON. This is less reliable than the API parameter approach.
 
-```typescript showLineNumbers copy
+```typescript
 import { z } from "zod";
 
 const response = await testAgent.generate("Help me plan my day.", {
@@ -198,7 +202,7 @@ const response = await agentWithTools.generate("Your prompt", {
 
 When schema validation fails, you can control how errors are handled using `errorStrategy`. The default `strict` strategy throws an error, while `warn` logs a warning and continues. The `fallback` strategy returns the values provided using `fallbackValue`.
 
-```typescript showLineNumbers copy
+```typescript
 import { z } from "zod";
 
 const response = await testAgent.generate("Tell me about TypeScript.", {

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

@@ -17,7 +17,7 @@ When creating tools, keep descriptions simple and focused on what the tool does,
 
 This example shows how to create a tool that fetches weather data from an API. When the agent calls the tool, it provides the required input as defined by the tool's `inputSchema`. The tool accesses this data through its `inputData` parameter, which in this example includes the `location` used in the weather API query.
 
-```typescript {14} title="src/mastra/tools/weather-tool.ts" showLineNumbers copy
+```typescript title="src/mastra/tools/weather-tool.ts"
 import { createTool } from "@mastra/core/tools";
 import { z } from "zod";
 
@@ -47,7 +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 {8,10} title="src/mastra/agents/weather-agent.ts" showLineNumbers copy
+```typescript {11} title="src/mastra/agents/weather-agent.ts"
 import { Agent } from "@mastra/core/agent";
 import { weatherTool } from "../tools/weather-tool";
 
@@ -66,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 title="src/test-tool.ts" showLineNumbers copy
+```typescript title="src/test-tool.ts"
 import { mastra } from "./mastra";
 
 const agent = mastra.getAgent("weatherAgent");
@@ -78,14 +78,13 @@ 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 {8} title="src/mastra/agents/weather-agent.ts" showLineNumbers copy
+```typescript {7} title="src/mastra/agents/weather-agent.ts"
 import { weatherTool } from "../tools/weather-tool";
 import { activitiesTool } from "../tools/activities-tool";
 
 export const weatherAgent = new Agent({
   id: "weather-agent",
   name: "Weather Agent",
-  // ..
   tools: { weatherTool, activitiesTool },
 });
 ```

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

@@ -26,7 +26,7 @@ tsconfig.json
 
 The `mastra build` command starts the build process:
 
-```bash copy
+```bash
 mastra build
 ```
 
@@ -34,7 +34,7 @@ mastra build
 
 If your Mastra files are located elsewhere, use the `--dir` flag to specify the custom location. The `--dir` flag tells Mastra where to find your entry point file (`index.ts` or `index.js`) and related directories.
 
-```bash copy
+```bash
 mastra build --dir ./my-project/mastra
 ```
 
@@ -68,6 +68,6 @@ If a `public` folder exists in `src/mastra`, its contents are copied into the `.
 
 Start the HTTP server:
 
-```bash copy
+```bash
 node .mastra/output/index.mjs
 ```

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

@@ -55,3 +55,10 @@ When Mastra is integrated with a web framework, it deploys alongside your applic
 We're building Mastra Cloud to be the easiest place to deploy and observe your Mastra agents. It's currently in beta.
 
 Learn more in the [Mastra Cloud docs](/docs/v1/mastra-cloud/overview).
+
+## Workflow Runners
+
+Mastra supports deploying workflows to specialized workflow execution platforms that handle orchestration, monitoring, and reliability. [Inngest](https://www.inngest.com) is a developer platform for running background workflows without managing infrastructure. Mastra workflows can be deployed to Inngest, which provides step memoization, automatic retries, real-time monitoring, and suspend/resume capabilities.
+
+- [Inngest deployment guide](/guides/v1/deployment/inngest)
+- [Inngest workflow example](https://github.com/mastra-ai/mastra/tree/main/examples/inngest)

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

@@ -8,7 +8,7 @@ description: "Learn how Mastra can be deployed when integrated with a Web Framew
 When Mastra is integrated with a web framework, it deploys alongside your application using the framework's standard deployment process. Follow the instructions below to ensure your Mastra integration deploys correctly.
 
 :::warning
-If you're deploying to a cloud provider, remove any usage of [LibSQLStore](/docs/v1/memory/storage/overview) from your Mastra configuration. LibSQLStore requires filesystem access and is not compatible with serverless platforms.
+If you're deploying to a cloud provider, remove any usage of [LibSQLStore](/reference/v1/storage/libsql) from your Mastra configuration. LibSQLStore requires filesystem access and is not compatible with serverless platforms.
 :::
 
 Integration guides:
@@ -20,7 +20,7 @@ Integration guides:
 
 If you've integrated Mastra with Next.js [by following our guide](/guides/v1/getting-started/next-js) and plan to deploy to Vercel, add `serverExternalPackages: ["@mastra/*"]` to your `next.config.ts`:
 
-```typescript {4} title="next.config.ts" showLineNumbers copy
+```typescript {4} title="next.config.ts"
 import type { NextConfig } from "next";
 
 const nextConfig: NextConfig = {
@@ -34,12 +34,11 @@ export default nextConfig;
 
 If you've integrated Mastra with Astro [by following our guide](/guides/v1/getting-started/astro) and plan to deploy to Vercel, add the Vercel adapter and server output to your `astro.config.mjs`:
 
-```javascript {2,6,7} title="astro.config.mjs" showLineNumbers copy
+```javascript {2,5-6} title="astro.config.mjs"
 import { defineConfig } from "astro/config";
 import vercel from "@astrojs/vercel";
 
 export default defineConfig({
-  // ...
   adapter: vercel(),
   output: "server",
 });
@@ -49,12 +48,11 @@ export default defineConfig({
 
 If you've integrated Mastra with Astro [by following our guide](/guides/v1/getting-started/astro) and plan to deploy to Netlify, add the Netlify adapter and server output to your `astro.config.mjs`:
 
-```javascript {2,6,7} title="astro.config.mjs" showLineNumbers copy
+```javascript {2,5-6} title="astro.config.mjs"
 import { defineConfig } from "astro/config";
 import netlify from "@astrojs/netlify";
 
 export default defineConfig({
-  // ...
   adapter: netlify(),
   output: "server",
 });

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

@@ -65,7 +65,6 @@ For type safety and compatibility with both live agent scoring and trace scoring
 
 ```typescript
 const myScorer = createScorer({
-  // ...
   type: "agent", // Automatically handles agent input/output types
 }).generateScore(({ run, results }) => {
   // run.output is automatically typed as ScorerRunOutputForAgent
@@ -241,9 +240,13 @@ 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/v1/evals/create-scorer) for the full API and configuration options.
+:::info
 
-```typescript title="src/mastra/scorers/gluten-checker.ts" showLineNumbers copy
+Visit [createScorer](/reference/v1/evals/create-scorer) for the full API and configuration options.
+
+:::
+
+```typescript title="src/mastra/scorers/gluten-checker.ts"
 import { createScorer } from "@mastra/core/evals";
 import { z } from "zod";
 
@@ -399,7 +402,7 @@ The reason generation step creates explanations that help users understand why a
 
 ## High gluten-free example
 
-```typescript title="src/example-high-gluten-free.ts" showLineNumbers copy
+```typescript title="src/example-high-gluten-free.ts"
 const result = await glutenCheckerScorer.run({
   input: [{ role: 'user', content: 'Mix rice, beans, and vegetables' }],
   output: { text: 'Mix rice, beans, and vegetables' },
@@ -425,7 +428,7 @@ console.log('Reason:', result.reason);
 
 ## Partial gluten example
 
-```typescript title="src/example-partial-gluten.ts" showLineNumbers copy
+```typescript title="src/example-partial-gluten.ts"
 const result = await glutenCheckerScorer.run({
   input: [{ role: "user", content: "Mix flour and water to make dough" }],
   output: { text: "Mix flour and water to make dough" },
@@ -451,7 +454,7 @@ console.log("Reason:", result.reason);
 
 ## Low gluten-free example
 
-```typescript title="src/example-low-gluten-free.ts" showLineNumbers copy
+```typescript title="src/example-low-gluten-free.ts"
 const result = await glutenCheckerScorer.run({
   input: [{ role: "user", content: "Add soy sauce and noodles" }],
   output: { text: "Add soy sauce and noodles" },

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

@@ -23,7 +23,7 @@ There are different kinds of scorers, each serving a specific purpose. Here are
 
 To access Mastra's scorers feature install the `@mastra/evals` package.
 
-```bash copy
+```bash
 npm install @mastra/evals@beta
 ```
 
@@ -35,7 +35,7 @@ npm install @mastra/evals@beta
 
 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
+```typescript title="src/mastra/agents/evaluated-agent.ts"
 import { Agent } from "@mastra/core/agent";
 import {
   createAnswerRelevancyScorer,
@@ -43,7 +43,6 @@ import {
 } from "@mastra/evals/scorers/prebuilt";
 
 export const evaluatedAgent = new Agent({
-  // ...
   scorers: {
     relevancy: {
       scorer: createAnswerRelevancyScorer({ model: "openai/gpt-4.1-nano" }),
@@ -61,13 +60,12 @@ export const evaluatedAgent = new Agent({
 
 You can also add scorers to individual workflow steps to evaluate outputs at specific points in your process:
 
-```typescript title="src/mastra/workflows/content-generation.ts" showLineNumbers copy
+```typescript title="src/mastra/workflows/content-generation.ts"
 import { createWorkflow, createStep } from "@mastra/core/workflows";
 import { z } from "zod";
 import { customStepScorer } from "../scorers/custom-step-scorer";
 
 const contentStep = createStep({
-  // ...
   scorers: {
     customStepScorer: {
       scorer: customStepScorer(),
@@ -115,7 +113,6 @@ To score traces, you first need to register your scorers with your Mastra instan
 
 ```typescript
 const mastra = new Mastra({
-  // ...
   scorers: {
     answerRelevancy: myAnswerRelevancyScorer,
     responseQuality: myResponseQualityScorer,

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

@@ -15,7 +15,7 @@ You can use any testing framework that supports ESM modules, such as [Vitest](ht
 
 Use `runEvals` to evaluate your agent against multiple test cases. The function accepts an array of data items, each containing an `input` and optional `groundTruth` for scorer validation.
 
-```typescript copy showLineNumbers title="src/mastra/agents/weather-agent.test.ts"
+```typescript title="src/mastra/agents/weather-agent.test.ts"
 import { describe, it, expect } from 'vitest';
 import { createScorer, runEvals } from "@mastra/core/evals";
 import { weatherAgent } from "./weather-agent";
@@ -72,7 +72,7 @@ The `runEvals` function returns an object with:
 
 Create separate test cases for different evaluation scenarios:
 
-```typescript copy showLineNumbers title="src/mastra/agents/weather-agent.test.ts"
+```typescript title="src/mastra/agents/weather-agent.test.ts"
 describe('Weather Agent Tests', () => {
   const locationScorer = createScorer({ /* ... */ });