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

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.
 
@@ -32,9 +32,9 @@ bun x skills add mastra-ai/skills
 
 Read the dedicated [Mastra Skills](https://mastra.ai/docs/build-with-ai/skills) guide to learn more about installation options and available skills.
 
-> **Tip:** If you're just 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.
+> **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,8 +1,8 @@
-# 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.
 
-Mastra is a framework, but it's **unopinionated** about how you organize or colocate your files. The CLI provides a sensible default structure that works well for most projects, but you're free to adapt it to your workflow or team conventions. You could even build your entire project in a single file if you wanted! Whatever structure you choose, keep it consistent to ensure your code stays maintainable and easy to navigate.
+Mastra is a framework, but it's **unopinionated** about how you organize or colocate your files. The CLI provides a sensible default structure that works well for most projects, but you're free to adapt it to your workflow or team conventions. You could even build your entire project in a single file if you wanted! Whatever structure you choose, keep it consistent to ensure your code stays maintainable and straightforward to navigate.
 
 ## Default project structure
 

package/.docs/docs/index.md

@@ -1,10 +1,10 @@
-# Get Started
+# Get started
 
-Mastra is a TypeScript framework for building AI agents, workflows, and tools. Create your first project in seconds and start building.
+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.
 
 ## Quickstart
 
-Run the command below to create a new Mastra project with an example agent:
+Run this command to create a new project you can test immediately in [Studio](https://mastra.ai/docs/getting-started/studio):
 
 **npm**:
 
@@ -30,11 +30,11 @@ yarn create mastra
 bunx create-mastra
 ```
 
-This sets up a project you can test immediately in [Studio](https://mastra.ai/docs/getting-started/studio). See the [quickstart guide](https://mastra.ai/guides/getting-started/quickstart) for a full walkthrough.
+See the [quickstart guide](https://mastra.ai/guides/getting-started/quickstart) for a full walkthrough.
 
 ## Integrate with your framework
 
-Add Mastra to an existing project or create a new app with your preferred framework.
+Add Mastra to an existing project, or create a new app with your preferred framework:
 
 - [Next.js](https://mastra.ai/guides/getting-started/next-js)
 - [React](https://mastra.ai/guides/getting-started/vite-react)
@@ -45,43 +45,89 @@ Add Mastra to an existing project or create a new app with your preferred framew
 
 For other frameworks, see the [framework integration guides](https://mastra.ai/guides/getting-started/next-js).
 
-## What you can do
+## What you can build
+
+Here are some of the ways you can use Mastra:
+
+<details>
+**Embed agents in your product**
+
+Add AI capabilities to your platform so your users can build or interact with agents.
+
+Used by [Replit](https://mastra.ai/blog/replitagent3), [Fireworks](https://mastra.ai/blog/fireworks-xml-prompting), [Medusa](https://mastra.ai/blog/medusa-ecommerce)
+
+</details>
+
+<details>
+**Customer-facing assistants**
+
+Build agents that handle inquiries, schedule appointments, send reminders, and answer questions via chat, WhatsApp, or voice.
+
+Used by [Vetnio](https://mastra.ai/blog/vetnio), [Lua](https://mastra.ai/blog/lua-scaling)
+
+Templates: [Docs Chatbot](https://mastra.ai/templates/docs-chatbot), [Slack Agent](https://mastra.ai/templates/slack-agent)
+
+</details>
 
 <details>
-**Conversational agents**
+**Internal copilots**
+
+Help employees work faster with AI that understands your domain—HR queries, clinical documentation, sales prep, or document generation.
 
-Customer support, onboarding, or internal query bots. Agents maintain context across sessions with thread-based message history and observational memory — background agents that compress conversation history into dense observation logs, keeping the context window small while preserving long-term recall. Stream responses token-by-token for responsive chat UIs. Attach tools so agents can look up orders, create tickets, or call APIs mid-conversation.
+Used by [Factorial](https://mastra.ai/blog/factorial-case-study), [Counsel Health](https://mastra.ai/blog/counsel-health), [Cedar](https://mastra.ai/blog/cedar-case-study), [SoftBank](https://mastra.ai/blog/softbank-productivity-mastra-2025-08-20)
+
+Templates: [Chat with PDF](https://mastra.ai/templates/chat-with-pdf), [Google Sheet Analysis](https://mastra.ai/templates/google-sheets-analysis)
 
 </details>
 
 <details>
-**Domain-specific copilots**
+**Data analysis agents**
+
+Let users query databases and dashboards in natural language. Connect to your data sources and return answers, charts, or reports.
 
-Assistants for coding, legal, finance, research, or creative work. Ground agents in your own data with a full RAG pipeline — chunking, embedding, vector storage across 12+ providers, metadata filtering, and re-ranking. Customize behavior with dynamic instructions that adapt per user or request. Connect to external services through typed tools and MCP servers. Add voice interaction with 12+ speech providers, and measure output quality with built-in evaluation scorers.
+Used by [Index](https://mastra.ai/blog/index-case-study), [PLAID Japan](https://mastra.ai/blog/plaid-jpn-gcp-agents)
+
+Templates: [Chat with Database](https://mastra.ai/templates/text-to-sql), [CSV to Questions](https://mastra.ai/templates/csv-to-questions)
 
 </details>
 
 <details>
-**Workflow automations**
+**Content automation**
+
+Generate, transform, and manage structured content at scale—whether for a CMS, knowledge base, or documentation system.
+
+Used by [Sanity](https://mastra.ai/blog/sanity)
 
-Multi-step processes that trigger, route, and complete tasks. Define type-safe steps with Zod-validated inputs and outputs, then compose them with sequential chaining, parallel fan-out, conditional branching, loops, and iteration with concurrency control. Suspend workflows mid-execution to wait for human approval or external events, then resume from where they left off. Nest workflows inside other workflows for reusable sub-pipelines.
+Templates: [Chat with YouTube](https://mastra.ai/templates/chat-with-youtube), [Flash Cards from PDF](https://mastra.ai/templates/flash-cards-from-pdf)
 
 </details>
 
 <details>
-**Decision-support tools**
+**DevOps & engineering automation**
 
-Systems that analyze data and provide actionable recommendations. Compose multiple tools so agents can query databases, call APIs, and run analysis functions in a single interaction. Use structured output with Zod schemas to return validated, typed results. Coordinate specialist agents through supervisor patterns, with task-completion scoring to verify recommendation quality before finalizing. Add human-in-the-loop gates for high-stakes decisions.
+Automate deployments, debug production issues, manage infrastructure, and handle on-call workflows.
+
+Used by [StarSling](https://mastra.ai/blog/starsling)
+
+Templates: [GitHub PR Code Review](https://mastra.ai/templates/github-pr-code-review-agent), [Browser Agent](https://mastra.ai/templates/browsing-agent)
 
 </details>
 
 <details>
-**AI-powered applications**
+**Sales & GTM workflows**
+
+Turn customer conversations into structured tasks, generate investment memos, or automate outreach sequences.
 
-Products that combine language understanding, reasoning, and action. Orchestrate multiple agents with supervisor delegation and multi-agent networks. Deploy to any Node.js runtime, cloud provider, or framework — Vercel, Cloudflare, Next.js, Astro, and more. Monitor production behavior with AI-specific tracing that captures token usage, latency, and decision paths. Choose from 10+ storage providers and configure composite backends optimized per workload. Test everything interactively in Studio before shipping.
+Used by [Kestral](https://mastra.ai/blog/kestral), [Orange Collective](https://mastra.ai/blog/orange-collective-vc-operating-system), [WorkOS](https://mastra.ai/blog/workos-teaching-mastra)
+
+Templates: [Customer Feedback Summarization](https://mastra.ai/templates/customer-feedback-summarization)
 
 </details>
 
-Browse [templates](https://mastra.ai/templates) from Mastra and the community to see working examples of these use cases.
+Browse [templates](https://mastra.ai/templates) for working examples.
+
+## Not ready to build yet?
+
+Watch this quick introduction:
 
 [YouTube video player](https://www.youtube-nocookie.com/embed/1qnmnRICX50)

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

@@ -6,7 +6,7 @@ Deploy your Mastra application to production and expose your agents, tools, and
 
 ## Enable deployments
 
-After [setting up your project](https://mastra.ai/docs/mastra-cloud/setup), click **Deployment** in the sidebar and select **Enable Deployments**.
+After [setting up your project](https://mastra.ai/docs/mastra-cloud/setup), select **Deployment** in the sidebar and select **Enable Deployments**.
 
 Once enabled, your project automatically builds and deploys. Future pushes to your main branch trigger automatic redeployments.
 

package/.docs/docs/mastra-cloud/studio.md

@@ -12,7 +12,7 @@ See the [Studio documentation](https://mastra.ai/docs/getting-started/studio) fo
 
 ## Sharing access
 
-To invite team members, go to [Mastra Cloud](https://cloud.mastra.ai), click **Team Settings**, then **Members** to add them. Once invited, they can sign in and access your project's Studio.
+To invite team members, go to [Mastra Cloud](https://cloud.mastra.ai), select **Team Settings**, then **Members** to add them. Once invited, they can sign in and access your project's Studio.
 
 ![Invite team members](/assets/images/mastra-cloud-invite-c91b5a0fff03de5ecba3e0162484c819.png)
 

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.
 
@@ -92,4 +92,4 @@ const tools = await mcp.listTools()
 const toolsets = await mcp.listToolsets()
 ```
 
-Note: If you published without an organization scope, the `args` might just be `["-y", "your-package-name@latest"]`.
+Note: If you published without an organization scope, the `args` might be `["-y", "your-package-name@latest"]`.

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,9 +159,9 @@ const agent = new Agent({
 })
 ```
 
-## Manual Control and Deduplication
+## Manual control and deduplication
 
-If you manually add a memory processor to `inputProcessors` or `outputProcessors`, Mastra will **not** automatically add it. This gives you full control over processor ordering:
+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:
 
 ```typescript
 import { Agent } from '@mastra/core/agent'
@@ -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.
 
@@ -98,12 +98,12 @@ await agent.stream('Hello', {
 
 > **Info:** Threads and messages are created automatically when you call `agent.generate()` or `agent.stream()`, but you can also create them manually with [`createThread()`](https://mastra.ai/reference/memory/createThread) and [`saveMessages()`](https://mastra.ai/reference/memory/memory-class).
 
-There are two ways to use this history:
+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:
 
@@ -118,7 +118,7 @@ The `Memory` instance gives you access to functions for listing threads, recalli
 
 Use these methods to fetch threads and messages for displaying conversation history in your UI or for custom memory retrieval logic.
 
-> **Warning:** The memory system does not enforce access control. Before running any query, verify in your application logic that the current user is authorized to access the `resourceId` being queried.
+> **Warning:** The memory system doesn't enforce access control. Before running any query, verify in your application logic that the current user is authorized to access the `resourceId` being queried.
 
 ### Threads
 

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.
 
@@ -61,6 +61,10 @@ OM solves both problems by compressing old context into dense observations.
 
 When message history tokens exceed a threshold (default: 30,000), the Observer creates observations — concise notes about what happened:
 
+Image parts contribute to this threshold with model-aware estimates, so multimodal conversations trigger observation at the right time. The same applies to image-like `file` parts when a transport normalizes an uploaded image as a file instead of an image part. For example, OpenAI image detail settings can materially change when OM decides to observe.
+
+The Observer can also see attachments in the history it reviews. OM keeps readable placeholders like `[Image #1: reference-board.png]` or `[File #1: floorplan.pdf]` in the transcript for readability, and forwards the actual attachment parts alongside the text. Image-like `file` parts are upgraded to image inputs for the Observer when possible, while non-image attachments are forwarded as file parts with normalized token counting. This applies to both normal thread observation and batched resource-scope observation.
+
 ```text
 Date: 2026-01-15
 - 🔴 12:10 User is building a Next.js app with Supabase auth, due in 1 week (meaning January 22nd 2026)
@@ -145,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.
 
@@ -177,9 +181,9 @@ OM caches tiktoken part estimates in message metadata to reduce repeat counting
 - Per-part estimates are stored on `part.providerMetadata.mastra` and reused on subsequent passes when the cache version/tokenizer source matches.
 - For string-only message content (without parts), OM uses a message-level metadata fallback cache.
 - 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 are not cached.
+- `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.
 
@@ -224,7 +228,7 @@ const memory = new Memory({
 
 Setting `bufferTokens: false` disables both observation and reflection async buffering. See [async buffering configuration](https://mastra.ai/reference/memory/observational-memory) for the full API.
 
-> **Note:** Async buffering is not supported with `scope: 'resource'`. It is automatically disabled in resource scope.
+> **Note:** Async buffering isn't supported with `scope: 'resource'`. It's automatically disabled in resource scope.
 
 ## Migrating existing threads
 

package/.docs/docs/memory/semantic-recall.md

@@ -1,10 +1,10 @@
-# Semantic Recall
+# Semantic recall
 
 If you ask your friend what they did last weekend, they will search in their memory for events associated with "last weekend" and then tell you what they did. That's sort of like how semantic recall works in Mastra.
 
 > **Watch 📹:** What semantic recall is, how it works, and how to configure it in Mastra → [YouTube (5 minutes)](https://youtu.be/UVZtK8cK8xQ)
 
-## How Semantic Recall Works
+## How semantic recall works
 
 Semantic recall is RAG-based search that helps agents maintain context across longer interactions when messages are no longer within [recent message history](https://mastra.ai/docs/memory/message-history).
 
@@ -16,7 +16,7 @@ When it's enabled, new messages are used to query a vector DB for semantically s
 
 After getting a response from the LLM, all new messages (user, assistant, and tool calls/results) are inserted into the vector DB to be recalled in later interactions.
 
-## Quick Start
+## Quick start
 
 Semantic recall is enabled by default, so if you give your agent memory it will be included:
 
@@ -33,9 +33,9 @@ const agent = new Agent({
 })
 ```
 
-## Using the recall() Method
+## Using the `recall()` method
 
-While `listMessages` retrieves messages by thread ID with basic pagination, [`recall()`](https://mastra.ai/reference/memory/recall) adds support for **semantic search**. When you need to find messages by meaning rather than just recency, use `recall()` with a `vectorSearchString`:
+While `listMessages` retrieves messages by thread ID with basic pagination, [`recall()`](https://mastra.ai/reference/memory/recall) adds support for **semantic search**. When you need to find messages by meaning rather than recency, use `recall()` with a `vectorSearchString`:
 
 ```typescript
 const memory = await agent.getMemory()
@@ -182,7 +182,7 @@ const agent = new Agent({
 })
 ```
 
-### Using FastEmbed (Local)
+### Using FastEmbed (local)
 
 To use FastEmbed (a local embedding model), install `@mastra/fastembed`:
 
@@ -224,7 +224,7 @@ const agent = new Agent({
 })
 ```
 
-## PostgreSQL Index Optimization
+## PostgreSQL index optimization
 
 When using PostgreSQL as your vector store, you can optimize semantic recall performance by configuring the vector index. This is particularly important for large-scale deployments with thousands of messages.
 
@@ -264,7 +264,7 @@ For detailed information about index configuration options and performance tunin
 
 ## Disabling
 
-There is a performance impact to using semantic recall. New messages are converted into embeddings and used to query a vector database before new messages are sent to the LLM.
+Semantic recall has a performance impact. New messages are converted into embeddings and used to query a vector database before new messages are sent to the LLM.
 
 Semantic recall is enabled by default but can be disabled when not needed:
 
@@ -283,6 +283,6 @@ You might want to disable semantic recall in scenarios like:
 - When message history provides sufficient context for the current conversation.
 - In performance-sensitive applications, like realtime two-way audio, where the added latency of creating embeddings and running vector queries is noticeable.
 
-## Viewing Recalled Messages
+## Viewing recalled messages
 
 When tracing is enabled, any messages retrieved via semantic recall will appear in the agent's trace output, alongside recent message history (if configured).

package/.docs/docs/memory/storage.md

@@ -170,7 +170,7 @@ export const agent = new Agent({
 })
 ```
 
-Title generation runs asynchronously after the agent responds and does not affect response time.
+Title generation runs asynchronously after the agent responds and doesn't affect response time.
 
 To optimize cost or behavior, provide a smaller [`model`](https://mastra.ai/models) and custom `instructions`: