@mastra/mcp-docs-server 1.2.15-alpha.9 → 1.2.16-alpha.1

package/.docs/docs/server/auth/fga.md

@@ -300,4 +300,4 @@ The actor signal is trusted input, so construct it server-side:
 
 - [`IFGAProvider` reference](https://mastra.ai/reference/auth/fga)
 - [Authentication overview](https://mastra.ai/docs/server/auth)
-- [WorkOS authentication](https://mastra.ai/docs/server/auth/workos)
+- [WorkOS authentication](https://mastra.ai/integrations/auth/workos)

package/.docs/docs/server/auth/simple-auth.md

@@ -171,4 +171,4 @@ SimpleAuth is designed for simplicity, not production security:
 - No cryptographic verification
 - All tokens must be known at startup
 
-For production applications, consider using [JWT](https://mastra.ai/docs/server/auth/jwt), [Clerk](https://mastra.ai/docs/server/auth/clerk), [Auth0](https://mastra.ai/docs/server/auth/auth0), or another identity provider.
+For production applications, consider using [JWT](https://mastra.ai/docs/server/auth/jwt), [Clerk](https://mastra.ai/integrations/auth/clerk), [Auth0](https://mastra.ai/integrations/auth/auth0), or another identity provider.

package/.docs/docs/server/auth/workers.md

@@ -2,6 +2,8 @@
 
 # Workers
 
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
 When workers run in separate processes from the API, they communicate over HTTP. The orchestration worker calls the API's step execution endpoint to run workflow steps on the API server. Push-mode PubSub brokers (like Google Cloud Pub/Sub in push mode) can also deliver events directly to the API's event endpoint. This is a distinct integration path from pull-mode workers, which pull events from the broker themselves. Both HTTP endpoints require authentication when an auth provider is configured.
 
 ## How it works
@@ -130,6 +132,6 @@ Your auth provider's `authenticateToken` callback must recognize whatever creden
 
 - [Auth overview](https://mastra.ai/docs/server/auth): Available auth providers and how they work
 - [Token-based auth](https://mastra.ai/docs/server/auth/simple-auth): Token-to-user mapping authentication
-- [Worker deployment](https://mastra.ai/guides/deployment/mastra-workers): Set up split worker processes
+- [Worker deployment](https://mastra.ai/docs/deployment/workers): Set up split worker processes
 - [Workers reference](https://mastra.ai/reference/workers/overview): Configuration details for all worker types
 - [CLI reference](https://mastra.ai/reference/cli/mastra): `mastra worker build` and `mastra worker start`

package/.docs/docs/server/auth.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Auth overview
+# Auth
 
 Mastra lets you choose how you handle authentication, so you can secure access to your API and [Studio](https://mastra.ai/docs/studio/overview) using the identity system that fits your stack.
 
@@ -17,27 +17,29 @@ Authentication is optional. If no auth is configured, all routes and Studio are
 
 See [Custom API Routes](https://mastra.ai/docs/server/custom-api-routes) for controlling authentication on custom endpoints. Visit the [Studio Auth docs](https://mastra.ai/docs/studio/auth) for more on securing your Studio deployment.
 
+> **Warning:** The default auth configuration protects `/api/*` and treats `/api`, `/api/auth/*` as public. When you set a custom `server.apiPrefix`, those defaults no longer match and built-in routes fall outside the protected pattern. Update `server.auth.protected` and `server.auth.public` to reference your new prefix.
+
 > **Note:** Authentication for Studio is currently supported by the following providers: Simple Auth, JWT, WorkOS, Better Auth, and Google.
 
 ## Available providers
 
 ### Built-in
 
-- [Simple Auth](https://mastra.ai/docs/server/auth/simple-auth): Token-to-user mapping for development and API keys
-- [JSON Web Token (JWT)](https://mastra.ai/docs/server/auth/jwt): HMAC-signed JWT verification
+- [Simple Auth](https://mastra.ai/docs/server/auth/simple-auth)
+- [JSON Web Token](https://mastra.ai/docs/server/auth/jwt)
 
 ### Third-party integrations
 
-- [Auth0](https://mastra.ai/docs/server/auth/auth0)
-- [Better Auth](https://mastra.ai/docs/server/auth/better-auth)
-- [Clerk](https://mastra.ai/docs/server/auth/clerk)
-- [Firebase](https://mastra.ai/docs/server/auth/firebase)
-- [Google](https://mastra.ai/docs/server/auth/google)
-- [Okta](https://mastra.ai/docs/server/auth/okta)
-- [Supabase](https://mastra.ai/docs/server/auth/supabase)
-- [WorkOS](https://mastra.ai/docs/server/auth/workos)
+- [Auth0](https://mastra.ai/integrations/auth/auth0)
+- [Better Auth](https://mastra.ai/integrations/auth/better-auth)
+- [Clerk](https://mastra.ai/integrations/auth/clerk)
+- [Firebase](https://mastra.ai/integrations/auth/firebase)
+- [Google](https://mastra.ai/integrations/auth/google)
+- [Okta](https://mastra.ai/integrations/auth/okta)
+- [Supabase](https://mastra.ai/integrations/auth/supabase)
+- [WorkOS](https://mastra.ai/integrations/auth/workos)
 
 ### Advanced
 
-- [Composite Auth](https://mastra.ai/docs/server/auth/composite-auth): Combine multiple auth providers
-- [Custom Auth Provider](https://mastra.ai/docs/server/auth/custom-auth-provider): Build your own provider
+- [Composite Auth](https://mastra.ai/docs/server/auth/composite-auth)
+- [Custom Provider](https://mastra.ai/docs/server/auth/custom-auth-provider)

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

@@ -6,7 +6,7 @@ Create a custom adapter when the prebuilt server adapters (Hono, Express, Fastif
 
 A custom adapter translates between Mastra's route definitions and your framework's routing system. You'll implement methods that register middleware, handle requests, and send responses using your framework's APIs.
 
-> **Info:** Use any of these prebuilt server adapters:
+> **Note:** Use any of these prebuilt server adapters:
 >
 > - [@mastra/hono](https://mastra.ai/reference/server/hono-adapter)
 > - [@mastra/express](https://mastra.ai/reference/server/express-adapter)

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

@@ -35,6 +35,41 @@ curl http://localhost:4111/my-custom-route
 
 Each route's handler receives the Hono `Context`. Within the handler you can access the `Mastra` instance to fetch or call agents and workflows.
 
+## Schema validation
+
+Use [`createRoute()`](https://mastra.ai/reference/server/create-route) in `apiRoutes` to parse and validate path parameters, query parameters, and request bodies with Zod. The schemas also infer the handler parameters and generate OpenAPI metadata.
+
+```typescript
+import { Mastra } from '@mastra/core'
+import { createRoute } from '@mastra/server/server-adapter'
+import { z } from 'zod'
+
+const createItemRoute = createRoute({
+  method: 'POST',
+  path: '/items',
+  responseType: 'json',
+  bodySchema: z.object({
+    name: z.string().min(1),
+  }),
+  responseSchema: z.object({
+    id: z.string(),
+    name: z.string(),
+  }),
+  handler: async ({ name }) => ({
+    id: crypto.randomUUID(),
+    name,
+  }),
+})
+
+export const mastra = new Mastra({
+  server: {
+    apiRoutes: [createItemRoute],
+  },
+})
+```
+
+By default, Mastra returns a `400` response when validation fails. The `onValidationError` callback can override the status and response body. Validated values and the `Mastra` server context are passed directly to the handler.
+
 ## Middleware
 
 To add route-specific middleware pass a `middleware` array when calling `registerApiRoute()`.

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

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Mastra client SDK
+# Mastra client
 
 The Mastra Client SDK provides a concise and type-safe interface for interacting with your [Mastra Server](https://mastra.ai/docs/server/mastra-server) from your client environment.
 
@@ -149,7 +149,7 @@ const testAgent = async () => {
 }
 ```
 
-> **Info:** You can also call `.generate()` with an array of message objects that include `role` and `content`. Visit the [.generate() reference](https://mastra.ai/reference/client-js/agents) for more information.
+> **Note:** You can also call `.generate()` with an array of message objects that include `role` and `content`. Visit the [.generate() reference](https://mastra.ai/reference/client-js/agents) for more information.
 
 ## Streaming responses
 
@@ -175,7 +175,7 @@ const testAgent = async () => {
 }
 ```
 
-> **Info:** You can also call `.stream()` with an array of message objects that include `role` and `content`. Visit the [.stream() reference](https://mastra.ai/reference/client-js/agents) for more information.
+> **Note:** You can also call `.stream()` with an array of message objects that include `role` and `content`. Visit the [.stream() reference](https://mastra.ai/reference/client-js/agents) for more information.
 
 ## Configuration options
 

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

@@ -1,10 +1,10 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Server overview
+# Server
 
 Mastra runs as an HTTP server that exposes your agents, workflows, and other functionality as API endpoints. The server handles request routing, middleware execution, authentication, and streaming responses.
 
-> **Info:** This page covers the [`server`](https://mastra.ai/reference/configuration) configuration options passed to the `Mastra` constructor. For running Mastra with your own HTTP server (Hono, Express, etc.), visit [Server Adapters](https://mastra.ai/docs/server/server-adapters).
+> **Note:** This page covers the [`server`](https://mastra.ai/reference/configuration) configuration options passed to the `Mastra` constructor. For running Mastra with your own HTTP server (Hono, Express, etc.), visit [Server Adapters](https://mastra.ai/docs/server/server-adapters).
 
 ## Server features
 

package/.docs/docs/storage/overview.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Storage overview
+# Storage
 
 Storage is the persistence layer for the Mastra runtime. It keeps memory, workflow state, observability data, eval results, schedules, and long-running agent state available after a process restarts.
 
@@ -188,22 +188,25 @@ You can also route `observability` to a dedicated analytics backend. See the [ob
 
 ## Supported providers
 
-Each provider page includes installation instructions, configuration parameters, and usage examples:
-
-- [libSQL](https://mastra.ai/reference/storage/libsql)
-- [PostgreSQL](https://mastra.ai/reference/storage/postgresql)
-- [MongoDB](https://mastra.ai/reference/storage/mongodb)
-- [Upstash](https://mastra.ai/reference/storage/upstash)
-- [Redis](https://mastra.ai/reference/storage/redis)
-- [Cloudflare D1](https://mastra.ai/reference/storage/cloudflare-d1)
-- [Cloudflare KV & Durable Objects](https://mastra.ai/reference/storage/cloudflare)
-- [Convex](https://mastra.ai/reference/storage/convex)
-- [DynamoDB](https://mastra.ai/reference/storage/dynamodb)
-- [LanceDB](https://mastra.ai/reference/storage/lance)
-- [Microsoft SQL Server](https://mastra.ai/reference/storage/mssql)
-- [Google Cloud Spanner](https://mastra.ai/reference/storage/spanner)
-
-> **Tip:** libSQL is the fastest path for local development because it doesn't require running a separate database server.
+Each provider page includes installation instructions, configuration parameters, and usage examples. libSQL is the fastest path for local development because it doesn't require running a separate database server.
+
+- [Aurora DSQL](https://mastra.ai/integrations/databases/aurora-dsql)
+- [ClickHouse](https://mastra.ai/integrations/databases/clickhouse)
+- [Cloudflare D1](https://mastra.ai/integrations/databases/cloudflare-d1)
+- [Cloudflare KV](https://mastra.ai/integrations/databases/cloudflare-kv)
+- [Convex](https://mastra.ai/integrations/databases/convex)
+- [DuckDB](https://mastra.ai/integrations/databases/duckdb)
+- [DynamoDB](https://mastra.ai/integrations/databases/dynamodb)
+- [Google Cloud Spanner](https://mastra.ai/integrations/databases/spanner)
+- [LanceDB](https://mastra.ai/integrations/databases/lancedb)
+- [libSQL](https://mastra.ai/integrations/databases/libsql)
+- [MongoDB](https://mastra.ai/integrations/databases/mongodb)
+- [MSSQL](https://mastra.ai/integrations/databases/mssql)
+- [Neon Postgres](https://mastra.ai/integrations/databases/neon)
+- [OracleDB](https://mastra.ai/integrations/databases/oracledb)
+- [PostgreSQL](https://mastra.ai/integrations/databases/postgresql)
+- [Redis](https://mastra.ai/integrations/databases/redis)
+- [Upstash](https://mastra.ai/integrations/databases/upstash)
 
 ## Next steps
 

package/.docs/docs/studio/observability.md

@@ -12,7 +12,7 @@ All require an observability storage backend to be configured.
 
 ## Quickstart
 
-For detailed instructions, follow the [observability instructions](https://mastra.ai/docs/observability/overview). To get up and running quickly, add the `@mastra/observability` package to your project and configure it with [LibSQL](https://mastra.ai/reference/storage/libsql) and [DuckDB](https://mastra.ai/reference/vectors/duckdb) for a local development setup that supports both traces and metrics.
+For detailed instructions, follow the [observability instructions](https://mastra.ai/docs/observability/overview). To get up and running quickly, add the `@mastra/observability` package to your project and configure it with [LibSQL](https://mastra.ai/integrations/databases/libsql) and [DuckDB](https://mastra.ai/reference/vectors/duckdb) for a local development setup that supports both traces and metrics.
 
 **npm**:
 

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

@@ -2,7 +2,7 @@
 
 # Dynamic workflows
 
-> **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.
 
 Dynamic workflows are workflow definitions expressed as data instead of code. A definition is a JSON document that describes the workflow's schemas and step graph. Mastra validates the definition and registers it as a runnable workflow, then persists it in storage so it survives process restarts.
 

package/.docs/docs/workflows/human-in-the-loop.md

@@ -1,12 +1,12 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Human-in-the-loop (HITL)
+# Human-in-the-loop
 
 Some workflows need to pause for human input before continuing. When a workflow is [suspended](https://mastra.ai/docs/workflows/suspend-and-resume), it can return a message explaining why it paused and what’s needed to proceed. The workflow can then either [resume](#resuming-workflows-with-human-input) or [bail](#handling-human-rejection-with-bail) based on the input received. This approach works well for manual approvals, rejections, gated decisions, or any step that requires human oversight.
 
 ## Pausing workflows for human input
 
-Human-in-the-loop input works much like [pausing a workflow](https://mastra.ai/docs/workflows/suspend-and-resume) using `suspend()`. The key difference is that when human input is required, you can return `suspend()` with a payload that provides context or guidance to the user on how to continue.
+Human-in-the-loop (HITL) input works much like [pausing a workflow](https://mastra.ai/docs/workflows/suspend-and-resume) using `suspend()`. The key difference is that when human input is required, you can return `suspend()` with a payload that provides context or guidance to the user on how to continue.
 
 ![Pausing a workflow with suspend()](/assets/images/workflows-suspend-4540783670f918109ac35beaf4db914b.jpg)
 

package/.docs/docs/workflows/overview.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Workflows overview
+# Workflows
 
 Workflows let you define complex sequences of tasks using clear, structured steps rather than relying on the reasoning of a single agent. They give you full control over how tasks are broken down and how data moves between them, plus what gets executed when. Workflows run using the built-in execution engine by default, or can be deployed to [workflow runners](https://mastra.ai/docs/deployment/workflow-runners) like Inngest for managed infrastructure.
 
@@ -287,7 +287,7 @@ You can run workflows from agents, tools, the Mastra Client, or the command line
 const testWorkflow = mastra.getWorkflow('testWorkflow')
 ```
 
-> **Info:** `mastra.getWorkflow()` is preferred over a direct import for two reasons:
+> **Note:** `mastra.getWorkflow()` is preferred over a direct import for two reasons:
 >
 > 1. It provides access to the Mastra instance configuration (logger, telemetry, storage, registered agents, and vector stores)
 > 2. It provides full TypeScript type inference for workflow input and output schemas
@@ -407,7 +407,7 @@ Here's an example of a successful workflow result, showing the `input`, `steps`,
 
 ## Streaming
 
-For generic `writer` API usage, see [Streaming](https://mastra.ai/guides/concepts/streaming).
+For generic `writer` API usage, see [Streaming](https://mastra.ai/docs/guides/streaming).
 
 ### Inspecting workflow stream payloads
 
@@ -539,7 +539,7 @@ Visit [Request Context](https://mastra.ai/docs/server/request-context) for more
 
 ## Related
 
-For a closer look at workflows, see our [Workflow Guide](https://mastra.ai/guides/guide/ai-recruiter), which walks through the core concepts with a practical example.
+For a closer look at workflows, see our [Workflow Guide](https://mastra.ai/blog/building-an-ai-recruiter), which walks through the core concepts with a practical example.
 
 - [Workflow State](https://mastra.ai/docs/workflows/workflow-state)
 - [Control Flow](https://mastra.ai/docs/workflows/control-flow)

package/.docs/docs/workflows/snapshots.md

@@ -81,13 +81,14 @@ Each snapshot includes the `runId`, input, step status (`success`, `suspended`,
 
 ## How snapshots are saved and retrieved
 
-Snapshots are saved to the configured storage system. By default, they use libSQL, but you can configure Upstash or PostgreSQL instead. Each snapshot is saved in the `workflow_snapshots` table and identified by the workflow's `runId`.
+Snapshots are saved to the configured storage system. By default, they use libSQL, but you can configure Upstash, PostgreSQL, or OracleDB instead. Each snapshot is saved in the `workflow_snapshots` table and identified by the workflow's `runId`.
 
 Read more about:
 
-- [libSQL Storage](https://mastra.ai/reference/storage/libsql)
-- [Upstash Storage](https://mastra.ai/reference/storage/upstash)
-- [PostgreSQL Storage](https://mastra.ai/reference/storage/postgresql)
+- [libSQL Storage](https://mastra.ai/integrations/databases/libsql)
+- [Upstash Storage](https://mastra.ai/integrations/databases/upstash)
+- [PostgreSQL Storage](https://mastra.ai/integrations/databases/postgresql)
+- [OracleDB Storage](https://mastra.ai/integrations/databases/oracledb)
 
 ### Saving snapshots
 
@@ -139,12 +140,13 @@ export const mastra = new Mastra({
 })
 ```
 
-- [libSQL Storage](https://mastra.ai/reference/storage/libsql)
-- [PostgreSQL Storage](https://mastra.ai/reference/storage/postgresql)
-- [MongoDB Storage](https://mastra.ai/reference/storage/mongodb)
-- [Upstash Storage](https://mastra.ai/reference/storage/upstash)
-- [Cloudflare D1](https://mastra.ai/reference/storage/cloudflare-d1)
-- [DynamoDB](https://mastra.ai/reference/storage/dynamodb)
+- [libSQL Storage](https://mastra.ai/integrations/databases/libsql)
+- [PostgreSQL Storage](https://mastra.ai/integrations/databases/postgresql)
+- [OracleDB Storage](https://mastra.ai/integrations/databases/oracledb)
+- [MongoDB Storage](https://mastra.ai/integrations/databases/mongodb)
+- [Upstash Storage](https://mastra.ai/integrations/databases/upstash)
+- [Cloudflare D1](https://mastra.ai/integrations/databases/cloudflare-d1)
+- [DynamoDB](https://mastra.ai/integrations/databases/dynamodb)
 - [More storage providers](https://mastra.ai/docs/storage/overview)
 
 ## Best practices

package/.docs/docs/workflows/time-travel.md

@@ -15,6 +15,8 @@ When you call `timeTravel()` on a workflow run:
 3. Execution begins from the specified step with the provided or reconstructed input data
 4. The workflow continues to completion from that point forward
 
+If the workflow definition has changed since the run was recorded (for example, a step was renamed), or the recorded run never reached a step that precedes the target, time travel fails with a descriptive error before anything executes, and the stored snapshot is left unchanged.
+
 Time travel requires storage to be configured since it relies on persisted workflow snapshots.
 
 ## Basic usage

package/.docs/docs/workspace/filesystem.md

@@ -21,15 +21,15 @@ A filesystem provider handles all file operations for a workspace:
 Available providers:
 
 - [`LocalFilesystem`](https://mastra.ai/reference/workspace/local-filesystem): Stores files in a directory on disk
-- [`S3Filesystem`](https://mastra.ai/reference/workspace/s3-filesystem): Stores files in Amazon S3 or S3-compatible storage (R2, MinIO, Tigris)
-- [`GCSFilesystem`](https://mastra.ai/reference/workspace/gcs-filesystem): Stores files in Google Cloud Storage
+- [`S3Filesystem`](https://mastra.ai/integrations/file-storage/amazon-s3): Stores files in Amazon S3 or S3-compatible storage (R2, MinIO, Tigris)
+- [`GCSFilesystem`](https://mastra.ai/integrations/file-storage/google-cloud-storage): Stores files in Google Cloud Storage
 - [`PlatformFilesystem`](https://mastra.ai/reference/workspace/platform-filesystem): Stores files in a Mastra Platform workspace bucket
-- [`GoogleDriveFilesystem`](https://mastra.ai/reference/workspace/google-drive-filesystem): Stores files inside a Google Drive folder
-- [`AzureBlobFilesystem`](https://mastra.ai/reference/workspace/azure-blob-filesystem): Stores files in Azure Blob Storage
-- [`FilesSDKFilesystem`](https://mastra.ai/reference/workspace/files-sdk-filesystem): Stores files in any [FilesSDK](https://files-sdk.dev) adapter (S3, R2, GCS, Azure Blob, Vercel Blob, local filesystem, and more): useful when you want one provider that can target multiple backends
-- [`AgentFSFilesystem`](https://mastra.ai/reference/workspace/agentfs-filesystem): Stores files in a Turso/SQLite database via AgentFS
-- [`MesaFilesystem`](https://mastra.ai/reference/workspace/mesa-filesystem): Stores files in versioned Mesa repos
-- [`ArchilFilesystem`](https://mastra.ai/reference/workspace/archil-filesystem): Stores files on Archil elastic, serverless disks
+- [`GoogleDriveFilesystem`](https://mastra.ai/integrations/file-storage/google-drive): Stores files inside a Google Drive folder
+- [`AzureBlobFilesystem`](https://mastra.ai/integrations/file-storage/azure-blob): Stores files in Azure Blob Storage
+- [`FilesSDKFilesystem`](https://mastra.ai/integrations/file-storage/vercel-files): Stores files in any [FilesSDK](https://files-sdk.dev) adapter (S3, R2, GCS, Azure Blob, Vercel Blob, local filesystem, and more): useful when you want one provider that can target multiple backends
+- [`AgentFSFilesystem`](https://mastra.ai/integrations/file-storage/agentfs): Stores files in a Turso/SQLite database via AgentFS
+- [`MesaFilesystem`](https://mastra.ai/integrations/file-storage/mesa): Stores files in versioned Mesa repos
+- [`ArchilFilesystem`](https://mastra.ai/integrations/file-storage/archil): Stores files on Archil elastic, serverless disks
 
 > **Tip:** `LocalFilesystem` is the simplest way to get started as it requires no external services. For cloud storage, use `S3Filesystem`, `GCSFilesystem`, or `AzureBlobFilesystem`. For versioned storage, use `MesaFilesystem`. For database-backed storage without external services, use `AgentFSFilesystem`.
 
@@ -227,12 +227,12 @@ When you configure a filesystem on a workspace, agents receive tools for reading
 ## Related
 
 - [LocalFilesystem reference](https://mastra.ai/reference/workspace/local-filesystem)
-- [S3Filesystem reference](https://mastra.ai/reference/workspace/s3-filesystem)
-- [GCSFilesystem reference](https://mastra.ai/reference/workspace/gcs-filesystem)
-- [GoogleDriveFilesystem reference](https://mastra.ai/reference/workspace/google-drive-filesystem)
-- [AzureBlobFilesystem reference](https://mastra.ai/reference/workspace/azure-blob-filesystem)
-- [FilesSDKFilesystem reference](https://mastra.ai/reference/workspace/files-sdk-filesystem)
-- [AgentFSFilesystem reference](https://mastra.ai/reference/workspace/agentfs-filesystem)
-- [MesaFilesystem reference](https://mastra.ai/reference/workspace/mesa-filesystem)
+- [S3Filesystem reference](https://mastra.ai/integrations/file-storage/amazon-s3)
+- [GCSFilesystem reference](https://mastra.ai/integrations/file-storage/google-cloud-storage)
+- [GoogleDriveFilesystem reference](https://mastra.ai/integrations/file-storage/google-drive)
+- [AzureBlobFilesystem reference](https://mastra.ai/integrations/file-storage/azure-blob)
+- [FilesSDKFilesystem reference](https://mastra.ai/integrations/file-storage/vercel-files)
+- [AgentFSFilesystem reference](https://mastra.ai/integrations/file-storage/agentfs)
+- [MesaFilesystem reference](https://mastra.ai/integrations/file-storage/mesa)
 - [Workspace overview](https://mastra.ai/docs/workspace/overview)
 - [Sandbox](https://mastra.ai/docs/workspace/sandbox)

package/.docs/docs/workspace/sandbox.md

@@ -19,18 +19,17 @@ A sandbox provider executes commands in a controlled environment:
 
 ## Supported providers
 
-- [`LocalSandbox`](https://mastra.ai/reference/workspace/local-sandbox): Executes commands on the local machine
-- [`AgentCoreRuntimeSandbox`](https://mastra.ai/reference/workspace/agentcore-runtime-sandbox): Executes commands in AWS Bedrock AgentCore Runtime sessions
-- [`AppleContainerSandbox`](https://mastra.ai/reference/workspace/apple-container-sandbox): Executes commands in local OCI Linux containers using Apple's `container` CLI
-- [`BlaxelSandbox`](https://mastra.ai/reference/workspace/blaxel-sandbox): Executes commands in isolated Blaxel cloud sandboxes
-- [`DaytonaSandbox`](https://mastra.ai/reference/workspace/daytona-sandbox): Executes commands in isolated Daytona cloud sandboxes
-- [`DockerSandbox`](https://mastra.ai/reference/workspace/docker-sandbox): Executes commands in long-lived Docker containers on the local machine
-- [`E2BSandbox`](https://mastra.ai/reference/workspace/e2b-sandbox): Executes commands in isolated E2B cloud sandboxes
-- [`ModalSandbox`](https://mastra.ai/reference/workspace/modal-sandbox): Executes commands in isolated Modal cloud sandboxes
-- [`PlatformSandbox`](https://mastra.ai/reference/workspace/platform-sandbox): Executes commands in a sandbox tied to a Mastra Platform environment
-- [`RailwaySandbox`](https://mastra.ai/reference/workspace/railway-sandbox): Executes commands in ephemeral, isolated Railway cloud sandboxes
-- [`VercelSandbox`](https://mastra.ai/reference/workspace/vercel-sandbox): Executes commands in an ephemeral Vercel Sandbox Firecracker MicroVM
-- [`VercelServerlessSandbox`](https://mastra.ai/reference/workspace/vercel-serverless): Executes commands as stateless Vercel serverless functions
+- [AgentCore](https://mastra.ai/integrations/sandboxes/agentcore)
+- [Apple Container](https://mastra.ai/integrations/sandboxes/apple-container)
+- [Blaxel](https://mastra.ai/integrations/sandboxes/blaxel)
+- [Daytona](https://mastra.ai/integrations/sandboxes/daytona)
+- [Docker](https://mastra.ai/integrations/sandboxes/docker)
+- [E2B](https://mastra.ai/integrations/sandboxes/e2b)
+- [LocalSandbox](https://mastra.ai/reference/workspace/local-sandbox)
+- [Mastra](https://mastra.ai/reference/workspace/platform-sandbox)
+- [Modal](https://mastra.ai/integrations/sandboxes/modal)
+- [Railway](https://mastra.ai/integrations/sandboxes/railway)
+- [Vercel](https://mastra.ai/integrations/sandboxes/vercel)
 
 ## Basic usage
 
@@ -234,13 +233,13 @@ Use `null` or `false` for cloud sandboxes (for example, E2B, Daytona, or Modal)
 ## Related
 
 - [`SandboxProcessManager` reference](https://mastra.ai/reference/workspace/process-manager)
-- [`AgentCoreRuntimeSandbox` reference](https://mastra.ai/reference/workspace/agentcore-runtime-sandbox)
-- [`AppleContainerSandbox` reference](https://mastra.ai/reference/workspace/apple-container-sandbox)
-- [`DaytonaSandbox` reference](https://mastra.ai/reference/workspace/daytona-sandbox)
-- [`E2BSandbox` reference](https://mastra.ai/reference/workspace/e2b-sandbox)
+- [`AgentCoreRuntimeSandbox` reference](https://mastra.ai/integrations/sandboxes/agentcore)
+- [`AppleContainerSandbox` reference](https://mastra.ai/integrations/sandboxes/apple-container)
+- [`DaytonaSandbox` reference](https://mastra.ai/integrations/sandboxes/daytona)
+- [`E2BSandbox` reference](https://mastra.ai/integrations/sandboxes/e2b)
 - [`LocalSandbox` reference](https://mastra.ai/reference/workspace/local-sandbox)
-- [`ModalSandbox` reference](https://mastra.ai/reference/workspace/modal-sandbox)
-- [`VercelSandbox` reference](https://mastra.ai/reference/workspace/vercel-sandbox)
-- [`VercelServerlessSandbox` reference](https://mastra.ai/reference/workspace/vercel-serverless)
+- [`ModalSandbox` reference](https://mastra.ai/integrations/sandboxes/modal)
+- [`VercelSandbox` reference](https://mastra.ai/integrations/sandboxes/vercel)
+- [`VercelServerlessSandbox` reference](https://mastra.ai/integrations/sandboxes/vercel)
 - [Workspace overview](https://mastra.ai/docs/workspace/overview)
 - [Filesystem](https://mastra.ai/docs/workspace/filesystem)

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

@@ -280,5 +280,5 @@ When you configure search on a workspace, agents receive tools for searching and
 ## Related
 
 - [Workspace overview](https://mastra.ai/docs/workspace/overview)
-- [RAG overview](https://mastra.ai/guides/rag/overview)
+- [RAG overview](https://mastra.ai/reference/rag/overview)
 - [Workspace class reference](https://mastra.ai/reference/workspace/workspace-class)

package/.docs/{guides/build-your-ui → integrations/agentic-ui}/ai-sdk-ui.md

@@ -1,12 +1,12 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Using AI SDK UI
+# AI SDK UI
 
 [AI SDK UI](https://sdk.vercel.ai) is a library of React utilities and components for building AI-powered interfaces. In this guide, you'll learn how to use `@mastra/ai-sdk` to convert Mastra's output to AI SDK-compatible formats, enabling you to use its hooks and components in your frontend.
 
-> **Note:** Migrating from AI SDK v4 to v5? See the [migration guide](https://mastra.ai/guides/migrations/ai-sdk-v4-to-v5).
+> **Note:** Migrating from AI SDK v4 to v5? See the [migration guide](https://mastra.ai/reference/migrations/ai-sdk-v4-to-v5).
 
-> **Tip:** Want to see more examples? Visit Mastra's [**UI Dojo**](https://ui-dojo.mastra.ai/) or the [Next.js quickstart guide](https://mastra.ai/guides/getting-started/next-js).
+> **Tip:** Want to see more examples? Visit Mastra's [**UI Dojo**](https://ui-dojo.mastra.ai/) or the [Next.js quickstart guide](https://mastra.ai/integrations/frameworks/next-js).
 
 ## Getting started
 
@@ -55,7 +55,7 @@ Once you have your API routes set up, you can use them in the [`useChat()`](#use
 
 Run Mastra as a standalone server and connect your frontend (e.g. using Vite + React) to its API endpoints. You'll be using Mastra's [custom API routes](https://mastra.ai/docs/server/custom-api-routes) feature for this.
 
-> **Info:** Mastra's [**UI Dojo**](https://ui-dojo.mastra.ai/) is an example of this setup.
+> **Note:** Mastra's [**UI Dojo**](https://ui-dojo.mastra.ai/) is an example of this setup.
 
 You can use [`chatRoute()`](https://mastra.ai/reference/ai-sdk/chat-route), [`workflowRoute()`](https://mastra.ai/reference/ai-sdk/workflow-route), and [`networkRoute()`](https://mastra.ai/reference/ai-sdk/network-route) to create API routes that stream Mastra content in AI SDK-compatible format. Once implemented, you can use these API routes in [`useChat()`](#usechat).
 
@@ -1023,7 +1023,7 @@ export const mastra = new Mastra({
 })
 ```
 
-> **Info:** You can access this data in your tools via the `requestContext` parameter. See the [Request Context documentation](https://mastra.ai/docs/server/request-context) for more details.
+> **Note:** You can access this data in your tools via the `requestContext` parameter. See the [Request Context documentation](https://mastra.ai/docs/server/request-context) for more details.
 
 **Next.js**:
 
@@ -1383,7 +1383,7 @@ export function NestedAgentChat() {
 Key points:
 
 - Piping `fullStream` to `context.writer` creates `data-tool-agent` parts
-- Read `data-tool-agent-step` when you need the full payload for the nested step that just finished
+- Read `data-tool-agent-step` when you need the full payload for the nested step that finished
 - The `AgentDataPart` has `id` (on the part) and `data.text` (the current nested-agent text snapshot)
 - The tool still returns its own output after the stream completes
 

package/.docs/{guides/build-your-ui → integrations/agentic-ui}/assistant-ui.md

@@ -1,10 +1,10 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Using Assistant UI
+# Assistant UI
 
 [Assistant UI](https://assistant-ui.com) is the TypeScript/React library for AI Chat. Built on shadcn/ui and Tailwind CSS, it enables developers to create beautiful, enterprise-grade chat experiences in minutes.
 
-> **Info:** For a full-stack integration approach where Mastra runs directly in your Next.js API routes, see the [Full-Stack Integration Guide](https://www.assistant-ui.com/docs/integrations/frameworks/mastra/full-stack) on Assistant UI's documentation site.
+> **Note:** For a full-stack integration approach where Mastra runs directly in your Next.js API routes, see the [Full-Stack Integration Guide](https://www.assistant-ui.com/docs/integrations/frameworks/mastra/full-stack) on Assistant UI's documentation site.
 
 Visit Mastra's [**"UI Dojo"**](https://ui-dojo.mastra.ai/) to see real-world examples of Assistant UI integrated with Mastra.