@mastra/mcp-docs-server 1.2.15-alpha.7 → 1.2.15

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

@@ -69,15 +69,15 @@ The Mastra Client SDK exposes all resources served by the Mastra Server.
 - **[Logs](https://mastra.ai/reference/client-js/logs)**: View logs and debug system behavior.
 - **[Telemetry](https://mastra.ai/reference/client-js/telemetry)**: View app performance and trace activity.
 
-## Create and run stored workflows
+## Create and run dynamic workflows
 
-Use `upsertStoredWorkflow()` to create or replace a persisted workflow definition. A successful upsert validates the complete definition, registers it with the running Mastra instance, and makes it available through the standard workflow execution API.
+Use `upsertDynamicWorkflow()` to create or replace a persisted workflow definition. A successful upsert validates the complete definition, registers it with the running Mastra instance, and makes it available through the standard workflow execution API.
 
 The following example shows the full lifecycle of a mapping workflow, from creation and inspection through execution and deletion:
 
 ```typescript
 import { MastraClient } from '@mastra/client-js'
-import type { UpsertStoredWorkflowParams } from '@mastra/client-js'
+import type { UpsertDynamicWorkflowParams } from '@mastra/client-js'
 
 const client = new MastraClient({
   baseUrl: process.env.MASTRA_API_URL || 'http://localhost:4111',
@@ -105,25 +105,25 @@ const definition = {
       }),
     },
   ],
-} satisfies UpsertStoredWorkflowParams
+} satisfies UpsertDynamicWorkflowParams
 
-await client.upsertStoredWorkflow(definition)
+await client.upsertDynamicWorkflow(definition)
 
-const storedWorkflow = client.getStoredWorkflow(definition.id)
-const storedDefinition = await storedWorkflow.details()
+const dynamicWorkflow = client.getDynamicWorkflow(definition.id)
+const dynamicDefinition = await dynamicWorkflow.details()
 
-const workflow = client.getWorkflow(storedDefinition.id)
+const workflow = client.getWorkflow(dynamicDefinition.id)
 const run = await workflow.createRun()
 const result = await run.startAsync({ inputData: { name: 'Ada' } })
 
 console.log(result)
 
-await storedWorkflow.delete()
+await dynamicWorkflow.delete()
 ```
 
-Use `listStoredWorkflows()` to list persisted definitions. Calling `upsertStoredWorkflow()` again with the same `id` replaces the stored definition and live workflow registration.
+Use `listDynamicWorkflows()` to list persisted definitions. Calling `upsertDynamicWorkflow()` again with the same `id` replaces the stored definition and live workflow registration.
 
-> **Warning:** Durable storage requires a configured storage adapter that supports the `workflowDefinitions` domain. Without that domain, Core can register a workflow in memory, but the server's stored-workflow API can't preserve it across restarts.
+> **Warning:** Durable storage requires a configured storage adapter that supports the `workflowDefinitions` domain. Without that domain, Core can register a workflow in memory, but the server's dynamic-workflow API can't preserve it across restarts.
 >
 > Stored definitions support declarative agent, tool, mapping, nested workflow, parallel, foreach, sleep, sleep-until, conditional, and loop entries. They can't contain JavaScript closures. Conditional and loop logic must use the declarative predicate format, and referenced agents, tools, and nested workflows must already be registered.
 >
@@ -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

@@ -4,7 +4,7 @@
 
 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

@@ -190,18 +190,20 @@ You can also route `observability` to a dedicated analytics backend. See the [ob
 
 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)
+- [Cloudflare D1](https://mastra.ai/integrations/databases/cloudflare-d1)
+- [Cloudflare KV & Durable Objects](https://mastra.ai/integrations/databases/cloudflare-kv)
+- [Convex](https://mastra.ai/integrations/databases/convex)
+- [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)
+- [Microsoft SQL Server](https://mastra.ai/integrations/databases/mssql)
+- [MongoDB](https://mastra.ai/integrations/databases/mongodb)
+- [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)
 
 > **Tip:** libSQL is the fastest path for local development because it doesn't require running a separate database server.
 

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/agents-and-tools.md

@@ -123,7 +123,7 @@ export const testWorkflow = createWorkflow({})
   .commit()
 ```
 
-`.agent()` records a declarative entry in the workflow graph rather than an opaque step, so workflows built this way can be persisted as [stored workflows](https://mastra.ai/docs/workflows/stored-workflows). Visit [Workflow.agent()](https://mastra.ai/reference/workflows/workflow-methods/agent) for all parameters.
+`.agent()` records a declarative entry in the workflow graph rather than an opaque step, so workflows built this way can be persisted as [dynamic workflows](https://mastra.ai/docs/workflows/dynamic-workflows). Visit [Workflow.agent()](https://mastra.ai/reference/workflows/workflow-methods/agent) for all parameters.
 
 ## Using tools in workflows
 
@@ -184,7 +184,7 @@ import { testTool } from '../tools/test-tool'
 export const testWorkflow = createWorkflow({}).then(step1).tool(testTool).commit()
 ```
 
-Like `.agent()`, `.tool()` records a declarative entry, so the workflow can be persisted as a [stored workflow](https://mastra.ai/docs/workflows/stored-workflows). Visit [Workflow.tool()](https://mastra.ai/reference/workflows/workflow-methods/tool) for all parameters.
+Like `.agent()`, `.tool()` records a declarative entry, so the workflow can be persisted as a [dynamic workflow](https://mastra.ai/docs/workflows/dynamic-workflows). Visit [Workflow.tool()](https://mastra.ai/reference/workflows/workflow-methods/tool) for all parameters.
 
 ## Related
 

package/.docs/docs/workflows/{stored-workflows.md → dynamic-workflows.md}

@@ -1,22 +1,22 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Stored workflows
+# 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.
 
-Stored 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.
+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.
 
-Because a definition contains no JavaScript closures, anything that can produce JSON can author a workflow: an HTTP client, an LLM, a visual editor, or your own tooling. Once registered, a stored workflow runs through the same execution API as a code-defined workflow.
+Because a definition contains no JavaScript closures, anything that can produce JSON can author a workflow: an HTTP client, an LLM, a visual editor, or your own tooling. Once registered, a dynamic workflow runs through the same execution API as a code-defined workflow.
 
-## When to use stored workflows
+## When to use dynamic workflows
 
-Use stored workflows when users, agents, visual editors, or external systems need to create workflows without changing application code or deploying again.
+Use dynamic workflows when users, agents, visual editors, or external systems need to create workflows without changing application code or deploying again.
 
-Keep defining workflows with [`createWorkflow()`](https://mastra.ai/docs/workflows/overview) when the workflow belongs in your application source or needs custom step functions. Stored workflows can invoke agents, tools, and workflows that are already registered on the `Mastra` instance.
+Keep defining workflows with [`createWorkflow()`](https://mastra.ai/docs/workflows/overview) when the workflow belongs in your application source or needs custom step functions. Dynamic workflows can invoke agents, tools, and workflows that are already registered on the `Mastra` instance.
 
 ## Quickstart
 
-The following example registers a tool and invokes it from a stored workflow. It then runs the workflow. `LibSQLStore` persists the definition in `mastra.db`, so Mastra can restore it after a restart.
+The following example registers a tool and invokes it from a dynamic workflow. It then runs the workflow. `LibSQLStore` persists the definition in `mastra.db`, so Mastra can restore it after a restart.
 
 ```typescript
 import { Mastra } from '@mastra/core/mastra'
@@ -46,7 +46,7 @@ const mastra = new Mastra({
   tools: { 'create-greeting': greetingTool },
 })
 
-await mastra.addStoredWorkflow({
+await mastra.addDynamicWorkflow({
   id: 'greeting-workflow',
   description: 'Create a greeting for the supplied name',
   inputSchema: {
@@ -83,9 +83,9 @@ if (result.status === 'success') {
 }
 ```
 
-The workflow prints `Hello, Ada!`. Calling [`addStoredWorkflow()`](https://mastra.ai/reference/core/addStoredWorkflow) validates the definition before it changes storage or the live workflow registry.
+The workflow prints `Hello, Ada!`. Calling [`addDynamicWorkflow()`](https://mastra.ai/reference/core/addDynamicWorkflow) validates the definition before it changes storage or the live workflow registry.
 
-The definition uses JSON Schema because it must survive a JSON round trip. The `graph` describes which registered components to invoke and how data moves between them. See the [stored workflow definition reference](https://mastra.ai/reference/workflows/stored-workflow-definition) for every field and graph entry.
+The definition uses JSON Schema because it must survive a JSON round trip. The `graph` describes which registered components to invoke and how data moves between them. See the [dynamic workflow definition reference](https://mastra.ai/reference/workflows/dynamic-workflow-definition) for every field and graph entry.
 
 ## Build and update definitions
 
@@ -93,54 +93,54 @@ A definition can come from any source that produces JSON. For example, an API ro
 
 ```typescript
 const definition = await request.json()
-await mastra.addStoredWorkflow(definition)
+await mastra.addDynamicWorkflow(definition)
 ```
 
 ### Register dependencies first
 
-Register referenced components on the same `Mastra` instance before adding the stored workflow. Agent and nested workflow entries use their intrinsic IDs. A tool entry uses its key from the `Mastra` `tools` object, so the quickstart registers the tool under `create-greeting` before referencing that key with `toolId`.
+Register referenced components on the same `Mastra` instance before adding the dynamic workflow. Agent and nested workflow entries use their intrinsic IDs. A tool entry uses its key from the `Mastra` `tools` object, so the quickstart registers the tool under `create-greeting` before referencing that key with `toolId`.
 
-Use a `mapping` entry when one step's output doesn't match the next step's input. Mapping entries can read data from the workflow input and previous step results, along with workflow state and request context. The [definition reference](https://mastra.ai/reference/workflows/stored-workflow-definition) lists the supported mapping descriptors.
+Use a `mapping` entry when one step's output doesn't match the next step's input. Mapping entries can read data from the workflow input and previous step results, along with workflow state and request context. The [definition reference](https://mastra.ai/reference/workflows/dynamic-workflow-definition) lists the supported mapping descriptors.
 
 ### Replace a workflow
 
 Add a new definition with the same `id` to replace the persisted definition and live registration:
 
 ```typescript
-await mastra.addStoredWorkflow(updatedDefinition)
+await mastra.addDynamicWorkflow(updatedDefinition)
 ```
 
 New runs use the updated graph. Runs that already started continue with their original graph.
 
 ### Add nested workflows together
 
-When a root workflow references helper workflows that aren't registered yet, add the full set with [`addStoredWorkflows()`](https://mastra.ai/reference/core/addStoredWorkflows):
+When a root workflow references helper workflows that aren't registered yet, add the full set with [`addDynamicWorkflows()`](https://mastra.ai/reference/core/addDynamicWorkflows):
 
 ```typescript
-await mastra.addStoredWorkflows([rootDefinition, helperDefinition])
+await mastra.addDynamicWorkflows([rootDefinition, helperDefinition])
 ```
 
 Mastra validates the bundle as a unit and determines the registration order from the dependencies. If validation fails, none of the definitions are registered.
 
 ### Manage definitions over HTTP
 
-Applications don't need direct access to the `Mastra` instance to manage stored workflows. Use one of these interfaces:
+Applications don't need direct access to the `Mastra` instance to manage dynamic workflows. Use one of these interfaces:
 
-- [Client SDK workflows API](https://mastra.ai/reference/client-js/workflows): Call `upsertStoredWorkflow()` from a JavaScript or TypeScript client.
+- [Client SDK workflows API](https://mastra.ai/reference/client-js/workflows): Call `upsertDynamicWorkflow()` from a JavaScript or TypeScript client.
 - [Server routes](https://mastra.ai/reference/server/routes): Send definitions to `POST /api/stored/workflows`.
 
-On authenticated servers, stored-workflow management requires the `stored-workflows:read` and `stored-workflows:write` permissions. Running the registered workflow requires `workflows:execute`.
+On authenticated servers, dynamic-workflow management requires the `stored-workflows:read` and `stored-workflows:write` permissions. Running the registered workflow requires `workflows:execute`.
 
 ### Persist definitions
 
 Stored definitions use the `workflowDefinitions` storage domain. On startup, Mastra loads active definitions from storage and registers them in dependency order.
 
-Without a storage adapter that supports this domain, `addStoredWorkflow()` still registers the workflow in memory, but the definition is lost when the process restarts. See the [storage reference](https://mastra.ai/reference/storage/overview) for adapter support.
+Without a storage adapter that supports this domain, `addDynamicWorkflow()` still registers the workflow in memory, but the definition is lost when the process restarts. See the [storage reference](https://mastra.ai/reference/storage/overview) for adapter support.
 
 ## Related
 
-- [Stored workflow definition](https://mastra.ai/reference/workflows/stored-workflow-definition)
-- [`Mastra.addStoredWorkflow()`](https://mastra.ai/reference/core/addStoredWorkflow)
-- [`Mastra.addStoredWorkflows()`](https://mastra.ai/reference/core/addStoredWorkflows)
+- [Dynamic workflow definition](https://mastra.ai/reference/workflows/dynamic-workflow-definition)
+- [`Mastra.addDynamicWorkflow()`](https://mastra.ai/reference/core/addDynamicWorkflow)
+- [`Mastra.addDynamicWorkflows()`](https://mastra.ai/reference/core/addDynamicWorkflows)
 - [Client SDK workflows API](https://mastra.ai/reference/client-js/workflows)
 - [Server routes](https://mastra.ai/reference/server/routes)

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

@@ -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
 

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

@@ -20,17 +20,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
+- [`AgentCoreRuntimeSandbox`](https://mastra.ai/integrations/sandboxes/agentcore): Executes commands in AWS Bedrock AgentCore Runtime sessions
+- [`AppleContainerSandbox`](https://mastra.ai/integrations/sandboxes/apple-container): Executes commands in local OCI Linux containers using Apple's `container` CLI
+- [`BlaxelSandbox`](https://mastra.ai/integrations/sandboxes/blaxel): Executes commands in isolated Blaxel cloud sandboxes
+- [`DaytonaSandbox`](https://mastra.ai/integrations/sandboxes/daytona): Executes commands in isolated Daytona cloud sandboxes
+- [`DockerSandbox`](https://mastra.ai/integrations/sandboxes/docker): Executes commands in long-lived Docker containers on the local machine
+- [`E2BSandbox`](https://mastra.ai/integrations/sandboxes/e2b): Executes commands in isolated E2B cloud sandboxes
+- [`ModalSandbox`](https://mastra.ai/integrations/sandboxes/modal): 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
+- [`RailwaySandbox`](https://mastra.ai/integrations/sandboxes/railway): Executes commands in ephemeral, isolated Railway cloud sandboxes
+- [`VercelSandbox`](https://mastra.ai/integrations/sandboxes/vercel): Executes commands in an ephemeral Vercel Sandbox Firecracker MicroVM
+- [`VercelServerlessSandbox`](https://mastra.ai/integrations/sandboxes/vercel): Executes commands as stateless Vercel serverless functions
 
 ## Basic usage
 
@@ -234,13 +234,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/agent-frameworks/ai-sdk.md

@@ -4,7 +4,7 @@
 
 If you're already using the [Vercel AI SDK](https://sdk.vercel.ai) directly and want to add Mastra capabilities like [processors](https://mastra.ai/docs/agents/processors) or [memory](https://mastra.ai/docs/memory/memory-processors) without switching to the full Mastra agent API, [`withMastra()`](https://mastra.ai/reference/ai-sdk/with-mastra) lets you wrap any AI SDK model with these features. This is useful when you want to keep your existing AI SDK code but add input/output processing, conversation persistence, or content filtering.
 
-> **Tip:** If you want to use Mastra together with AI SDK UI (e.g. `useChat()`), visit the [AI SDK UI guide](https://mastra.ai/guides/build-your-ui/ai-sdk-ui).
+> **Tip:** If you want to use Mastra together with AI SDK UI (e.g. `useChat()`), visit the [AI SDK UI guide](https://mastra.ai/integrations/agentic-ui/ai-sdk-ui).
 
 ## Installation
 
@@ -139,4 +139,4 @@ const { text } = await generateText({
 - [`withMastra()`](https://mastra.ai/reference/ai-sdk/with-mastra): API reference for `withMastra()`
 - [Processors](https://mastra.ai/docs/agents/processors): Learn about input and output processors
 - [Memory](https://mastra.ai/docs/memory/overview): Overview of Mastra's memory system
-- [AI SDK UI](https://mastra.ai/guides/build-your-ui/ai-sdk-ui): Using AI SDK UI hooks with Mastra agents, workflows, and networks
+- [AI SDK UI](https://mastra.ai/integrations/agentic-ui/ai-sdk-ui): Using AI SDK UI hooks with Mastra agents, workflows, and networks

package/.docs/guides/deployment/mastra-workers.md

@@ -4,7 +4,9 @@
 
 Run [Mastra workers](https://mastra.ai/docs/deployment/workers) as separate processes so you can scale orchestration, scheduling, and background tasks independently from the API. This guide walks through a fully split deployment using Docker Compose or Kubernetes.
 
-> **Info:** This guide covers splitting workers into their own containers. If you only need workers to run in-process alongside the API, see [Workers](https://mastra.ai/docs/deployment/workers). No extra setup is required.
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
+> **Note:** This guide covers splitting workers into their own containers. If you only need workers to run in-process alongside the API, see [Workers](https://mastra.ai/docs/deployment/workers). No extra setup is required.
 
 ## Before you begin
 
@@ -573,4 +575,4 @@ Workers recover from crashes because the distributed PubSub backend persists una
 - [CLI reference](https://mastra.ai/reference/cli/mastra): `mastra worker build` and `mastra worker start`
 - [PubSub](https://mastra.ai/docs/server/pubsub): Event delivery backends
 - [Deploy a Mastra server](https://mastra.ai/docs/deployment/mastra-server): Build output and server configuration
-- [Deploy Mastra to Kubernetes](https://mastra.ai/guides/deployment/kubernetes): Multi-pod deployment with durable agents
+- [Deploy Mastra to Kubernetes](https://mastra.ai/integrations/deploy/kubernetes): Multi-pod deployment with durable agents

package/.docs/guides/getting-started/quickstart.md

@@ -2,11 +2,11 @@
 
 # Mastra Quickstart
 
-**For AI agents:** Create a new Mastra project non-interactively with `npm create mastra@latest <project-name> -- --llm <provider>`, replacing `<provider>` with `openai`, `anthropic`, `google`, or `xai`. For a minimal project without an agent or model provider, use `npm create mastra@latest <project-name> -- --empty`. To build a Mastra project from scratch, see the [manual installation guide](https://mastra.ai/guides/getting-started/manual-install).
+**For AI agents:** Create a new Mastra project non-interactively with `npm create mastra@latest <project-name> -- --llm <provider>`, replacing `<provider>` with `openai`, `anthropic`, `google`, or `xai`. For a minimal project without an agent or model provider, use `npm create mastra@latest <project-name> -- --empty`. To build a Mastra project from scratch, see the [manual installation guide](https://mastra.ai/reference/manual-install).
 
 The `create-mastra` CLI is the quickest way to start a Mastra project. It creates an agent harness with workspace tools, memory, task tracking, web access, schedules, storage, and observability.
 
-For more control, see the [manual installation guide](https://mastra.ai/guides/getting-started/manual-install). To add Mastra to an existing project, use [`mastra init`](https://mastra.ai/reference/cli/mastra).
+For more control, see the [manual installation guide](https://mastra.ai/reference/manual-install). To add Mastra to an existing project, use [`mastra init`](https://mastra.ai/reference/cli/mastra).
 
 > **📹 Watch:** Watch the [Mastra AI agent course](https://www.youtube.com/watch?v=lCmf_qrGfGA) for a guided introduction to building agents with Mastra.
 
@@ -82,7 +82,7 @@ Open [Studio at localhost:4111](http://localhost:4111), select the agent, and se
 
 ## Next steps
 
-- Integrate Mastra with [Next.js](https://mastra.ai/guides/getting-started/next-js), [React](https://mastra.ai/guides/getting-started/vite-react), or [Astro](https://mastra.ai/guides/getting-started/astro)
+- Integrate Mastra with [Next.js](https://mastra.ai/integrations/frameworks/next-js), [React](https://mastra.ai/integrations/frameworks/vite-react), or [Astro](https://mastra.ai/integrations/frameworks/astro)
 - Learn how to [build Mastra with AI](https://mastra.ai/reference/build-with-ai)
 - Build an agent from scratch with a [guide](https://mastra.ai/guides)
 - Watch the [Mastra YouTube channel](https://www.youtube.com/@mastra-ai)

package/.docs/guides/guide/signal-provider.md

@@ -6,7 +6,7 @@ In this guide, you'll build a signal provider that polls an external service on
 
 The example watches build pipelines in a fake CI service, but the pattern applies to any pull-based source: an issue tracker, a status API, a queue, or your own backend.
 
-> **Beta:** Signal providers 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.
 
 ## Prerequisites
 

package/.docs/guides/index.md

@@ -14,11 +14,11 @@ The `npm create mastra@latest` command is the fastest way to build your first ag
 
 Add Mastra to an existing project, or scaffold a new Mastra-powered app if you’re starting from scratch.
 
-- [Next.js](https://mastra.ai/guides/getting-started/next-js)
-- [React](https://mastra.ai/guides/getting-started/vite-react)
-- [SvelteKit](https://mastra.ai/guides/getting-started/sveltekit)
-- [Astro](https://mastra.ai/guides/getting-started/astro)
-- [Nuxt](https://mastra.ai/guides/getting-started/nuxt)
-- [Express](https://mastra.ai/guides/getting-started/express)
-- [Hono](https://mastra.ai/guides/getting-started/hono)
-- [Electron](https://mastra.ai/guides/getting-started/electron)
+- [Next.js](https://mastra.ai/integrations/frameworks/next-js)
+- [React](https://mastra.ai/integrations/frameworks/vite-react)
+- [SvelteKit](https://mastra.ai/integrations/frameworks/sveltekit)
+- [Astro](https://mastra.ai/integrations/frameworks/astro)
+- [Nuxt](https://mastra.ai/integrations/frameworks/nuxt)
+- [Express](https://mastra.ai/integrations/frameworks/express)
+- [Hono](https://mastra.ai/integrations/frameworks/hono)
+- [Electron](https://mastra.ai/integrations/frameworks/electron)