@mastra/mcp-docs-server 1.2.16-alpha.3 → 1.2.16-alpha.6

package/.docs/docs/mastra-platform/github.md

@@ -53,7 +53,7 @@ To cancel a pending request, select **Cancel** next to it in the dashboard.
 
 ## Create a project from a template
 
-Templates are the fastest way to get started. The platform creates a new repository from a Mastra template, links it to a fresh project, provisions any managed databases the template declares, and runs the first deploy.
+Templates are the fastest way to get started. The platform creates a new repository from a Mastra template and links it to a fresh project. It then provisions any managed databases declared by the template and runs the first deploy.
 
 1. In the dashboard, select **Create project** and choose **Start from a template**.
 

package/.docs/docs/mastra-platform/observability.md

@@ -36,7 +36,7 @@ yarn create mastra
 bunx create-mastra
 ```
 
-The create command authenticates with Mastra Platform, creates an observability project, mints an access token, and writes `MASTRA_PLATFORM_ACCESS_TOKEN` and `MASTRA_PROJECT_ID` to `.env`.
+The create command authenticates with Mastra Platform and creates an observability project. It then mints an access token and writes `MASTRA_PLATFORM_ACCESS_TOKEN` and `MASTRA_PROJECT_ID` to `.env`.
 
 ### Existing project
 

package/.docs/docs/mastra-platform/overview.md

@@ -10,7 +10,7 @@ The [Mastra platform](https://projects.mastra.ai) provides three products for de
 
 Deploy with a single command, [`mastra deploy`](https://mastra.ai/docs/mastra-platform/deploy), or connect a GitHub repository for push-to-deploy. See the [GitHub integration](https://mastra.ai/docs/mastra-platform/github) for the repository-linked flow.
 
-Each project can run multiple [**Environments**](https://mastra.ai/docs/mastra-platform/environments) (for example `production` and `staging`), provision [**Hosted databases**](https://mastra.ai/docs/mastra-platform/database) from the CLI or project settings to persist application data, and get a managed [**Workspaces**](https://mastra.ai/docs/mastra-platform/workspaces) per environment that gives agents a filesystem and a sandbox with no manual configuration.
+Each project can run multiple [**Environments**](https://mastra.ai/docs/mastra-platform/environments) (for example `production` and `staging`) and provision [**Hosted databases**](https://mastra.ai/docs/mastra-platform/database) from the CLI or project settings to persist application data. Each environment also gets a managed [**Workspace**](https://mastra.ai/docs/mastra-platform/workspaces) that gives agents a filesystem and sandbox with no manual configuration.
 
 [**Trace Intelligence**](https://mastra.ai/docs/mastra-platform/trace-intelligence) finds recurring goals, outcomes, behaviors, and sentiment across your agent traces. Trace Intelligence is available in private beta for selected projects.
 
@@ -19,7 +19,7 @@ Each project can run multiple [**Environments**](https://mastra.ai/docs/mastra-p
 Choose the path that matches what you want to do:
 
 - **Add hosted observability**: Use [Observability](https://mastra.ai/docs/mastra-platform/observability) to collect searchable traces, logs, and metrics across projects and deploys. Start here if you want monitoring without deploying Studio or Server first.
-- **Deploy Studio**: Use [Studio](https://mastra.ai/docs/mastra-platform/studio) to host the visual development environment for your team. Start here if you want a shared UI for testing agents, running workflows, and inspecting traces.
+- **Deploy Studio**: Use [Studio](https://mastra.ai/docs/mastra-platform/studio) to host the visual development environment for your team. Start here if you want a shared UI for testing agents and running workflows, as well as inspecting traces.
 - **Deploy Server**: Use [Server](https://mastra.ai/docs/mastra-platform/server) to run your Mastra application as a production API server. Start here when you’re ready to serve agents, tools, and workflows from the cloud.
 
 ## Key concepts
@@ -28,7 +28,7 @@ Choose the path that matches what you want to do:
 
 Your Mastra application is built from three building blocks:
 
-- [Agents](https://mastra.ai/docs/agents/overview): AI agents that can use tools, follow instructions, and maintain context
+- [Agents](https://mastra.ai/docs/agents/overview): AI agents that can use tools and follow instructions while maintaining context
 - [Tools](https://mastra.ai/docs/agents/using-tools): Callable functions and integrations available to your agents
 - [Workflows](https://mastra.ai/docs/workflows/overview): Multi-step orchestration pipelines that coordinate agents and tools
 

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

@@ -4,7 +4,7 @@
 
 Server on Mastra platform is a production deployment target that runs your Mastra application as an API server. Use it when you want the platform to build, deploy, host, and manage your Mastra server.
 
-You get a stable API endpoint, environment variable management, custom domain support, and deploy history out of the box.
+You get a stable API endpoint with environment variable management and custom domain support, plus deploy history out of the box.
 
 > **Note:** `mastra server deploy` is the earlier split deploy path. New projects should use the unified [`mastra deploy`](https://mastra.ai/docs/mastra-platform/deploy) command, which adds preflight validation, environments, and CLI-managed databases.
 
@@ -60,7 +60,7 @@ You get a stable API endpoint, environment variable management, custom domain su
 
 ## Deploy lifecycle
 
-A deploy transitions through **queued → uploading → building → deploying → running** (or **failed**, **cancelled**, **crashed**, or **stopped**). Only one build runs per project at a time. If multiple deploys queue up, only the latest proceeds and the rest are cancelled. Builds running longer than 15 minutes are automatically failed. The first deploy provisions infrastructure and seeds environment variables from your local `.env`. Your server URL remains stable across deploys.
+A deploy transitions through **queued → uploading → building → deploying → running** (or **failed**, **cancelled**, **crashed**, or **stopped**). A project runs one build at a time. When multiple deploys queue up, the latest proceeds and the rest are cancelled. Builds running longer than 15 minutes are automatically failed. The first deploy provisions infrastructure and seeds environment variables from your local `.env`. Your server URL remains stable across deploys.
 
 ## Idle behavior
 

package/.docs/docs/mastra-platform/trace-intelligence.md

@@ -2,7 +2,7 @@
 
 # Trace Intelligence on Mastra platform
 
-Trace Intelligence finds recurring patterns across your agent's interactions. It analyzes traces captured by Mastra Observability, produces trace signals for four dimensions, and clusters similar trace signals into themes.
+Trace Intelligence finds recurring patterns across your agent's interactions. It analyzes traces captured by Mastra Observability and produces trace signals for four dimensions. It then clusters similar trace signals into themes.
 
 Use Trace Intelligence to investigate questions such as:
 
@@ -27,7 +27,7 @@ Once Mastra enrolls the project, you don't need to change your agent definition
 
 Trace Intelligence needs enough processed traces from one agent to identify recurring patterns. Initial themes are usually available after at least **100 completed traces** from that agent have been processed.
 
-The trace count under **Traces** can reach 100 before Trace Intelligence is ready because the analysis pipeline runs asynchronously. Processing can take several minutes after the threshold is reached. Traces that can't be analyzed don't contribute, so 100 is a minimum, not an exact UI trigger.
+The trace count under **Traces** can reach 100 before Trace Intelligence is ready because the analysis pipeline runs asynchronously. Processing can take several minutes after the threshold is reached. Traces that can't be analyzed don't contribute. As a result, 100 is a minimum rather than an exact UI trigger.
 
 Trace Intelligence updates automatically as more traces arrive. Studio needs themes for at least two trace signal types before it can display the relationship flow.
 
@@ -90,7 +90,7 @@ Filtering the flow by a theme is unavailable for snapshots with more than 2,000
 
 ### Intelligence isn't in the sidebar
 
-Confirm that Mastra enrolled the correct project, that you use the beta-compatible Mastra version, and that you redeployed Studio. The private beta doesn't support local Studio.
+Confirm that Mastra enrolled the correct project, that you use the beta-compatible Mastra version, and that you redeployed Studio because the private beta doesn't support local Studio.
 
 ### An agent is missing
 

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

@@ -163,7 +163,7 @@ const agent = new Agent({
 
 ## 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:
+If you manually add a memory processor to `inputProcessors` or `outputProcessors`, Mastra **won't** automatically add it. Manual configuration gives you full control over processor ordering:
 
 ```typescript
 import { Agent } from '@mastra/core/agent'

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

