@mastra/mcp-docs-server 1.2.15-alpha.13 → 1.2.15-alpha.19

package/.docs/reference/client-js/agents.md

@@ -421,12 +421,13 @@ Returns `{ accepted: true, runId: string, toolCallId?: string }`.
 
 ### `declineToolCall()`
 
-Decline a pending tool call and return a continuation stream. Use this when you are rendering the resumed chunks from the decline response.
+Decline a pending tool call and return a continuation stream. Use this when you are rendering the resumed chunks from the decline response. Pass an optional `reason` to tell the model why the call was rejected. The default is `Tool call was not approved by the user`.
 
 ```typescript
 const response = await agent.declineToolCall({
   runId: 'run-123',
   toolCallId: 'tool-call-456',
+  reason: 'This file is outside the allowed directory', // optional
 })
 
 response.processDataStream({

package/.docs/reference/client-js/workflows.md

@@ -14,7 +14,7 @@ const workflows = await mastraClient.listWorkflows()
 
 ## Getting workflow run counts
 
-Retrieve per-workflow counts of `running` and [`suspended`](https://mastra.ai/docs/workflows/suspend-and-resume) runs in a single request. The counts are computed on the server and keyed by the workflow's registry key — the key used when registering the workflow in the Mastra config, which can differ from the workflow's own `id`:
+Retrieve per-workflow counts of `running` and [`suspended`](https://mastra.ai/docs/workflows/suspend-and-resume) runs in a single request. The counts are computed on the server and keyed by the workflow's registry key, the key used when registering the workflow in the Mastra config, which can differ from the workflow's own `id`:
 
 ```typescript
 const runCounts = await mastraClient.listWorkflowRunCounts()
@@ -23,7 +23,7 @@ const runCounts = await mastraClient.listWorkflowRunCounts()
 
 Returns: `Record<string, { running: number; suspended: number }>`
 
-The server may cache the counts for a few seconds between requests. Servers that predate this endpoint respond with `404 Not Found` — handle the error when the client can talk to older deployments.
+The server may cache the counts for a few seconds between requests. Servers that predate this endpoint respond with `404 Not Found`. Handle the error when the client can talk to older deployments.
 
 ## Working with a specific workflow
 
@@ -227,7 +227,7 @@ A workflow run result yields the following:
 
 ## Dynamic workflows
 
