@mastra/mcp-docs-server 1.2.13-alpha.6 → 1.2.13-alpha.9

package/.docs/models/providers/opencode-go.md

@@ -2,7 +2,7 @@
 
 # ![OpenCode Go logo](https://models.dev/logos/opencode-go.svg)OpenCode Go
 
-Access 22 OpenCode Go models through Mastra's model router. Authentication is handled automatically using the `OPENCODE_API_KEY` environment variable.
+Access 23 OpenCode Go models through Mastra's model router. Authentication is handled automatically using the `OPENCODE_API_KEY` environment variable.
 
 Learn more in the [OpenCode Go documentation](https://opencode.ai/docs/zen).
 
@@ -40,6 +40,7 @@ for await (const chunk of stream) {
 | `opencode-go/deepseek-v4-pro`   | 1.0M    |       |           |       |       |       | $0.43      | $0.87       |
 | `opencode-go/glm-5.1`           | 203K    |       |           |       |       |       | $1         | $4          |
 | `opencode-go/glm-5.2`           | 1.0M    |       |           |       |       |       | $1         | $4          |
+| `opencode-go/gpt-5.6-luna`      | 1.1M    |       |           |       |       |       | $0.10      | $0.60       |
 | `opencode-go/grok-4.5`          | 500K    |       |           |       |       |       | $2         | $6          |
 | `opencode-go/hy3`               | 256K    |       |           |       |       |       | $0.14      | $0.58       |
 | `opencode-go/kimi-k2.6`         | 262K    |       |           |       |       |       | $0.95      | $4          |

package/.docs/models/providers/opencode.md

@@ -77,7 +77,7 @@ for await (const chunk of stream) {
 | `opencode/gpt-5.4-pro`            | 1.1M    |       |           |       |       |       | $30        | $180        |
 | `opencode/gpt-5.5`                | 1.1M    |       |           |       |       |       | $5         | $30         |
 | `opencode/gpt-5.5-pro`            | 1.1M    |       |           |       |       |       | $30        | $180        |
-| `opencode/gpt-5.6-luna`           | 1.1M    |       |           |       |       |       | $1         | $6          |
+| `opencode/gpt-5.6-luna`           | 1.1M    |       |           |       |       |       | $0.20      | $1          |
 | `opencode/gpt-5.6-sol`            | 1.1M    |       |           |       |       |       | $5         | $30         |
 | `opencode/gpt-5.6-terra`          | 1.1M    |       |           |       |       |       | $3         | $15         |
 | `opencode/grok-4.5`               | 500K    |       |           |       |       |       | $2         | $6          |

package/.docs/models/providers/zai-coding-plan.md

@@ -2,7 +2,7 @@
 
 # ![Z.AI Coding Plan logo](https://models.dev/logos/zai-coding-plan.svg)Z.AI Coding Plan
 
-Access 6 Z.AI Coding Plan models through Mastra's model router. Authentication is handled automatically using the `ZHIPU_API_KEY` environment variable.
+Access 4 Z.AI Coding Plan models through Mastra's model router. Authentication is handled automatically using the `ZHIPU_API_KEY` environment variable.
 
 Learn more in the [Z.AI Coding Plan documentation](https://docs.z.ai/devpack/overview).
 
@@ -17,7 +17,7 @@ const agent = new Agent({
   id: "my-agent",
   name: "My Agent",
   instructions: "You are a helpful assistant",
-  model: "zai-coding-plan/glm-4.5-air"
+  model: "zai-coding-plan/glm-4.7"
 });
 
 // Generate a response
@@ -34,14 +34,12 @@ for await (const chunk of stream) {
 
 ## Models
 
-| Model                          | Context | Tools | Reasoning | Image | Audio | Video | Input $/1M | Output $/1M |
-| ------------------------------ | ------- | ----- | --------- | ----- | ----- | ----- | ---------- | ----------- |
-| `zai-coding-plan/glm-4.5-air`  | 131K    |       |           |       |       |       | —          | —           |
-| `zai-coding-plan/glm-4.7`      | 205K    |       |           |       |       |       | —          | —           |
-| `zai-coding-plan/glm-5-turbo`  | 200K    |       |           |       |       |       | —          | —           |
-| `zai-coding-plan/glm-5.1`      | 200K    |       |           |       |       |       | —          | —           |
-| `zai-coding-plan/glm-5.2`      | 1.0M    |       |           |       |       |       | —          | —           |
-| `zai-coding-plan/glm-5v-turbo` | 200K    |       |           |       |       |       | —          | —           |
+| Model                                   | Context | Tools | Reasoning | Image | Audio | Video | Input $/1M | Output $/1M |
+| --------------------------------------- | ------- | ----- | --------- | ----- | ----- | ----- | ---------- | ----------- |
+| `zai-coding-plan/glm-4.7`               | 205K    |       |           |       |       |       | —          | —           |
+| `zai-coding-plan/glm-5-turbo`           | 200K    |       |           |       |       |       | —          | —           |
+| `zai-coding-plan/glm-5.2`               | 1.0M    |       |           |       |       |       | —          | —           |
+| `zai-coding-plan/glm-5.2-highspeed[1m]` | 1.0M    |       |           |       |       |       | —          | —           |
 
 ## Advanced configuration
 
@@ -53,7 +51,7 @@ const agent = new Agent({
   name: "custom-agent",
   model: {
     url: "https://api.z.ai/api/coding/paas/v4",
-    id: "zai-coding-plan/glm-4.5-air",
+    id: "zai-coding-plan/glm-4.7",
     apiKey: process.env.ZHIPU_API_KEY,
     headers: {
       "X-Custom-Header": "value"
@@ -71,8 +69,8 @@ const agent = new Agent({
   model: ({ requestContext }) => {
     const useAdvanced = requestContext.task === "complex";
     return useAdvanced
-      ? "zai-coding-plan/glm-5v-turbo"
-      : "zai-coding-plan/glm-4.5-air";
+      ? "zai-coding-plan/glm-5.2-highspeed[1m]"
+      : "zai-coding-plan/glm-4.7";
   }
 });
 ```

package/.docs/models/providers/zhipuai-coding-plan.md

@@ -17,7 +17,7 @@ const agent = new Agent({
   id: "my-agent",
   name: "My Agent",
   instructions: "You are a helpful assistant",
-  model: "zhipuai-coding-plan/glm-4.5-air"
+  model: "zhipuai-coding-plan/glm-4.6v"
 });
 
 // Generate a response
@@ -34,15 +34,15 @@ for await (const chunk of stream) {
 
 ## Models
 
-| Model                              | Context | Tools | Reasoning | Image | Audio | Video | Input $/1M | Output $/1M |
-| ---------------------------------- | ------- | ----- | --------- | ----- | ----- | ----- | ---------- | ----------- |
-| `zhipuai-coding-plan/glm-4.5-air`  | 131K    |       |           |       |       |       | —          | —           |
-| `zhipuai-coding-plan/glm-4.6v`     | 128K    |       |           |       |       |       | $0.30      | $0.90       |
-| `zhipuai-coding-plan/glm-4.7`      | 205K    |       |           |       |       |       | —          | —           |
-| `zhipuai-coding-plan/glm-5-turbo`  | 200K    |       |           |       |       |       | —          | —           |
-| `zhipuai-coding-plan/glm-5.1`      | 200K    |       |           |       |       |       | —          | —           |
-| `zhipuai-coding-plan/glm-5.2`      | 1.0M    |       |           |       |       |       | —          | —           |
-| `zhipuai-coding-plan/glm-5v-turbo` | 200K    |       |           |       |       |       | —          | —           |
+| Model                                       | Context | Tools | Reasoning | Image | Audio | Video | Input $/1M | Output $/1M |
+| ------------------------------------------- | ------- | ----- | --------- | ----- | ----- | ----- | ---------- | ----------- |
+| `zhipuai-coding-plan/glm-4.6v`              | 128K    |       |           |       |       |       | $0.30      | $0.90       |
+| `zhipuai-coding-plan/glm-4.7`               | 205K    |       |           |       |       |       | —          | —           |
+| `zhipuai-coding-plan/glm-5-turbo`           | 200K    |       |           |       |       |       | —          | —           |
+| `zhipuai-coding-plan/glm-5.1`               | 200K    |       |           |       |       |       | —          | —           |
+| `zhipuai-coding-plan/glm-5.2`               | 1.0M    |       |           |       |       |       | —          | —           |
+| `zhipuai-coding-plan/glm-5.2-highspeed[1m]` | 1.0M    |       |           |       |       |       | —          | —           |
+| `zhipuai-coding-plan/glm-5v-turbo`          | 200K    |       |           |       |       |       | —          | —           |
 
 ## Advanced configuration
 
@@ -54,7 +54,7 @@ const agent = new Agent({
   name: "custom-agent",
   model: {
     url: "https://open.bigmodel.cn/api/coding/paas/v4",
-    id: "zhipuai-coding-plan/glm-4.5-air",
+    id: "zhipuai-coding-plan/glm-4.6v",
     apiKey: process.env.ZHIPU_API_KEY,
     headers: {
       "X-Custom-Header": "value"
@@ -73,7 +73,7 @@ const agent = new Agent({
     const useAdvanced = requestContext.task === "complex";
     return useAdvanced
       ? "zhipuai-coding-plan/glm-5v-turbo"
-      : "zhipuai-coding-plan/glm-4.5-air";
+      : "zhipuai-coding-plan/glm-4.6v";
   }
 });
 ```

package/.docs/reference/agents/durable-agent.md

@@ -174,7 +174,7 @@ const { output, cleanup } = await durableAgent.observe(runId, {
 await output.text
 ```
 
-By default `observe()` waits indefinitely for events. If the process running the run stops unexpectedly, the run stops producing events but never emits a completion event, so the observed stream would wait forever. Pass `idleTimeoutMs` to bound that wait: after that many milliseconds of silence the stream ends. An optional `isAlive` check is consulted first — return `true` while the run is still being worked on (for example a long-running tool call, or a run paused waiting for human input) to keep waiting; returning `false`, or omitting `isAlive`, ends the stream with an error. A transient throw from `isAlive` is treated as "still alive", so a momentary check failure never ends a live stream.
+By default `observe()` waits indefinitely for events. If the process running the run stops unexpectedly, the run stops producing events but never emits a completion event, so the observed stream would wait forever. Pass `idleTimeoutMs` to bound that wait: after that many milliseconds of silence the stream ends. An optional `isAlive` check is consulted first. Return `true` while the run is still being worked on (for example a long-running tool call, or a run paused waiting for human input) to keep waiting. Returning `false`, or omitting `isAlive`, ends the stream with an error. A transient throw from `isAlive` is treated as "still alive", so a momentary check failure never ends a live stream.
 
 ```typescript
 const { output } = await durableAgent.observe(runId, {
@@ -183,7 +183,7 @@ const { output } = await durableAgent.observe(runId, {
 })
 ```
 
-Ending a run on idle timeout runs the same cleanup as a run that errors (see the warning below), so its cached state is released rather than retained. Both options are opt-in; omit them for the previous wait-indefinitely behavior.
+Ending a run on idle timeout runs the same cleanup as a run that errors (see the warning below), so its cached state is released rather than retained. Both options are opt-in. Omit them for the previous wait-indefinitely behavior.
 
 Returns: `Promise<DurableAgentStreamResult>`
 
@@ -344,7 +344,7 @@ Returns: [`Promise<DurableAgentStreamResult>`](#durableagentstreamresult)
 
 ## DurableAgentStreamResult
 
-The object returned by `stream()`, `resume()`, and `observe()`.
+The object returned by `stream()`, `resume()`, `observe()`, and `recover()`.
 
 ```typescript
 interface DurableAgentStreamResult<OUTPUT = undefined> {

package/.docs/reference/cli/mastra.md

@@ -171,7 +171,7 @@ Comma-separated list of custom arguments to pass to the Node.js process, e.g. `-
 
 ## `mastra worker build`
 
-Bundles your Mastra application for worker deployment. Produces the same output as `mastra build` — a self-contained `.mastra/output/` directory.
+Bundles your Mastra application for worker deployment. Produces the same output as `mastra build`: a self-contained `.mastra/output/` directory.
 
 ```bash
 mastra worker build [options]
@@ -179,29 +179,45 @@ mastra worker build [options]
 
 ### Flags
 
-| Flag                  | Description                                                  |
-| --------------------- | ------------------------------------------------------------ |
-| `--dir <path>`        | Path to your Mastra source directory (default: `src/mastra`) |
-| `--root <path>`       | Project root directory (default: current directory)          |
-| `--tools <paths>`     | Comma-separated tool paths to include                        |
-| `--output-dir <path>` | Custom output directory (default: `.mastra/output`)          |
-| `--debug`             | Enable debug logging                                         |
+#### `--dir`
+
+Path to your Mastra source directory. Defaults to `src/mastra`.
+
+#### `--root`
+
+Project root directory. Defaults to the current directory.
+
+#### `--tools`
+
+Comma-separated tool paths to include in the bundle.
+
+#### `--output-dir`
+
+Custom output directory. Defaults to `.mastra/output`.
+
+#### `--debug`
+
+Enable debug logging during the build.
 
 ## `mastra worker start`
 
 > **Info:** You need to run `mastra worker build` or `mastra build` before using `mastra worker start`.
 
-Starts a worker process from a previously built bundle.
+Starts a worker process from a previously built bundle. The optional `name` argument sets `MASTRA_WORKERS` in the spawned process, controlling which worker starts.
 
 ```bash
 mastra worker start [name] [options]
 ```
 
-| Argument/Flag  | Description                                                         |
-| -------------- | ------------------------------------------------------------------- |
-| `name`         | Worker name to start. Sets `MASTRA_WORKERS` in the spawned process. |
-| `--dir <path>` | Path to the build output (default: `.mastra/output`)                |
-| `--env <path>` | Path to environment file (default: `.env.production`, then `.env`)  |
+### Flags
+
+#### `--dir`
+
+Path to the build output directory. Defaults to `.mastra/output`.
+
+#### `--env`
+
+Path to the environment file. Defaults to `.env.production`, falling back to `.env`.
 
 ### Examples
 

package/.docs/reference/core/mastra-class.md

@@ -135,7 +135,7 @@ Visit the [Configuration reference](https://mastra.ai/reference/configuration) f
 
 Re-drives every orphaned `running` durable-agent run across all registered durable agents. Called automatically on boot when `recovery.durableAgents` is `'auto'`. You can also call it directly for manual recovery or from a scheduled task.
 
-Requires persistent storage — with an in-memory store there is nothing to recover after a process restart.
+Requires persistent storage. With an in-memory store, there's nothing to recover after a process restart.
 
 ```typescript
 const result = await mastra.recoverAllDurableAgents()

package/.docs/reference/evals/summarization.md

@@ -2,7 +2,7 @@
 
 # Summarization scorer
 
-The `createSummarizationScorer()` function creates a scorer that evaluates a summary on two axes: whether every claim it makes is supported by the source text, and whether it preserves the information the source states. The final score is the lower of the two, so a summary cannot pass by being faithful but empty, or thorough but wrong.
+The `createSummarizationScorer()` function creates a scorer that evaluates a summary on two axes: whether every claim it makes is supported by the source text, and whether it preserves the information the source states. The final score is the lower of the two, so a summary can't pass by being faithful but empty, or thorough but wrong.
 
 The summary is the agent's last message that carries text, and the source text defaults to the first user message of the run input. Pass `source` or `sourceExtractor` when the text being summarized lives somewhere else, such as a tool result.
 
@@ -96,13 +96,13 @@ These ranges assume the default `scale` of 1. When using a custom scale, multipl
 
 - **0.9-1.0**: Excellent summary, faithful to the source and covering its main points
 - **0.7-0.8**: Good summary with a small omission or an unsupported detail
-- **0.4-0.6**: Moderate summary, either missing significant information or drifting from the source
+- **0.4-0.6**: Moderate summary, either missing important information or drifting from the source
 - **0.1-0.3**: Poor summary, most of the source is lost or contradicted
-- **0.0**: The summary supports no claims, answers no questions, or produced nothing to judge
+- **0.0**: The summary produced nothing to judge, or it failed to support any claims. A summary that answers no questions also receives this score
 
 ### Reading the two axes
 
-Both axes leave their verdicts on the run result: the alignment verdicts on the preprocess step, and the coverage verdicts on the analyze step. Each verdict carries the claim or question it belongs to and the reason behind it. The two failure modes look different:
+Both axes leave their verdicts on the run result: the alignment verdicts on the preprocess step, and the coverage verdicts on the analyze step. Each verdict carries the claim or question it belongs to and the reason behind it. A low alignment score has a different meaning from a low coverage score:
 
 - A low alignment score with high coverage means the summary invents or distorts detail
 - A low coverage score with high alignment means the summary is accurate but leaves too much out
@@ -115,7 +115,7 @@ Length plays no part in the score. A summary that repeats the source word for wo
 
 ### Cost
 
-Each evaluation makes three model calls. `maxQuestions` bounds the coverage half of the work, which otherwise grows with source length. Raise it for long documents where ten questions cannot represent the content.
+Each evaluation makes three model calls. `maxQuestions` bounds the coverage half of the work, which otherwise grows with source length. Raise it for long documents where ten questions can't represent the content.
 
 ## Scorer configuration
 

package/.docs/reference/processors/regex-filter-processor.md

@@ -125,7 +125,7 @@ A replacement string can reference capture groups with `$1` or `$&`. Those refer
 
 ## Redaction reporting
 
-The `redact` strategy rewrites text in place, so nothing downstream can tell what changed. Assign `onViolation` to record it. The processor calls it once per redacted message, message part, or stream chunk, and offsets are relative to that piece of text. Async callbacks are awaited, and errors are caught so an unavailable audit sink cannot fail the request.
+The `redact` strategy rewrites text in place, so nothing downstream can tell what changed. Assign `onViolation` to record it. The processor calls it once per redacted message, message part, or stream chunk, and offsets are relative to that piece of text. Async callbacks are awaited, and errors are caught so an unavailable audit sink can't fail the request.
 
 ```typescript
 import { RegexFilterProcessor, type RegexRedactionDetail } from '@mastra/core/processors'

package/.docs/reference/tools/isolated-vm-transport.md

@@ -34,7 +34,7 @@ yarn add @mastra/isolated-vm
 bun add @mastra/isolated-vm
 ```
 
-`isolated-vm` is a native addon. It ships prebuilt binaries for common platforms, so installation usually needs no extra setup. A C++ toolchain is only needed on platforms without a matching prebuild, where it falls back to compiling from source.
+`isolated-vm` is a native addon. It provides prebuilt binaries for common platforms, so installation usually needs no extra setup. A C++ toolchain is only needed on platforms without a matching prebuild, where it falls back to compiling from source.
 
 On Node.js 20 and later, the host process must be started with the `--no-node-snapshot` flag, otherwise creating an isolate crashes the process. The constructor throws an error when the flag is missing. Pass the flag when starting your server, or set it through `NODE_OPTIONS`:
 

package/.docs/reference/vectors/mongodb.md

@@ -109,7 +109,7 @@ Waits for an index to become ready after creation. Useful when you need to ensur
 
 ### `upsert()`
 
-Adds or updates vectors and their metadata in the collection. On a bring-your-own index this requires `allowWrites: true` at `createIndex()` time — BYO collections are read-only by default.
+Adds or updates vectors and their metadata in the collection. On a bring-your-own index, this requires `allowWrites: true` at `createIndex()` time because BYO collections are read-only by default.
 
 **indexName** (`string`): Name of the collection to insert into
 
@@ -148,12 +148,12 @@ Provisions an Atlas Search (BM25/full-text) index on the collection backing an i
 **Managed vs. bring-your-own collections:**
 
 - For a **managed** index (created without `collectionName`), `createIndex()` already provisions a _dynamic_ full-text index named `${collectionName}_search_index` (covering all string fields). `createSearchIndex()` is therefore only needed when you want a **field-restricted** mapping or a **custom index name**.
-- For a **bring-your-own** index (created with `collectionName`), `createIndex()` does **not** auto-create any full-text index — enabling `textQuery()`/`hybridQuery()` on a caller-owned operational collection is **opt-in**. Call `createSearchIndex()` explicitly to provision the (billable) text index; until you do, `textQuery()`/`hybridQuery()` throw a clear error rather than querying a non-existent index.
+- For a **bring-your-own** index (created with `collectionName`), `createIndex()` doesn't auto-create any full-text index. Enabling `textQuery()`/`hybridQuery()` on a caller-owned operational collection is opt-in. Call `createSearchIndex()` explicitly to provision the (billable) text index. Until you do, `textQuery()`/`hybridQuery()` throw a clear error rather than querying a non-existent index.
 
 Naming:
 
-- When `fields` is provided **without** an explicit `searchIndexName`, the field-mapped index is created under a **distinct** default name (`${collectionName}_${indexName}_search_fields_index`, unique per logical index) so it does not collide with — and get silently ignored by — a managed collection's auto-created dynamic index. This distinct index is persisted as the text-search index, so `textQuery()`/`hybridQuery()` use the restricted mapping automatically.
-- When `searchIndexName` is provided, that exact name is used and persisted. `textQuery()`/`hybridQuery()` resolve the persisted name automatically; you can also override the name per call via their `searchIndexName` / `textSearchIndexName` parameters.
+- When `fields` is provided **without** an explicit `searchIndexName`, the field-mapped index is created under a **distinct** default name (`${collectionName}_${indexName}_search_fields_index`, unique per logical index) so it doesn't collide with a managed collection's auto-created dynamic index and get silently ignored. This distinct index is persisted as the text-search index, so `textQuery()`/`hybridQuery()` use the restricted mapping automatically.
+- When `searchIndexName` is provided, that exact name is used and persisted. `textQuery()`/`hybridQuery()` resolve the persisted name automatically. You can also override the name per call via their `searchIndexName` / `textSearchIndexName` parameters.
 
 **indexName** (`string`): Name of the Mastra index whose collection will have the search index
 
@@ -170,7 +170,7 @@ await store.createSearchIndex({
 })
 ```
 
-> **Note:** The field-mapped index name includes the logical `indexName`, so two logical indexes on the same collection get distinct text indexes. Recreating the _same_ logical index with different `fields` still requires dropping the existing index first (`IndexAlreadyExists`).
+The field-mapped index name includes the logical `indexName`, so two logical indexes on the same collection get distinct text indexes. Recreating the _same_ logical index with different `fields` still requires dropping the existing index first (`IndexAlreadyExists`).
 
 ### `waitForSearchIndexReady()`
 
@@ -193,7 +193,7 @@ await store.waitForSearchIndexReady({ indexName: 'precedents' })
 
 Runs a full-text (BM25) search against an Atlas Search index. By default it targets the text-search index recorded for this index (set by `createSearchIndex()`, or the dynamic `${collectionName}_search_index` auto-created by `createIndex()`). Pass `searchIndexName` to target a specific index for this call.
 
-**Note:** metadata filters here (like `hybridQuery()`) are applied via a `$match` stage. For the vector branch of `hybridQuery()`, filters on fields not declared via `filterFields` at index creation are transparently materialised as candidate `_id`s (the same fallback `query()` uses), so undeclared-field filters do not error.
+Metadata filters here (like `hybridQuery()`) are applied via a `$match` stage. For the vector branch of `hybridQuery()`, filters on fields not declared via `filterFields` at index creation are transparently materialised as candidate `_id`s (the same fallback `query()` uses), so undeclared-field filters don't error.
 
 **indexName** (`string`): Name of the Mastra index to search
 
@@ -220,7 +220,7 @@ const results = await store.textQuery({
 
 ### `hybridQuery()`
 
-Runs a hybrid search that fuses vector similarity and full-text results using MongoDB's server-side `$rankFusion` (requires MongoDB >= 8.0; generally available from 8.1, and on 8.0.x it may need a MongoDB support case to enable — it runs where enabled, e.g. Atlas 8.0.x). A full-text search index must exist: it is auto-created for managed indexes, but for a bring-your-own collection you must call `createSearchIndex()` first (opt-in).
+Runs a hybrid search that fuses vector similarity and full-text results using MongoDB's server-side `$rankFusion`. It requires MongoDB >= 8.0 and is generally available from 8.1. On 8.0.x, it may need a MongoDB support case to enable, and it runs where enabled, such as Atlas 8.0.x. A full-text search index must exist: it's auto-created for managed indexes, but for a bring-your-own collection you must call `createSearchIndex()` first (opt-in).
 
 **indexName** (`string`): Name of the Mastra index to search
 
@@ -253,7 +253,7 @@ const results = await store.hybridQuery({
 })
 ```
 
-**Note:** `hybridQuery()` requires MongoDB >= 8.0 for the `$rankFusion` stage (generally available from 8.1; on 8.0.x it may need a MongoDB support case to enable, and runs where enabled, such as Atlas 8.0.x). If you're running an older version, or `$rankFusion` is not enabled on your 8.0.x deployment, use `query()` and `textQuery()` separately and merge the results client-side.
+`hybridQuery()` requires MongoDB >= 8.0 for the `$rankFusion` stage. The stage is generally available from 8.1. On 8.0.x, it may need a MongoDB support case to enable and runs where enabled, such as Atlas 8.0.x. If you're running an older version, or `$rankFusion` isn't enabled on your 8.0.x deployment, use `query()` and `textQuery()` separately and merge the results client-side.
 
 ### `describeIndex()`
 
@@ -276,15 +276,15 @@ interface IndexStats {
 Deletes a vector index. Behavior depends on how the index was created:
 
 - **Managed index** (created without `collectionName`): drops the entire collection and all its data.
-- **Bring-your-own index** (created with `collectionName`): drops the Atlas vectorSearch index **and**, if one was provisioned via `createSearchIndex()`, the companion full-text search index. The caller's operational collection and its documents are **preserved** — this store never drops a collection it did not create.
+- **Bring-your-own index** (created with `collectionName`): drops the Atlas vectorSearch index and, if one was provisioned via `createSearchIndex()`, the companion full-text search index. The caller's operational collection and its documents are preserved. This store never drops a collection it didn't create.
 
-The BYO classification is recorded durably when the index is created, so it is applied correctly even by a different process (e.g. an index created by a setup job and later deleted by a long-lived service). Always pass the **logical index name** (the `indexName` used at `createIndex`), not the physical collection name.
+The BYO classification is recorded durably when the index is created, so it's applied correctly even by a different process (e.g. an index created by a setup job and later deleted by a long-lived service). Always pass the **logical index name** (the `indexName` used at `createIndex`), not the physical collection name.
 
 **indexName** (`string`): Logical name of the index to delete
 
 ### `listIndexes()`
 
-Lists the **logical** Mastra index names (the `indexName` values passed to `createIndex`), not physical collection names. For a bring-your-own index whose data lives in an operational collection, the logical index name is returned — never the physical collection name — so the value can be passed straight back into `deleteIndex()` / `describeIndex()`. Managed indexes created before durable metadata was introduced are still discovered via their `${name}_vector_index` search index. The internal registry collection is never listed.
+Lists the **logical** Mastra index names (the `indexName` values passed to `createIndex`), not physical collection names. For a bring-your-own index whose data lives in an operational collection, the logical index name is returned instead of the physical collection name. The value can be passed straight back into `deleteIndex()` / `describeIndex()`. Managed indexes created before durable metadata was introduced are still discovered via their `${name}_vector_index` search index. The internal registry collection is never listed.
 
 Returns: `Promise<string[]>`
 
@@ -408,12 +408,12 @@ await store.createSearchIndex({ indexName: 'precedents', fields: ['note'] })
 
 - The collection must already exist and contain documents with an `embedding` field (or the custom `embeddingFieldPath` you configured)
 - The collection is never created or dropped when using `collectionName`
-- **A BYO index is read-only by default.** `upsert()`, `updateVector()`, `deleteVector()`, and `deleteVectors()` throw a clear error rather than mutating caller-owned operational documents. To let the store write embeddings into (or delete documents from) your collection, opt in explicitly with `createIndex({ ..., allowWrites: true })`. The policy is persisted and survives restarts; entries written by older versions without the flag are treated as read-only (fail closed).
+- **A BYO index is read-only by default.** `upsert()`, `updateVector()`, `deleteVector()`, and `deleteVectors()` throw a clear error rather than mutating caller-owned operational documents. To let the store write embeddings into (or delete documents from) your collection, opt in explicitly with `createIndex({ ..., allowWrites: true })`. The policy is persisted and survives restarts. Entries written by older versions without the flag are treated as read-only (fail closed).
 - Use `metadataMode: 'document'` when querying to retrieve the full source document as `metadata`
 - In `'document'` mode the embedding is omitted from `metadata` by default; pass `includeVector: true` to retain it (and also expose it as a top-level `vector`)
 - **Filtering in `'document'` mode operates on root document fields**, not a nested `metadata.` subdocument. `filter: { lane: 'fraud' }` matches the top-level `lane` field of your operational documents (in the default `'field'` mode, bare fields are rewritten to `metadata.<field>` for managed collections). Both the pushdown and `$match` fallback paths honor this.
 - **Native `ObjectId` `_id`s are supported.** Operational collections commonly key on `ObjectId`; query results coerce `_id` to a string (the `QueryResult.id` contract), and `deleteVector()`/`updateVector()`/`deleteVectors()` accept that string and match the underlying `ObjectId` document. Managed collections (string `_id`s) are unaffected.
-- Full-text and hybrid search on a BYO collection are **opt-in**: no full-text index is auto-created, so call `createSearchIndex()` before `textQuery()`/`hybridQuery()`. The full-text index builds asynchronously — call `waitForSearchIndexReady()` (or pass `waitUntilReady: true`) before an immediate text/hybrid query.
+- Full-text and hybrid search on a BYO collection are **opt-in**: no full-text index is auto-created, so call `createSearchIndex()` before `textQuery()`/`hybridQuery()`. The full-text index builds asynchronously. Call `waitForSearchIndexReady()` (or pass `waitUntilReady: true`) before an immediate text/hybrid query.
 - `deleteIndex()` on a BYO index drops the vector index (and the text index if one was created) but **preserves** the collection and its documents
 
 ## Best practices

package/.docs/reference/workers/overview.md

@@ -10,14 +10,14 @@ For usage patterns and deployment topologies, see [Workers](https://mastra.ai/do
 
 Controls which workers start in the current process.
 
-| Value                       | Behavior                                                              |
-| --------------------------- | --------------------------------------------------------------------- |
-| _(not set)_                 | Default workers are auto-created based on configuration               |
-| `"false"`                   | Disables all event processing. The process only serves HTTP requests. |
-| `"orchestration"`           | Only the orchestration worker starts                                  |
-| `"scheduler"`               | Only the scheduler worker starts                                      |
-| `"backgroundTasks"`         | Only the background task worker starts                                |
-| `"orchestration,scheduler"` | Multiple workers (comma-separated)                                    |
+| Value                       | Behavior                                                                                                                                                  |
+| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| _(not set)_                 | Default workers are auto-created based on configuration                                                                                                   |
+| `"false"`                   | Disables worker event processing. The process serves HTTP requests and can still publish events to PubSub (e.g., workflow starts) without consuming them. |
+| `"orchestration"`           | Only the orchestration worker starts                                                                                                                      |
+| `"scheduler"`               | Only the scheduler worker starts                                                                                                                          |
+| `"backgroundTasks"`         | Only the background task worker starts                                                                                                                    |
+| `"orchestration,scheduler"` | Multiple workers (comma-separated)                                                                                                                        |
 
 Use this to run different worker types in separate containers from the same build artifact.
 
@@ -29,6 +29,8 @@ The base URL of the API server, used by the orchestration worker to execute work
 MASTRA_STEP_EXECUTION_URL=http://api:4111/api
 ```
 
+Use HTTPS URLs in production. See [Security recommendations](https://mastra.ai/docs/server/auth/workers).
+
 The orchestration worker sends step execution requests to:
 
 ```text

package/.docs/reference/workspace/platform-filesystem.md

@@ -4,7 +4,7 @@
 
 Stores files in a Mastra Platform workspace bucket. Each Mastra Platform environment can have one bucket, and `PlatformFilesystem` gives agents `read`, `write`, `list`, `delete`, and `move` operations against it.
 
-Use `PlatformFilesystem` when your agent runs on a Mastra Platform deployment and you want the filesystem to be backed by the platform-provisioned bucket. For direct S3 access, see [`S3Filesystem`](https://mastra.ai/reference/workspace/s3-filesystem). For a local directory during development, see [`LocalFilesystem`](https://mastra.ai/reference/workspace/local-filesystem).
+Related providers: [`S3Filesystem`](https://mastra.ai/reference/workspace/s3-filesystem) for direct S3 access, [`LocalFilesystem`](https://mastra.ai/reference/workspace/local-filesystem) for local directories.
 
 > **Info:** For interface details, see [WorkspaceFilesystem interface](https://mastra.ai/reference/workspace/filesystem).
 
@@ -157,7 +157,8 @@ Filesystem-specific errors match the standard workspace error types:
 Other Platform API failures raise `PlatformApiError`. Structured `{ error: { message, type } }` responses are parsed into `.code` (machine-readable kind) and `.proxyMessage` (human string):
 
 ```typescript
-import { FileNotFoundError, PlatformApiError } from '@mastra/platform-workspace'
+import { FileNotFoundError } from '@mastra/core/workspace'
+import { PlatformApiError } from '@mastra/platform-workspace'
 
 try {
   await fs.readFile('/missing.txt')
@@ -173,6 +174,8 @@ try {
 }
 ```
 
+`FileNotFoundError`, `FileExistsError`, and `WorkspaceReadOnlyError` are re-exports of the standard workspace error types from `@mastra/core/workspace`. `PlatformApiError` is specific to `@mastra/platform-workspace`.
+
 `code` and `proxyMessage` are `undefined` when the response body isn't JSON, for example an HTML 502 from a load balancer.
 
 ## Related

package/.docs/reference/workspace/platform-sandbox.md

@@ -2,9 +2,11 @@
 
 # PlatformSandbox
 
-Executes commands inside a Mastra Platform sandbox tied to a Platform environment. Sandboxes boot from a pre-built recipe checkpoint with Python 3, Node 22, TypeScript, tsx, and common build tooling already installed.
+Client for provisioning sandboxes in a Mastra Platform environment. Each `PlatformSandbox` instance owns one remote sandbox: `start()` provisions it, `executeCommand()` runs against it, and `destroy()` tears it down. Construct additional instances to own additional remote sandboxes; use `clone()` to derive them from a configured template (see [Cloning](#cloning-for-a-fleet-of-sandboxes)).
 
-Use `PlatformSandbox` when your agent runs on a Mastra Platform deployment and you want the sandbox to be provisioned and managed by the platform. For self-hosted Railway sandboxes, see [`RailwaySandbox`](https://mastra.ai/reference/workspace/railway-sandbox). For a local sandbox during development, see [`LocalSandbox`](https://mastra.ai/reference/workspace/local-sandbox).
+Sandboxes boot from a pre-built recipe checkpoint with Python 3, Node 22, TypeScript, tsx, and common build tooling already installed. Pass a stable `id` to opt into [checkpoint recovery](#checkpoint-recovery) so a new sandbox boots from the previous one's filesystem.
+
+Related providers: [`RailwaySandbox`](https://mastra.ai/reference/workspace/railway-sandbox) for self-hosted Railway sandboxes, [`LocalSandbox`](https://mastra.ai/reference/workspace/local-sandbox) for local sandboxes.
 
 > **Info:** For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
 
@@ -103,7 +105,7 @@ The default `ISOLATED` mode allows outbound internet access only, with no privat
 
 ### Reattaching to a running sandbox
 
-Pass an existing `sandboxId` to reattach to a live sandbox instead of creating a new one. This is useful for stateful agents that resume between requests:
+Pass an existing `sandboxId` to reattach to a live sandbox instead of creating a new one:
 
 ```typescript
 const sandbox = new PlatformSandbox({
@@ -116,6 +118,42 @@ const result = await sandbox.executeCommand('cat', ['/workspace/state.json'])
 
 When `sandboxId` is set, `environmentId` isn't required because the sandbox already exists.
 
+### Checkpoint recovery
+
+The constructor `id` (explicit or auto-generated) is sent to the platform on `POST /sandbox` as an advisory recovery key:
+
+- If the platform recognises the `id` from a previous session, the new sandbox boots from the most recent checkpoint of that earlier sandbox's filesystem instead of the base recipe.
+- If the `id` isn't recognised, the platform falls through to a fresh sandbox from the base recipe. Auto-generated ids never match, so omitting `id` disables checkpoint recovery.
+
+Pass a stable `id` to preserve a sandbox's filesystem across sessions or across a `destroy()`/`start()` cycle:
+
+```typescript
+const sandbox = new PlatformSandbox({
+  id: `project-${projectId}`,
+})
+await sandbox.start() // Boots from the most recent checkpoint for this id, or fresh if unknown
+```
+
+Checkpoint recovery is coarser than `sandboxId` reattachment. Reattaching (via `sandboxId`) rejoins the exact live sandbox and its running processes. Checkpoint recovery constructs a brand new sandbox and restores its filesystem from the latest checkpoint the platform captured for the previous sandbox with that `id`. Running processes and any filesystem writes made after the last checkpoint aren't restored.
+
+Each `id` maps to one independent filesystem. Reusing the same `id` across unrelated sandboxes causes the platform to boot them from each other's checkpoint.
+
+### Cloning for a fleet of sandboxes
+
+`clone()` returns an independent sibling `PlatformSandbox` that inherits credentials and defaults (access token, project, environment, network isolation, timeout, instructions, env, idle timeout) with per-instance overrides. The returned sandbox is unstarted and provisions on its own `start()`, so `clone()` performs no I/O:
+
+```typescript
+const template = new PlatformSandbox({
+  networkIsolation: 'PRIVATE',
+  idleTimeoutMinutes: 30,
+})
+
+const perProject = template.clone({ id: `project-${projectId}` })
+await perProject.start()
+```
+
+Combine `clone()` with a stable `id` per clone to opt each clone into [checkpoint recovery](#checkpoint-recovery) independently.
+
 ### Executing commands
 
 `executeCommand` runs a command on the remote sandbox and returns its output. Pass `args` to have arguments safely shell-quoted:
@@ -153,7 +191,7 @@ console.log(result.exitCode)
 
 **instructions** (`string | ((opts: { defaultInstructions: string; requestContext?: RequestContext }) => string)`): Custom instructions returned by getInstructions(). A string fully replaces the defaults; a function receives the defaults and can extend or customize them per-request.
 
-**id** (`string`): Unique identifier for this sandbox instance. (Default: `Auto-generated`)
+**id** (`string`): Unique identifier for this sandbox instance. Sent to the platform as an advisory recovery key: if the platform recognizes the id from a previous sandbox, the new sandbox boots from that sandbox's most recent checkpoint instead of the base recipe. Unknown ids fall through to a fresh sandbox. Auto-generated when omitted, which disables checkpoint recovery. (Default: `Auto-generated`)
 
 **fetch** (`typeof fetch`): Custom fetch implementation, mainly for testing.
 
@@ -169,6 +207,22 @@ console.log(result.exitCode)
 
 **processes** (`PlatformProcessManager`): Background process manager. See SandboxProcessManager reference.
 
+## Methods
+
+**start** (`() => Promise<void>`): Provision the remote sandbox, or reattach when sandboxId was passed to the constructor. Idempotent once the sandbox is running. A destroyed reattach target falls through to a fresh provision.
+
+**destroy** (`() => Promise<void>`): Tear down the remote sandbox and clear the cached exec lease. A subsequent start() provisions a fresh sandbox (or restores from checkpoint when a stable id is set).
+
+**stop** (`() => Promise<void>`): Alias for destroy().
+
+**executeCommand** (`(command: string, args?: string[], options?: ExecuteCommandOptions) => Promise<CommandResult>`): Run a command on the remote sandbox and return its stdout, stderr, exitCode, and executionTimeMs. command is a shell string, args are safely shell-quoted.
+
+**clone** (`(options?: SandboxCloneOptions) => PlatformSandbox`): Construct an unstarted sibling PlatformSandbox that inherits credentials and defaults with per-instance overrides (id, sandboxId, env, idleTimeoutMinutes). Performs no I/O. Use to build a fleet of independent sandboxes from one configured template.
+
+**getInfo** (`() => Promise<SandboxInfo>`): Return the sandbox's platform id, provider, status, createdAt, and metadata (sandboxId, providerResourceId, platformStatus).
+
+**getInstructions** (`(opts?: { requestContext?: RequestContext }) => string`): Return the sandbox instructions the workspace surfaces in tool descriptions. Honors the instructions constructor option; otherwise returns platform-default instructions that include the current remote sandbox id when running.
+
 ## Errors
 
 Platform API failures raise `PlatformApiError`. Structured `{ error: { message, type } }` responses are parsed into `.code` (machine-readable kind) and `.proxyMessage` (human string); the raw response body stays available on `.body`:

package/CHANGELOG.md

@@ -1,5 +1,20 @@
 # @mastra/mcp-docs-server
 
+## 1.2.13-alpha.9
+
+### Patch Changes
+
+- Updated dependencies [[`db4e6ff`](https://github.com/mastra-ai/mastra/commit/db4e6ff744503112eb64deeaf6c2b54bf26a54c7), [`6d19a65`](https://github.com/mastra-ai/mastra/commit/6d19a6517f5da3911023d446b7e2d5dad8adb1cb)]:
+  - @mastra/core@1.56.0-alpha.5
+
+## 1.2.13-alpha.7
+
+### Patch Changes
+
+- Updated dependencies [[`4844167`](https://github.com/mastra-ai/mastra/commit/4844167cff2d5ec5004e94edd34970833040fa3f), [`5faf93f`](https://github.com/mastra-ai/mastra/commit/5faf93f03e19daea394b9e2a923f2e4f833407f2), [`80ad891`](https://github.com/mastra-ai/mastra/commit/80ad891f8cd10379aa5b5af7510c763783b2ab56), [`c78aa4e`](https://github.com/mastra-ai/mastra/commit/c78aa4ecc422ba70476da73709c3e7d85edc71d6), [`a1cb98d`](https://github.com/mastra-ai/mastra/commit/a1cb98d11990b560b98482292a1f34aa1a2d9092), [`598ad82`](https://github.com/mastra-ai/mastra/commit/598ad82d41c41389a686338a1d0e50b7400e1938), [`1fd6aad`](https://github.com/mastra-ai/mastra/commit/1fd6aad1ea4a9d32f65efa832307c35e981a4c0a)]:
+  - @mastra/core@1.56.0-alpha.4
+  - @mastra/mcp@1.15.1-alpha.0
+
 ## 1.2.13-alpha.5
 
 ### Patch Changes