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

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,7 +127,7 @@ 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.
 

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,5 +1,7 @@
 # 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.
 
 ## Storage
@@ -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
 
-> **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

@@ -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

@@ -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 makes it easy to 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
   }
 }
 ```

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

@@ -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/using-tools.md

@@ -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

@@ -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

@@ -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/discord.md

@@ -6,4 +6,4 @@ The Discord server has over 1000 members and serves as the main discussion forum
 
 ## 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

@@ -4,7 +4,7 @@
 
 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/mastra-server.md

@@ -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/studio.md

@@ -2,7 +2,7 @@
 
 [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

@@ -2,7 +2,7 @@
 
 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/evals/overview.md

@@ -8,7 +8,7 @@ Scorers can be run in the cloud, capturing real-time results. But scorers can al
 
 ## 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

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

@@ -32,7 +32,7 @@ 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
 

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

@@ -2,7 +2,7 @@
 
 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
 
-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/publishing-mcp-server.md

@@ -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

@@ -161,7 +161,7 @@ const agent = new Agent({
 
 ## 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'

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

@@ -98,7 +98,7 @@ 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.
@@ -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

@@ -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)
@@ -177,7 +181,7 @@ 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
 
@@ -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

@@ -35,7 +35,7 @@ const agent = new Agent({
 
 ## 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()
@@ -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:
 

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`:
 

package/.docs/docs/memory/working-memory.md

@@ -170,11 +170,11 @@ const memory = new Memory({
 
 ## Designing Effective Templates
 
-A well-structured template keeps the information easy for the agent to parse and update. Treat the template as a short form that you want the assistant to keep up to date.
+A well-structured template keeps the information straightforward for the agent to parse and update. Treat the template as a short form that you want the assistant to keep up to date.
 
-- **Short, focused labels.** Avoid paragraphs or very long headings. Keep labels brief (for example `## Personal Info` or `- Name:`) so updates are easy to read and less likely to be truncated.
+- **Short, focused labels.** Avoid paragraphs or very long headings. Keep labels brief (for example `## Personal Info` or `- Name:`) so updates are readable and less likely to be truncated.
 - **Use consistent casing.** Inconsistent capitalization (`Timezone:` vs `timezone:`) can cause messy updates. Stick to Title Case or lower case for headings and bullet labels.
-- **Keep placeholder text simple.** Use hints such as `[e.g., Formal]` or `[Date]` to help the LLM fill in the correct spots.
+- **Keep placeholder text minimal.** Use hints such as `[e.g., Formal]` or `[Date]` to help the LLM fill in the correct spots.
 - **Abbreviate very long values.** If you only need a short form, include guidance like `- Name: [First name or nickname]` or `- Address (short):` rather than the full legal text.
 - **Mention update rules in `instructions`.** You can instruct how and when to fill or clear parts of the template directly in the agent's `instructions` field.
 
@@ -263,13 +263,13 @@ Schema-based working memory uses **merge semantics**, meaning the agent only nee
 
 - **Object fields are deep merged:** Only provided fields are updated; others remain unchanged
 - **Set a field to `null` to delete it:** This explicitly removes the field from memory
-- **Arrays are replaced entirely:** When an array field is provided, it replaces the existing array (arrays are not merged element-by-element)
+- **Arrays are replaced entirely:** When an array field is provided, it replaces the existing array (arrays aren't merged element-by-element)
 
 ## Choosing Between Template and Schema
 
 - Use a **template** (Markdown) if you want the agent to maintain memory as a free-form text block, such as a user profile or scratchpad. Templates use **replace semantics** — the agent must provide the complete memory content on each update.
 - Use a **schema** if you need structured, type-safe data that can be validated and programmatically accessed as JSON. Schemas use **merge semantics** — the agent only provides fields to update, and existing fields are preserved.
-- Only one mode can be active at a time: setting both `template` and `schema` is not supported.
+- Only one mode can be active at a time: setting both `template` and `schema` isn't supported.
 
 ## Example: Multi-step Retention
 
@@ -301,7 +301,7 @@ Below is a simplified view of how the `User Profile` template updates across a s
 
 The agent can now refer to `Sam` or `Berlin` in later responses without requesting the information again because it has been stored in working memory.
 
-If your agent is not properly updating working memory when you expect it to, you can add system instructions on _how_ and _when_ to use this template in your agent's `instructions` setting.
+If your agent isn't properly updating working memory when you expect it to, you can add system instructions on _how_ and _when_ to use this template in your agent's `instructions` setting.
 
 ## Setting Initial Working Memory