@mastra/mcp-docs-server 1.2.7-alpha.12 → 1.2.7-alpha.4

package/.docs/reference/storage/clickhouse.md

@@ -101,38 +101,6 @@ const observabilityStore = new ObservabilityStorageClickhouse({
 
 New projects should use `ObservabilityStorageClickhouseVNext` instead.
 
-### Migrating from legacy to vNext
-
-To migrate historical spans from the legacy `mastra_ai_spans` table to the vNext schema, run:
-
-**npm**:
-
-```bash
-npx mastra migrate
-```
-
-**pnpm**:
-
-```bash
-pnpm dlx mastra migrate
-```
-
-**Yarn**:
-
-```bash
-yarn dlx mastra migrate
-```
-
-**Bun**:
-
-```bash
-bun x mastra migrate
-```
-
-The migration copies span data from `mastra_ai_spans` into `mastra_span_events` in day-sized batches. It handles column mapping, deduplicates legacy rows, and preserves the original table as a backup. After migration, traces appear in Studio through the vNext adapter.
-
-> **Note:** The legacy table is not deleted. Drop it manually after verifying the migration.
-
 ### ClickHouse for every domain
 
 `ClickhouseStoreVNext` backs the `memory`, `workflows`, and `observability` domains with ClickHouse and uses the vNext observability adapter automatically. Use it when you want ClickHouse to back the entire application without wiring a composite store manually.

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

@@ -156,32 +156,6 @@ export const mastra = new Mastra({
 })
 ```
 
-### Disabling a domain
-
-Set a domain to `false` to disable it. A disabled domain doesn't fall back to `default`, so data for that domain isn't persisted:
-
-```typescript
-import { MastraCompositeStore } from '@mastra/core/storage'
-import { PostgresStore } from '@mastra/pg'
-import { Mastra } from '@mastra/core'
-
-const pgStore = new PostgresStore({
-  id: 'pg',
-  connectionString: process.env.DATABASE_URL,
-})
-
-export const mastra = new Mastra({
-  storage: new MastraCompositeStore({
-    id: 'composite',
-    default: pgStore,
-    domains: {
-      // don't persist traces and spans
-      observability: false,
-    },
-  }),
-})
-```
-
 ## Options
 
 **id** (`string`): Unique identifier for this storage instance.
@@ -190,7 +164,7 @@ export const mastra = new Mastra({
 
 **disableInit** (`boolean`): When true, automatic initialization is disabled. You must call init() explicitly.
 
-**domains** (`object`): Individual domain overrides. Each domain can come from a different storage adapter. These take precedence over both editor and default storage. Set a domain to false to disable it entirely; a disabled domain does not fall back to editor or default.
+**domains** (`object`): Individual domain overrides. Each domain can come from a different storage adapter. These take precedence over both editor and default storage.
 
 **domains.memory** (`MemoryStorage`): Storage for threads, messages, and resources.
 

package/.docs/reference/storage/retention.md

@@ -105,8 +105,6 @@ Deletes rows older than their configured `maxAge` across every domain that has a
 
 `prune()` is designed to be safe on tables with millions of rows. It deletes in bounded, batched chunks — each batch is its own transaction — so it never takes a long lock or bloats the transaction log. It never runs a `VACUUM`.
 
-Pass `options.retention` to replace the configured policies for that call only — for example to skip a domain (keep chat history) or prune more aggressively than the standing config. The store's configured `retention` is unchanged.
-
 Anchor-column indexes are created lazily on the first `prune()` call for each table with a policy — never at `init()` — so deployments that don't configure retention pay no extra index write or disk overhead. The first prune of an existing large table pays a one-time index build; subsequent prunes reuse the index.
 
 ```typescript
@@ -118,13 +116,6 @@ const results = await storage.prune({
 for (const r of results) {
   console.log(`${r.domain}.${r.table}: deleted ${r.deleted}, done=${r.done}`)
 }
-
-// One-off pass with different policies (configured retention untouched):
-await storage.prune({
-  retention: {
-    observability: { spans: { maxAge: '1d' } },
-  },
-})
 ```
 
 Returns: `Promise<PruneResult[]>`
@@ -139,8 +130,6 @@ Returns: `Promise<PruneResult[]>`
 
 **signal** (`AbortSignal`): Cooperative cancellation. The batch loop checks it between batches and stops cleanly, returning partial results with done: false.
 
-**retention** (`RetentionConfig`): Replaces the store's configured retention policies for this call only — e.g. to skip a domain or prune more aggressively. The configured retention is unchanged.
-
 ##### PruneResult
 
 Each result describes one table's progress:

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

@@ -601,28 +601,6 @@ mcpClient.prompts.onListChanged('myWeatherServer', () => {
 })
 ```
 
-### `tools` Property
-
-The `MCPClient` instance has a `tools` property for subscribing to tool list change notifications. To fetch tools, use `listTools()` or `listToolsets()`.
-
-#### `tools.onListChanged(serverName: string, handler: () => void)`
-
-Sets a notification handler that will be called when the list of available tools changes on a specific server (for example, when the server adds or removes tools at runtime).
-
-```typescript
-async onListChanged(serverName: string, handler: () => void): Promise<void>
-```
-
-Example:
-
-```typescript
-await mcpClient.tools.onListChanged('myWeatherServer', async () => {
-  console.log('Tool list changed on myWeatherServer.')
-  // You should re-fetch the tools
-  // const tools = await mcpClient.listTools();
-})
-```
-
 ### `progress` Property
 
 The `MCPClient` instance has a `progress` property for subscribing to progress notifications emitted by MCP servers while tools execute.

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

@@ -399,31 +399,12 @@ 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.
 >
-> By default, serverless mode buffers each request into a single JSON response, so `notifications/progress` sent by a tool never reach the client. Set `serverlessStreaming: true` to handle the request with request-scoped SSE streaming instead, which delivers progress notifications before the final result:
->
-> ```typescript
-> await server.startHTTP({
->   url,
->   httpPath: '/mcp',
->   req: nodeReq,
->   res: nodeRes,
->   options: {
->     serverless: true,
->     serverlessStreaming: true, // ← Stream request-scoped notifications/progress
->   },
-> })
-> ```
->
-> This is still stateless: no `mcp-session-id` is required or persisted. It only enables notifications scoped to the current request (such as progress). The session-dependent features below remain unavailable.
->
-> **Note:** The following MCP features require session state or persistent connections and **won't work** in serverless mode (including with `serverlessStreaming: true`):
+> **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
 > - **Resource update notifications** - `resources.notifyUpdated()` requires active subscriptions and persistent connections to notify clients
 > - **Prompt list change notifications** - `prompts.notifyListChanged()` requires persistent connections to push updates to clients
-> - **Tool list change notifications** - `toolActions.notifyListChanged()` requires persistent connections to push updates to clients
-> - **Server log notifications** - `sendLoggingMessage()` requires persistent connections to push log messages to clients
 >
 > These features work normally in long-lived server environments (Node.js servers, Docker containers, etc.).
 
@@ -443,8 +424,6 @@ The `StreamableHTTPServerTransportOptions` object allows you to customize the be
 
 **serverless** (`boolean`): If true, runs in stateless mode without session management. Each request is handled independently with a fresh server instance. Essential for serverless environments (Cloudflare Workers, Supabase Edge Functions, Vercel Edge, etc.) where sessions cannot persist between invocations. Defaults to false.
 
-**serverlessStreaming** (`boolean`): If true, serverless requests use request-scoped SSE streaming instead of a buffered JSON response, allowing in-request notifications/progress to reach the client before the final result. Only takes effect together with serverless: true. Defaults to false (buffered JSON responses), which preserves backward-compatible behavior. This enables only request-scoped notifications such as progress; elicitation, subscriptions, and out-of-request notifications still require session state.
-
 **sessionIdGenerator** (`(() => string) | undefined`): A function that generates a unique session ID. This should be a cryptographically secure, globally unique string. Return undefined to disable session management.
 
 **onsessioninitialized** (`(sessionId: string) => void`): A callback that is invoked when a new session is initialized. This is useful for tracking active MCP sessions.
@@ -797,144 +776,6 @@ await serverWithPrompts.prompts.notifyListChanged()
 - Handle errors with informative messages.
 - Document argument expectations and available versions.
 
-## Dynamic tool management
-
-Tools are usually provided when constructing the `MCPServer`, but you can also add or remove tools while the server is running. The server exposes these operations through the `toolActions` property. When the tool list changes, connected clients receive a `notifications/tools/list_changed` message prompting them to re-fetch the tool list.
-
-The property is named `toolActions` because `tools()` is the method that returns the registered tool registry.
-
-### `toolActions.add(tools)`
-
-Registers new tools on the running server and notifies connected clients. Tools are keyed by their record key, the same as tools passed to the constructor. Adding a tool under an existing key replaces it.
-
-```typescript
-async server.toolActions.add(tools: ToolsInput): Promise<void>
-```
-
-Example:
-
-```typescript
-import { createTool } from '@mastra/core/tools'
-import { z } from 'zod'
-
-const searchTool = createTool({
-  id: 'search',
-  description: 'Searches the knowledge base.',
-  inputSchema: z.object({ query: z.string() }),
-  execute: async ({ query }) => ({ results: [] }),
-})
-
-await server.toolActions.add({ searchTool })
-```
-
-### `toolActions.remove(toolIds)`
-
-Removes tools from the running server by tool ID and notifies connected clients. Unknown tool IDs are ignored. If no tools were removed, no notification is sent.
-
-```typescript
-async server.toolActions.remove(toolIds: string[]): Promise<void>
-```
-
-Example:
-
-```typescript
-await server.toolActions.remove(['searchTool'])
-```
-
-### `toolActions.notifyListChanged()`
-
-Sends a `notifications/tools/list_changed` message to connected clients without modifying the tool registry. Call this when tool availability changes through other means (for example, authorization changes).
-
-```typescript
-async server.toolActions.notifyListChanged(): Promise<void>
-```
-
-### Mastra registry synchronization
-
-When the server is registered with a Mastra instance, `toolActions.add()` and `toolActions.remove()` also update the Mastra instance's tool registry, matching the automatic tool registration that happens at startup. Added tools become available through `mastra.listTools()` (keyed by the tool's intrinsic `id` when present), and removed tools are deleted from the registry.
-
-## Logging
-
-MCP servers can send structured log messages to clients using `notifications/message`. Clients control verbosity by sending a `logging/setLevel` request; the server drops messages below the requested minimum level (following RFC 5424 severity ordering). The level is tracked per session, so different clients can request different verbosity.
-
-### `sendLoggingMessage()`
-
-Sends a log notification to all connected clients, honoring each client's minimum logging level.
-
-```typescript
-async server.sendLoggingMessage(params: {
-  level: LoggingLevel;
-  data: unknown;
-  logger?: string;
-}): Promise<void>
-```
-
-Example:
-
-```typescript
-await server.sendLoggingMessage({
-  level: 'info',
-  data: { message: 'Sync completed', itemsProcessed: 42 },
-})
-```
-
-### `context.mcp.log()`
-
-Inside a tool's `execute` function, use `context.mcp.log()` to send a log message to the client that called the tool.
-
-```typescript
-async context.mcp.log(
-  level: LoggingLevel,
-  message: string,
-  data?: Record<string, unknown>
-): Promise<void>
-```
-
-Example:
-
-```typescript
-execute: async ({ location }, context) => {
-  await context.mcp.log('debug', 'Fetching weather', { location })
-  const weather = await fetchWeather(location)
-  await context.mcp.log('info', 'Weather fetched')
-  return weather
-}
-```
-
-## Progress notifications
-
-Long-running tools can report progress to the calling client with `notifications/progress`. Progress is only sent when the caller requested progress tracking by including a `progressToken` in the request (the Mastra `MCPClient` does this when `enableProgressTracking` is set). When no token was sent, `context.mcp.progress()` is a no-op.
-
-### `context.mcp.progress()`
-
-```typescript
-async context.mcp.progress(params: {
-  progress: number;
-  total?: number;
-  message?: string;
-}): Promise<void>
-```
-
-Example:
-
-```typescript
-execute: async ({ items }, context) => {
-  for (const [index, item] of items.entries()) {
-    await processItem(item)
-    await context.mcp.progress({
-      progress: index + 1,
-      total: items.length,
-      message: `Processed ${item.name}`,
-    })
-  }
-  return { done: true }
-}
-```
-
-## Notification delivery
-
-Notification methods (`resources.notifyListChanged()`, `prompts.notifyListChanged()`, `toolActions.notifyListChanged()`, and `sendLoggingMessage()`) broadcast to every connected client across all transports: the stdio/SSE connection and each streamable HTTP session. `resources.notifyUpdated()` is the exception: it only notifies clients that subscribed to the resource URI via `resources/subscribe`. Subscriptions are tracked per session for streamable HTTP clients; legacy SSE clients share the main server instance and therefore share one subscription set. Clients using the stateless serverless mode can't receive notifications because each request uses a transient server instance.
-
 ## Examples
 
 For practical examples of setting up and deploying an MCPServer, see the [Publishing an MCP Server guide](https://mastra.ai/guides/guide/publishing-mcp-server).
@@ -1561,7 +1402,9 @@ const server = new MCPServer({
 })
 ```
 
-Link a tool to its app resource by setting `_meta.ui.resourceUri` on the tool to the matching `ui://` URI. The server auto-normalizes this metadata when registering tools. Visit [MCP Apps](https://mastra.ai/docs/mcp/mcp-apps) for the full app bridge API and usage patterns.
+Link a tool to its app resource by setting `_meta.ui.resourceUri` on the tool to the matching `ui://` URI. The server auto-normalizes this metadata when registering tools.
+
+> **Note:** Visit [MCP Apps](https://mastra.ai/docs/mcp/mcp-apps) for the full app bridge API and usage patterns.
 
 ## Related information
 

package/.docs/reference/workspace/agentcore-runtime-sandbox.md

@@ -4,7 +4,9 @@
 
 Executes shell commands in an [AWS Bedrock AgentCore Runtime](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-execute-command.html) session by using `InvokeAgentRuntimeCommand`.
 
-Use `AgentCoreRuntimeSandbox` when your agent already runs in AgentCore Runtime and you want Mastra workspace command execution to use the same runtime session. For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
+Use `AgentCoreRuntimeSandbox` when your agent already runs in AgentCore Runtime and you want Mastra workspace command execution to use the same runtime session.
+
+> **Info:** For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
 
 > **Warning:** `AgentCoreRuntimeSandbox` only supports one-shot command execution. It doesn't support background process management, stdin, or filesystem mounts. AgentCore Code Interpreter is a separate AWS service and isn't part of this provider.
 

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

@@ -2,7 +2,9 @@
 
 # AgentFSFilesystem
 
-Stores files in a Turso/SQLite database via the [AgentFS](https://github.com/nichochar/agentfs) SDK. Files are persisted across sessions in a local SQLite database, giving agents durable storage without external cloud services. For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
+Stores files in a Turso/SQLite database via the [AgentFS](https://github.com/nichochar/agentfs) SDK. Files are persisted across sessions in a local SQLite database, giving agents durable storage without external cloud services.
+
+> **Info:** For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
 
 ## Installation
 

package/.docs/reference/workspace/apple-container-sandbox.md

@@ -2,7 +2,9 @@
 
 # AppleContainerSandbox
 
-Executes commands inside local OCI Linux containers through Apple's [`container`](https://github.com/apple/container) CLI. The provider starts a long-lived container and uses `container exec` for workspace commands. For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
+Executes commands inside local OCI Linux containers through Apple's [`container`](https://github.com/apple/container) CLI. The provider starts a long-lived container and uses `container exec` for workspace commands.
+
+> **Info:** For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
 
 ## Installation
 

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

@@ -2,7 +2,9 @@
 
 # ArchilFilesystem
 
-Stores files on [Archil](https://docs.archil.com) elastic, serverless disks. Combines an S3-compatible object API for fast reads/writes with `exec()` for POSIX shell operations and `grep()` for parallel server-side search. For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
+Stores files on [Archil](https://docs.archil.com) elastic, serverless disks. Combines an S3-compatible object API for fast reads/writes with `exec()` for POSIX shell operations and `grep()` for parallel server-side search.
+
+> **Info:** For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
 
 ## Installation
 

package/.docs/reference/workspace/azure-blob-filesystem.md

@@ -2,7 +2,9 @@
 
 # AzureBlobFilesystem
 
-Stores files in Azure Blob Storage containers. For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
+Stores files in Azure Blob Storage containers.
+
+> **Info:** For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
 
 ## Installation
 

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

@@ -2,7 +2,9 @@
 
 # BlaxelSandbox
 
-Executes commands in isolated [Blaxel](https://blaxel.ai/) cloud sandboxes. Provides secure, isolated code execution environments with support for mounting cloud storage (S3, GCS) via FUSE. For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
+Executes commands in isolated [Blaxel](https://blaxel.ai/) cloud sandboxes. Provides secure, isolated code execution environments with support for mounting cloud storage (S3, GCS) via FUSE.
+
+> **Info:** For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
 
 ## Installation
 

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

@@ -2,7 +2,9 @@
 
 # DaytonaSandbox
 
-Executes commands in isolated [Daytona](https://www.daytona.io) cloud sandboxes. Supports multiple runtimes, resource configuration, volumes, snapshots, streaming output, sandbox reconnection, filesystem mounting (S3, GCS), and network isolation. For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
+Executes commands in isolated [Daytona](https://www.daytona.io) cloud sandboxes. Supports multiple runtimes, resource configuration, volumes, snapshots, streaming output, sandbox reconnection, filesystem mounting (S3, GCS), and network isolation.
+
+> **Info:** For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
 
 ## Installation
 

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

@@ -2,7 +2,9 @@
 
 # DockerSandbox
 
-Executes commands inside Docker containers on the local machine. Uses long-lived containers with `docker exec` for command execution. Targets local development, CI/CD, air-gapped deployments, and cost-sensitive scenarios where cloud sandboxes are unnecessary. For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
+Executes commands inside Docker containers on the local machine. Uses long-lived containers with `docker exec` for command execution. Targets local development, CI/CD, air-gapped deployments, and cost-sensitive scenarios where cloud sandboxes are unnecessary.
+
+> **Info:** For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
 
 ## Installation
 

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

@@ -2,7 +2,9 @@
 
 # E2BSandbox
 
-Executes commands in isolated [E2B](https://e2b.dev) cloud sandboxes. Provides secure, ephemeral environments with support for mounting cloud storage. For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
+Executes commands in isolated [E2B](https://e2b.dev) cloud sandboxes. Provides secure, ephemeral environments with support for mounting cloud storage.
+
+> **Info:** For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
 
 ## Installation
 

package/.docs/reference/workspace/files-sdk-filesystem.md

@@ -2,7 +2,9 @@
 
 # FilesSDKFilesystem
 
-Stores files in any storage backend supported by [FilesSDK](https://files-sdk.dev) — a unified abstraction over S3, Cloudflare R2, Google Cloud Storage, Azure Blob, Vercel Blob, MinIO, the local filesystem, and more. For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
+Stores files in any storage backend supported by [FilesSDK](https://files-sdk.dev) — a unified abstraction over S3, Cloudflare R2, Google Cloud Storage, Azure Blob, Vercel Blob, MinIO, the local filesystem, and more.
+
+> **Info:** For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
 
 Use `FilesSDKFilesystem` when you want a single adapter that can target multiple storage backends with the same code. Swap the underlying driver without changing the workspace setup. If you only target one backend and want first-class options for that backend, prefer the dedicated provider (for example [`S3Filesystem`](https://mastra.ai/reference/workspace/s3-filesystem) or [`GCSFilesystem`](https://mastra.ai/reference/workspace/gcs-filesystem)).
 

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

@@ -2,7 +2,9 @@
 
 # GCSFilesystem
 
-Stores files in Google Cloud Storage. For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
+Stores files in Google Cloud Storage.
+
+> **Info:** For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
 
 ## Installation
 

package/.docs/reference/workspace/google-drive-filesystem.md

@@ -2,7 +2,9 @@
 
 # GoogleDriveFilesystem
 
-Stores files in a single Google Drive folder. Each directory maps to a Drive folder under the configured root, and paths use POSIX semantics (for example `/notes/todo.txt`). For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
+Stores files in a single Google Drive folder. Each directory maps to a Drive folder under the configured root, and paths use POSIX semantics (for example `/notes/todo.txt`).
+
+> **Info:** For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
 
 ## Installation
 

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

@@ -4,7 +4,9 @@
 
 **Added in:** `@mastra/core@1.1.0`
 
-Stores files in a directory on the local filesystem. For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
+Stores files in a directory on the local filesystem.
+
+> **Info:** For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
 
 ## Usage
 

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

@@ -4,7 +4,9 @@
 
 **Added in:** `@mastra/core@1.1.0`
 
-Executes commands on the local system. For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
+Executes commands on the local system.
+
+> **Info:** For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
 
 ## Usage
 

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

@@ -2,7 +2,9 @@
 
 # ModalSandbox
 
-Executes commands in isolated [Modal](https://modal.com) cloud sandboxes. Provides secure, ephemeral environments backed by Modal's infrastructure. For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
+Executes commands in isolated [Modal](https://modal.com) cloud sandboxes. Provides secure, ephemeral environments backed by Modal's infrastructure.
+
+> **Info:** For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
 
 ## Installation
 

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

@@ -2,7 +2,9 @@
 
 # RailwaySandbox
 
-Executes commands in ephemeral, isolated [Railway](https://docs.railway.com/sandboxes) sandboxes. Each sandbox is an isolated Debian Linux VM provisioned on demand through the Railway TypeScript SDK. Supports command execution with streaming output, command timeouts, configurable idle timeout, `ISOLATED`/`PRIVATE` network isolation, custom base images via the Railway template builder, forking a running sandbox, and reattaching to an existing sandbox by ID. For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
+Executes commands in ephemeral, isolated [Railway](https://docs.railway.com/sandboxes) sandboxes. Each sandbox is an isolated Debian Linux VM provisioned on demand through the Railway TypeScript SDK. Supports command execution with streaming output, command timeouts, configurable idle timeout, `ISOLATED`/`PRIVATE` network isolation, custom base images via the Railway template builder, forking a running sandbox, and reattaching to an existing sandbox by ID.
+
+> **Info:** For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
 
 ## Installation
 

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

@@ -2,7 +2,9 @@
 
 # S3Filesystem
 
-Stores files in Amazon S3 or S3-compatible storage services like Cloudflare R2, MinIO, DigitalOcean Spaces, and Tigris. For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
+Stores files in Amazon S3 or S3-compatible storage services like Cloudflare R2, MinIO, DigitalOcean Spaces, and Tigris.
+
+> **Info:** For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
 
 ## Installation
 

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

@@ -2,7 +2,9 @@
 
 # VercelSandbox
 
-Executes commands inside [Vercel Sandbox](https://vercel.com/docs/vercel-sandbox) which is an ephemeral [Firecracker](https://firecracker-microvm.github.io/) MicroVM running Amazon Linux 2023. Provides a persistent in-session filesystem, `sudo` access, exposed ports, and background processes. For interface details, see the [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
+Executes commands inside [Vercel Sandbox](https://vercel.com/docs/vercel-sandbox) which is an ephemeral [Firecracker](https://firecracker-microvm.github.io/) MicroVM running Amazon Linux 2023. Provides a persistent in-session filesystem, `sudo` access, exposed ports, and background processes.
+
+> **Info:** For interface details, see the [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
 
 > **Note:** This is distinct from [`VercelServerlessSandbox`](https://mastra.ai/reference/workspace/vercel-serverless), which runs commands as stateless Vercel serverless **Functions**. `VercelSandbox` runs a full Linux MicroVM with a persistent filesystem and long-running processes.
 
@@ -146,7 +148,7 @@ Both callbacks are optional and can be used independently.
 
 **resources** (`{ vcpus?: number }`): Resource allocation. Each vCPU comes with 2048 MB of memory.
 
-**ports** (`number[]`): Ports to expose from the sandbox (up to 15). Public HTTPS domains are available via getInfo().metadata.domains.
+**ports** (`number[]`): Ports to expose from the sandbox (up to 4). Public HTTPS domains are available via getInfo().metadata.domains.
 
 **env** (`Record<string, string>`): Default environment variables inherited by all commands. (Default: `{}`)
 
@@ -197,9 +199,9 @@ See the [`SandboxProcessManager` reference](https://mastra.ai/reference/workspac
 
 ## Limits
 
-- Up to 32 vCPUs, with 2048 MB of memory per vCPU.
-- Up to 15 exposed ports.
+- Up to 8 vCPUs, with 2048 MB of memory per vCPU.
+- Up to 4 exposed ports.
 - The filesystem is ephemeral — persisted only within the session and lost when the sandbox stops.
-- Maximum runtime is plan-dependent (45 minutes on Hobby, up to 24 hours on Pro and Enterprise), with a default of 5 minutes.
+- Maximum runtime is plan-dependent (45 minutes on Hobby, up to 5 hours on Pro/Enterprise), with a default of 5 minutes.
 
 See the [Vercel Sandbox documentation](https://vercel.com/docs/vercel-sandbox) for current limits and pricing.

package/.docs/reference/workspace/vercel-serverless.md

@@ -2,7 +2,9 @@
 
 # VercelServerlessSandbox
 
-Executes commands as [Vercel](https://vercel.com) serverless functions. Provides globally distributed, zero-infrastructure execution with automatic scaling. For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
+Executes commands as [Vercel](https://vercel.com) serverless functions. Provides globally distributed, zero-infrastructure execution with automatic scaling.
+
+> **Info:** For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
 
 > **Warning:** VercelServerlessSandbox is stateless. It doesn't provide a persistent filesystem, interactive shell, or long-running background processes. Only `/tmp` is writable, and it's ephemeral between invocations.
 

package/CHANGELOG.md

@@ -1,34 +1,5 @@
 # @mastra/mcp-docs-server
 
-## 1.2.7-alpha.11
-
-### Patch Changes
-
-- Updated dependencies [[`fb8aea3`](https://github.com/mastra-ai/mastra/commit/fb8aea384291e77311be3a64ee1717320d5c3c73), [`4ce0163`](https://github.com/mastra-ai/mastra/commit/4ce0163dc86e675a86809685c8ce6c49f1aeb87e)]:
-  - @mastra/core@1.51.0-alpha.5
-
-## 1.2.7-alpha.9
-
-### Patch Changes
-
-- Updated dependencies [[`a5c6337`](https://github.com/mastra-ai/mastra/commit/a5c6337d23c7686c81a32ce62f550f610543a240), [`eb70da9`](https://github.com/mastra-ai/mastra/commit/eb70da98e1007b18e1463d75121bc07db55f8e09), [`8b97958`](https://github.com/mastra-ai/mastra/commit/8b979589f9aa59ba67cac565949475f2ffeb4ac3), [`8410541`](https://github.com/mastra-ai/mastra/commit/84105412c60ecd3bb33a9838146f59c4b588228f), [`01b338c`](https://github.com/mastra-ai/mastra/commit/01b338c56271f0219606710e3e8b26dee27ac6c2), [`8b7361d`](https://github.com/mastra-ai/mastra/commit/8b7361d35de68b80d05d30a74e0c69e7218fd612), [`85fb642`](https://github.com/mastra-ai/mastra/commit/85fb642f4d112d0da9f39808617397f7e47fe622), [`481c112`](https://github.com/mastra-ai/mastra/commit/481c1125b752489673ec671fcb7ca80f9c86ffb1), [`c43f3a9`](https://github.com/mastra-ai/mastra/commit/c43f3a9d1efde99b38789364ba4d0ba670f430e3), [`c43f3a9`](https://github.com/mastra-ai/mastra/commit/c43f3a9d1efde99b38789364ba4d0ba670f430e3)]:
-  - @mastra/core@1.51.0-alpha.4
-  - @mastra/mcp@1.14.0-alpha.0
-
-## 1.2.7-alpha.7
-
-### Patch Changes
-
-- Updated dependencies [[`177010f`](https://github.com/mastra-ai/mastra/commit/177010ff096d2e4b28d89803be5b1a4cad2a0d6b), [`54a51e0`](https://github.com/mastra-ai/mastra/commit/54a51e0a484fe1ebad3fb1f7ef5282a075709eb7)]:
-  - @mastra/core@1.51.0-alpha.3
-
-## 1.2.7-alpha.5
-
-### Patch Changes
-
-- Updated dependencies [[`e955965`](https://github.com/mastra-ai/mastra/commit/e955965dce575a903e37cf054d28ea99aa48785e), [`860ef7e`](https://github.com/mastra-ai/mastra/commit/860ef7e77d92b63469cbe5857aa1e626197e43e9), [`17e818c`](https://github.com/mastra-ai/mastra/commit/17e818c51a958ba90641b1a959dc38faf8c034e9), [`4451dfe`](https://github.com/mastra-ai/mastra/commit/4451dfe857428e7abcc0261a507a2e186dae6d47), [`1d39058`](https://github.com/mastra-ai/mastra/commit/1d39058e548efd691799985d5c8af2737f1c3bd2)]:
-  - @mastra/core@1.51.0-alpha.2
-
 ## 1.2.7-alpha.2
 
 ### Patch Changes