@mastra/mcp-docs-server 1.1.8 → 1.1.9-alpha.1

package/.docs/docs/agents/adding-voice.md

@@ -39,7 +39,7 @@ try {
 }
 ```
 
-## Working with Audio Streams
+## Working with audio streams
 
 The `speak()` and `listen()` methods work with Node.js streams. Here's how to save and load audio files:
 
@@ -87,7 +87,7 @@ try {
 }
 ```
 
-## Speech-to-Speech Voice Interactions
+## Speech-to-speech voice interactions
 
 For more dynamic and interactive voice experiences, you can use real-time voice providers that support speech-to-speech capabilities:
 
@@ -323,7 +323,7 @@ For the complete list of supported AI SDK providers and their capabilities:
 - [Transcription](https://ai-sdk.dev/docs/providers/openai/transcription)
 - [Speech](https://ai-sdk.dev/docs/providers/elevenlabs/speech)
 
-## Supported Voice Providers
+## Supported voice providers
 
 Mastra supports multiple voice providers for text-to-speech (TTS) and speech-to-text (STT) capabilities:
 
@@ -341,7 +341,7 @@ Mastra supports multiple voice providers for text-to-speech (TTS) and speech-to-
 | Azure           | `@mastra/voice-azure`           | TTS, STT                  | [Documentation](https://mastra.ai/reference/voice/mastra-voice)    |
 | Cloudflare      | `@mastra/voice-cloudflare`      | TTS                       | [Documentation](https://mastra.ai/reference/voice/mastra-voice)    |
 
-## Next Steps
+## Next steps
 
 - [Voice API Reference](https://mastra.ai/reference/voice/mastra-voice) - Detailed API documentation for voice capabilities
 - [Text to Speech Examples](https://github.com/mastra-ai/voice-examples/tree/main/text-to-speech) - Interactive story generator and other TTS implementations

package/.docs/docs/agents/agent-approval.md

@@ -92,7 +92,7 @@ const handleDecline = async () => {
 }
 ```
 
-## Tool approval with generate()
+## Tool approval with `generate()`
 
 Tool approval also works with the `generate()` method for non-streaming use cases. When a tool requires approval during a `generate()` call, the method returns immediately instead of executing the tool.
 
@@ -504,7 +504,7 @@ for await (const chunk of stream.fullStream) {
 }
 ```
 
-### Using suspend() in supervisor pattern
+### Using `suspend()` in supervisor pattern
 
 Tools can also use [`suspend()`](#approval-using-suspend) to pause execution and return context to the user. This approach works through the supervisor delegation chain the same way `requireApproval` does — the suspension surfaces at the supervisor level:
 
@@ -553,7 +553,7 @@ for await (const chunk of stream.fullStream) {
 }
 ```
 
-### Tool approval with generate()
+### Tool approval with `generate()`
 
 Tool approval propagation also works with `generate()` in supervisor pattern:
 

package/.docs/docs/agents/agent-memory.md

@@ -96,7 +96,7 @@ export const memoryAgent = new Agent({
 })
 ```
 
-> **Mastra Cloud Store limitation:** Agent-level storage is not supported when using [Mastra Cloud Store](https://mastra.ai/docs/mastra-cloud/deployment). If you use Mastra Cloud Store, configure storage on the Mastra instance instead. This limitation does not apply if you bring your own database.
+> **Mastra Cloud Store limitation:** Agent-level storage isn't supported when using [Mastra Cloud Store](https://mastra.ai/docs/mastra-cloud/deployment). If you use Mastra Cloud Store, configure storage on the Mastra instance instead. This limitation doesn't apply if you bring your own database.
 
 ## Message history
 
@@ -127,11 +127,11 @@ const response = await memoryAgent.generate("What's my favorite color?", {
 })
 ```
 
-> **Warning:** Each thread has an owner (`resourceId`) that cannot be changed after creation. Avoid reusing the same thread ID for threads with different owners, as this will cause errors when querying.
+> **Warning:** Each thread has an owner (`resourceId`) that can't be changed after creation. Avoid reusing the same thread ID for threads with different owners, as this will cause errors when querying.
 
 To learn more about memory see the [Memory](https://mastra.ai/docs/memory/overview) documentation.
 
-## Observational Memory
+## Observational memory
 
 For long-running conversations, raw message history grows until it fills the context window, degrading agent performance. [Observational Memory](https://mastra.ai/docs/memory/observational-memory) solves this by running background agents that compress old messages into dense observations, keeping the context window small while preserving long-term memory.
 

package/.docs/docs/agents/guardrails.md

@@ -40,7 +40,7 @@ export const moderatedAgent = new Agent({
 
 ## Input processors
 
-Input processors are applied before user messages reach the language model. They are useful for normalization, validation, content moderation, prompt injection detection, and security checks.
+Input processors are applied before user messages reach the language model. They're useful for normalization, validation, content moderation, prompt injection detection, and security checks.
 
 ### Normalizing user messages
 
@@ -111,7 +111,7 @@ export const multilingualAgent = new Agent({
 
 ## Output processors
 
-Output processors are applied after the language model generates a response, but before it is returned to the user. They are useful for response optimization, moderation, transformation, and applying safety controls.
+Output processors are applied after the language model generates a response, but before it's returned to the user. They're useful for response optimization, moderation, transformation, and applying safety controls.
 
 ### Batching streamed output
 
@@ -188,7 +188,7 @@ const scrubbedAgent = new Agent({
 
 ## Hybrid processors
 
-Hybrid processors can be applied either before messages are sent to the language model or before responses are returned to the user. They are useful for tasks like content moderation and PII redaction.
+Hybrid processors can be applied either before messages are sent to the language model or before responses are returned to the user. They're useful for tasks like content moderation and PII redaction.
 
 ### Moderating input and output
 

package/.docs/docs/agents/network-approval.md

@@ -1,4 +1,6 @@
-# Network Approval
+# Network approval
+
+> **Deprecated:** Agent networks are deprecated and will be removed in a future release. Use the [supervisor pattern](https://mastra.ai/docs/agents/supervisor-agents) instead. See the [migration guide](https://mastra.ai/guides/migrations/network-to-supervisor) to upgrade.
 
 Agent networks can require the same [human-in-the-loop](https://mastra.ai/docs/workflows/human-in-the-loop) oversight used in individual agents and workflows. When a tool, subagent, or workflow within a network requires approval or suspends execution, the network pauses and emits events that allow your application to collect user input before resuming.
 
@@ -269,7 +271,8 @@ Both approaches work with the same tool definitions. Automatic resumption trigge
 
 ## Related
 
-- [Agent Networks](https://mastra.ai/docs/agents/networks)
+- [Supervisor Agents](https://mastra.ai/docs/agents/supervisor-agents)
+- [Migration: .network() to Supervisor Pattern](https://mastra.ai/guides/migrations/network-to-supervisor)
 - [Agent Approval](https://mastra.ai/docs/agents/agent-approval)
 - [Human-in-the-Loop](https://mastra.ai/docs/workflows/human-in-the-loop)
 - [Agent Memory](https://mastra.ai/docs/agents/agent-memory)

package/.docs/docs/agents/networks.md

@@ -1,6 +1,6 @@
-# Agent Networks
+# Agent networks
 
-> **Supervisor Pattern Recommended:** The [supervisor pattern](https://mastra.ai/docs/agents/supervisor-agents) using `agent.stream()` or `agent.generate()` is now the recommended approach for coordinating multiple agents. It provides the same multi-agent coordination capabilities as `.network()` with significant improvements:
+> **Agent Network Deprecated — Supervisor Pattern Recommended:** Agent networks are deprecated and will be removed in a future release. The [supervisor pattern](https://mastra.ai/docs/agents/supervisor-agents) using `agent.stream()` or `agent.generate()` is now the recommended approach for coordinating multiple agents. It provides the same multi-agent coordination capabilities as `.network()` with significant improvements:
 >
 > - **Better control**: Iteration hooks, delegation hooks, and task completion scoring give you fine-grained control over execution
 > - **Simpler API**: Uses familiar `stream()` and `generate()` methods instead of a separate `.network()` API

package/.docs/docs/agents/overview.md

@@ -1,4 +1,4 @@
-# Using Agents
+# Using agents
 
 Agents use LLMs and tools to solve open-ended tasks. They reason about goals, decide which tools to use, retain conversation memory, and iterate internally until the model emits a final answer or an optional stop condition is met. Agents produce structured responses you can render in your UI or process programmatically. Use agents directly or compose them into workflows or agent networks.
 
@@ -59,7 +59,7 @@ Agents use LLMs and tools to solve open-ended tasks. They reason about goals, de
 
 ### Instruction formats
 
-Instructions define the agent's behavior, personality, and capabilities. They are system-level prompts that establish the agent's core identity and expertise.
+Instructions define the agent's behavior, personality, and capabilities. They're system-level prompts that establish the agent's core identity and expertise.
 
 Instructions can be provided in multiple formats for greater flexibility. The examples below illustrate the supported shapes:
 

package/.docs/docs/agents/processors.md

@@ -160,7 +160,7 @@ This is useful for:
 - Filtering or modifying semantic recall content to prevent "prompt too long" errors
 - Dynamically adjusting system instructions based on the conversation
 
-### Per-step processing with processInputStep
+### Per-step processing with `processInputStep`
 
 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.
 
@@ -219,7 +219,7 @@ The method can return any combination of:
 - `modelSettings`: Modify model settings
 - `structuredOutput`: Modify structured output configuration
 
-#### Ensuring a final response with maxSteps
+#### Ensuring a final response with `maxSteps`
 
 When using `maxSteps` to limit agent execution, the agent may return an empty response if it attempts a tool call on the final step. Use `processInputStep` to force a text response on the last step:
 
@@ -283,7 +283,7 @@ const result = await agent.generate('Your prompt', { maxSteps: MAX_STEPS })
 
 This ensures that on the final allowed step (step 4 when `maxSteps` is 5, since steps are 0-indexed), the LLM generates a summary instead of attempting another tool call, and clearly indicates if the task is incomplete.
 
-#### Using prepareStep callback
+#### Using `prepareStep` callback
 
 For simpler per-step logic, you can use the `prepareStep` callback on `generate()` or `stream()` instead of creating a full processor:
 
@@ -303,31 +303,49 @@ await agent.generate('Complex task', {
 ### Custom output processor
 
 ```typescript
-import type { Processor, MastraDBMessage, RequestContext } from '@mastra/core'
+import type { Processor, MastraDBMessage, ChunkType } from '@mastra/core'
 
 export class CustomOutputProcessor implements Processor {
   id = 'custom-output'
 
-  async processOutputResult({
-    messages,
-    context,
-  }: {
-    messages: MastraDBMessage[]
-    context: RequestContext
-  }): Promise<MastraDBMessage[]> {
+  async processOutputResult({ messages }): Promise<MastraDBMessage[]> {
     // Transform messages after the LLM generates them
     return messages.filter(msg => msg.role !== 'system')
   }
 
-  async processOutputStream({
-    stream,
-    context,
-  }: {
-    stream: ReadableStream
-    context: RequestContext
-  }): Promise<ReadableStream> {
-    // Transform streaming responses
-    return stream
+  async processOutputStream({ part }): Promise<ChunkType | null> {
+    // Transform or filter streaming chunks
+    return part
+  }
+}
+```
+
+The `processOutputStream` method receives all streaming chunks. To also receive custom `data-*` chunks emitted by tools via `writer.custom()`, set `processDataParts = true` on your processor. This lets you inspect, modify, or block tool-emitted data chunks before they reach the client.
+
+#### Accessing generation result data
+
+The `processOutputResult` method receives a `result` object containing the resolved generation data — the same information available in the `onFinish` callback. This lets you access token usage, generated text, finish reason, and step details.
+
+```typescript
+import type { Processor } from '@mastra/core'
+
+export class UsageTracker implements Processor {
+  id = 'usage-tracker'
+
+  async processOutputResult({ messages, result }) {
+    console.log(`Text: ${result.text}`)
+    console.log(`Tokens: ${result.usage.inputTokens} in, ${result.usage.outputTokens} out`)
+    console.log(`Finish reason: ${result.finishReason}`)
+    console.log(`Steps: ${result.steps.length}`)
+
+    // Each step contains toolCalls, toolResults, reasoning, sources, files, etc.
+    for (const step of result.steps) {
+      if (step.toolCalls?.length) {
+        console.log(`Step used ${step.toolCalls.length} tool calls`)
+      }
+    }
+
+    return messages
   }
 }
 ```
@@ -448,13 +466,13 @@ const response = await stream.response
 console.log(response.uiMessages)
 ```
 
-## Built-in Utility Processors
+## Built-in utility processors
 
 Mastra provides utility processors for common tasks:
 
 **For security and validation processors**, see the [Guardrails](https://mastra.ai/docs/agents/guardrails) page for input/output guardrails and moderation processors. **For memory-specific processors**, see the [Memory Processors](https://mastra.ai/docs/memory/memory-processors) page for processors that handle message history, semantic recall, and working memory.
 
-### TokenLimiter
+### `TokenLimiter`
 
 Prevents context window overflow by removing older messages when the total token count exceeds a specified limit.
 
@@ -488,7 +506,7 @@ const agent = new Agent({
 })
 ```
 
-### ToolCallFilter
+### `ToolCallFilter`
 
 Removes tool calls from messages sent to the LLM, saving tokens by excluding potentially verbose tool interactions.
 
@@ -514,7 +532,7 @@ 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](https://mastra.ai/docs/memory/memory-processors) for details.
 
-### ToolSearchProcessor
+### `ToolSearchProcessor`
 
 Enables dynamic tool discovery and loading for agents with large tool libraries. Instead of providing all tools upfront, the agent searches for tools by keyword and loads them on demand, reducing context token usage.
 

package/.docs/docs/agents/structured-output.md

@@ -1,4 +1,4 @@
-# Structured Output
+# Structured output
 
 Structured output lets an agent return an object that matches the shape defined by a schema instead of returning text. The schema tells the model what fields to produce, and the model ensures the final result fits that shape.
 
@@ -188,7 +188,7 @@ const response = await testAgent.generate('Help me plan my day.', {
 console.log(response.object)
 ```
 
-> **Gemini 2.5 with tools:** Gemini 2.5 models do not support combining `response_format` (structured output) with function calling (tools) in the same API call. If your agent has tools and you're using `structuredOutput` with a Gemini 2.5 model, you must set `jsonPromptInjection: true` to avoid the error `Function calling with a response mime type: 'application/json' is unsupported`.
+> **Gemini 2.5 with tools:** Gemini 2.5 models don't support combining `response_format` (structured output) with function calling (tools) in the same API call. If your agent has tools and you're using `structuredOutput` with a Gemini 2.5 model, you must set `jsonPromptInjection: true` to avoid the error `Function calling with a response mime type: 'application/json' is unsupported`.
 >
 > ```typescript
 > const response = await agentWithTools.generate('Your prompt', {

package/.docs/docs/agents/supervisor-agents.md

@@ -1,4 +1,4 @@
-# Supervisor Agents
+# Supervisor agents
 
 A supervisor agent coordinates multiple subagents using `agent.stream()` or `agent.generate()`. You configure subagents on the supervisor's `agents` property, and the supervisor uses its instructions and each subagent's `description` to decide when and how to delegate tasks.
 
@@ -57,7 +57,7 @@ for await (const chunk of stream.textStream) {
 
 Delegation hooks let you intercept, modify, or reject delegations as they happen. Configure them under the `delegation` option, either in the agent's `defaultOptions` or per-call.
 
-### onDelegationStart
+### `onDelegationStart`
 
 Called before the supervisor delegates to a subagent. Return an object to control the delegation:
 
@@ -104,7 +104,7 @@ The `context` object includes:
 | `prompt`      | The prompt the supervisor is sending      |
 | `iteration`   | Current iteration number                  |
 
-### onDelegationComplete
+### `onDelegationComplete`
 
 Called after a delegation finishes. Use it to inspect results, provide feedback, or stop execution:
 

package/.docs/docs/agents/using-tools.md

@@ -1,4 +1,4 @@
-# Using Tools
+# Using tools
 
 Agents use tools to call APIs, query databases, or run custom functions from your codebase. Tools give agents capabilities beyond language generation by providing structured access to data and performing clearly defined operations. You can also load tools from remote [MCP servers](https://mastra.ai/docs/mcp/overview) to expand an agent's capabilities.
 
@@ -8,7 +8,7 @@ Use tools when an agent needs additional context or information from remote reso
 
 ## Creating a tool
 
-When creating tools, keep descriptions simple and focused on what the tool does, emphasizing its primary use case. Descriptive schema names can also help guide the agent on how to use the tool.
+When creating tools, keep descriptions concise and focused on what the tool does, emphasizing its primary use case. Descriptive schema names can also help guide the agent on how to use the tool.
 
 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.
 
@@ -211,7 +211,7 @@ This lets you specify how tools are identified in the stream. If you want the `t
 
 ### Subagents and workflows as tools
 
-Subagents and workflows follow the same pattern. They are converted to tools with a prefix followed by your object key:
+Subagents and workflows follow the same pattern. They're converted to tools with a prefix followed by your object key:
 
 | Property    | Prefix      | Example key | `toolName`          |
 | ----------- | ----------- | ----------- | ------------------- |

package/.docs/docs/build-with-ai/mcp-docs-server.md

@@ -1,4 +1,4 @@
-# Mastra Docs Server
+# Mastra docs server
 
 The `@mastra/mcp-docs-server` package provides direct access to Mastra’s full documentation via the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/getting-started/intro). It works with Cursor, Windsurf, Cline, Claude Code, VS Code, Codex or any tool that supports MCP.
 
@@ -56,7 +56,7 @@ This creates a project-scoped `.mcp.json` file if one doesn't already exist. You
 
 ### Cursor
 
-Install by clicking the button below:
+Install by selecting the button below:
 
 [![Install MCP Server](https://cursor.com/deeplink/mcp-install-light.svg)](cursor://anysphere.cursor-deeplink/mcp/install?name=mastra\&config=eyJjb21tYW5kIjoibnB4IC15IEBtYXN0cmEvbWNwLWRvY3Mtc2VydmVyIn0%3D)
 
@@ -77,7 +77,7 @@ Google Antigravity is an agent-first development platform that supports MCP serv
 
    ![The Antigravity MCP store. At the top is a search bar and below a list of available MCP servers. On the very top right is a dropdown menu.](/assets/images/antigravity_mcp_server-689ea495d9c7139cc431f1f1b9827f9b.png)
 
-2. To add a custom MCP server, select **Manage MCP Servers** at the top of the MCP Store and click **View raw config** in the main tab.
+2. To add a custom MCP server, select **Manage MCP Servers** at the top of the MCP Store and select **View raw config** in the main tab.
 
    ![The Antigravity MCP store showing the Manage MCP Servers option and the View raw config button.](/assets/images/antigravity_managed_mcp-b661e8c04b3219000f8d842e5eb26a1a.png)
 
@@ -137,11 +137,11 @@ Once you installed the MCP server, you can use it like so:
 
    ![Entry in VSCode\'s settings page. The option is called \"Chat \> MCP: Enabled (Preview)\". The description says: \"Enables integration with Model Context Protocol servers to provide additional tools and functionality.\"](/assets/images/vscode-mcp-setting-8d1eb4f3df1e33606503f8c5e937e9e3.png)
 
-MCP only works in Agent mode in VSCode. Once you are in agent mode, open the `mcp.json` file and click the "start" button. Note that the "start" button will only appear if the `.vscode` folder containing `mcp.json` is in your workspace root, or the highest level of the in-editor file explorer.
+MCP only works in Agent mode in VSCode. Once you are in agent mode, open the `mcp.json` file and select the "start" button. Note that the "start" button will only appear if the `.vscode` folder containing `mcp.json` is in your workspace root, or the highest level of the in-editor file explorer.
 
 ![A screenshot of the mcp.json file showing the start button in the editor](/assets/images/vscode-start-mcp-26480d86080c4907cb497a325de106a4.png)
 
-After starting the MCP server, click the tools button in the Copilot pane to see available tools.
+After starting the MCP server, select the tools button in the Copilot pane to see available tools.
 
 ![Tools page of VSCode to see available tools](/assets/images/vscode-mcp-running-d92d6ed234d1148093dc804b0ead3515.png)
 

package/.docs/docs/build-with-ai/skills.md

@@ -1,4 +1,4 @@
-# Mastra Skills
+# Mastra skills
 
 Mastra Skills are folders of instructions, scripts, and resources that agents can discover and use to gain Mastra knowledge. They contain setup instructions, best practices, and methods to fetch up-to-date information from Mastra's documentation.
 
@@ -32,4 +32,4 @@ bun x skills add mastra-ai/skills
 
 Mastra skills work with any coding agent that supports the [Skills standard](https://agentskills.io/), including Claude Code, Cursor, Codex, OpenCode, and others.
 
-They are also available on [GitHub](https://github.com/mastra-ai/skills).
+They're also available on [GitHub](https://github.com/mastra-ai/skills).

package/.docs/docs/community/contributing-templates.md

@@ -1,3 +1,3 @@
-# Contributing Templates
+# Contributing templates
 
 The Mastra community plays a vital role in creating templates that showcase innovative application patterns. We're currently reworking our template contribution process to ensure high-quality, valuable templates for the community. For the time being, we're not accepting new template contributions. Please keep an eye on this page for updates on when contributions will reopen and the new submission process.

package/.docs/docs/community/discord.md

@@ -1,9 +1,9 @@
-# Discord Community
+# Discord community
 
 The Discord server has over 1000 members and serves as the main discussion forum for Mastra. The Mastra team monitors Discord during North American and European business hours, with community members active across other time zones.
 
 [Join the Discord server](https://discord.gg/BTYqqHKUrf)
 
-## Discord MCP Bot
+## Discord MCP bot
 
-In addition to community members, we have an (experimental!) Discord bot that can also help answer questions. It uses [Model Context Protocol (MCP)](https://mastra.ai/docs/mcp/overview). You can ask it a question with `/ask` (either in public channels or DMs) and clear history (in DMs only) with `/cleardm`.
+In addition to community members, we've an (experimental!) Discord bot that can also help answer questions. It uses [Model Context Protocol (MCP)](https://mastra.ai/docs/mcp/overview). You can ask it a question with `/ask` (either in public channels or DMs) and clear history (in DMs only) with `/cleardm`.

package/.docs/docs/community/licensing.md

@@ -1,10 +1,10 @@
 # License
 
-## Apache License 2.0
+## Apache license 2.0
 
 Mastra is licensed under the Apache License 2.0, a permissive open-source license that provides users with broad rights to use, modify, and distribute the software.
 
-### What is Apache License 2.0?
+### What's Apache License 2.0?
 
 The Apache License 2.0 is a permissive open-source license that grants users extensive rights to use, modify, and distribute the software. It allows:
 

package/.docs/docs/deployment/cloud-providers.md

@@ -1,8 +1,8 @@
-# Deploy to Cloud Providers
+# Deploy to cloud providers
 
 Mastra applications can be deployed to cloud providers and serverless platforms. Mastra includes optional built-in deployers for Vercel, Netlify, and Cloudflare to automate the deployment process.
 
-## Supported Cloud Providers
+## Supported cloud providers
 
 The following guides show how to deploy Mastra to specific cloud providers:
 

package/.docs/docs/deployment/mastra-server.md

@@ -1,4 +1,4 @@
-# Deploy a Mastra Server
+# Deploy a Mastra server
 
 Mastra compiles your application into a standalone Node.js server that can run on any platform supporting Node.js, Bun, or Deno.
 
@@ -100,7 +100,7 @@ The built server exposes endpoints for health checks, agents, workflows, and mor
 | `GET /openapi.json` | OpenAPI specification (if `server.build.openAPIDocs` is enabled)       |
 | `GET /swagger-ui`   | Interactive API documentation (if `server.build.swaggerUI` is enabled) |
 
-This list is not exhaustive. To view all endpoints, run `mastra dev` and visit `http://localhost:4111/swagger-ui`.
+This list isn't exhaustive. To view all endpoints, run `mastra dev` and visit `http://localhost:4111/swagger-ui`.
 
 To add your own endpoints, see [Custom API Routes](https://mastra.ai/docs/server/custom-api-routes).
 

package/.docs/docs/deployment/monorepo.md

@@ -1,4 +1,4 @@
-# Deploy in a Monorepo
+# Deploy in a monorepo
 
 Deploying Mastra in a monorepo follows the same process as a standalone application. This guide covers monorepo-specific considerations. For the core build and deployment steps, see [Deploy a Mastra Server](https://mastra.ai/docs/deployment/mastra-server).
 

package/.docs/docs/deployment/overview.md

@@ -1,4 +1,4 @@
-# Deployment Overview
+# Deployment overview
 
 Mastra applications can be deployed to any Node.js-compatible environment. You can deploy a Mastra server, integrate with an existing web framework, deploy to cloud providers, or use Mastra Cloud for managed hosting.
 
@@ -11,7 +11,7 @@ Mastra can run against any of these runtime environments:
 - Deno
 - Cloudflare
 
-## Deployment Options
+## Deployment options
 
 ### Mastra Server
 
@@ -55,7 +55,7 @@ We're building Mastra Cloud to be the easiest place to deploy and observe your M
 
 Learn more in the [Mastra Cloud docs](https://mastra.ai/docs/mastra-cloud/overview).
 
-## Workflow Runners
+## Workflow runners
 
 Mastra workflows run using the built-in execution engine by default. For production workloads requiring managed infrastructure, workflows can also be deployed to specialized platforms like [Inngest](https://www.inngest.com) that provide step memoization, automatic retries, and real-time monitoring.
 

package/.docs/docs/deployment/studio.md

@@ -1,8 +1,8 @@
-# Deploying Studio
+# Deploying studio
 
 [Studio](https://mastra.ai/docs/getting-started/studio) provides an interactive UI for building and testing your agents. It's a React-based Single Page Application (SPA) that runs in the browser and connects to a running [Mastra server](https://mastra.ai/docs/deployment/mastra-server).
 
-There are two primary ways of deploying Studio:
+You can deploy Studio in two primary ways:
 
 - [Mastra Cloud](https://mastra.ai/docs/mastra-cloud/overview) hosts Studio for you and allows you to share access with your team via link
 - You can self-host Studio on your own infrastructure, either alongside your Mastra server or separately as a standalone SPA
@@ -61,7 +61,7 @@ The command uses Node's built-in `http` module and [`serve-handler`](https://www
 
 ## Running a server
 
-Running `mastra studio` as a long-running process is no different from running any other Node.js service. All the best practices, tools, and options for deployment apply here as well. You can use process managers like PM2, use Docker, or cloud services that support Node.js applications. You'll need to ensure CORS is configured correctly and errors are monitored, just like with any web service.
+Running `mastra studio` as a long-running process is no different from running any other Node.js service. All the best practices, tools, and options for deployment apply here as well. You can use process managers like PM2, use Docker, or cloud services that support Node.js applications. You'll need to ensure CORS is configured correctly and errors are monitored, as with any web service.
 
 > **Warning:** Once Studio is connected to your Mastra server, it has full access to your agents, workflows, and tools. Be sure to secure it properly in production (e.g. behind authentication, VPN, etc.) to prevent unauthorized access.
 

package/.docs/docs/deployment/web-framework.md

@@ -1,8 +1,8 @@
-# Deploy with a Web Framework
+# Deploy with a web framework
 
 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](https://mastra.ai/reference/storage/libsql) from your Mastra configuration. LibSQLStore requires filesystem access and is not compatible with serverless platforms.
+> **Warning:** If you're deploying to a cloud provider, remove any usage of [LibSQLStore](https://mastra.ai/reference/storage/libsql) from your Mastra configuration. LibSQLStore requires filesystem access and isn't compatible with serverless platforms.
 
 Integration guides:
 

package/.docs/docs/deployment/workflow-runners.md

@@ -1,4 +1,4 @@
-# Workflow Runners
+# Workflow runners
 
 Mastra [workflows](https://mastra.ai/docs/workflows/overview) can be executed using the built-in workflow runner or deployed to specialized workflow execution platforms that handle orchestration, monitoring, and reliability.
 

package/.docs/docs/evals/built-in-scorers.md

@@ -1,4 +1,4 @@
-# Built-in Scorers
+# 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.
 

package/.docs/docs/evals/custom-scorers.md

@@ -2,7 +2,7 @@
 
 Mastra provides a unified `createScorer` factory that allows you to build custom evaluation logic using either JavaScript functions or LLM-based prompt objects for each step. This flexibility lets you choose the best approach for each part of your evaluation pipeline.
 
-## The Four-Step Pipeline
+## The four-step pipeline
 
 All scorers in Mastra follow a consistent four-step evaluation pipeline:
 
@@ -13,7 +13,7 @@ All scorers in Mastra follow a consistent four-step evaluation pipeline:
 
 Each step can use either **functions** or **prompt objects** (LLM-based evaluation), giving you the flexibility to combine deterministic algorithms with AI judgment as needed.
 
-## Functions vs Prompt Objects
+## Functions vs prompt objects
 
 **Functions** use JavaScript for deterministic logic. They're ideal for:
 
@@ -33,7 +33,7 @@ Each step can use either **functions** or **prompt objects** (LLM-based evaluati
 
 You can mix and match approaches within a single scorer - for example, use a function for preprocessing data and an LLM for analyzing quality.
 
-## Initializing a Scorer
+## Initializing a scorer
 
 Every scorer starts with the `createScorer` factory function, which requires an id and description, and optionally accepts a type specification and judge configuration.
 
@@ -113,7 +113,7 @@ const myScorer = createScorer({
 })
 ```
 
-## Step-by-Step Breakdown
+## Step-by-step breakdown
 
 ### preprocess Step (Optional)
 
@@ -207,7 +207,7 @@ const glutenCheckerScorer = createScorer({...})
 
 **Data Flow:** Results are available to subsequent steps as `results.analyzeStepResult`
 
-### generateScore Step (Required)
+### `generateScore` step (required)
 
 Converts analysis results into a numerical score. This is the only required step in the pipeline.
 
@@ -230,7 +230,7 @@ const glutenCheckerScorer = createScorer({...})
 
 **Data Flow:** The score is available to generateReason as the `score` parameter
 
-### generateReason Step (Optional)
+### `generateReason` step (optional)
 
 Generates human-readable explanations for the score, useful for debugging, transparency, or user feedback.
 

package/.docs/docs/evals/overview.md

@@ -6,9 +6,9 @@ Scorers are automated tests that evaluate Agents outputs using model-graded, rul
 
 Scorers can be run in the cloud, capturing real-time results. But scorers can also be part of your CI/CD pipeline, allowing you to test and monitor your agents over time.
 
-## Types of Scorers
+## Types of scorers
 
-There are different kinds of scorers, each serving a specific purpose. Here are some common types:
+Mastra provides different kinds of scorers, each serving a specific purpose. Here are some common types:
 
 1. **Textual Scorers**: Evaluate accuracy, reliability, and context understanding of agent responses
 2. **Classification Scorers**: Measure accuracy in categorizing data based on predefined categories