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

package/.docs/reference/evals/mastra-scorer.md

@@ -2,7 +2,7 @@
 
 The `MastraScorer` class is the base class for all scorers in Mastra. It provides a standard `.run()` method for evaluating input/output pairs and supports multi-step scoring workflows with preprocess → analyze → generateScore → generateReason execution flow.
 
-**Note:** Most users should use [`createScorer`](https://mastra.ai/reference/evals/create-scorer) to create scorer instances. Direct instantiation of `MastraScorer` is not recommended.
+**Note:** Most users should use [`createScorer`](https://mastra.ai/reference/evals/create-scorer) to create scorer instances. Direct instantiation of `MastraScorer` isn't recommended.
 
 ## How to Get a MastraScorer Instance
 

package/.docs/reference/evals/noise-sensitivity.md

@@ -2,7 +2,7 @@
 
 The `createNoiseSensitivityScorerLLM()` function creates a **CI/testing scorer** that evaluates how robust an agent is when exposed to irrelevant, distracting, or misleading information. Unlike live scorers that evaluate single production runs, this scorer requires predetermined test data including both baseline responses and noisy variations.
 
-**Important:** This is not a live scorer. It requires pre-computed baseline responses and cannot be used for real-time agent evaluation. Use this scorer in your CI/CD pipeline or testing suites only.
+**Important:** This isn't a live scorer. It requires pre-computed baseline responses and can't be used for real-time agent evaluation. Use this scorer in your CI/CD pipeline or testing suites only.
 
 Before using the noise sensitivity scorer, prepare your test data:
 
@@ -26,7 +26,7 @@ This scorer is designed exclusively for CI/testing environments and has specific
 1. **Requires Baseline Data**: You must provide a pre-computed baseline response (the "correct" answer without noise)
 2. **Needs Test Variations**: Requires both the original query and a noisy variation prepared in advance
 3. **Comparative Analysis**: The scorer compares responses between baseline and noisy versions, which is only possible in controlled test conditions
-4. **Not Suitable for Production**: Cannot evaluate single, real-time agent responses without predetermined test data
+4. **Not Suitable for Production**: Can't evaluate single, real-time agent responses without predetermined test data
 
 ### Test Data Preparation
 

package/.docs/reference/evals/textual-difference.md

@@ -4,7 +4,7 @@ The `createTextualDifferenceScorer()` function uses sequence matching to measure
 
 ## Parameters
 
-The `createTextualDifferenceScorer()` function does not take any options.
+The `createTextualDifferenceScorer()` function doesn't take any options.
 
 This function returns an instance of the MastraScorer class. See the [MastraScorer reference](https://mastra.ai/reference/evals/mastra-scorer) for details on the `.run()` method and its input/output.
 

package/.docs/reference/evals/tone-consistency.md

@@ -4,7 +4,7 @@ The `createToneScorer()` function evaluates the text's emotional tone and sentim
 
 ## Parameters
 
-The `createToneScorer()` function does not take any options.
+The `createToneScorer()` function doesn't take any options.
 
 This function returns an instance of the MastraScorer class. See the [MastraScorer reference](https://mastra.ai/reference/evals/mastra-scorer) for details on the `.run()` method and its input/output.
 

package/.docs/reference/evals/tool-call-accuracy.md

@@ -43,7 +43,7 @@ The code-based scorer operates in two distinct modes:
 
 #### Single Tool Mode
 
-When `expectedToolOrder` is not provided, the scorer evaluates single tool selection:
+When `expectedToolOrder` isn't provided, the scorer evaluates single tool selection:
 
 - **Standard Mode (strictMode: false)**: Returns `1` if the expected tool is called, regardless of other tools
 - **Strict Mode (strictMode: true)**: Returns `1` only if exactly one tool is called and it matches the expected tool

package/.docs/reference/harness/harness-class.md

@@ -82,6 +82,8 @@ await harness.sendMessage({ content: 'Hello!' })
 
 **subagents.allowedHarnessTools** (`string[]`): Tool IDs from the harness's shared \`tools\` config. Merged with \`tools\` above to let subagents use a subset of harness tools.
 
+**subagents.allowedWorkspaceTools** (`string[]`): Workspace tool names the subagent is allowed to use. Uses the exposed names (after any renames via workspace tool config). When set, workspace tools not in this list are hidden from the model. Non-workspace tools are never affected. When omitted, all workspace tools are visible.
+
 **subagents.defaultModelId** (`string`): Default model ID for this subagent type.
 
 **subagents.maxSteps** (`number`): Optional maximum number of steps for the spawned subagent. Defaults to \`50\` when omitted.
@@ -94,7 +96,7 @@ await harness.sendMessage({ content: 'Hello!' })
 
 **heartbeatHandlers** (`HeartbeatHandler[]`): Periodic background tasks started during \`init()\`. Use for gateway sync, cache refresh, and similar tasks.
 
-**idGenerator** (`() => string`): Custom ID generator for threads, messages, and other entities. (Default: `timestamp + random string`)
+**idGenerator** (`() => string`): Custom ID generator for Harness-managed IDs such as threads and mode-run identifiers. (Default: `timestamp + random string`)
 
 **modelAuthChecker** (`ModelAuthChecker`): Custom auth checker for model providers. Return \`true\`/\`false\` to override the default environment variable check, or \`undefined\` to fall back to defaults.
 
@@ -567,7 +569,7 @@ if (harness.isWorkspaceReady()) {
 
 #### `destroyWorkspace()`
 
-Destroy the workspace and release resources. Only applies to static workspaces — dynamic workspaces are not destroyed.
+Destroy the workspace and release resources. Only applies to static workspaces — dynamic workspaces aren't destroyed.
 
 ```typescript
 await harness.destroyWorkspace()

package/.docs/reference/index.md

@@ -266,12 +266,14 @@ The Reference section provides documentation of Mastra's API, including paramete
 - [.start()](https://mastra.ai/reference/workflows/run-methods/start)
 - [.startAsync()](https://mastra.ai/reference/workflows/run-methods/startAsync)
 - [.timeTravel()](https://mastra.ai/reference/workflows/run-methods/timeTravel)
+- [BlaxelSandbox](https://mastra.ai/reference/workspace/blaxel-sandbox)
 - [DaytonaSandbox](https://mastra.ai/reference/workspace/daytona-sandbox)
 - [E2BSandbox](https://mastra.ai/reference/workspace/e2b-sandbox)
 - [GCSFilesystem](https://mastra.ai/reference/workspace/gcs-filesystem)
 - [LocalFilesystem](https://mastra.ai/reference/workspace/local-filesystem)
 - [LocalSandbox](https://mastra.ai/reference/workspace/local-sandbox)
 - [S3Filesystem](https://mastra.ai/reference/workspace/s3-filesystem)
+- [SandboxProcessManager](https://mastra.ai/reference/workspace/process-manager)
 - [Workspace Class](https://mastra.ai/reference/workspace/workspace-class)
 - [WorkspaceFilesystem](https://mastra.ai/reference/workspace/filesystem)
 - [WorkspaceSandbox](https://mastra.ai/reference/workspace/sandbox)

package/.docs/reference/memory/cloneThread.md

@@ -135,4 +135,4 @@ When [Observational Memory](https://mastra.ai/docs/memory/observational-memory)
 - **Resource-scoped OM (same `resourceId`)**: The OM record is shared between the source and cloned threads since they belong to the same resource. No duplication occurs.
 - **Resource-scoped OM (different `resourceId`)**: The OM record is cloned to the new resource. Message IDs are remapped and any thread-identifying tags within observations are updated to reference the cloned thread.
 
-Only the current (most recent) OM generation is cloned — older history generations are not copied. Transient processing state (observation/reflection in-progress flags) is reset on the cloned record.
+Only the current (most recent) OM generation is cloned — older history generations aren't copied. Transient processing state (observation/reflection in-progress flags) is reset on the cloned record.

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

@@ -26,6 +26,8 @@ export const agent = new Agent({
 
 The `observationalMemory` option accepts `true`, a configuration object, or `false`. Setting `true` enables OM with `google/gemini-2.5-flash` as the default model. When passing a config object, a `model` must be explicitly set — either at the top level, or on `observation.model` and/or `reflection.model`.
 
+Observer input is multimodal-aware. OM keeps text placeholders like `[Image #1: screenshot.png]` in the transcript it builds for the Observer, and also sends the underlying image parts when possible. This applies to both single-thread observation and batched multi-thread observation. Non-image files appear as placeholders only.
+
 **enabled** (`boolean`): Enable or disable Observational Memory. When omitted from a config object, defaults to \`true\`. Only \`enabled: false\` explicitly disables it. (Default: `true`)
 
 **model** (`string | LanguageModel | DynamicModel | ModelWithRetries[]`): Model for both the Observer and Reflector agents. Sets the model for both at once. Cannot be used together with \`observation.model\` or \`reflection.model\` — an error will be thrown if both are set. When using \`observationalMemory: true\`, defaults to \`google/gemini-2.5-flash\`. When passing a config object, this or \`observation.model\`/\`reflection.model\` must be set. Use \`"default"\` to explicitly use the default model (\`google/gemini-2.5-flash\`). (Default: `'google/gemini-2.5-flash' (when using observationalMemory: true)`)
@@ -40,7 +42,7 @@ The `observationalMemory` option accepts `true`, a configuration object, or `fal
 
 **observation.instruction** (`string`): Custom instruction appended to the Observer's system prompt. Use this to customize what the Observer focuses on, such as domain-specific preferences or priorities.
 
-**observation.messageTokens** (`number`): Token count of unobserved messages that triggers observation. When unobserved message tokens exceed this threshold, the Observer agent is called.
+**observation.messageTokens** (`number`): Token count of unobserved messages that triggers observation. When unobserved message tokens exceed this threshold, the Observer agent is called. Image parts are included with model-aware estimates when possible, with deterministic fallbacks when image metadata is incomplete. Image-like \`file\` parts are counted the same way when uploads are normalized as files.
 
 **observation.maxTokensPerBatch** (`number`): Maximum tokens per batch when observing multiple threads in resource scope. Threads are chunked into batches of this size and processed in parallel. Lower values mean more parallelism but more API calls.
 
@@ -80,9 +82,9 @@ OM persists token payload estimates so repeated counting can reuse prior tiktoke
 
 - Part-level cache: `part.providerMetadata.mastra`.
 - String-content fallback cache: message-level metadata when no parts exist.
-- Cache entries are ignored and recomputed if cache version/tokenizer source does not match.
-- Per-message and per-conversation overhead are always recomputed at runtime and are not cached.
-- `data-*` and `reasoning` parts are skipped and do not receive cache entries.
+- Cache entries are ignored and recomputed if cache version/tokenizer source doesn't match.
+- Per-message and per-conversation overhead are always recomputed at runtime and aren't cached.
+- `data-*` and `reasoning` parts are skipped and don't receive cache entries.
 
 ## Examples
 
@@ -283,7 +285,7 @@ observationalMemory: {
 
 Setting `bufferTokens: false` disables both observation and reflection async buffering. Observations and reflections will run synchronously when their thresholds are reached.
 
-> **Note:** Async buffering is not supported with `scope: 'resource'` and is automatically disabled in resource scope.
+> **Note:** Async buffering isn't supported with `scope: 'resource'` and is automatically disabled in resource scope.
 
 ## Streaming data parts
 

package/.docs/reference/observability/tracing/bridges/otel.md

@@ -38,7 +38,7 @@ Executes a synchronous function within the OTEL context of a Mastra span.
 async shutdown(): Promise<void>
 ```
 
-Shuts down the bridge and cleans up resources. Ends any spans that were not properly closed.
+Shuts down the bridge and cleans up resources. Ends any spans that weren't properly closed.
 
 ## Usage Examples
 

package/.docs/reference/observability/tracing/processors/sensitive-data-filter.md

@@ -105,7 +105,7 @@ When no custom fields are provided:
 - **Exact matching**: After normalization, fields must match exactly
 
   - `token` matches `token`, `Token`, `TOKEN`
-  - `token` does NOT match `promptTokens` or `tokenCount`
+  - `token` doesn't match `promptTokens` or `tokenCount`
 
 ### Redaction Styles
 

package/.docs/reference/observability/tracing/spans.md

@@ -45,6 +45,8 @@ interface BaseSpan<TType extends SpanType> {
     details?: Record<string, any>
   }
 
+  /** Snapshot of the RequestContext */
+  requestContext?: Record<string, any>
   /** Is an event span? (occurs at startTime, has no endTime) */
   isEvent: boolean
 }

package/.docs/reference/processors/message-history-processor.md

@@ -66,7 +66,7 @@ export const agent = new Agent({
 
 1. Retrieves `threadId` from the request context
 2. Fetches historical messages from storage (ordered by creation date, descending)
-3. Filters out system messages (they should not be stored in the database)
+3. Filters out system messages (they shouldn't be stored in the database)
 4. Merges historical messages with incoming messages, avoiding duplicates by ID
 5. Adds historical messages with `source: 'memory'` tag
 

package/.docs/reference/processors/processor-interface.md

@@ -88,7 +88,7 @@ interface Processor<TId extends string = string> {
 
 ### processInput
 
-Processes input messages before they are sent to the LLM. Runs once at the start of agent execution.
+Processes input messages before they're sent to the LLM. Runs once at the start of agent execution.
 
 ```typescript
 processInput?(args: ProcessInputArgs): Promise<ProcessInputResult> | ProcessInputResult;
@@ -124,7 +124,7 @@ The method can return one of three types:
 
 ### processInputStep
 
-Processes input messages at each step of the agentic loop, before they are sent to the LLM. Unlike `processInput` which runs once at the start, this runs at every step including tool call continuations.
+Processes input messages at each step of the agentic loop, before they're sent to the LLM. Unlike `processInput` which runs once at the start, this runs at every step including tool call continuations.
 
 ```typescript
 processInputStep?(args: ProcessInputStepArgs): ProcessorMessageResult;
@@ -269,6 +269,10 @@ processOutputResult?(args: ProcessOutputResultArgs): ProcessorMessageResult;
 
 **messageList** (`MessageList`): MessageList instance for managing messages.
 
+**state** (`Record<string, unknown>`): Per-processor state that persists across all method calls within this request. Shared with processOutputStream and other methods.
+
+**result** (`OutputResult`): Resolved generation result containing \`text\` (accumulated text), \`usage\` (token usage with inputTokens, outputTokens, totalTokens), \`finishReason\` (why generation ended), and \`steps\` (all LLM step results, each with toolCalls, toolResults, reasoning, sources, files, etc.).
+
 **abort** (`(reason?: string) => never`): Function to abort processing.
 
 **tracingContext** (`TracingContext`): Tracing context for observability.

package/.docs/reference/processors/token-limiter-processor.md

@@ -47,8 +47,8 @@ const processor = new TokenLimiterProcessor({
 
 When used as an input processor, `TokenLimiterProcessor` throws a `TripWire` error in the following cases:
 
-- **Empty messages**: If there are no messages to process, a TripWire is thrown because you cannot send an LLM request with no messages.
-- **System messages exceed limit**: If system messages alone exceed the token limit, a TripWire is thrown because you cannot send an LLM request with only system messages and no user/assistant messages.
+- **Empty messages**: If there are no messages to process, a TripWire is thrown because you can't send an LLM request with no messages.
+- **System messages exceed limit**: If system messages alone exceed the token limit, a TripWire is thrown because you can't send an LLM request with only system messages and no user/assistant messages.
 
 ```typescript
 import { TripWire } from '@mastra/core/agent'

package/.docs/reference/rag/metadata-filters.md

@@ -48,7 +48,7 @@ const results = await store.query({
 
 ## Common Rules and Restrictions
 
-1. Field names cannot:
+1. Field names can't:
 
    - Contain dots (.) unless referring to nested fields
    - Start with $ or contain null characters
@@ -63,11 +63,11 @@ const results = await store.query({
 3. Logical operators:
 
    - Must contain valid conditions
-   - Cannot be empty
+   - Can't be empty
    - Must be properly nested
    - Can only be used at top level or nested within other logical operators
-   - Cannot be used at field level or nested inside a field
-   - Cannot be used inside an operator
+   - Can't be used at field level or nested inside a field
+   - Can't be used inside an operator
    - Valid: `{ "$and": [{ "field": { "$gt": 100 } }] }`
    - Valid: `{ "$or": [{ "$and": [{ "field": { "$gt": 100 } }] }] }`
    - Invalid: `{ "field": { "$and": [{ "$gt": 100 }] } }`
@@ -76,7 +76,7 @@ const results = await store.query({
 4. $not operator:
 
    - Must be an object
-   - Cannot be empty
+   - Can't be empty
    - Can be used at field level or top level
    - Valid: `{ "$not": { "field": "value" } }`
    - Valid: `{ "field": { "$not": { "$eq": "value" } } }`
@@ -98,7 +98,7 @@ const results = await store.query({
 ### ChromaDB
 
 - Where filters only return results where the filtered field exists in metadata
-- Empty metadata fields are not included in filter results
+- Empty metadata fields aren't included in filter results
 - Metadata fields must be present for negative matches (e.g., $ne won't match documents missing the field)
 
 ### Cloudflare Vectorize
@@ -109,7 +109,7 @@ const results = await store.query({
 - String values are indexed up to first 64 bytes (truncated on UTF-8 boundaries)
 - Number values use float64 precision
 - Filter JSON must be under 2048 bytes
-- Field names cannot contain dots (.) or start with $
+- Field names can't contain dots (.) or start with $
 - Field names limited to 512 characters
 - Vectors must be re-upserted after creating new metadata indexes to be included in filtered results
 - Range queries may have reduced accuracy with very large datasets (\~10M+ vectors)
@@ -186,12 +186,12 @@ const results = await store.query({
 
 ### Couchbase
 
-- Currently does not have support for metadata filters. Filtering must be done client-side after retrieving results or by using the Couchbase SDK's Search capabilities directly for more complex queries.
+- Currently doesn't have support for metadata filters. Filtering must be done client-side after retrieving results or by using the Couchbase SDK's Search capabilities directly for more complex queries.
 
 ### Amazon S3 Vectors
 
-- Equality values must be primitives (string/number/boolean). `null`/`undefined`, arrays, objects, and Date are not allowed for equality. Range operators accept numbers or Date (Dates are normalized to epoch ms).
-- `$in`/`$nin` require **non-empty arrays of primitives**; Date elements are allowed and normalized to epoch ms. **Array equality** is not supported.
+- Equality values must be primitives (string/number/boolean). `null`/`undefined`, arrays, objects, and Date aren't allowed for equality. Range operators accept numbers or Date (Dates are normalized to epoch ms).
+- `$in`/`$nin` require **non-empty arrays of primitives**; Date elements are allowed and normalized to epoch ms. **Array equality** isn't supported.
 - Implicit AND is canonicalized (`{a:1,b:2}` → `{$and:[{a:1},{b:2}]}`). Logical operators must contain field conditions, use non-empty arrays, and appear only at the root or within other logical operators (not inside field values).
 - Keys listed in `nonFilterableMetadataKeys` at index creation are stored but not filterable; this setting is immutable.
 - $exists requires a boolean value.

package/.docs/reference/server/create-route.md

@@ -46,6 +46,8 @@ function createRoute<TPath, TQuery, TBody, TResponse, TResponseType>(
 
 **deprecated** (`boolean`): Mark route as deprecated
 
+**onValidationError** (`(error: ZodError, context: 'query' | 'body' | 'path') => { status: number; body: unknown } | undefined`): Custom validation error handler for this route. Overrides the server-level \`onValidationError\` hook. Return \`{ status, body }\` to customize the response, or \`undefined\` to use the default.
+
 ## Handler parameters
 
 The handler receives validated parameters plus runtime context:

package/.docs/reference/server/koa-adapter.md

@@ -97,7 +97,7 @@ const server = new MastraServer({ app, mastra })
 await server.init()
 ```
 
-The [`server.onError`](https://mastra.ai/reference/configuration) hook is also supported. When configured, it is called before the error propagates to middleware, and its response is used directly:
+The [`server.onError`](https://mastra.ai/reference/configuration) hook is also supported. When configured, it's called before the error propagates to middleware, and its response is used directly:
 
 ```typescript
 const mastra = new Mastra({

package/.docs/reference/server/register-api-route.md

@@ -18,7 +18,7 @@ The URL path for the route. Supports path parameters using `:param` syntax.
 registerApiRoute("/items/:itemId", { ... })
 ```
 
-**Note:** Paths cannot start with `/api/` as this prefix is reserved for Mastra server routes.
+**Note:** Paths can't start with `/api/` as this prefix is reserved for Mastra server routes.
 
 ### options
 
@@ -34,7 +34,7 @@ registerApiRoute("/items/:itemId", { ... })
 
 ## OpenAPI Options
 
-The `openapi` property accepts standard OpenAPI 3.1 operation fields from [hono-openapi](https://github.com/honojs/middleware/tree/main/packages/openapi). Routes without an `openapi` property are not included in Swagger UI.
+The `openapi` property accepts standard OpenAPI 3.1 operation fields from [hono-openapi](https://github.com/honojs/middleware/tree/main/packages/openapi). Routes without an `openapi` property aren't included in Swagger UI.
 
 **summary** (`string`): Short summary of the operation
 

package/.docs/reference/storage/cloudflare-d1.md

@@ -2,7 +2,7 @@
 
 The Cloudflare D1 storage implementation provides a serverless SQL database solution using Cloudflare D1, supporting relational operations and transactional consistency.
 
-> **Observability Not Supported:** Cloudflare D1 storage **does not support the observability domain**. Traces from the `DefaultExporter` cannot be persisted to D1, and Mastra Studio's observability features won't work with D1 as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
+> **Observability Not Supported:** Cloudflare D1 storage **doesn't support the observability domain**. Traces from the `DefaultExporter` can't be persisted to D1, and Mastra Studio's observability features won't work with D1 as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
 
 > **Row Size Limit:** Cloudflare D1 enforces a **1 MiB maximum row size**. This limit can be exceeded when storing messages with base64-encoded attachments such as images. See [Handling large attachments](https://mastra.ai/docs/memory/storage) for workarounds including uploading attachments to external storage.
 
@@ -85,7 +85,7 @@ export default {
 > - The **property name** (`D1Database`) must match the `binding` name in your `wrangler.toml`
 > - The **type** (`: D1Database`) is from `@cloudflare/workers-types` for TypeScript type checking
 >
-> At runtime, Cloudflare Workers provides the actual D1 database instance via `env.D1Database`. You cannot use `D1Database` directly outside of the worker's context.
+> At runtime, Cloudflare Workers provides the actual D1 database instance via `env.D1Database`. You can't use `D1Database` directly outside of the worker's context.
 
 ### Using with REST API
 
@@ -207,7 +207,7 @@ export default {
 }
 ```
 
-> **Warning:** If `init()` is not called, tables won't be created and storage operations will fail silently or throw errors.
+> **Warning:** If `init()` isn't called, tables won't be created and storage operations will fail silently or throw errors.
 
 ### Transactions & Consistency
 

package/.docs/reference/storage/cloudflare.md

@@ -2,7 +2,7 @@
 
 The Cloudflare KV storage implementation provides a globally distributed, serverless key-value store solution using Cloudflare Workers KV.
 
-> **Observability Not Supported:** Cloudflare KV storage **does not support the observability domain**. Traces from the `DefaultExporter` cannot be persisted to KV, and Mastra Studio's observability features won't work with Cloudflare KV as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
+> **Observability Not Supported:** Cloudflare KV storage **doesn't support the observability domain**. Traces from the `DefaultExporter` can't be persisted to KV, and Mastra Studio's observability features won't work with Cloudflare KV as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
 
 ## Installation
 

package/.docs/reference/storage/convex.md

@@ -2,7 +2,7 @@
 
 The Convex storage implementation provides a serverless storage solution using [Convex](https://convex.dev), a full-stack TypeScript development platform with real-time sync and automatic caching.
 
-> **Observability Not Supported:** Convex storage **does not support the observability domain**. Traces from the `DefaultExporter` cannot be persisted to Convex, and Mastra Studio's observability features won't work with Convex as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
+> **Observability Not Supported:** Convex storage **doesn't support the observability domain**. Traces from the `DefaultExporter` can't be persisted to Convex, and Mastra Studio's observability features won't work with Convex as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
 
 > **Record Size Limit:** Convex enforces a **1 MiB maximum record size**. This limit can be exceeded when storing messages with base64-encoded attachments such as images. See [Handling large attachments](https://mastra.ai/docs/memory/storage) for workarounds including uploading attachments to external storage like S3, Cloudflare R2, or [Convex file storage](https://docs.convex.dev/file-storage).
 

package/.docs/reference/storage/dynamodb.md

@@ -2,7 +2,7 @@
 
 The DynamoDB storage implementation provides a scalable and performant NoSQL database solution for Mastra, leveraging a single-table design pattern with [ElectroDB](https://electrodb.dev/).
 
-> **Observability Not Supported:** DynamoDB storage **does not support the observability domain**. Traces from the `DefaultExporter` cannot be persisted to DynamoDB, and Mastra Studio's observability features won't work with DynamoDB as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
+> **Observability Not Supported:** DynamoDB storage **doesn't support the observability domain**. Traces from the `DefaultExporter` can't be persisted to DynamoDB, and Mastra Studio's observability features won't work with DynamoDB as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
 
 > **Item Size Limit:** DynamoDB enforces a **400 KB maximum item size**. This limit can be exceeded when storing messages with base64-encoded attachments such as images. See [Handling large attachments](https://mastra.ai/docs/memory/storage) for workarounds including uploading attachments to external storage.
 
@@ -211,7 +211,7 @@ aws dynamodb update-time-to-live \
 1. Go to the DynamoDB console
 2. Select your table
 3. Go to "Additional settings" tab
-4. Under "Time to Live (TTL)", click "Manage TTL"
+4. Under "Time to Live (TTL)", select "Manage TTL"
 5. Enable TTL and specify the attribute name (default: `ttl`)
 
 > **Note:** DynamoDB deletes expired items within 48 hours after expiration. Items remain queryable until actually deleted.

package/.docs/reference/storage/lance.md

@@ -2,7 +2,7 @@
 
 The LanceDB storage implementation provides a high-performance storage solution using the LanceDB database system, which excels at handling both traditional data storage and vector operations.
 
-> **Observability Not Supported:** LanceDB storage **does not support the observability domain**. Traces from the `DefaultExporter` cannot be persisted to LanceDB, and Mastra Studio's observability features won't work with LanceDB as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
+> **Observability Not Supported:** LanceDB storage **doesn't support the observability domain**. Traces from the `DefaultExporter` can't be persisted to LanceDB, and Mastra Studio's observability features won't work with LanceDB as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
 
 ## Installation
 
@@ -101,7 +101,7 @@ const memoryStore = await storage.getStore('memory')
 const thread = await memoryStore?.getThreadById({ threadId: '...' })
 ```
 
-> **Warning:** If `init()` is not called, tables won't be created and storage operations will fail silently or throw errors.
+> **Warning:** If `init()` isn't called, tables won't be created and storage operations will fail silently or throw errors.
 
 ### Deployment Options
 

package/.docs/reference/storage/mongodb.md

@@ -136,7 +136,7 @@ const memoryStore = await storage.getStore('memory')
 const thread = await memoryStore?.getThreadById({ threadId: '...' })
 ```
 
-> **Warning:** If `init()` is not called, collections won't be created and storage operations will fail silently or throw errors.
+> **Warning:** If `init()` isn't called, collections won't be created and storage operations will fail silently or throw errors.
 
 ## Vector Search Capabilities
 

package/.docs/reference/storage/mssql.md

@@ -138,7 +138,7 @@ const memoryStore = await storage.getStore('memory')
 const thread = await memoryStore?.getThreadById({ threadId: '...' })
 ```
 
-> **Warning:** If `init()` is not called, tables won't be created and storage operations will fail silently or throw errors.
+> **Warning:** If `init()` isn't called, tables won't be created and storage operations will fail silently or throw errors.
 
 ### Direct Database and Pool Access
 

package/.docs/reference/storage/postgresql.md

@@ -177,7 +177,7 @@ const memoryStore = await storage.getStore('memory')
 const thread = await memoryStore?.getThreadById({ threadId: '...' })
 ```
 
-> **Warning:** If `init()` is not called, tables won't be created and storage operations will fail silently or throw errors.
+> **Warning:** If `init()` isn't called, tables won't be created and storage operations will fail silently or throw errors.
 
 ### Using an Existing Pool
 
@@ -201,7 +201,7 @@ const storage = new PostgresStore({
 
 **Pool lifecycle behavior:**
 
-- When you **provide a pool**: Mastra uses your pool but does **not** close it when `store.close()` is called. You manage the pool lifecycle.
+- When you **provide a pool**: Mastra uses your pool but **doesn't** close it when `store.close()` is called. You manage the pool lifecycle.
 - When Mastra **creates a pool**: Mastra owns the pool and will close it when `store.close()` is called.
 
 ### Direct Database and Pool Access

package/.docs/reference/storage/upstash.md

@@ -4,7 +4,7 @@ The Upstash storage implementation provides a serverless-friendly storage soluti
 
 > **Pricing:** When using Mastra with Upstash, the pay-as-you-go model can result in unexpectedly high costs due to the high volume of Redis commands generated during agent conversations. We strongly recommend using a **fixed pricing plan** for predictable costs. See [Upstash pricing](https://upstash.com/pricing/redis) for details and [GitHub issue #5850](https://github.com/mastra-ai/mastra/issues/5850) for context.
 
-> **Observability Not Supported:** Upstash storage **does not support the observability domain**. Traces from the `DefaultExporter` cannot be persisted to Upstash, and Mastra Studio's observability features won't work with Upstash as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
+> **Observability Not Supported:** Upstash storage **doesn't support the observability domain**. Traces from the `DefaultExporter` can't be persisted to Upstash, and Mastra Studio's observability features won't work with Upstash as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
 
 ## Installation
 

package/.docs/reference/streaming/workflows/observeStream.md

@@ -1,6 +1,6 @@
 # Run.observeStream()
 
-The `.observeStream()` method opens a new `ReadableStream` to a workflow run that is currently running, allowing you to observe the stream of events if the original stream is no longer available.
+The `.observeStream()` method opens a new `ReadableStream` to a workflow run that's currently running, allowing you to observe the stream of events if the original stream is no longer available.
 
 ## Usage example
 

package/.docs/reference/templates/overview.md

@@ -130,7 +130,7 @@ Templates must be:
 - **Single projects** - Not monorepos with multiple applications
 - **Framework-free** - No Next.js, Express, or other web framework boilerplate
 - **Mastra-focused** - Demonstrate Mastra functionality without additional layers
-- **Mergeable** - Structure code for easy integration into existing projects
+- **Mergeable** - Structure code for seamless integration into existing projects
 - **Node.js compatible** - Support Node.js v22.13.0 and later
 - **ESM modules** - Use ES modules (`"type": "module"` in package.json)
 

package/.docs/reference/tools/create-tool.md

@@ -251,7 +251,7 @@ Additionally:
 
 ### Error Handling
 
-Hook errors are caught and logged automatically, but do not prevent tool execution from continuing. If a hook throws an error, it will be logged to the console but will not fail the tool call.
+Hook errors are caught and logged automatically, but don't prevent tool execution from continuing. If a hook throws an error, it will be logged to the console but won't fail the tool call.
 
 ## MCP Tool Annotations
 

package/.docs/reference/tools/mcp-server.md

@@ -96,9 +96,9 @@ A powerful feature of `MCPServer` is its ability to automatically expose your Ma
   - **Execution**: When this tool is called, it invokes the `generate()` method of the corresponding agent, passing the provided `query`.
   - **Output**: The direct result from the agent's `generate()` method is returned as the output of the tool.
 
-- **Name Collisions**: If an explicit tool defined in the `tools` configuration has the same name as an agent-derived tool (e.g., you have a tool named `ask_myAgentKey` and also an agent with the key `myAgentKey`), the _explicitly defined tool will take precedence_. The agent will not be converted into a tool in this conflicting case, and a warning will be logged.
+- **Name Collisions**: If an explicit tool defined in the `tools` configuration has the same name as an agent-derived tool (e.g., you have a tool named `ask_myAgentKey` and also an agent with the key `myAgentKey`), the _explicitly defined tool will take precedence_. The agent won't be converted into a tool in this conflicting case, and a warning will be logged.
 
-This makes it straightforward to allow MCP clients to interact with your agents using natural language queries, just like any other tool.
+This makes it straightforward to allow MCP clients to interact with your agents using natural language queries, like any other tool.
 
 ### Agent-to-Tool Conversion
 
@@ -391,7 +391,7 @@ serve(async req => {
 >
 > The serverless mode disables session management and creates fresh server instances per request, which is necessary for stateless environments where memory doesn't persist between invocations.
 >
-> **Note:** The following MCP features require session state or persistent connections and will **not work** in serverless mode:
+> **Note:** The following MCP features require session state or persistent connections and **won't work** in serverless mode:
 >
 > - **Elicitation** - Interactive user input requests during tool execution require session management to route responses back to the correct client
 > - **Resource subscriptions** - `resources/subscribe` and `resources/unsubscribe` need persistent connections to maintain subscription state
@@ -778,7 +778,7 @@ The example at the beginning of this page also demonstrates how to instantiate `
 
 ## Elicitation
 
-### What is Elicitation?
+### What's Elicitation?
 
 Elicitation is a feature in the Model Context Protocol (MCP) that allows servers to request structured information from users. This enables interactive workflows where servers can collect additional data dynamically.
 

package/.docs/reference/vectors/chroma.md

@@ -30,7 +30,7 @@ The ChromaVector class provides vector search using [Chroma](https://docs.trychr
 
 ## Running a Chroma Server
 
-If you are a Chroma Cloud user, simply provide the `ChromaVector` constructor your API key, tenant, and database name.
+If you are a Chroma Cloud user, provide the `ChromaVector` constructor your API key, tenant, and database name.
 
 When you install the `@mastra/chroma` package, you get access to the [Chroma CLI](https://docs.trychroma.com/docs/cli/db), which can set these as environment variables for you: `chroma db connect [DB-NAME] --env-file`.
 
@@ -54,7 +54,7 @@ Otherwise, you have several options for setting up your single-node Chroma serve
 
 Note: Forking is only supported on Chroma Cloud, or if you deploy your own OSS **distributed** Chroma.
 
-`forkIndex` lets you fork an existing Chroma index instantly. Operations on the forked index do not affect the original one. Learn more on the [Chroma docs](https://docs.trychroma.com/cloud/collection-forking).
+`forkIndex` lets you fork an existing Chroma index instantly. Operations on the forked index don't affect the original one. Learn more on the [Chroma docs](https://docs.trychroma.com/cloud/collection-forking).
 
 **indexName** (`string`): Name of the index to fork