-> **Beta:** Dynamic workflows are in beta. Breaking changes may occur without a major version bump until the API is stable.
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
 
 Dynamic workflows are workflow definitions expressed as JSON. The server persists each definition and registers it as a runnable workflow. See [Dynamic workflows](https://mastra.ai/docs/workflows/dynamic-workflows) for the definition format.
 

package/.docs/reference/code-sdk/mount-agent-controller.md

@@ -2,7 +2,7 @@
 
 # mountAgentControllerOnMastra()
 
-> **Beta:** The `@mastra/code-sdk` package is experimental and subject to breaking changes in minor versions.
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
 
 The `mountAgentControllerOnMastra()` function builds the Mastra Code agent controller (the coding agent behind the [`mastracode`](https://www.npmjs.com/package/mastracode) CLI, with its modes, tools, memory, and thread management) and registers it on a server-owned [Mastra](https://mastra.ai/reference/core/mastra-class) instance. Use it to serve the Mastra Code agent to your own UI (web app, editor, bot): each client creates or resumes its own isolated session through the returned [`AgentController`](https://mastra.ai/reference/agent-controller/agent-controller-class).
 

package/.docs/reference/configuration.md

@@ -574,7 +574,7 @@ export const mastra = new Mastra({
 
 Minifies the bundled output, stripping comments and whitespace and shortening local identifiers. Exported names are preserved.
 
-Off by default so build output stays readable and stack traces stay meaningful. Enable it when bundle size matters, such as packaging a container image for an on-prem deployment. `mastra dev` is never minified.
+Off by default so build output stays readable and stack traces stay usable. Enable it when bundle size matters, such as packaging a container image for an on-prem deployment. `mastra dev` is never minified.
 
 ```typescript
 import { Mastra } from '@mastra/core'

package/.docs/reference/core/addDynamicWorkflow.md

@@ -2,7 +2,7 @@
 
 # Mastra.addDynamicWorkflow()
 
-> **Beta:** Dynamic workflows are in beta. Breaking changes may occur without a major version bump until the API is stable.
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
 
 The `.addDynamicWorkflow()` method validates a dynamic workflow definition and registers it as a live workflow on the instance, persisting it through the `workflowDefinitions` storage domain. Once registered, the workflow runs like any other workflow via [`getWorkflow()`](https://mastra.ai/reference/core/getWorkflow).
 

package/.docs/reference/core/addDynamicWorkflows.md

@@ -2,7 +2,7 @@
 
 # Mastra.addDynamicWorkflows()
 
-> **Beta:** Dynamic workflows are in beta. Breaking changes may occur without a major version bump until the API is stable.
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
 
 The `.addDynamicWorkflows()` method adds a bundle of dynamic workflow definitions that may reference each other. The typical case is a root workflow plus helper workflows it nests, where none of the definitions exist yet.
 

package/.docs/reference/datasets/startExperiment.md

@@ -79,6 +79,14 @@ console.log(`Status: ${summary2.status}`)
 
 **unmockedToolPolicy** (`'allow' | 'deny'`): Controls undeclared agent tool calls. allow executes them live. deny fails the item with TOOL\_MOCK\_NOT\_DECLARED before execution. An item-level value overrides this experiment default. (Default: `'allow'`)
 
+**beforeAll** (`(args: ExperimentHookArgs) => void | Promise<void>`): Runs once before any item executes. Receives experimentId, mastra, and signal. A failure fails the experiment and no items run.
+
+**beforeEach** (`(args: ExperimentItemHookArgs) => void | Promise<void>`): Runs before each item executes. Also receives the item (id, input, groundTruth, metadata). A failure fails that item with EXPERIMENT\_ITEM\_BEFORE\_EACH\_FAILED and skips its target, scorers, and afterEach.
+
+**afterEach** (`(args: ExperimentItemResultHookArgs) => void | Promise<void>`): Runs after each item completes. Also receives the item's result with its scores. Skipped when beforeEach failed. A failure is logged and doesn't change the item's outcome.
+
+**afterAll** (`(args: ExperimentRunResultHookArgs) => void | Promise<void>`): Runs once after the experiment finishes, on every exit path including failure. Also receives the summary. A failure is logged and doesn't change the summary.
+
 **persistence** (`ExperimentPersistencePolicy`): Controls whether this run writes experiment records and score records. Targets and scorers still execute, and results remain available in the returned summary.
 
 **persistence.experiments** (`'default' | 'none'`): Set to none to skip experiment creation, item results, progress, and terminal status writes.

package/.docs/reference/file-based-agents/config.md

@@ -2,6 +2,8 @@
 
 # config.ts
 
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
 An agent's `config.ts` sets its model and runtime options. Use it for options that belong to the [`Agent`](https://mastra.ai/reference/agents/agent) itself, while sibling files provide instructions, tools, skills, et cetera.
 
 ## What belongs in `config.ts`

package/.docs/reference/file-based-agents/instructions.md

@@ -2,6 +2,8 @@
 
 # Instructions
 
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
 An agent's instructions hold its always-on system prompt: the model reads it on every turn. Use them to define the agent's identity, tone, role, and standing rules.
 
 Write them in one of two files at the agent root. Use `instructions.md` when the prompt is fixed text. Use `instructions.ts` when the prompt needs code, for example when it's built from shared constants or resolved per request.

package/.docs/reference/file-based-agents/logger.md

@@ -2,6 +2,8 @@
 
 # Logger
 
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
 Mastra sets the project's [logger](https://mastra.ai/docs/observability/logging) from a `logger.ts` file directly under `src/mastra/`. The file default-exports a logger, which replaces the built-in `ConsoleLogger` used across agents, workflows, and other components.
 
 Use this page for the file-based convention. For log levels, transports, and provider details, see [logging](https://mastra.ai/docs/observability/logging).

package/.docs/reference/file-based-agents/memory.md

@@ -2,6 +2,8 @@
 
 # Memory
 
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
 A file-based agent gets [memory](https://mastra.ai/docs/memory/overview) from a `memory.ts` file that default-exports a [`Memory`](https://mastra.ai/reference/memory/memory-class) instance. Use this page for the file-based convention; use the memory docs for message history, semantic recall, storage, and processors.
 
 Without `memory.ts` or `config.memory`, the agent has no memory by default. Each `generate()` or `stream()` call starts without remembered conversation state unless you pass the prior context yourself.

package/.docs/reference/file-based-agents/observability.md

@@ -2,6 +2,8 @@
 
 # Observability
 
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
 Mastra configures [observability](https://mastra.ai/docs/observability/overview) from an `observability.ts` file directly under `src/mastra/`. The file default-exports an `Observability` instance that sets up tracing, logging, metrics, and feedback for the project.
 
 Use this page for the file-based convention. For the signal model, exporters, storage, and multi-config setup, see the [observability overview](https://mastra.ai/docs/observability/overview) and [observability configuration](https://mastra.ai/docs/observability/overview).

package/.docs/reference/file-based-agents/processors.md

@@ -2,6 +2,8 @@
 
 # Processors
 
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
 A file-based agent discovers [processors](https://mastra.ai/docs/agents/processors) from its `processors/` directory. Use this page for the file-based convention; use the processors guide for built-in processors, custom processors, streaming behavior, and advanced patterns.
 
 Files under `processors/input/` run before messages reach the model. Files under `processors/output/` run after the model responds. Each file default-exports one [`Processor`](https://mastra.ai/reference/processors/processor-interface), and the filename becomes its discovery key.

package/.docs/reference/file-based-agents/schedules.md

@@ -2,6 +2,8 @@
 
 # Schedules
 
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
 A file-based agent discovers **schedules** from its `schedules/` directory. Each file declares one recurring task: a cron expression plus what the agent should do when it fires. Mastra registers them into schedule storage at startup, so a scheduled agent needs no runtime registration code.
 
 Use this page for the file-based convention. To create schedules at runtime instead, see [Schedules](https://mastra.ai/reference/schedules/overview).

package/.docs/reference/file-based-agents/scorers.md

@@ -2,6 +2,8 @@
 
 # Scorers
 
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
 A file-based agent discovers [scorers](https://mastra.ai/docs/evals/overview) from its `scorers/` directory. Use this page for the file-based convention; use the scorers guide for built-in scorers, custom scorers, and sampling.
 
 Each file under `scorers/` default-exports one scorer, and the filename becomes its key. The default export is either a [`MastraScorer`](https://mastra.ai/reference/evals/create-scorer) or a `{ scorer, sampling }` entry.

package/.docs/reference/file-based-agents/server.md

@@ -2,6 +2,8 @@
 
 # Server
 
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
 Mastra configures its HTTP [server](https://mastra.ai/docs/server/mastra-server) from a `server.ts` file directly under `src/mastra/`. The server exposes agents, workflows, and other registered primitives as REST endpoints, and the file default-exports the same `ServerConfig` shape you'd pass to [`new Mastra()`](https://mastra.ai/reference/core/mastra-class).
 
 Use this page for the file-based convention. For server features, middleware, custom routes, generated API docs, and deployment behavior, see [Server overview](https://mastra.ai/docs/server/mastra-server).

package/.docs/reference/file-based-agents/skills.md

@@ -2,6 +2,8 @@
 
 # Skills
 
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
 A file-based agent discovers skills from its `skills/` directory and bundles them at build time. Skills are reusable procedures or reference material that the agent can load when relevant, instead of putting every detail into the always-on prompt.
 
 Use this page for the file-based convention. For code-defined skills, see [Agent skills](https://mastra.ai/docs/agents/skills). For the `SKILL.md` package format, see [Workspace skills](https://mastra.ai/docs/workspace/skills).

package/.docs/reference/file-based-agents/storage.md

@@ -2,6 +2,8 @@
 
 # Storage
 
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
 Mastra sets the project's default [storage](https://mastra.ai/docs/storage/overview) from a `storage.ts` file directly under `src/mastra/`. The file default-exports a store, which replaces the built-in in-memory store used for memory, workflows, observability, and other storage domains.
 
 Use this page for the file-based convention. For backend choice, storage domains, retention, and provider details, see [storage overview](https://mastra.ai/docs/storage/overview).

package/.docs/reference/file-based-agents/studio.md

@@ -2,6 +2,8 @@
 
 # Studio
 
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
 Mastra configures [Studio](https://mastra.ai/docs/studio/overview) from a `studio.ts` file directly under `src/mastra/`. The file default-exports a `StudioConfig` object for Studio authentication and authorization: who can access Studio, and what authenticated users can do.
 
 Use this page for the file-based convention. For auth providers, role-based access control (RBAC), and fine-grained authorization (FGA), see [Studio auth](https://mastra.ai/docs/studio/auth).

package/.docs/reference/file-based-agents/subagents.md

@@ -2,6 +2,8 @@
 
 # Subagents
 
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
 A file-based agent can declare **subagents**, specialist child agents it delegates to. The parent model sees each subagent as a delegation tool named after the subagent directory and calls that tool to hand off a task. The subagent's result returns to the parent conversation.
 
 Use this page for the file-based convention. For broader delegation patterns, hooks, memory isolation, tool approval propagation, and scoring, see [Supervisor agents](https://mastra.ai/docs/capabilities/subagents).

package/.docs/reference/file-based-agents/tools.md

@@ -2,6 +2,8 @@
 
 # Tools
 
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
 A file-based agent discovers tools from `.ts` and `.js` files directly under its `tools/` directory. Each discovered file is imported at build time, the file must default-export a [`createTool()`](https://mastra.ai/reference/tools/create-tool) result, and the filename without its extension becomes the tool key the model can call.
 
 Use this page for the file-based convention. For tool schemas, execution options, output shaping, and approval options, see the [`createTool()` reference](https://mastra.ai/reference/tools/create-tool).

package/.docs/reference/file-based-agents/workflows.md

@@ -2,6 +2,8 @@
 
 # Workflows
 
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
 Mastra discovers project-level workflows from `.ts` and `.js` files under `src/mastra/workflows/`. This convention isn't scoped to one agent: every file with a default export becomes a registered workflow, and the filename becomes the workflow key.
 
 Use this page for the file-based convention. For steps, schemas, control flow, streaming, state, and workflow execution, see [Workflows overview](https://mastra.ai/docs/workflows/overview).

package/.docs/reference/file-based-agents/workspace.md

@@ -2,6 +2,8 @@
 
 # Workspace
 
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
 A [workspace](https://mastra.ai/docs/workspace/overview) gives an agent filesystem access and command execution. File-based agents get a default workspace automatically when discovered through `mastra dev` or `mastra build`, so they can read and write files and run shell commands without extra configuration.
 
 Use this page for the file-based convention. For workspace providers, tools, search, lifecycle, and sandbox details, see [Workspaces](https://mastra.ai/docs/workspace/overview).

package/.docs/reference/index.md

@@ -313,6 +313,7 @@ The Reference section provides documentation of Mastra's API, including paramete
 - [MCPClient](https://mastra.ai/reference/tools/mcp-client)
 - [MCPServer](https://mastra.ai/reference/tools/mcp-server)
 - [Perplexity Tools](https://mastra.ai/reference/tools/perplexity)
+- [QuickJsCodeModeTransport](https://mastra.ai/reference/tools/quickjs-transport)
 - [submitPlanTool](https://mastra.ai/reference/tools/submit-plan-tool)
 - [Task tools](https://mastra.ai/reference/tools/task-tools)
 - [Tavily Tools](https://mastra.ai/reference/tools/tavily)

package/.docs/reference/observability/tracing/exporters/datadog.md

@@ -4,7 +4,7 @@
 
 Sends Tracing data to Datadog's LLM Observability product for monitoring and analytics.
 
-> **Info:** If you also use `dd-trace` APM auto-instrumentation and need it correctly parented under Mastra spans, use the [DatadogBridge](https://mastra.ai/reference/observability/tracing/bridges/datadog) instead. The exporter sends LLM Observability data after execution completes, so it doesn't participate in `dd-trace`'s live scope.
+> **Note:** If you also use `dd-trace` APM auto-instrumentation and need it correctly parented under Mastra spans, use the [DatadogBridge](https://mastra.ai/reference/observability/tracing/bridges/datadog) instead. The exporter sends LLM Observability data after execution completes, so it doesn't participate in `dd-trace`'s live scope.
 
 ## Constructor
 

package/.docs/reference/processors/pii-detector.md

@@ -42,6 +42,8 @@ const processor = new PIIDetector({
 
 **options.providerOptions** (`ProviderOptions`): Provider-specific options passed to the internal detection agent. Use this to control model behavior like reasoning effort for thinking models (e.g., { openai: { reasoningEffort: 'low' } })
 
+**options.onDetection** (`(event: PIIDetectionEvent) => void | Promise<void>`): Called whenever a detection result is produced, with detectionResult, the analyzed input, whether it was flagged, and the strategyApplied (the configured strategy when flagged, otherwise none). Fires for every analyzed message in processInput and processOutputResult, and for every LLM buffer flush during streaming; the streaming regex pass only reports when PII is found. Errors thrown by the callback are logged and ignored
+
 ## Returns
 
 **id** (`string`): Processor identifier set to 'pii-detector'

package/.docs/reference/processors/prompt-injection-detector.md

@@ -38,6 +38,8 @@ const processor = new PromptInjectionDetector({
 
 **options.providerOptions** (`ProviderOptions`): Provider-specific options passed to the internal detection agent. Use this to control model behavior like reasoning effort for thinking models (e.g., { openai: { reasoningEffort: 'low' } })
 
+**options.onDetection** (`(event: PromptInjectionDetectionEvent) => void | Promise<void>`): Called for every analyzed message with detectionResult, the analyzed input, whether it was flagged, and the strategyApplied (the configured strategy when flagged, otherwise none). Use it to emit custom metrics. Errors thrown by the callback are logged and ignored
+
 ## Returns
 
 **id** (`string`): Processor identifier set to 'prompt-injection-detector'

package/.docs/reference/processors/response-cache.md

@@ -2,6 +2,8 @@
 
 # ResponseCache
 
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
 `ResponseCache` is an input processor that caches LLM responses on the request/response boundary inside the agentic loop. It hooks into `processLLMRequest` for cache lookup and short-circuits on a hit. It uses `processLLMResponse` to write the completed response.
 
 The cache key is derived from the resolved `LanguageModelV2Prompt` Mastra is about to send to the model (i.e. _after_ memory has loaded and earlier input processors have transformed the prompt) so two users with different memory contexts produce different cache keys. Each step in an agentic tool loop is independently cached.

package/.docs/reference/schedules/overview.md

@@ -4,6 +4,8 @@
 
 **Added in:** `@mastra/core@1.50.0`
 
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
 `mastra.schedules` is the CRUD service for persisted cron schedules. Use it to create, list, update, pause, resume, manually run, and delete schedules for agents or workflows.
 
 For usage patterns and concepts, see [Schedules](https://mastra.ai/docs/long-running-agents/schedules).

package/.docs/reference/signals/create-notification-inbox-tool.md

@@ -4,6 +4,8 @@
 
 **Added in:** `@mastra/core@1.39.0`
 
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
 `createNotificationInboxTool()` creates a Mastra tool that lets an agent inspect and manage notification inbox records for the current thread.
 
 Use this tool with durable notification signals. For sending notification records, see [`Agent.sendNotificationSignal()`](https://mastra.ai/reference/agents/agent).

package/.docs/reference/signals/signal-provider.md

@@ -4,6 +4,8 @@
 
 **Added in:** `@mastra/core@1.39.0`
 
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
 Abstract base class for building signal providers. A signal provider monitors external sources (APIs, webhooks, event streams) and pushes notification signals into agent threads through a built-in subscription registry.
 
 Signal providers aren't processors by default. Providers that need to intercept agent execution return processors from `getInputProcessors()` or `getOutputProcessors()`. Providers that expose agent-callable tools return them from `getTools()`.

package/.docs/reference/signals/task-signal-provider.md

@@ -2,6 +2,8 @@
 
 # TaskSignalProvider
 
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
 Bundles the built-in task tools (`task_write`, `task_update`, `task_complete`, `task_check`) and the `TaskStateProcessor` behind a single agent registration. Use it to add a structured, durable task list to an agent without wiring the tools and processor separately.
 
 Extends [`SignalProvider`](https://mastra.ai/reference/signals/signal-provider). The task list is stored in the thread-scoped `tasks` storage domain (the source of truth) and projected onto the agent state-signal lane by the processor, so it survives observational-memory truncation without invalidating the prompt cache.

package/.docs/reference/signals/webhook-signal-provider.md

@@ -4,6 +4,8 @@
 
 **Added in:** `@mastra/core@1.39.0`
 
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
 Concrete signal provider for push-based event delivery. Routes incoming webhook payloads to subscribed agent threads by matching the payload against a configurable resource ID extractor.
 
 Extends [`SignalProvider`](https://mastra.ai/reference/signals/signal-provider) with public subscription management and a built-in `handleWebhook()` implementation.

package/.docs/reference/storage/composite.md

@@ -394,4 +394,4 @@ const storage = new MastraCompositeStore({
 
 Don't set `replication` on ClickHouse Cloud. Cloud rewrites `MergeTree` to `SharedMergeTree` server-side. See the [ClickHouse storage reference](https://mastra.ai/reference/storage/clickhouse) for the full config shape and operator notes.
 
-> **Info:** This approach is also required when using storage providers that don't support observability (like Convex, DynamoDB, or Cloudflare). See the [MastraStorageExporter documentation](https://mastra.ai/docs/observability/integrations/exporters/mastra-storage) for the full list of supported providers.
+> **Note:** This approach is also required when using storage providers that don't support observability (like Convex, DynamoDB, or Cloudflare). See the [MastraStorageExporter documentation](https://mastra.ai/docs/observability/integrations/exporters/mastra-storage) for the full list of supported providers.

package/.docs/reference/streaming/agents/stream.md

@@ -10,7 +10,7 @@ The `.stream()` method enables real-time streaming of responses from an agent wi
 const stream = await agent.stream('message for agent')
 ```
 
-> **Info:** **Model Compatibility**: This method is designed for V2 models. V1 models should use the [`.streamLegacy()`](https://mastra.ai/reference/streaming/agents/streamLegacy) method. The framework automatically detects your model version and will throw an error if there's a mismatch.
+> **Note:** **Model Compatibility**: This method is designed for V2 models. V1 models should use the [`.streamLegacy()`](https://mastra.ai/reference/streaming/agents/streamLegacy) method. The framework automatically detects your model version and will throw an error if there's a mismatch.
 
 ## Parameters
 

package/.docs/reference/streaming/agents/streamLegacy.md

@@ -152,7 +152,7 @@ await agent.streamLegacy('message for agent', {
 
 ## Migration to new API
 
-> **Info:** The new `.stream()` method offers enhanced capabilities including AI SDK v5+ compatibility, better structured output handling, and improved callback system. See the [migration guide](https://mastra.ai/guides/migrations/vnext-to-standard-apis) for detailed migration instructions.
+> **Note:** The new `.stream()` method offers enhanced capabilities including AI SDK v5+ compatibility, better structured output handling, and improved callback system. See the [migration guide](https://mastra.ai/guides/migrations/vnext-to-standard-apis) for detailed migration instructions.
 
 ### Quick Migration Example
 

package/.docs/reference/streaming/agents/streamUntilIdle.md

@@ -32,7 +32,7 @@ for await (const chunk of stream.fullStream) {
 }
 ```
 
-> **Info:** `streamUntilIdle()` requires both a [`BackgroundTaskManager`](https://mastra.ai/reference/configuration) and a [memory](https://mastra.ai/docs/memory/overview) backend. Without either, it uses a plain `agent.stream()` call.
+> **Note:** `streamUntilIdle()` requires both a [`BackgroundTaskManager`](https://mastra.ai/reference/configuration) and a [memory](https://mastra.ai/docs/memory/overview) backend. Without either, it uses a plain `agent.stream()` call.
 
 ## Parameters
 

package/.docs/reference/tools/create-code-mode.md

@@ -4,6 +4,8 @@
 
 **Added in:** `@mastra/core@1.38.0`
 
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
 The `createCodeMode()` function returns a tool and generated instructions that let an agent run multi-tool computations as one TypeScript function. The generated code runs in a workspace sandbox, and each `external_*` call runs the real tool on the host with validation, request context, and tracing.
 
 For a conceptual overview, see [Code mode](https://mastra.ai/docs/agents/code-mode).
@@ -62,7 +64,7 @@ export const shopAgent = new Agent({
 
 **config.id** (`string`): The generated tool id.
 
-**transport** (`CodeModeTransport`): Optional transport implementation used to run the generated code in the sandbox. The default transport uses stdio JSON-RPC over the workspace sandbox process API. Transports that declare requiresSandbox: false (such as IsolatedVmCodeModeTransport) run without a sandbox.
+**transport** (`CodeModeTransport`): Optional transport implementation used to run the generated code in the sandbox. The default transport uses stdio JSON-RPC over the workspace sandbox process API. Transports that declare requiresSandbox: false (such as IsolatedVmCodeModeTransport and QuickJsCodeModeTransport) run without a sandbox.
 
 ## Returns
 

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

@@ -2,7 +2,7 @@
 
 # IsolatedVmCodeModeTransport
 
-> **Beta:** This feature is in beta. Breaking changes may occur without a major version bump until the API is stable.
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
 
 The `IsolatedVmCodeModeTransport` class runs [Code mode](https://mastra.ai/docs/agents/code-mode) programs in an in-process V8 isolate, backed by [isolated-vm](https://github.com/laverdet/isolated-vm). The isolate is the execution boundary, so no workspace sandbox is required: the program has no filesystem, network, process, or module access. Its only capabilities are the `external_*` functions, which call back into the real tools on the host.
 

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

@@ -244,6 +244,57 @@ const res = await agent.stream(prompt, {
 })
 ```
 
+### `listToolDefinitions()`
+
+Returns every server's tools as plain, serializable definitions, grouped by server name and keyed by the server's own tool name (without the `serverName_toolName` namespacing that `listTools()` applies).
+
+Unlike `listTools()`, the result contains no functions or references to a live client, so it can be passed through `JSON.stringify` and cached in Redis, a database, or a build artifact. Each definition holds the data from the MCP `tools/list` response (name, description, input schema, output schema, annotations, and `_meta`), plus the server name, version, and instructions captured at discovery time.
+
+```typescript
+const definitions = await mcp.listToolDefinitions()
+
+await cache.set('mcp-tools', JSON.stringify(definitions))
+```
+
+### `listToolDefinitionsWithErrors()`
+
+Like `listToolDefinitions()`, but also returns per-server errors for servers that failed to connect. Use this when caching a catalog, so you don't persist a partial manifest that omits a server that was down at discovery time.
+
+```typescript
+const { definitions, errors } = await mcp.listToolDefinitionsWithErrors()
+
+if (Object.keys(errors).length === 0) {
+  await cache.set('mcp-tools', JSON.stringify(definitions))
+}
+```
+
+### `toolFromDefinition()`
+
+Rebuilds a single executable tool from a cached definition. No connection is opened here. The client connects lazily, the first time the tool is executed.
+
+The returned tool behaves exactly like one from `listTools()`, with the same strict-mode metadata, approval policy, structured content handling, tool error handling, and reconnect behavior.
+
+```typescript
+const definitions = JSON.parse(await cache.get('mcp-tools'))
+
+const tool = await mcp.toolFromDefinition({
+  serverName: 'weather',
+  definition: definitions.weather.getForecast,
+})
+```
+
+### `toolsFromDefinitions()`
+
+Rebuilds an entire cached catalog into a namespaced tool map, without connecting. This is the cached counterpart to `listTools()`. It produces the same `serverName_toolName` keys, so you can reconstruct an agent's tool map on a cold start, and connections only open for the servers whose tools are actually called.
+
+Servers present in the catalog but no longer configured on the client are skipped, so a stale cached manifest degrades gracefully.
+
+```typescript
+const definitions = JSON.parse(await cache.get('mcp-tools'))
+
+new Agent({ id: 'agent', tools: await mcp.toolsFromDefinitions({ definitions }) })
+```
+
 ### `getServerInstructions()`
 
 Returns the instructions currently known for each configured MCP server. Servers that haven't connected yet, or don't advertise instructions, return `undefined`.

package/.docs/reference/tools/quickjs-transport.md

@@ -0,0 +1,92 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
+# QuickJsCodeModeTransport
+
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
+The `QuickJsCodeModeTransport` class runs [Code mode](https://mastra.ai/docs/agents/code-mode) programs in an in-process [QuickJS](https://bellard.org/quickjs/) runtime compiled to WebAssembly. The runtime is the execution boundary, so no workspace sandbox is required: the program has no filesystem, network, process, or module access. Its only capabilities are the `external_*` functions, which call back into the real tools on the host.
+
+Unlike [`IsolatedVmCodeModeTransport`](https://mastra.ai/reference/tools/isolated-vm-transport), this transport installs no native binaries and needs no Node.js flags, so it runs on serverless platforms that disallow both. The tradeoff is speed: see [Choosing a transport](#choosing-a-transport).
+
+## Installation
+
+**npm**:
+
+```bash
+npm install @mastra/quickjs
+```
+
+**pnpm**:
+
+```bash
+pnpm add @mastra/quickjs
+```
+
+**Yarn**:
+
+```bash
+yarn add @mastra/quickjs
+```
+
+**Bun**:
+
+```bash
+bun add @mastra/quickjs
+```
+
+The package contains the WebAssembly module, so installing it copies files and runs nothing else.
+
+## Usage
+
+Pass the transport as the second argument to `createCodeMode()`. No `sandbox` is needed:
+
+```typescript
+import { createCodeMode } from '@mastra/core/tools'
+import { QuickJsCodeModeTransport } from '@mastra/quickjs'
+
+const { tool, instructions } = createCodeMode(
+  { tools: { getTopProducts, getProductRatings } },
+  new QuickJsCodeModeTransport({ memoryLimitMb: 128 }),
+)
+```
+
+## Constructor parameters
+
+**options** (`QuickJsCodeModeTransportOptions`): Configuration for the QuickJS runtime.
+
+**options.memoryLimitMb** (`number`): Runtime heap limit in MiB. A program that exceeds the limit is terminated and the tool returns an error result.
+
+**options.maxStackSizeBytes** (`number`): Runtime stack limit in bytes. A program that exceeds the limit, usually through runaway recursion, is terminated and the tool returns an error result.
+
+**options.module** (`QuickJSWASMModule`): A preloaded QuickJS WebAssembly module. Supply one to control when the module is loaded, or to share a single module across transports. Loaded on first run when omitted.
+
+## Choosing a transport
+
+All three transports enforce the same allow-list, tool validation, and tracing on the host. They differ in what the program itself can reach and what the host has to provide.
+
+|                     | `StdioCodeModeTransport`       | `IsolatedVmCodeModeTransport`                | `QuickJsCodeModeTransport`  |
+| ------------------- | ------------------------------ | -------------------------------------------- | --------------------------- |
+| Isolation boundary  | Workspace sandbox              | V8 isolate                                   | QuickJS WebAssembly runtime |
+| Requires a sandbox  | Yes                            | No                                           | No                          |
+| Native binary       | Node.js runtime in the sandbox | Yes                                          | No                          |
+| Node.js flags       | None                           | `--no-node-snapshot` on Node.js 20 and later | None                        |
+| Runs in the browser | No                             | No                                           | Yes                         |
+| Execution speed     | Fastest                        | Fast                                         | Slowest                     |
+
+Choose `QuickJsCodeModeTransport` when the host can't install native addons or set Node.js flags, which is common on serverless platforms. Choose `IsolatedVmCodeModeTransport` when the host allows both and programs do heavy computation.
+
+The speed difference is in the program body, not the tool calls. QuickJS interprets rather than JIT-compiles, so a compute-heavy loop can run tens of times slower than in a V8 isolate, while a program that mostly awaits `external_*` calls performs about the same because the time goes to the tools. Code Mode programs are usually the second kind.
+
+## How it works
+
+Each run creates a fresh QuickJS runtime with its own heap. TypeScript is stripped on the host with [ts-blank-space](https://github.com/bloomberg/ts-blank-space), which erases type annotations without a native compiler, then the program is evaluated inside the runtime. Every `external_*` call crosses the boundary as JSON strings in both directions, so no host object references leak into model-authored code.
+
+An `external_*` call returns a pending promise to the program and hands control straight back to the host, so many calls can be in flight at once and `Promise.all` behaves as expected.
+
+The `timeout` configured on `createCodeMode()` applies to both asynchronous hangs and synchronous infinite loops, and the runtime is disposed after every run.
+
+## Related
+
+- [Code mode](https://mastra.ai/docs/agents/code-mode)
+- [createCodeMode() reference](https://mastra.ai/reference/tools/create-code-mode)
+- [IsolatedVmCodeModeTransport reference](https://mastra.ai/reference/tools/isolated-vm-transport)

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

@@ -4,7 +4,7 @@
 
 The ChromaVector class provides vector search using [Chroma](https://docs.trychroma.com/docs/overview/getting-started), an open-source embedding database. It offers efficient vector search with metadata filtering and hybrid search capabilities.
 
-> **Info:**
+> **Note:**
 >
 > **Chroma Cloud**
 >

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

@@ -2,6 +2,8 @@
 
 # Workers
 
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
 For usage patterns and deployment topologies, see [Workers](https://mastra.ai/docs/deployment/workers).
 
 ## Environment variables