@mastra/mcp-docs-server 1.2.15-alpha.20 → 1.2.15-alpha.21

package/.docs/{reference/storage → integrations/databases}/duckdb.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# DuckDB storage
+# DuckDB
 
 [DuckDB](https://duckdb.org/) is an embedded, in-process analytical database. The `@mastra/duckdb` package provides an OLAP-backed observability store for local development, suitable for traces, logs, metrics, scores, and feedback without running an external service.
 
@@ -10,9 +10,9 @@ For vector search, see the [DuckDB vector store reference](https://mastra.ai/ref
 
 Local development of observability features. DuckDB is embedded and file-based, so it doesn't require a server and starts instantly. It supports the same observability signals as ClickHouse, which makes it useful for testing dashboards and trace exploration before deploying to a production backend.
 
-DuckDB currently implements only the `observability` domain. Pair it with another storage adapter (such as [LibSQL](https://mastra.ai/reference/storage/libsql)) for `memory` and `workflows` in a [composite storage](https://mastra.ai/reference/storage/composite) setup.
+DuckDB currently implements only the `observability` domain. Pair it with another storage adapter (such as [LibSQL](https://mastra.ai/integrations/databases/libsql)) for `memory` and `workflows` in a [composite storage](https://mastra.ai/reference/storage/composite) setup.
 
-> **Warning:** DuckDB is for development and not recommended for production. It runs in-process, persists to a single local file, and doesn't work on platforms with ephemeral filesystems (such as Railway, Fly.io, Render, Heroku, or serverless containers). For production observability, use [ClickHouse](https://mastra.ai/reference/storage/clickhouse).
+> **Warning:** DuckDB is for development and not recommended for production. It runs in-process, persists to a single local file, and doesn't work on platforms with ephemeral filesystems (such as Railway, Fly.io, Render, Heroku, or serverless containers). For production observability, use [ClickHouse](https://mastra.ai/integrations/databases/clickhouse).
 
 ## Installation
 
@@ -130,7 +130,7 @@ DuckDB currently implements one storage domain:
 | `scores`        | No        |
 | `agents`        | No        |
 
-For a full storage solution, compose `DuckDBStore` with an adapter that covers the missing domains (most commonly [LibSQL](https://mastra.ai/reference/storage/libsql) for local development).
+For a full storage solution, compose `DuckDBStore` with an adapter that covers the missing domains (most commonly [LibSQL](https://mastra.ai/integrations/databases/libsql) for local development).
 
 ## Initialization
 
@@ -151,6 +151,6 @@ DuckDB supports the `event-sourced` strategy used by `MastraStorageExporter`, wh
 
 - [Storage overview](https://mastra.ai/reference/storage/overview)
 - [Composite storage](https://mastra.ai/reference/storage/composite)
-- [ClickHouse storage](https://mastra.ai/reference/storage/clickhouse): Production observability backend
+- [ClickHouse storage](https://mastra.ai/integrations/databases/clickhouse): Production observability backend
 - [DuckDB vector store](https://mastra.ai/reference/vectors/duckdb): Vector search using the same package
 - [Observability overview](https://mastra.ai/docs/observability/overview)

package/.docs/{reference/storage → integrations/databases}/dynamodb.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# DynamoDB storage
+# DynamoDB
 
 The DynamoDB storage implementation provides a high-capacity and performant NoSQL database solution for Mastra, using a single-table design pattern with [ElectroDB](https://electrodb.dev/).
 

package/.docs/{reference/storage/lance.md → integrations/databases/lancedb.md}

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# LanceDB storage
+# LanceDB
 
 The LanceDB storage implementation provides a high-performance storage solution using the LanceDB database system, which excels at handling both traditional data storage and vector operations.
 

package/.docs/{reference/storage → integrations/databases}/libsql.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# libSQL storage
+# libSQL
 
 [libSQL](https://docs.turso.tech/libsql) is an open-source, SQLite-compatible database that supports both local and remote deployments. It can be used to store message history, workflow snapshots, traces, and eval scores.
 
@@ -140,4 +140,4 @@ const thread = await memoryStore?.getThreadById({ threadId: '...' })
 
 libSQL supports observability and is ideal for local development. Use the `realtime` [tracing strategy](https://mastra.ai/docs/observability/integrations/exporters/mastra-storage) for immediate visibility while debugging.
 
-For production environments with higher trace volumes, consider using [PostgreSQL](https://mastra.ai/reference/storage/postgresql) or [ClickHouse via composite storage](https://mastra.ai/reference/storage/composite).
+For production environments with higher trace volumes, consider using [PostgreSQL](https://mastra.ai/integrations/databases/postgresql) or [ClickHouse via composite storage](https://mastra.ai/reference/storage/composite).

package/.docs/{reference/storage → integrations/databases}/mongodb.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# MongoDB storage
+# MongoDB
 
 The MongoDB storage implementation provides a high-capacity storage solution using MongoDB databases with support for both document storage and vector operations.
 

package/.docs/{reference/storage → integrations/databases}/mssql.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# MSSQL storage
+# MSSQL
 
 The MSSQL storage implementation provides a production-ready storage solution using Microsoft SQL Server databases.
 

package/.docs/integrations/databases/neon.md

@@ -0,0 +1,220 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
+# Neon Postgres
+
+[Neon](https://neon.com) is a managed PostgreSQL service. Mastra connects to Neon through [`PostgresStore`](https://mastra.ai/integrations/databases/postgresql), which uses the Node.js `pg` driver. Neon doesn't require a separate Mastra storage package.
+
+## Quickstart
+
+Create a Neon project, then copy its [pooled connection string](https://neon.com/docs/connect/connect-from-any-app) into `DATABASE_URL`.
+
+Install the PostgreSQL storage package:
+
+**npm**:
+
+```bash
+npm install @mastra/pg@latest
+```
+
+**pnpm**:
+
+```bash
+pnpm add @mastra/pg@latest
+```
+
+**Yarn**:
+
+```bash
+yarn add @mastra/pg@latest
+```
+
+**Bun**:
+
+```bash
+bun add @mastra/pg@latest
+```
+
+Pass the pooled connection string to `PostgresStore`:
+
+```typescript
+import { Mastra } from '@mastra/core/mastra'
+import { PostgresStore } from '@mastra/pg'
+
+export const mastra = new Mastra({
+  storage: new PostgresStore({
+    id: 'neon-storage',
+    connectionString: process.env.DATABASE_URL!,
+  }),
+})
+```
+
+On startup, Mastra calls `storage.init()` and creates its tables and indexes in Neon.
+
+## Set up Neon with the CLI
+
+The Neon CLI requires Node.js 20.19 or newer.
+
+Install the [Neon CLI](https://neon.com/docs/cli/install):
+
+**npm**:
+
+```bash
+npm install -g neon
+```
+
+**pnpm**:
+
+```bash
+pnpm add -g neon
+```
+
+**Yarn**:
+
+```bash
+yarn global add neon
+```
+
+**Bun**:
+
+```bash
+bun add --global neon
+```
+
+From your project directory, link an existing Neon project or create one:
+
+```bash
+neon link
+```
+
+`neon link` signs you in and writes project context to `.neon`. It also pulls the current branch's environment variables. Run `neon env pull` again whenever you need to refresh them:
+
+```bash
+neon env pull
+```
+
+The command writes `DATABASE_URL` and `DATABASE_URL_UNPOOLED` to `.env.local` or to `.env` when that file already exists.
+
+### Add `neon.ts`
+
+To manage branch settings in the repository, create a [`neon.ts`](https://neon.com/docs/reference/neon-ts) file:
+
+```bash
+neon config init
+```
+
+This installs `@neon/config` and `@neon/env` and creates a starter config. For example, the following policy expires new non-default branches after seven days:
+
+```typescript
+import { defineConfig } from '@neon/config/v1'
+
+export default defineConfig({
+  branch: branch => {
+    if (branch.isDefault) {
+      return {}
+    }
+
+    if (!branch.exists) {
+      return { ttl: '7d' }
+    }
+
+    return {}
+  },
+})
+```
+
+Apply the config:
+
+```bash
+neon deploy
+```
+
+## Install Neon agent skills
+
+Install the [`neon` and `neon-postgres` agent skills](https://neon.com/docs/ai/agent-skills) from your project directory:
+
+**npm**:
+
+```bash
+npx skills add neondatabase/agent-skills --skill neon --skill neon-postgres -y
+```
+
+**pnpm**:
+
+```bash
+pnpm dlx skills add neondatabase/agent-skills --skill neon --skill neon-postgres -y
+```
+
+**Yarn**:
+
+```bash
+yarn dlx skills add neondatabase/agent-skills --skill neon --skill neon-postgres -y
+```
+
+**Bun**:
+
+```bash
+bun x skills add neondatabase/agent-skills --skill neon --skill neon-postgres -y
+```
+
+The skills give compatible coding agents Neon setup instructions and Postgres-specific guidance.
+
+## Production connections
+
+Neon provides direct and pooled connection strings:
+
+- `DATABASE_URL` uses Neon's pooled endpoint. Use it for normal application traffic.
+- `DATABASE_URL_UNPOOLED` connects directly to Postgres. Use it for administrative tasks or schema changes that run outside the application.
+
+For most applications, use the pooled `DATABASE_URL` shown in the quickstart and let Mastra initialize the schema at startup. `PostgresStore` supports initialization through a transaction-pooled connection.
+
+### Separate schema initialization
+
+If the runtime database role shouldn't create tables or indexes, initialize the schema during deployment with the direct connection:
+
+```typescript
+import { PostgresStore } from '@mastra/pg'
+
+const storage = new PostgresStore({
+  id: 'neon-storage-init',
+  connectionString: process.env.DATABASE_URL_UNPOOLED!,
+})
+
+try {
+  await storage.init()
+} finally {
+  await storage.close()
+}
+```
+
+After the schema exists, use the pooled connection at runtime and disable automatic initialization:
+
+```typescript
+import { Mastra } from '@mastra/core/mastra'
+import { PostgresStore } from '@mastra/pg'
+
+export const mastra = new Mastra({
+  storage: new PostgresStore({
+    id: 'neon-storage',
+    connectionString: process.env.DATABASE_URL!,
+    disableInit: true,
+  }),
+})
+```
+
+See [Neon connection pooling](https://neon.com/docs/connect/connection-pooling) for details.
+
+## Vector search
+
+Neon supports the [`pgvector` extension](https://neon.com/docs/extensions/pgvector). Use the direct `DATABASE_URL_UNPOOLED` connection while creating the extension and indexes. After setup, configure [`PgVector`](https://mastra.ai/reference/vectors/pg) with the pooled connection for runtime queries:
+
+```typescript
+import { PgVector } from '@mastra/pg'
+
+const vector = new PgVector({
+  id: 'neon-vector',
+  connectionString: process.env.DATABASE_URL!,
+  disableInit: true,
+})
+```
+
+Setting `disableInit: true` prevents the runtime process from creating or changing the extension, tables and indexes.

package/.docs/{reference/storage → integrations/databases}/oracledb.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# OracleDB storage
+# OracleDB
 
 The OracleDB storage provider stores Mastra application state in Oracle Database. It implements Mastra's composite storage interface, so one `OracleStore` instance can back memory, workflow snapshots, observability, scores, scorer definitions, MCP client metadata, and agent registry data.
 

package/.docs/{reference/storage → integrations/databases}/postgresql.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# PostgreSQL storage
+# PostgreSQL
 
 The PostgreSQL storage implementation provides a production-ready storage solution using PostgreSQL databases.
 

package/.docs/{reference/storage → integrations/databases}/redis.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Redis Storage
+# Redis
 
 The Redis storage implementation provides a high-performance storage solution using direct Redis connections via [`node-redis`](https://github.com/redis/node-redis) (the official Redis client for Node.js). It supports standalone Redis, and through custom client configuration, Redis Sentinel and Cluster deployments.
 

package/.docs/{reference/storage → integrations/databases}/spanner.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Google Cloud Spanner storage
+# Google Cloud Spanner
 
 The Google Cloud Spanner storage implementation provides a horizontally high-capacity, strongly consistent storage backend for Mastra. It targets the GoogleSQL dialect of Cloud Spanner.
 

package/.docs/{reference/storage → integrations/databases}/upstash.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Upstash storage
+# Upstash
 
 The Upstash storage implementation provides a serverless-friendly storage solution using Upstash's Redis-compatible key-value store.
 

package/.docs/{guides/deployment → integrations/deploy}/aws-bedrock-agentcore.md

@@ -6,7 +6,7 @@ Deploy your Mastra application to [Amazon Bedrock AgentCore Runtime](https://doc
 
 This guide follows the [official AgentCore TypeScript walkthrough](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-get-started-cli-typescript.html) and adapts it to call a Mastra agent from the invocation handler.
 
-> **Note:** For a Lambda-based deployment of the full Mastra server, see the [AWS Lambda guide](https://mastra.ai/guides/deployment/aws-lambda). For a long-lived virtual machine, see the [Amazon EC2 guide](https://mastra.ai/guides/deployment/amazon-ec2).
+> **Note:** For a Lambda-based deployment of the full Mastra server, see the [AWS Lambda guide](https://mastra.ai/integrations/deploy/aws-lambda). For a long-lived virtual machine, see the [Amazon EC2 guide](https://mastra.ai/integrations/deploy/amazon-ec2).
 
 ## Before you begin
 

package/.docs/{guides/deployment → integrations/deploy}/aws-lambda.md

@@ -15,7 +15,7 @@ You'll need:
 - **[AWS CLI](https://aws.amazon.com/cli/)** installed: Run `aws configure` to authenticate
 - **[Docker](https://www.docker.com/)** installed and running
 
-> **Warning:** On AWS Lambda, the filesystem is ephemeral, so any local database file will be lost between invocations. If you're using [LibSQLStore](https://mastra.ai/reference/storage/libsql) with a local file, configure it to use a remote LibSQL-compatible database (for example, [Turso](https://turso.tech/)) instead.
+> **Warning:** On AWS Lambda, the filesystem is ephemeral, so any local database file will be lost between invocations. If you're using [LibSQLStore](https://mastra.ai/integrations/databases/libsql) with a local file, configure it to use a remote LibSQL-compatible database (for example, [Turso](https://turso.tech/)) instead.
 
 ## Create a Dockerfile
 

package/.docs/{guides/deployment → integrations/deploy}/azure-app-services.md

@@ -14,7 +14,7 @@ You'll need:
 - An [Azure account](https://azure.microsoft.com/) with an active subscription
 - A [GitHub repository](https://github.com/) containing your Mastra application
 
-> **Warning:** On Azure App Services, the filesystem is ephemeral for some pricing tiers, so any local database file will be lost between deployments. If you're using [LibSQLStore](https://mastra.ai/reference/storage/libsql) with a local file, configure it to use a remote LibSQL-compatible database (for example, [Turso](https://turso.tech/)) instead.
+> **Warning:** On Azure App Services, the filesystem is ephemeral for some pricing tiers, so any local database file will be lost between deployments. If you're using [LibSQLStore](https://mastra.ai/integrations/databases/libsql) with a local file, configure it to use a remote LibSQL-compatible database (for example, [Turso](https://turso.tech/)) instead.
 
 ## Create a new app service
 

package/.docs/{guides/deployment → integrations/deploy}/cloudflare.md

@@ -10,7 +10,7 @@ Use `@mastra/deployer-cloudflare` to deploy your Mastra server to Cloudflare Wor
 
 You'll need a [Mastra application](https://mastra.ai/guides/getting-started/quickstart) and a [Cloudflare](https://cloudflare.com/) account.
 
-> **Warning:** Cloudflare Workers use an ephemeral filesystem, so any storage you configure (including observability storage) must be hosted externally. If you're using [LibSQLStore](https://mastra.ai/reference/storage/libsql) with a file URL, switch to a remotely hosted database.
+> **Warning:** Cloudflare Workers use an ephemeral filesystem, so any storage you configure (including observability storage) must be hosted externally. If you're using [LibSQLStore](https://mastra.ai/integrations/databases/libsql) with a file URL, switch to a remotely hosted database.
 
 ## Installation
 

package/.docs/{guides/deployment → integrations/deploy}/digital-ocean.md

@@ -10,7 +10,7 @@ This guide covers Digital Ocean's App Platform and Droplets. Each of these offer
 
 You'll need a [Mastra application](https://mastra.ai/guides/getting-started/quickstart) and a [Digital Ocean](https://www.digitalocean.com/) account.
 
-The **App Platform** uses an ephemeral filesystem, so any storage you configure (including observability storage) must be hosted externally. If you're using [LibSQLStore](https://mastra.ai/reference/storage/libsql) with a file URL, switch to a remotely hosted database.
+The **App Platform** uses an ephemeral filesystem, so any storage you configure (including observability storage) must be hosted externally. If you're using [LibSQLStore](https://mastra.ai/integrations/databases/libsql) with a file URL, switch to a remotely hosted database.
 
 ## App platform
 

package/.docs/{guides/deployment → integrations/deploy}/netlify.md

@@ -10,7 +10,7 @@ Use `@mastra/deployer-netlify` to deploy your Mastra server on Netlify. The depl
 
 You'll need a [Mastra application](https://mastra.ai/guides/getting-started/quickstart) and a [Netlify](https://www.netlify.com/) account.
 
-> **Warning:** Netlify Functions use an ephemeral filesystem, so any storage you configure (including observability storage) must be hosted externally. If you're using [LibSQLStore](https://mastra.ai/reference/storage/libsql) with a file URL, switch to a remotely hosted database.
+> **Warning:** Netlify Functions use an ephemeral filesystem, so any storage you configure (including observability storage) must be hosted externally. If you're using [LibSQLStore](https://mastra.ai/integrations/databases/libsql) with a file URL, switch to a remotely hosted database.
 
 ## Installation
 

package/.docs/{guides/deployment → integrations/deploy}/vercel.md

@@ -10,7 +10,7 @@ Use `@mastra/deployer-vercel` to deploy your Mastra server as serverless functio
 
 You'll need a [Mastra application](https://mastra.ai/guides/getting-started/quickstart) and a [Vercel](https://vercel.com/) account.
 
-> **Warning:** Vercel Functions use an ephemeral filesystem, so any storage you configure (including observability storage) must be hosted externally. If you're using [LibSQLStore](https://mastra.ai/reference/storage/libsql) with a file URL, switch to a remotely hosted database.
+> **Warning:** Vercel Functions use an ephemeral filesystem, so any storage you configure (including observability storage) must be hosted externally. If you're using [LibSQLStore](https://mastra.ai/integrations/databases/libsql) with a file URL, switch to a remotely hosted database.
 
 ## Installation
 
@@ -113,7 +113,7 @@ export default async function handler(req: VercelRequest, res: VercelResponse) {
 }
 ```
 
-> **Warning:** The Vercel deployer doesn't include `flush` calls. If you need this, you'll need to wrap the handler yourself to add the logic before returning the response. Alternatively, deploy to a long-running server like a [virtual machine](https://mastra.ai/guides/deployment/digital-ocean) where this isn't an issue.
+> **Warning:** The Vercel deployer doesn't include `flush` calls. If you need this, you'll need to wrap the handler yourself to add the logic before returning the response. Alternatively, deploy to a long-running server like a [virtual machine](https://mastra.ai/integrations/deploy/digital-ocean) where this isn't an issue.
 
 ## Related
 

package/.docs/{reference/workspace/s3-filesystem.md → integrations/file-storage/amazon-s3.md}

@@ -262,13 +262,13 @@ const workspace = new Workspace({
 })
 ```
 
-See [E2BSandbox reference](https://mastra.ai/reference/workspace/e2b-sandbox) for more details on mounting.
+See [E2BSandbox reference](https://mastra.ai/integrations/sandboxes/e2b) for more details on mounting.
 
 ## Related
 
 - [WorkspaceFilesystem interface](https://mastra.ai/reference/workspace/filesystem)
-- [ArchilFilesystem reference](https://mastra.ai/reference/workspace/archil-filesystem)
-- [GCSFilesystem reference](https://mastra.ai/reference/workspace/gcs-filesystem)
-- [AzureBlobFilesystem reference](https://mastra.ai/reference/workspace/azure-blob-filesystem)
-- [E2BSandbox reference](https://mastra.ai/reference/workspace/e2b-sandbox)
+- [ArchilFilesystem reference](https://mastra.ai/integrations/file-storage/archil)
+- [GCSFilesystem reference](https://mastra.ai/integrations/file-storage/google-cloud-storage)
+- [AzureBlobFilesystem reference](https://mastra.ai/integrations/file-storage/azure-blob)
+- [E2BSandbox reference](https://mastra.ai/integrations/sandboxes/e2b)
 - [Workspace overview](https://mastra.ai/docs/workspace/overview)

package/.docs/{reference/workspace/archil-filesystem.md → integrations/file-storage/archil.md}

@@ -198,7 +198,7 @@ const { url } = await filesystem.share('/reports/output.pdf', {
 ## Related
 
 - [WorkspaceFilesystem interface](https://mastra.ai/reference/workspace/filesystem)
-- [S3Filesystem reference](https://mastra.ai/reference/workspace/s3-filesystem)
-- [GCSFilesystem reference](https://mastra.ai/reference/workspace/gcs-filesystem)
-- [AzureBlobFilesystem reference](https://mastra.ai/reference/workspace/azure-blob-filesystem)
+- [S3Filesystem reference](https://mastra.ai/integrations/file-storage/amazon-s3)
+- [GCSFilesystem reference](https://mastra.ai/integrations/file-storage/google-cloud-storage)
+- [AzureBlobFilesystem reference](https://mastra.ai/integrations/file-storage/azure-blob)
 - [Archil documentation](https://docs.archil.com)

package/.docs/{reference/workspace/azure-blob-filesystem.md → integrations/file-storage/azure-blob.md}

@@ -215,6 +215,6 @@ const config = filesystem.getMountConfig()
 ## Related
 
 - [WorkspaceFilesystem interface](https://mastra.ai/reference/workspace/filesystem)
-- [S3Filesystem reference](https://mastra.ai/reference/workspace/s3-filesystem)
-- [GCSFilesystem reference](https://mastra.ai/reference/workspace/gcs-filesystem)
+- [S3Filesystem reference](https://mastra.ai/integrations/file-storage/amazon-s3)
+- [GCSFilesystem reference](https://mastra.ai/integrations/file-storage/google-cloud-storage)
 - [Workspace overview](https://mastra.ai/docs/workspace/overview)

package/.docs/{reference/workspace/gcs-filesystem.md → integrations/file-storage/google-cloud-storage.md}

@@ -185,13 +185,13 @@ const workspace = new Workspace({
 })
 ```
 
-See [E2BSandbox reference](https://mastra.ai/reference/workspace/e2b-sandbox) for more details on mounting.
+See [E2BSandbox reference](https://mastra.ai/integrations/sandboxes/e2b) for more details on mounting.
 
 ## Related
 
 - [WorkspaceFilesystem interface](https://mastra.ai/reference/workspace/filesystem)
-- [ArchilFilesystem reference](https://mastra.ai/reference/workspace/archil-filesystem)
-- [S3Filesystem reference](https://mastra.ai/reference/workspace/s3-filesystem)
-- [AzureBlobFilesystem reference](https://mastra.ai/reference/workspace/azure-blob-filesystem)
-- [E2BSandbox reference](https://mastra.ai/reference/workspace/e2b-sandbox)
+- [ArchilFilesystem reference](https://mastra.ai/integrations/file-storage/archil)
+- [S3Filesystem reference](https://mastra.ai/integrations/file-storage/amazon-s3)
+- [AzureBlobFilesystem reference](https://mastra.ai/integrations/file-storage/azure-blob)
+- [E2BSandbox reference](https://mastra.ai/integrations/sandboxes/e2b)
 - [Workspace overview](https://mastra.ai/docs/workspace/overview)

package/.docs/{reference/workspace/mesa-filesystem.md → integrations/file-storage/mesa.md}

@@ -4,7 +4,7 @@
 
 Stores workspace files in [Mesa](https://docs.mesa.dev/content/getting-started/introduction) repos through the standard Mastra `WorkspaceFilesystem` interface.
 
-Use `MesaFilesystem` when agents need versioned file storage. For a local directory, use [`LocalFilesystem`](https://mastra.ai/reference/workspace/local-filesystem). For object storage, use [`S3Filesystem`](https://mastra.ai/reference/workspace/s3-filesystem), [`GCSFilesystem`](https://mastra.ai/reference/workspace/gcs-filesystem), or [`AzureBlobFilesystem`](https://mastra.ai/reference/workspace/azure-blob-filesystem).
+Use `MesaFilesystem` when agents need versioned file storage. For a local directory, use [`LocalFilesystem`](https://mastra.ai/reference/workspace/local-filesystem). For object storage, use [`S3Filesystem`](https://mastra.ai/integrations/file-storage/amazon-s3), [`GCSFilesystem`](https://mastra.ai/integrations/file-storage/google-cloud-storage), or [`AzureBlobFilesystem`](https://mastra.ai/integrations/file-storage/azure-blob).
 
 > **Note:** `MesaFilesystem` runs in the Mastra process.
 >

package/.docs/{reference/workspace/files-sdk-filesystem.md → integrations/file-storage/vercel-files.md}

@@ -4,7 +4,7 @@
 
 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).
 
-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)).
+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/integrations/file-storage/amazon-s3) or [`GCSFilesystem`](https://mastra.ai/integrations/file-storage/google-cloud-storage)).
 
 ## Installation
 
@@ -173,7 +173,7 @@ const url = await filesystem.files.url('reports/q3.pdf')
 - **`mkdir`** is a no-op. Directories exist implicitly when keys with that prefix exist.
 - **`exists`** returns `true` only when an exact key is present as a file, or when the path is a prefix that contains at least one child key. Empty leftover directories on hierarchical adapters don't count.
 - **`deleteFile`** throws `FileNotFoundError` when the key doesn't exist, unless `{ force: true }` is passed.
-- **`deleteFile`** on a directory delegates to `rmdir({ recursive: true })`, matching the [`S3Filesystem`](https://mastra.ai/reference/workspace/s3-filesystem) and [`GCSFilesystem`](https://mastra.ai/reference/workspace/gcs-filesystem) behavior.
+- **`deleteFile`** on a directory delegates to `rmdir({ recursive: true })`, matching the [`S3Filesystem`](https://mastra.ai/integrations/file-storage/amazon-s3) and [`GCSFilesystem`](https://mastra.ai/integrations/file-storage/google-cloud-storage) behavior.
 - **`moveFile`** is implemented as `copyFile` followed by `deleteFile`. It isn't **atomic**. If the source delete fails after a successful copy, the destination remains and the source isn't removed.
 - **`appendFile`** is a read-modify-write operation. Concurrent appends to the same key may overwrite each other. This is inherent to object storage and not specific to FilesSDK.
 - **`readdir({ recursive: true })`** emits intermediate directory entries (for example, `a/b` is emitted alongside `a/b/c.txt`).
@@ -181,8 +181,8 @@ const url = await filesystem.files.url('reports/q3.pdf')
 ## Related
 
 - [WorkspaceFilesystem interface](https://mastra.ai/reference/workspace/filesystem)
-- [S3Filesystem reference](https://mastra.ai/reference/workspace/s3-filesystem)
-- [GCSFilesystem reference](https://mastra.ai/reference/workspace/gcs-filesystem)
-- [AzureBlobFilesystem reference](https://mastra.ai/reference/workspace/azure-blob-filesystem)
+- [S3Filesystem reference](https://mastra.ai/integrations/file-storage/amazon-s3)
+- [GCSFilesystem reference](https://mastra.ai/integrations/file-storage/google-cloud-storage)
+- [AzureBlobFilesystem reference](https://mastra.ai/integrations/file-storage/azure-blob)
 - [Workspace overview](https://mastra.ai/docs/workspace/overview)
 - [FilesSDK documentation](https://files-sdk.dev)

package/.docs/{guides/getting-started → integrations/frameworks}/astro.md

@@ -396,5 +396,5 @@ From here, you can extend the project with your own tools and logic:
 
 When you're ready, read more about how Mastra integrates with AI SDK UI and how to deploy your agent anywhere:
 
-- Integrate Mastra with [AI SDK UI](https://mastra.ai/guides/build-your-ui/ai-sdk-ui)
+- Integrate Mastra with [AI SDK UI](https://mastra.ai/integrations/agentic-ui/ai-sdk-ui)
 - Deploy your agent [anywhere](https://mastra.ai/docs/deployment/overview)

package/.docs/{guides/getting-started → integrations/frameworks}/electron.md

@@ -502,5 +502,5 @@ From here, you can extend the project with your own tools and logic:
 
 When you're ready, read more about how Mastra integrates with AI SDK UI and React, and how to deploy your agent anywhere:
 
-- Integrate Mastra with [AI SDK UI](https://mastra.ai/guides/build-your-ui/ai-sdk-ui)
+- Integrate Mastra with [AI SDK UI](https://mastra.ai/integrations/agentic-ui/ai-sdk-ui)
 - Deploy your agent [anywhere](https://mastra.ai/docs/deployment/overview)

package/.docs/{guides/getting-started → integrations/frameworks}/next-js.md

@@ -340,6 +340,6 @@ From here, you can extend the project with your own tools and logic:
 
 When you're ready, read more about how Mastra integrates with AI SDK UI and Next.js, and how to deploy your agent anywhere, including Vercel:
 
-- Integrate Mastra with [AI SDK UI](https://mastra.ai/guides/build-your-ui/ai-sdk-ui)
-- Deploy your agent to [Vercel](https://mastra.ai/guides/deployment/vercel)
+- Integrate Mastra with [AI SDK UI](https://mastra.ai/integrations/agentic-ui/ai-sdk-ui)
+- Deploy your agent to [Vercel](https://mastra.ai/integrations/deploy/vercel)
 - Deploy your agent [anywhere](https://mastra.ai/docs/deployment/overview)

package/.docs/{guides/getting-started → integrations/frameworks}/nuxt.md

@@ -495,5 +495,5 @@ From here, you can extend the project with your own tools and logic:
 
 When you're ready, read more about how Mastra integrates with AI SDK UI and Nuxt, and how to deploy your agent anywhere:
 
-- Integrate Mastra with [AI SDK UI](https://mastra.ai/guides/build-your-ui/ai-sdk-ui)
+- Integrate Mastra with [AI SDK UI](https://mastra.ai/integrations/agentic-ui/ai-sdk-ui)
 - Deploy your agent [anywhere](https://mastra.ai/docs/deployment/overview)

package/.docs/{guides/getting-started → integrations/frameworks}/sveltekit.md

@@ -293,6 +293,6 @@ From here, you can extend the project with your own tools and logic:
 
 When you're ready, read more about how Mastra integrates with AI SDK UI and SvelteKit, and how to deploy your agent anywhere:
 
-- Integrate Mastra with [AI SDK UI](https://mastra.ai/guides/build-your-ui/ai-sdk-ui)
+- Integrate Mastra with [AI SDK UI](https://mastra.ai/integrations/agentic-ui/ai-sdk-ui)
 - Deploy your agent [anywhere](https://mastra.ai/docs/deployment/overview)
 - Try the [unofficial Svelte AI Elements](https://svelte-ai-elements.vercel.app/)

package/.docs/{guides/getting-started → integrations/frameworks}/vite-react.md

@@ -423,5 +423,5 @@ From here, you can extend the project with your own tools and logic:
 
 When you're ready, read more about how Mastra integrates with AI SDK UI and React, and how to deploy your agent anywhere:
 
-- Integrate Mastra with [AI SDK UI](https://mastra.ai/guides/build-your-ui/ai-sdk-ui)
+- Integrate Mastra with [AI SDK UI](https://mastra.ai/integrations/agentic-ui/ai-sdk-ui)
 - Deploy your agent [anywhere](https://mastra.ai/docs/deployment/overview)

package/.docs/{docs/observability/integrations/exporters → integrations/observability}/arize.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Arize exporter
+# Arize
 
 [Arize](https://arize.com/) provides observability platforms for AI applications through [Phoenix](https://phoenix.arize.com/) (open-source) and [Arize AX](https://arize.com/generative-ai/) (enterprise). The Arize exporter sends traces using OpenTelemetry and [OpenInference](https://github.com/Arize-ai/openinference/tree/main/spec) semantic conventions, compatible with any OpenTelemetry platform that supports OpenInference.
 

package/.docs/{docs/observability/integrations/exporters → integrations/observability}/arthur.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Arthur exporter
+# Arthur
 
 [Arthur](https://arthur.ai/) provides an observability and evaluation platform for AI applications through [Arthur Engine](https://github.com/arthur-ai/arthur-engine) (open-source). The Arthur exporter sends traces using OpenTelemetry and [OpenInference](https://github.com/Arize-ai/openinference/tree/main/spec) semantic conventions.