@@ -117,7 +117,7 @@ await agent.stream('Hello', {
 
 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.
+- **Automatic inclusion**: Mastra automatically fetches recent messages and includes them in the context window. By default, the last 10 messages keep 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.
 
 > **Tip:** When memory is enabled, [Studio](https://mastra.ai/docs/studio/overview) uses message history to display past conversations in the chat sidebar.
@@ -339,7 +339,7 @@ const { thread, clonedMessages } = await memory.cloneThread({
 })
 ```
 
-You can filter which messages get cloned (by count or date range), specify custom thread IDs, and use utility methods to inspect clone relationships.
+You can filter cloned messages by count or date range and specify custom thread IDs. Utility methods are also available to inspect clone relationships.
 
 See [`cloneThread()`](https://mastra.ai/reference/memory/cloneThread) and [clone utilities](https://mastra.ai/reference/memory/clone-utilities) for the full API.
 

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

@@ -418,7 +418,7 @@ With default settings, the context window doesn't grow unbounded. It oscillates
 3. **Repeat**: History grows from \~6k back toward 30k and shrinks again. Each cycle appends to the observation log, which grows much more slowly than raw history.
 4. **Observations reach 40k**: The Reflector creates a smaller log from the current observations and any earlier reflections.
 
-In the normal buffered cycle, raw history oscillates between roughly 6k and 30k tokens. The observation log stays around 40k tokens, however long the conversation runs. These are activation thresholds rather than hard caps. If background buffering doesn't keep pace, history can grow past the threshold until `blockAfter` (default `1.2`) forces a synchronous observation at \~36k tokens (\~48k for reflection) as a safety ceiling.
+In the normal buffered cycle, raw history oscillates between roughly 6k and 30k tokens. The observation log stays around 40k tokens, however long the conversation runs. These are activation thresholds rather than hard caps, so history can grow past the threshold whenever background buffering doesn't keep pace. Above `blockAfter` (default `1.2`, \~36k tokens) activation is allowed to overshoot the retention target instead of activating fewer chunks. It doesn't drain the buffer, and with the default settings it removes the same amount of history as below the threshold. Reflection falls back to a synchronous run above its own `blockAfter` (\~48k tokens).
 
 With [`shareTokenBudget`](https://mastra.ai/reference/memory/observational-memory) enabled, the two budgets pool together. While the observation log is small, message history can expand into the unused observation space (up to \~70k tokens with the defaults) before observation triggers. It then shrinks as observations accumulate.
 
@@ -714,23 +714,23 @@ When message tokens reach the `messageTokens` threshold, buffered chunks activat
 
 Buffered observations also include continuation hints, a suggested next response and the current task, so the main agent maintains conversational continuity after activation shrinks the context window.
 
-If the agent produces messages faster than the Observer can process them, a `blockAfter` safety threshold forces a synchronous observation as a last resort. Buffered activation still preserves a minimum remaining context (the smaller of \~1k tokens or the configured retention floor).
+If the agent produces messages faster than the Observer can process them, the `blockAfter` safety threshold lets activation overshoot the retention target instead of activating fewer chunks. It never activates more chunks than are needed to reach that target, and with the default settings it changes nothing. A synchronous observation runs when the `messageTokens` threshold is reached and buffered activation didn't happen. Buffered activation usually preserves a minimum remaining context (the smaller of \~1k tokens or the configured retention floor), but a single buffered chunk that covers the whole pending window still activates and can leave less.
 
 Reflection works similarly, the Reflector runs in the background when observations reach a fraction of the reflection threshold.
 
 ### Settings
 
-| Setting                               | Default | What it controls                                                                                                                                                                                                                                                              |
-| ------------------------------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `observation.bufferTokens`            | `0.2`   | How often to buffer. `0.2` means every 20% of `messageTokens`. With the default 30k threshold, that's roughly every 6k tokens. Can also be an absolute token count (e.g. `5000`).                                                                                             |
-| `observation.bufferActivation`        | `0.8`   | How aggressively to clear the message window on activation. `0.8` means remove enough messages to keep only 20% of `messageTokens` remaining. Lower values keep more message history.                                                                                         |
-| `observation.blockAfter`              | `1.2`   | Safety net if buffering can't keep up. Values from 1 up to (but not including) 100 multiply `messageTokens`: at `1.2`, synchronous observation is forced at 36k tokens (1.2 × 30k). Values of 100 or more are absolute token counts (e.g. `50_000`).                          |
-| `activateAfterIdle`                   | none    | Forces buffered observations to activate after a period of inactivity, even before `observation.messageTokens` is reached. Accepts a numeric millisecond value such as `300_000`, duration strings like `"5m"` or `"1hr"`, or `"auto"` for a provider-aware prompt cache TTL. |
-| `activateOnProviderChange`            | `false` | Forces buffered observations to activate when the next step uses a different `provider/model` than the one that produced the latest assistant step. Use this when switching providers or models would invalidate prompt cache reuse.                                          |
-| `reflection.bufferActivation`         | `0.5`   | When to start background reflection. `0.5` means reflection begins when observations reach 50% of the `observationTokens` threshold.                                                                                                                                          |
-| `reflection.activateAfterIdle`        | none    | Opts buffered reflections into idle activation. Reflections don't inherit top-level `activateAfterIdle`.                                                                                                                                                                      |
-| `reflection.activateOnProviderChange` | `false` | Opts buffered reflections into provider-change activation. Reflections don't inherit top-level `activateOnProviderChange`.                                                                                                                                                    |
-| `reflection.blockAfter`               | `1.2`   | Safety threshold for reflection, same logic as observation.                                                                                                                                                                                                                   |
+| Setting                               | Default | What it controls                                                                                                                                                                                                                                                                                                                                                      |
+| ------------------------------------- | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `observation.bufferTokens`            | `0.2`   | How often to buffer. `0.2` means every 20% of `messageTokens`. With the default 30k threshold, that's roughly every 6k tokens. Can also be an absolute token count (e.g. `5000`).                                                                                                                                                                                     |
+| `observation.bufferActivation`        | `0.8`   | How aggressively to clear the message window on activation. `0.8` means remove enough messages to keep only 20% of `messageTokens` remaining. Lower values keep more message history.                                                                                                                                                                                 |
+| `observation.blockAfter`              | `1.2`   | Safety net if buffering can't keep up. Values from 1 up to (but not including) 100 multiply `messageTokens`: at `1.2`, the threshold is 36k tokens (1.2 × 30k). Above it, activation may overshoot the retention target instead of activating fewer chunks. Values of 100 or more are absolute token counts (e.g. `50_000`) and must be greater than `messageTokens`. |
+| `activateAfterIdle`                   | none    | Forces buffered observations to activate after a period of inactivity, even before `observation.messageTokens` is reached. Accepts a numeric millisecond value such as `300_000`, duration strings like `"5m"` or `"1hr"`, or `"auto"` for a provider-aware prompt cache TTL.                                                                                         |
+| `activateOnProviderChange`            | `false` | Forces buffered observations to activate when the next step uses a different `provider/model` than the one that produced the latest assistant step. Use this when switching providers or models would invalidate prompt cache reuse.                                                                                                                                  |
+| `reflection.bufferActivation`         | `0.5`   | When to start background reflection. `0.5` means reflection begins when observations reach 50% of the `observationTokens` threshold.                                                                                                                                                                                                                                  |
+| `reflection.activateAfterIdle`        | none    | Opts buffered reflections into idle activation. Reflections don't inherit top-level `activateAfterIdle`.                                                                                                                                                                                                                                                              |
+| `reflection.activateOnProviderChange` | `false` | Opts buffered reflections into provider-change activation. Reflections don't inherit top-level `activateOnProviderChange`.                                                                                                                                                                                                                                            |
+| `reflection.blockAfter`               | `1.2`   | Safety threshold for reflection. Same value format as observation (absolute values must be greater than `observationTokens`), but above it reflection runs synchronously when no buffered reflection is ready to activate.                                                                                                                                            |
 
 If you're relying on prompt caching, set `activateAfterIdle` to `"auto"` or to a specific cache TTL. That way, once a thread has been idle long enough for the cache to expire, the next request can activate buffered observations first and send a smaller compressed context window.
 

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

@@ -270,7 +270,7 @@ Supported embedding models:
 
 - **OpenAI**: `text-embedding-3-small`, `text-embedding-3-large`, `text-embedding-ada-002`
 - **Google**: `gemini-embedding-001`
-- **OpenRouter**: Access embedding models from various providers
+- **OpenRouter**: Access embedding models from multiple providers
 
 ```ts
 import { Agent } from '@mastra/core/agent'

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

@@ -213,7 +213,7 @@ const paragraphMemory = new Memory({
 
 ## Structured working memory
 
-Working memory can also be defined using a structured schema instead of a Markdown template. This allows you to specify the exact fields and types that should be tracked, using a [Standard JSON Schema](https://standardschema.dev/json-schema) ([Zod](https://zod.dev/), [Valibot](https://valibot.dev/), [ArkType](https://arktype.io/), etc.). When using a schema, the agent will see and update working memory as a JSON object matching your schema.
+Working memory can also be defined using a structured schema instead of a Markdown template. A [Standard JSON Schema](https://standardschema.dev/json-schema) ([Zod](https://zod.dev/), [Valibot](https://valibot.dev/), [ArkType](https://arktype.io/), etc.). When using a schema, the agent will see and update working memory as a JSON object matching your schema.
 
 **Requirement:** You must specify either `template` or `schema`, but not both.
 

package/.docs/docs/observability/logging.md

@@ -28,7 +28,7 @@ Visit [PinoLogger](https://mastra.ai/reference/logging/pino-logger) for all avai
 
 ## Logging to observability storage
 
-When [observability](https://mastra.ai/docs/observability/overview) is configured, all logger calls are automatically forwarded to your observability storage. This means every `debug`, `info`, `warn`, `error`, and `trackException` call from your application and from Mastra's internal components is stored alongside your traces.
+When [observability](https://mastra.ai/docs/observability/overview) is configured, all logger calls are automatically forwarded to your observability storage. Every `debug`, `info`, `warn`, `error`, and `trackException` call from your application and from Mastra's internal components is stored alongside your traces.
 
 No code changes are required. Mastra wraps the configured logger so that it writes to both the original logger (console, file, or custom transport) and the observability system simultaneously.
 

package/.docs/docs/observability/metrics/querying.md

@@ -2,7 +2,7 @@
 
 # Querying metrics
 
-Mastra exposes the same five OLAP queries (`getMetricAggregate`, `getMetricBreakdown`, `getMetricTimeSeries`, `getMetricPercentiles`, and discovery helpers) through three surfaces: an in-process store accessor, the runtime HTTP API, and the `mastra api metric` CLI. All three accept the same Zod-validated input shapes, so you can move from a one-off CLI investigation to a programmatic dashboard tool without re-learning the API.
+Mastra exposes the same five OLAP queries (`getMetricAggregate`, `getMetricBreakdown`, `getMetricTimeSeries`, `getMetricPercentiles`, and discovery helpers) through three surfaces: an in-process store accessor and the runtime HTTP API, plus the `mastra api metric` CLI. All three accept the same Zod-validated input shapes, so you can move from a one-off CLI investigation to a programmatic dashboard tool without re-learning the API.
 
 **For AI agents:** Run `npx mastra api metric aggregate '{"name":"mastra_agent_duration_ms","aggregation":"avg"}'` to query average agent latency directly instead of writing a temporary script. Querying local metrics requires a running Mastra server with an OLAP-capable observability store; start the local server with `npx mastra dev`, or pass the reachable server's base URL with `--url`. Run `npx mastra api metric aggregate --schema` before constructing a different query. Install Mastra's skill with `npx skills add mastra-ai/skills --skill mastra` for complete API CLI discovery, targeting, schema, authentication, and error-handling guidance.
 

package/.docs/docs/observability/tracing/overview.md

@@ -148,7 +148,7 @@ Per-call `tracingOptions.metadata.environment` always takes precedence, so indiv
 
 ### Automatic metadata from `RequestContext`
 
-Instead of manually adding metadata to each span, you can configure Mastra to automatically extract values from RequestContext and attach them as metadata to all spans in a trace. This is useful for consistently tracking user identifiers, environment information, feature flags, or any request-scoped data across your entire trace.
+Instead of manually adding metadata to each span, you can configure Mastra to automatically extract values from RequestContext and attach them as metadata to all spans in a trace. This is useful for consistently tracking user identifiers and environment information, along with feature flags or other request-scoped data across your entire trace.
 
 #### Configuration-level extraction
 
@@ -365,7 +365,7 @@ You get fine-grained control over which child spans include RequestContext metad
 
 ## Creating child spans
 
-Child spans allow you to track fine-grained operations within your workflow steps or tools. They provide visibility into sub-operations like database queries, API calls, file operations, or complex calculations. This hierarchical structure helps you identify performance bottlenecks and understand the exact sequence of operations.
+Child spans allow you to track fine-grained operations within your workflow steps or tools. They provide visibility into sub-operations like database queries and API calls, as well as file operations or complex calculations. This hierarchical structure helps you identify performance bottlenecks and understand the exact sequence of operations.
 
 Create child spans inside a tool call or workflow step to track specific operations:
 
@@ -681,7 +681,7 @@ export const mastra = new Mastra({
 
 ### Use cases
 
-**Increasing limits for debugging**: If your agents or tools work with large documents, API responses, or data structures, increase these limits to capture more context in your traces:
+**Increasing limits for debugging**: Increase these limits to capture more context for large documents and API responses, as well as other data structures:
 
 ```ts
 serializationOptions: {

package/.docs/docs/server/custom-adapters.md

@@ -176,7 +176,7 @@ async getParams(
 
 ### `sendResponse()`
 
-Send the response back to the client based on the route's response type. Mastra routes can return different response types: JSON for most API responses, streams for agent generation, and special types for MCP transports. Your implementation should handle each type appropriately for your framework.
+Send the response back to the client based on the route's response type. Mastra routes can return different response types: JSON for most API responses and streams for agent generation, plus special types for MCP transports. Your implementation should handle each type appropriately for your framework.
 
 ```typescript
 async sendResponse(
@@ -211,7 +211,7 @@ async sendResponse(
 
 ### `stream()`
 
-Handle streaming responses for agent generation. When an agent generates a response, it produces a stream of chunks that should be sent to the client as they become available. This method reads from the stream, optionally applies redaction to hide sensitive data, and writes chunks to the response in the appropriate format (SSE or newline-delimited JSON).
+Handle streaming responses for agent generation. When an agent generates a response, it produces a stream of chunks that should be sent to the client as they become available. This method reads from the stream and optionally applies redaction to hide sensitive data before writing chunks to the response in the appropriate format (SSE or newline-delimited JSON).
 
 ```typescript
 async stream(

package/.docs/docs/server/custom-api-routes.md

@@ -37,7 +37,7 @@ Each route's handler receives the Hono `Context`. Within the handler you can acc
 
 ## Schema validation
 
-Use [`createRoute()`](https://mastra.ai/reference/server/create-route) in `apiRoutes` to parse and validate path parameters, query parameters, and request bodies with Zod. The schemas also infer the handler parameters and generate OpenAPI metadata.
+Use [`createRoute()`](https://mastra.ai/reference/server/create-route) in `apiRoutes` to parse and validate path and query parameters, along with request bodies, using Zod. The schemas also infer the handler parameters and generate OpenAPI metadata.
 
 ```typescript
 import { Mastra } from '@mastra/core'

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

@@ -71,7 +71,7 @@ The Mastra Client SDK exposes all resources served by the Mastra Server.
 
 ## Create and run dynamic workflows
 
-Use `upsertDynamicWorkflow()` to create or replace a persisted workflow definition. A successful upsert validates the complete definition, registers it with the running Mastra instance, and makes it available through the standard workflow execution API.
+Use `upsertDynamicWorkflow()` to create or replace a persisted workflow definition. A successful upsert validates the complete definition and registers it with the running Mastra instance. The workflow then becomes available through the standard execution API.
 
 The following example shows the full lifecycle of a mapping workflow, from creation and inspection through execution and deletion:
 

package/.docs/docs/server/server-adapters.md

@@ -480,7 +480,7 @@ With this prefix, Mastra routes become `/api/v2/agents`, `/api/v2/workflows`, et
 
 ## OpenAPI spec
 
-Mastra can generate an OpenAPI specification for all registered routes. This is useful for documentation, client generation, or integration with API tools. Enable it by setting the `openapiPath` option:
+Mastra can generate an OpenAPI specification for all registered routes. This is useful for documentation or client generation, including integration with API tools. Enable it by setting the `openapiPath` option:
 
 ```typescript
 const server = new MastraServer({

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

@@ -15,7 +15,7 @@ On this page you'll learn how to deploy Studio on your own infrastructure. As th
 
 The easiest way to run Studio is the [`mastra studio`](https://mastra.ai/reference/cli/mastra) command.
 
-Whereas `mastra dev` runs both Studio and an API for development purposes, the purpose of `mastra studio` is to serve a standalone, static UI that connects to an already-running Mastra server. This allows you to deploy Studio on its own, separate from the Mastra server, if desired.
+Whereas `mastra dev` runs both Studio and an API for development purposes, the purpose of `mastra studio` is to serve a standalone, static UI that connects to an already-running Mastra server. You can deploy Studio separately from the Mastra server.
 
 Open a terminal and install the `mastra` CLI globally:
 
@@ -67,7 +67,7 @@ For hosted Studio on Mastra platform, see [Studio on Mastra platform](https://ma
 
 ## 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, as with any web service.
+Running `mastra studio` as a long-running process is no different from running any other Node.js service. The same deployment practices and tools apply here. Use process managers such as PM2 or Docker. Cloud services that support Node.js applications are another option. As with any web service, configure CORS correctly and monitor errors.
 
 > **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/studio/observability.md

@@ -106,7 +106,7 @@ To export a trace, select **Download trace JSON** in the trace panel header. Thi
 
 ## Logs
 
-Browse internal Mastra logs forwarded to your observability storage. Logs provide full-text search (across message content, entity names, and trace IDs), date presets (last 24 hours to 30 days), and multi-select filters for level, entity type, and entity name. Selecting a log opens a detail panel showing the full message, structured data, and metadata. If the log is correlated with a trace, you can move through directly to the trace and span timeline.
+Browse internal Mastra logs forwarded to your observability storage. Logs provide full-text search across message content and entity names, including trace IDs. Date presets range from the last 24 hours to 30 days. Multi-select filters cover level and entity type, along with entity name. Selecting a log opens a detail panel showing the full message, structured data, and metadata. If the log is correlated with a trace, you can move through directly to the trace and span timeline.
 
 Log forwarding is enabled by default when you configure observability. See [logging](https://mastra.ai/docs/observability/logging) for level configuration, query examples, and customization details.
 

package/.docs/docs/studio/overview.md

@@ -59,6 +59,8 @@ You can send a follow-up message in the same thread during an agent response str
 
 Use [Editor](https://mastra.ai/docs/editor/overview) to let non-technical team members iterate on agents and version every change, plus run experiments without redeploying.
 
+Use [Agent Builder](https://agent-builder.mastra.ai) to create and manage fully stored agents through a separate browser-based interface.
+
 ### Workflows
 
 Visualize your workflow as a graph and run it step by step with a custom input. During execution, the interface updates in real time to show the active step and the path taken.

package/.docs/docs/workflows/dynamic-workflows.md

@@ -6,7 +6,7 @@
 
 Dynamic workflows are workflow definitions expressed as data instead of code. A definition is a JSON document that describes the workflow's schemas and step graph. Mastra validates the definition and registers it as a runnable workflow, then persists it in storage so it survives process restarts.
 
-Because a definition contains no JavaScript closures, anything that can produce JSON can author a workflow: an HTTP client, an LLM, a visual editor, or your own tooling. Once registered, a dynamic workflow runs through the same execution API as a code-defined workflow.
+Because a definition contains no JavaScript closures, anything that produces JSON can author a workflow. Sources include an HTTP client or LLM. A visual editor or your own tooling can also produce the definition. Once registered, a dynamic workflow runs through the same execution API as a code-defined workflow.
 
 ## When to use dynamic workflows
 

package/.docs/docs/workflows/scheduled-workflows.md

@@ -161,7 +161,7 @@ Deploy targets such as Fly Machines, Railway, Render, AWS ECS, GKE, or your own
 
 ### Serverless platforms
 
-Functions-as-a-service platforms such as Vercel, Netlify, AWS Lambda, and Cloudflare Workers shut the process down after each request. Because the tick loop doesn't get a second tick, schedules declared in code don't fire on these platforms with the built-in scheduler today.
+Functions-as-a-service platforms such as Vercel, Netlify, AWS Lambda, and Cloudflare Workers shut the process down after each request, so the tick loop doesn't get a second tick and schedules declared in code don't fire with the built-in scheduler today.
 
 On these platforms, use [`@mastra/inngest`](#inngest-workflows) instead. Inngest is serverless-native and holds the cron state for you.
 

package/.docs/docs/workflows/suspend-and-resume.md

@@ -2,7 +2,7 @@
 
 # Suspend and resume
 
-Workflows can be paused at any step to collect additional data, wait for API callbacks, throttle costly operations, or request [human-in-the-loop](https://mastra.ai/docs/workflows/human-in-the-loop) input. When a workflow is suspended, its current execution state is saved as a snapshot. You can later resume the workflow from a [specific step ID](https://mastra.ai/docs/workflows/snapshots), restoring the exact state captured in that snapshot. [Snapshots](https://mastra.ai/docs/workflows/snapshots) are stored in your configured storage provider and persist across deployments and application restarts.
+Workflows can be paused at any step to collect additional data or wait for API callbacks. Pauses can also throttle costly operations or request [human-in-the-loop](https://mastra.ai/docs/workflows/human-in-the-loop) input. When a workflow is suspended, its current execution state is saved as a snapshot. You can later resume the workflow from a [specific step ID](https://mastra.ai/docs/workflows/snapshots), restoring the exact state captured in that snapshot. [Snapshots](https://mastra.ai/docs/workflows/snapshots) are stored in your configured storage provider and persist across deployments and application restarts.
 
 ## Pausing a workflow with `suspend()`
 

package/.docs/docs/workspace/overview.md

@@ -412,4 +412,5 @@ External providers may perform additional setup like establishing connections or
 - [Skills](https://mastra.ai/docs/workspace/skills)
 - [Search and indexing](https://mastra.ai/docs/workspace/search)
 - [Workspace class reference](https://mastra.ai/reference/workspace/workspace-class)
-- 📹 [Introduction to Mastra Workspaces workshop](https://www.youtube.com/watch?v=QcQLiYlJuNQ)
+- 📹 [Introduction to Mastra Workspaces workshop](https://www.youtube.com/watch?v=QcQLiYlJuNQ)
+- [Mastra Factory](https://factory.mastra.ai) and [Mastra Code](https://code.mastra.ai) are examples of workspace-powered coding agents

package/.docs/docs/workspace/search.md

@@ -94,7 +94,7 @@ When the provider supports batching (for example, OpenAI's `embedMany`), pass an
 The following example replaces the single-text embedder with a batched one. The embedder function takes an array and returns an array of embeddings in the same order, plus carries two extra properties:
 
 - `batch: true`: marks the function as batch-capable. Without this property, Mastra calls it one text at a time.
-- `maxBatchSize`: the largest array the provider accepts in one call. Mastra splits larger requests into chunks of this size and sends them in parallel. Set this to your provider's documented limit (for example, 2048 for OpenAI, 96 for Cohere, 128 for Voyage). Omit it to send every pending text in one request.
+- `maxBatchSize`: the largest array the provider accepts in one call. Mastra splits larger requests into chunks of this size and sends them in parallel. Set this to your provider's documented limit. For example, OpenAI accepts 2048 and Cohere accepts 96. Voyage accepts 128. Omit it to send every pending text in one request.
 
 ```typescript
 import { Workspace, LocalFilesystem } from '@mastra/core/workspace'

package/.docs/docs/workspace/skills.md

@@ -136,7 +136,7 @@ When multiple skill directories contain a skill with the same name, all of them
 When the agent activates a skill by name, tie-breaking determines which one is returned:
 
 1. **Source-type priority**: local skills take precedence over managed (`.mastra/`) skills, which take precedence over external (`node_modules/`) skills.
-2. **Unresolvable conflicts throw**: if two skills share the same name and the same source type (for example, two local skills both named `brand-guidelines`), `get()` throws an error. Rename one or move it to a different source type to resolve the conflict.
+2. **Unresolvable conflicts throw**: if two skills share the same name and the same source type (for example, two local skills that both use the name `brand-guidelines`), `get()` throws an error. Rename one or move it to a different source type to resolve the conflict.
 3. **Path escape hatch**: the agent can pass a skill's full path instead of its name to activate a specific skill, bypassing tie-breaking entirely.
 
 ```typescript

package/.docs/integrations/browsers/agent-browser.md

@@ -88,7 +88,7 @@ AgentBrowser uses accessibility tree refs to identify elements. When an agent ca
 
 ## Recording
 
-AgentBrowser can opt into alpha browser recording tools:
+AgentBrowser can opt into Beta browser recording tools:
 
 ```typescript
 const browser = new AgentBrowser({
@@ -99,12 +99,11 @@ const browser = new AgentBrowser({
 })
 ```
 
-This adds `browser_record` and `browser_record_caption` to the agent's toolset. See [Browser recording (alpha)](https://mastra.ai/docs/browser/recording) for details. See [AgentBrowser reference](https://mastra.ai/reference/browser/agent-browser) for all configuration options and tool details.
+This adds `browser_record` and `browser_record_caption` to the agent's toolset. See [Browser recording (Beta)](https://mastra.ai/docs/browser/overview) for details. See [AgentBrowser reference](https://mastra.ai/reference/browser/agent-browser) for all configuration options and tool details.
 
 ## Related
 
 - [Browser overview](https://mastra.ai/docs/browser/overview)
 - [Stagehand](https://mastra.ai/integrations/browsers/stagehand)
 - [Firecrawl](https://mastra.ai/integrations/browsers/firecrawl)
-- [Browser recording (alpha)](https://mastra.ai/docs/browser/recording)
 - [AgentBrowser reference](https://mastra.ai/reference/browser/agent-browser)

package/.docs/integrations/browsers/firecrawl.md

@@ -125,5 +125,4 @@ const browser = new FirecrawlBrowser({
 
 - [Browser overview](https://mastra.ai/docs/browser/overview)
 - [AgentBrowser](https://mastra.ai/integrations/browsers/agent-browser)
-- [Browser recording (alpha)](https://mastra.ai/docs/browser/recording)
 - [FirecrawlBrowser reference](https://mastra.ai/reference/browser/firecrawl-browser)

package/.docs/integrations/browsers/stagehand.md

@@ -150,7 +150,7 @@ See [StagehandBrowser reference](https://mastra.ai/reference/browser/stagehand-b
 
 ## Recording
 
-Stagehand can opt into alpha browser recording tools:
+Stagehand can opt into Beta browser recording tools:
 
 ```typescript
 const browser = new StagehandBrowser({
@@ -162,11 +162,10 @@ const browser = new StagehandBrowser({
 })
 ```
 
-This adds `browser_record` and `browser_record_caption` to the agent's toolset. See [Browser recording (alpha)](https://mastra.ai/docs/browser/recording) for details.
+This adds `browser_record` and `browser_record_caption` to the agent's toolset. See [Browser recording (Beta)](https://mastra.ai/docs/browser/overview) for details.
 
 ## Related
 
 - [Browser overview](https://mastra.ai/docs/browser/overview)
 - [AgentBrowser](https://mastra.ai/integrations/browsers/agent-browser)
-- [Browser recording (alpha)](https://mastra.ai/docs/browser/recording)
 - [StagehandBrowser reference](https://mastra.ai/reference/browser/stagehand-browser)

package/.docs/models/gateways/openrouter.md

@@ -2,7 +2,7 @@
 
 # ![OpenRouter logo](https://models.dev/logos/openrouter.svg)OpenRouter
 
-OpenRouter aggregates models from multiple providers with enhanced features like rate limiting and failover. Access 349 models through Mastra's model router.
+OpenRouter aggregates models from multiple providers with enhanced features like rate limiting and failover. Access 348 models through Mastra's model router.
 
 Learn more in the [OpenRouter documentation](https://openrouter.ai/models).
 
@@ -143,7 +143,6 @@ ANTHROPIC_API_KEY=ant-...
 | `inclusionai/ling-2.6-1t`                                  |
 | `inclusionai/ling-2.6-flash`                               |
 | `inclusionai/ling-3.0-flash`                               |
-| `inclusionai/ling-3.0-tiny:free`                           |
 | `inclusionai/ring-2.6-1t`                                  |
 | `kwaipilot/kat-coder-air-v2.5`                             |
 | `kwaipilot/kat-coder-pro-v2`                               |

package/.docs/models/index.md

@@ -2,7 +2,7 @@
 
 # Model Providers
 
-Mastra provides a unified interface for working with LLMs across multiple providers, giving you access to 5658 models from 171 providers through a single API.
+Mastra provides a unified interface for working with LLMs across multiple providers, giving you access to 5657 models from 171 providers through a single API.
 
 ## Features
 

package/.docs/models/providers/kilo.md

@@ -2,7 +2,7 @@
 
 # ![Kilo Gateway logo](https://models.dev/logos/kilo.svg)Kilo Gateway
 
-Access 357 Kilo Gateway models through Mastra's model router. Authentication is handled automatically using the `KILO_API_KEY` environment variable.
+Access 356 Kilo Gateway models through Mastra's model router. Authentication is handled automatically using the `KILO_API_KEY` environment variable.
 
 Learn more in the [Kilo Gateway documentation](https://kilo.ai).
 
@@ -58,7 +58,7 @@ for await (const chunk of stream) {
 | `kilo/amazon/nova-micro-v1`                                     | 128K    |       |           |       |       |       | $0.04      | $0.14       |
 | `kilo/amazon/nova-premier-v1`                                   | 1.0M    |       |           |       |       |       | $3         | $13         |
 | `kilo/amazon/nova-pro-v1`                                       | 300K    |       |           |       |       |       | $0.80      | $3          |
-| `kilo/anthracite-org/magnum-v4-72b`                             | 16K     |       |           |       |       |       | $3         | $5          |
+| `kilo/anthracite-org/magnum-v4-72b`                             | 33K     |       |           |       |       |       | $3         | $5          |
 | `kilo/anthropic/claude-3-haiku`                                 | 200K    |       |           |       |       |       | $0.25      | $1          |
 | `kilo/anthropic/claude-fable-5`                                 | 1.0M    |       |           |       |       |       | $10        | $50         |
 | `kilo/anthropic/claude-haiku-4.5`                               | 200K    |       |           |       |       |       | $1         | $5          |
@@ -143,7 +143,6 @@ for await (const chunk of stream) {
 | `kilo/inclusionai/ling-2.6-1t`                                  | 262K    |       |           |       |       |       | $0.30      | $3          |
 | `kilo/inclusionai/ling-2.6-flash`                               | 262K    |       |           |       |       |       | $0.10      | $0.30       |
 | `kilo/inclusionai/ling-3.0-flash`                               | 262K    |       |           |       |       |       | $0.06      | $0.18       |
-| `kilo/inclusionai/ling-3.0-tiny:free`                           | 262K    |       |           |       |       |       | —          | —           |
 | `kilo/inclusionai/ring-2.6-1t`                                  | 262K    |       |           |       |       |       | $0.30      | $3          |
 | `kilo/kilo-auto/balanced`                                       | 1.0M    |       |           |       |       |       | $0.33      | $2          |
 | `kilo/kilo-auto/efficient`                                      | 1.0M    |       |           |       |       |       | $0.33      | $2          |
@@ -217,7 +216,7 @@ for await (const chunk of stream) {
 | `kilo/nvidia/nemotron-3-ultra-550b-a55b`                        | 512K    |       |           |       |       |       | $0.50      | $2          |
 | `kilo/nvidia/nemotron-3-ultra-550b-a55b:free`                   | 1.0M    |       |           |       |       |       | —          | —           |
 | `kilo/nvidia/nemotron-3.5-content-safety:free`                  | 128K    |       |           |       |       |       | —          | —           |
-| `kilo/nvidia/nemotron-3.5-lightning`                            | 262K    |       |           |       |       |       | $0.05      | $0.20       |
+| `kilo/nvidia/nemotron-3.5-lightning`                            | 262K    |       |           |       |       |       | $0.08      | $0.20       |
 | `kilo/nvidia/nemotron-3.5-lightning:free`                       | 1.0M    |       |           |       |       |       | —          | —           |
 | `kilo/openai/gpt-3.5-turbo`                                     | 16K     |       |           |       |       |       | $0.50      | $2          |
 | `kilo/openai/gpt-3.5-turbo-0613`                                | 4K      |       |           |       |       |       | $1         | $2          |
@@ -315,7 +314,7 @@ for await (const chunk of stream) {
 | `kilo/qwen/qwen3-max`                                           | 262K    |       |           |       |       |       | $0.78      | $4          |
 | `kilo/qwen/qwen3-max-thinking`                                  | 262K    |       |           |       |       |       | $0.78      | $4          |
 | `kilo/qwen/qwen3-next-80b-a3b-instruct`                         | 262K    |       |           |       |       |       | $0.10      | $0.78       |
-| `kilo/qwen/qwen3-next-80b-a3b-thinking`                         | 262K    |       |           |       |       |       | $0.15      | $1          |
+| `kilo/qwen/qwen3-next-80b-a3b-thinking`                         | 131K    |       |           |       |       |       | $0.15      | $1          |
 | `kilo/qwen/qwen3-vl-235b-a22b-instruct`                         | 131K    |       |           |       |       |       | $0.26      | $1          |
 | `kilo/qwen/qwen3-vl-235b-a22b-thinking`                         | 131K    |       |           |       |       |       | $0.40      | $4          |
 | `kilo/qwen/qwen3-vl-30b-a3b-instruct`                           | 262K    |       |           |       |       |       | $0.13      | $0.52       |
@@ -384,14 +383,14 @@ for await (const chunk of stream) {
 | `kilo/z-ai/glm-4.5`                                             | 131K    |       |           |       |       |       | $0.60      | $2          |
 | `kilo/z-ai/glm-4.5-air`                                         | 131K    |       |           |       |       |       | $0.13      | $0.85       |
 | `kilo/z-ai/glm-4.5v`                                            | 66K     |       |           |       |       |       | $0.60      | $2          |
-| `kilo/z-ai/glm-4.6`                                             | 205K    |       |           |       |       |       | $0.55      | $2          |
+| `kilo/z-ai/glm-4.6`                                             | 203K    |       |           |       |       |       | $0.55      | $2          |
 | `kilo/z-ai/glm-4.6v`                                            | 131K    |       |           |       |       |       | $0.30      | $0.90       |
 | `kilo/z-ai/glm-4.7`                                             | 203K    |       |           |       |       |       | $0.60      | $2          |
 | `kilo/z-ai/glm-4.7-flash`                                       | 203K    |       |           |       |       |       | $0.07      | $0.40       |
 | `kilo/z-ai/glm-5`                                               | 205K    |       |           |       |       |       | $1         | $3          |
 | `kilo/z-ai/glm-5-turbo`                                         | 203K    |       |           |       |       |       | $1         | $4          |
 | `kilo/z-ai/glm-5.1`                                             | 203K    |       |           |       |       |       | $1         | $4          |
-| `kilo/z-ai/glm-5.2`                                             | 1.0M    |       |           |       |       |       | $1         | $4          |
+| `kilo/z-ai/glm-5.2`                                             | 262K    |       |           |       |       |       | $1         | $4          |
 | `kilo/z-ai/glm-5v-turbo`                                        | 203K    |       |           |       |       |       | $1         | $4          |
 
 ## Advanced configuration

package/.docs/models/providers/nano-gpt.md

@@ -2,7 +2,7 @@
 
 # ![NanoGPT logo](https://models.dev/logos/nano-gpt.svg)NanoGPT
 
-Access 598 NanoGPT models through Mastra's model router. Authentication is handled automatically using the `NANO_GPT_API_KEY` environment variable.
+Access 599 NanoGPT models through Mastra's model router. Authentication is handled automatically using the `NANO_GPT_API_KEY` environment variable.
 
 Learn more in the [NanoGPT documentation](https://docs.nano-gpt.com).
 
@@ -547,6 +547,7 @@ for await (const chunk of stream) {
 | `nano-gpt/TEE/kimi-k3`                                           | 1.0M    |       |           |       |       |       | $3         | $15         |
 | `nano-gpt/TEE/llama3-3-70b`                                      | 128K    |       |           |       |       |       | $2         | $3          |
 | `nano-gpt/TEE/minimax-m2.5`                                      | 197K    |       |           |       |       |       | $0.20      | $1          |
+| `nano-gpt/TEE/muse-glimmer-30b`                                  | 131K    |       |           |       |       |       | $0.35      | $2          |
 | `nano-gpt/TEE/qwen2.5-vl-72b-instruct`                           | 66K     |       |           |       |       |       | $0.70      | $0.70       |
 | `nano-gpt/TEE/qwen3.5-122b-a10b`                                 | 262K    |       |           |       |       |       | $0.46      | $4          |
 | `nano-gpt/TEE/qwen3.5-27b`                                       | 262K    |       |           |       |       |       | $0.30      | $2          |