@mastra/mcp-docs-server 1.1.9-alpha.0 → 1.1.9-alpha.2

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

@@ -131,7 +131,7 @@ const response = await memoryAgent.generate("What's my favorite color?", {
 
 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/network-approval.md

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

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

@@ -1,4 +1,4 @@
-# Agent Networks
+# Agent networks
 
 > **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:
 >

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.
 

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:
 
@@ -324,7 +324,7 @@ The `processOutputStream` method receives all streaming chunks. To also receive
 
 #### 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 makes it easy to access token usage, generated text, finish reason, and step details.
+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'
@@ -466,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.
 
@@ -506,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.
 
@@ -532,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.
 

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.
 

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.
 

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.
 

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'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,6 +1,6 @@
 # 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.
 

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.
 

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,4 +1,4 @@
-# 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).
 

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

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

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,7 +6,7 @@ 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
 
 Mastra provides different kinds of scorers, each serving a specific purpose. Here are some common types:
 

package/.docs/docs/evals/running-in-ci.md

@@ -1,12 +1,12 @@
-# Running Scorers in CI
+# Running scorers in CI
 
 Running scorers in your CI pipeline provides quantifiable metrics for measuring agent quality over time. The `runEvals` function processes multiple test cases through your agent or workflow and returns aggregate scores.
 
-## Basic Setup
+## Basic setup
 
 You can use any testing framework that supports ESM modules, such as [Vitest](https://vitest.dev/), [Jest](https://jestjs.io/), or [Mocha](https://mochajs.org/).
 
-## Creating Test Cases
+## Creating test cases
 
 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.
 
@@ -44,7 +44,7 @@ describe('Weather Agent Tests', () => {
 })
 ```
 
-## Understanding Results
+## Understanding results
 
 The `runEvals` function returns an object with:
 
@@ -63,7 +63,7 @@ The `runEvals` function returns an object with:
 }
 ```
 
-## Multiple Test Scenarios
+## Multiple test scenarios
 
 Create separate test cases for different evaluation scenarios:
 
@@ -117,7 +117,7 @@ describe('Weather Agent Tests', () => {
 })
 ```
 
-## Next Steps
+## Next steps
 
 - Learn about [creating custom scorers](https://mastra.ai/docs/evals/custom-scorers)
 - Explore [built-in scorers](https://mastra.ai/docs/evals/built-in-scorers)

package/.docs/docs/getting-started/build-with-ai.md

@@ -2,7 +2,7 @@
 
 AI agents may not have up-to-date knowledge about Mastra's APIs, patterns, and best practices. These resources give your AI tools direct access to current Mastra documentation, enabling them to generate accurate code and help you build faster.
 
-## Mastra Skills
+## Mastra skills
 
 Agent Skills are folders of instructions, scripts, and resources that agents can discover and use to do things more accurately and efficiently. [Mastra Skills](https://mastra.ai/docs/build-with-ai/skills) contain setup instructions, best practices, and instructions on how to fetch up-to-date information from Mastra's documentation.
 
@@ -34,7 +34,7 @@ Read the dedicated [Mastra Skills](https://mastra.ai/docs/build-with-ai/skills)
 
 > **Tip:** If you're interested in giving your agent access to Mastra's documentation, we recommend using **Skills**. While the MCP Docs Server also provides this information, Skills will perform better. Use the MCP Docs Server when you need its tools, e.g. the migration tool.
 
-## MCP Docs Server
+## MCP docs server
 
 In addition to documentation access, the [MCP Docs Server](https://mastra.ai/docs/build-with-ai/mcp-docs-server) also provides tools to help you migrate to newer versions of Mastra or follow the [Mastra 101 course](https://mastra.ai/course).
 

package/.docs/docs/getting-started/manual-install.md

@@ -1,4 +1,4 @@
-# Manual Install
+# Manual install
 
 > **Info:** Use this guide to manually build a standalone Mastra server step by step. In most cases, it's quicker to follow the [quickstart guide](https://mastra.ai/guides/getting-started/quickstart), which achieves the same result using the [`mastra create`](https://mastra.ai/reference/cli/create-mastra) command. For existing projects, you can also use [`mastra init`](https://mastra.ai/reference/cli/mastra).
 

package/.docs/docs/getting-started/project-structure.md

@@ -1,4 +1,4 @@
-# Project Structure
+# Project structure
 
 Your new Mastra project, created with the `create mastra` command, comes with a predefined set of files and folders to help you get started.
 

package/.docs/docs/index.md

@@ -1,4 +1,4 @@
-# Get Started
+# Get started
 
 Build AI agents your users actually depend on. Mastra is a TypeScript framework that gives you everything you need to prototype fast and ship with confidence. Create your first agent with a single command and start building.
 

package/.docs/docs/mcp/overview.md

@@ -1,4 +1,4 @@
-# MCP Overview
+# MCP overview
 
 Mastra supports the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction), an open standard for connecting AI agents to external tools and resources. It serves as a universal plugin system, enabling agents to call tools regardless of language or hosting environment.
 

package/.docs/docs/mcp/publishing-mcp-server.md

@@ -1,4 +1,4 @@
-# Publishing an MCP Server
+# Publishing an MCP server
 
 This example guides you through setting up a basic Mastra MCPServer using the stdio transport, building it, and preparing it for publishing to NPM.
 
@@ -10,7 +10,7 @@ Install the necessary packages:
 pnpm add @mastra/mcp @mastra/core tsup
 ```
 
-## Setting up an MCP Server
+## Setting up an MCP server
 
 1. Create a file for your stdio server, for example, `/src/mastra/stdio.ts`.
 
@@ -70,7 +70,7 @@ To make your MCP server available for others (or yourself) to use via `npx` or a
 
    For more details on publishing packages, refer to the [NPM documentation](https://docs.npmjs.com/creating-and-publishing-scoped-public-packages).
 
-## Using a published MCP Server
+## Using a published MCP server
 
 Once published, your MCP server can be used by an `MCPClient` by specifying the command to run your package. You can also use any other MCP client like Claude desktop, Cursor, or Windsurf.
 

package/.docs/docs/memory/memory-processors.md

@@ -1,4 +1,4 @@
-# Memory Processors
+# Memory processors
 
 Memory processors transform and filter messages as they pass through an agent with memory enabled. They manage context window limits, remove unnecessary content, and optimize the information sent to the language model.
 
@@ -6,11 +6,11 @@ When memory is enabled on an agent, Mastra adds memory processors to the agent's
 
 Memory processors are [processors](https://mastra.ai/docs/agents/processors) that operate specifically on memory-related messages and state.
 
-## Built-in Memory Processors
+## Built-in memory processors
 
 Mastra automatically adds these processors when memory is enabled:
 
-### MessageHistory
+### `MessageHistory`
 
 Retrieves message history and persists new messages.
 
@@ -56,7 +56,7 @@ const agent = new Agent({
 })
 ```
 
-### SemanticRecall
+### `SemanticRecall`
 
 Retrieves semantically relevant messages based on the current input and creates embeddings for new messages.
 
@@ -114,7 +114,7 @@ const agent = new Agent({
 })
 ```
 
-### WorkingMemory
+### `WorkingMemory`
 
 Manages working memory state across conversations.
 
@@ -159,7 +159,7 @@ const agent = new Agent({
 })
 ```
 
-## Manual Control and Deduplication
+## Manual control and deduplication
 
 If you manually add a memory processor to `inputProcessors` or `outputProcessors`, Mastra **won't** automatically add it. This gives you full control over processor ordering:
 
@@ -192,7 +192,7 @@ const agent = new Agent({
 })
 ```
 
-## Processor Execution Order
+## Processor execution order
 
 Understanding the execution order is important when combining guardrails with memory:
 
@@ -218,7 +218,7 @@ This means memory loads message history before your processors can validate or f
 
 This ordering is designed to be **safe by default**: if your output guardrail calls `abort()`, the memory processors never run and **no messages are saved**.
 
-## Guardrails and Memory
+## Guardrails and memory
 
 The default execution order provides safe guardrail behavior:
 

package/.docs/docs/memory/message-history.md

@@ -1,4 +1,4 @@
-# Message History
+# Message history
 
 Message history is the most basic and important form of memory. It gives the LLM a view of recent messages in the context window, enabling your agent to reference earlier exchanges and respond coherently.
 
@@ -103,7 +103,7 @@ You can use this history in two ways:
 - **Automatic inclusion** - Mastra automatically fetches and includes recent messages in the context window. By default, it includes the last 10 messages, keeping agents grounded in the conversation. You can adjust this number with `lastMessages`, but in most cases you don't need to think about it.
 - [**Manual querying**](#querying) - For more control, use the `recall()` function to query threads and messages directly. This lets you choose exactly which memories are included in the context window, or fetch messages to render conversation history in your UI.
 
-## Accessing Memory
+## Accessing memory
 
 To access memory functions for querying, cloning, or deleting threads and messages, call `getMemory()` on an agent:
 

package/.docs/docs/memory/observational-memory.md

@@ -1,10 +1,10 @@
-# Observational Memory
+# Observational memory
 
 **Added in:** `@mastra/memory@1.1.0`
 
 Observational Memory (OM) is Mastra's memory system for long-context agentic memory. Two background agents — an **Observer** and a **Reflector** — watch your agent's conversations and maintain a dense observation log that replaces raw message history as it grows.
 
-## Quick Start
+## Quick start
 
 Enable `observationalMemory` in the memory options when creating your agent:
 
@@ -46,7 +46,7 @@ See [configuration options](https://mastra.ai/reference/memory/observational-mem
 - **Compression**: Raw message history and tool results get compressed into a dense observation log. Smaller context means faster responses and longer coherent conversations.
 - **Zero context rot**: The agent sees relevant information instead of noisy tool calls and irrelevant tokens, so the agent stays on task over long sessions.
 
-## How It Works
+## How it works
 
 You don't remember every word of every conversation you've ever had. You observe what happened subconsciously, then your brain reflects — reorganizing, combining, and condensing into long-term memory. OM works the same way.
 
@@ -149,7 +149,7 @@ For your use-case this may not be a problem, so your mileage may vary.
 
 > **Warning:** In resource scope, unobserved messages across _all_ threads are processed together. For users with many existing threads, this can be slow. Use thread scope for existing apps.
 
-## Token Budgets
+## Token budgets
 
 OM uses token thresholds to decide when to observe and reflect. See [token budget configuration](https://mastra.ai/reference/memory/observational-memory) for details.
 
@@ -183,7 +183,7 @@ OM caches tiktoken part estimates in message metadata to reduce repeat counting
 - Message and conversation overhead are still recalculated on every pass. The cache only stores payload estimates, so counting semantics stay the same.
 - `data-*` and `reasoning` parts are still skipped and aren't cached.
 
-## Async Buffering
+## Async buffering
 
 Without async buffering, the Observer runs synchronously when the message threshold is reached — the agent pauses mid-conversation while the Observer LLM call completes. With async buffering (enabled by default), observations are pre-computed in the background as the conversation grows. When the threshold is hit, buffered observations activate instantly with no pause.