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

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.
 
@@ -521,11 +521,11 @@ const stats = await storage.db.one(`
 
 PostgreSQL offers different index types optimized for specific scenarios:
 
-| Index Type          | Best For                                | Storage    | Speed                      |
-| ------------------- | --------------------------------------- | ---------- | -------------------------- |
-| **btree** (default) | Range queries, sorting, general purpose | Moderate   | Fast                       |
-| **hash**            | Equality comparisons only               | Small      | Very fast for `=`          |
-| **gin**             | JSONB, arrays, full-text search         | Large      | Fast for contains          |
-| **gist**            | Geometric data, full-text search        | Moderate   | Fast for nearest-neighbor  |
-| **spgist**          | Non-balanced data, text patterns        | Small      | Fast for specific patterns |
-| **brin**            | Large tables with natural ordering      | Very small | Fast for ranges            |
+| Index Type          | Best For                                | Storage size | Speed                      |
+| ------------------- | --------------------------------------- | ------------ | -------------------------- |
+| **btree** (default) | Range queries, sorting, general purpose | Moderate     | Fast                       |
+| **hash**            | Equality comparisons only               | Small        | Very fast for `=`          |
+| **gin**             | JSONB, arrays, full-text search         | Large        | Fast for contains          |
+| **gist**            | Geometric data, full-text search        | Moderate     | Fast for nearest-neighbor  |
+| **spgist**          | Non-balanced data, text patterns        | Small        | Fast for specific patterns |
+| **brin**            | Large tables with natural ordering      | Very small   | Fast for ranges            |

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}/amazon-ec2.md

@@ -1,16 +1,16 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Deploy Mastra to Amazon EC2
+# Amazon EC2
 
 Deploy your Mastra server to Amazon EC2. The server runs on infrastructure you manage and can support long-running agents and workflows.
 
-> **Info:** This guide covers deploying the [Mastra server](https://mastra.ai/docs/server/mastra-server). If you're using a [server adapter](https://mastra.ai/docs/server/server-adapters) or [web framework](https://mastra.ai/docs/deployment/web-framework), deploy the way you normally would for that framework.
+> **Note:** This guide covers deploying the [Mastra server](https://mastra.ai/docs/server/mastra-server). If you're using a [server adapter](https://mastra.ai/docs/server/server-adapters) or [web framework](https://mastra.ai/docs/deployment/web-framework), deploy the way you normally would for that framework.
 
 ## Before you begin
 
 You'll need:
 
-- A [Mastra application](https://mastra.ai/guides/getting-started/quickstart)
+- A [Mastra application](https://mastra.ai/docs)
 - An [EC2](https://aws.amazon.com/ec2/) instance (Ubuntu or Amazon Linux) with Git and Node.js 22.13.0+ installed
 
 For production, you'll also need:

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

@@ -1,12 +1,12 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Deploy Mastra to Amazon Bedrock AgentCore
+# Amazon Bedrock AgentCore
 
 Deploy your Mastra application to [Amazon Bedrock AgentCore Runtime](https://docs.aws.amazon.com/bedrock-agentcore/) using the [AgentCore CLI](https://github.com/aws/agentcore-cli). The CLI scaffolds a bring-your-own-code (BYO) TypeScript project, builds the container with AWS CodeBuild, and provisions the runtime. A local Docker daemon isn't required for deployment.
 
 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.
 
-> **Info:** 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

@@ -1,21 +1,21 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Deploy Mastra to AWS Lambda
+# AWS Lambda
 
 Deploy your Mastra application to AWS Lambda using Docker containers and the [AWS Lambda Web Adapter](https://github.com/awslabs/aws-lambda-web-adapter). This approach runs your Mastra server as a containerized Lambda function with automatic scaling.
 
-> **Info:** This guide covers deploying the [Mastra server](https://mastra.ai/docs/server/mastra-server). If you're using a [server adapter](https://mastra.ai/docs/server/server-adapters) or [web framework](https://mastra.ai/docs/deployment/web-framework), deploy the way you normally would for that framework.
+> **Note:** This guide covers deploying the [Mastra server](https://mastra.ai/docs/server/mastra-server). If you're using a [server adapter](https://mastra.ai/docs/server/server-adapters) or [web framework](https://mastra.ai/docs/deployment/web-framework), deploy the way you normally would for that framework.
 
 ## Before you begin
 
 You'll need:
 
-- A [Mastra application](https://mastra.ai/guides/getting-started/quickstart)
+- A [Mastra application](https://mastra.ai/docs)
 - An [AWS account](https://aws.amazon.com/) with permissions for Lambda, ECR, and IAM
 - **[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

@@ -1,20 +1,20 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Deploy Mastra to Azure App Services
+# Azure App Services
 
 Deploy your Mastra applications to Azure App Services.
 
-> **Info:** This guide covers deploying the [Mastra server](https://mastra.ai/docs/server/mastra-server). If you're using a [server adapter](https://mastra.ai/docs/server/server-adapters) or [web framework](https://mastra.ai/docs/deployment/web-framework), deploy the way you normally would for that framework.
+> **Note:** This guide covers deploying the [Mastra server](https://mastra.ai/docs/server/mastra-server). If you're using a [server adapter](https://mastra.ai/docs/server/server-adapters) or [web framework](https://mastra.ai/docs/deployment/web-framework), deploy the way you normally would for that framework.
 
 ## Before you begin
 
 You'll need:
 
-- A [Mastra application](https://mastra.ai/guides/getting-started/quickstart)
+- A [Mastra application](https://mastra.ai/docs)
 - 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

@@ -1,16 +1,16 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Deploy Mastra to Cloudflare
+# Cloudflare
 
 Use `@mastra/deployer-cloudflare` to deploy your Mastra server to Cloudflare Workers. The deployer bundles your code and generates a `wrangler.jsonc` file conforming to Cloudflare's [wrangler configuration](https://developers.cloudflare.com/workers/wrangler/configuration/), ready to deploy with no additional configuration.
 
-> **Info:** If you're using a [server adapter](https://mastra.ai/docs/server/server-adapters) or [web framework](https://mastra.ai/docs/deployment/web-framework), deploy the way you normally would for that framework.
+> **Note:** If you're using a [server adapter](https://mastra.ai/docs/server/server-adapters) or [web framework](https://mastra.ai/docs/deployment/web-framework), deploy the way you normally would for that framework.
 
 ## Before you begin
 
-You'll need a [Mastra application](https://mastra.ai/guides/getting-started/quickstart) and a [Cloudflare](https://cloudflare.com/) account.
+You'll need a [Mastra application](https://mastra.ai/docs) 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

@@ -1,16 +1,16 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Deploy Mastra to Digital Ocean
+# Digital Ocean
 
 This guide covers Digital Ocean's App Platform and Droplets. Each of these offerings has its own set of strengths and is suited for different types of projects and developer expertise. Read [Digital Ocean's comparison](https://www.digitalocean.com/community/conceptual-articles/digitalocean-app-platform-vs-doks-vs-droplets) to understand the differences and choose the best option for your project.
 
-> **Info:** This guide covers deploying the [Mastra server](https://mastra.ai/docs/server/mastra-server). If you're using a [server adapter](https://mastra.ai/docs/server/server-adapters) or [web framework](https://mastra.ai/docs/deployment/web-framework), deploy the way you normally would for that framework.
+> **Note:** This guide covers deploying the [Mastra server](https://mastra.ai/docs/server/mastra-server). If you're using a [server adapter](https://mastra.ai/docs/server/server-adapters) or [web framework](https://mastra.ai/docs/deployment/web-framework), deploy the way you normally would for that framework.
 
 ## Before you begin
 
-You'll need a [Mastra application](https://mastra.ai/guides/getting-started/quickstart) and a [Digital Ocean](https://www.digitalocean.com/) account.
+You'll need a [Mastra application](https://mastra.ai/docs) 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
 
@@ -158,7 +158,7 @@ After setting up your project, push it to your remote Git provider of choice (e.
    mastra start
    ```
 
-   > **Info:** Your Mastra application will run on port 4111 by default. Ensure your reverse proxy is configured to forward requests to this port.
+   > **Note:** Your Mastra application will run on port 4111 by default. Ensure your reverse proxy is configured to forward requests to this port.
 
 6. You can now call your Mastra endpoints over HTTP.
 

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

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Inngest workflow
+# Inngest
 
 [Inngest](https://www.inngest.com/docs) is a developer platform for building and running background workflows, without managing infrastructure.
 

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

@@ -1,18 +1,18 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Deploy Mastra to Kubernetes
+# Kubernetes
 
 Run a Mastra application across multiple pods on [Kubernetes](https://kubernetes.io/), so it scales horizontally behind a load balancer. Because each pod is a separate process, the pods must share a pub/sub backend and a database, otherwise work started on one pod is invisible to the others.
 
-> **Info:** This guide covers deploying the [Mastra server](https://mastra.ai/docs/server/mastra-server). If you're using a [server adapter](https://mastra.ai/docs/server/server-adapters) or [web framework](https://mastra.ai/docs/deployment/web-framework), deploy the way you normally would for that framework.
+> **Note:** This guide covers deploying the [Mastra server](https://mastra.ai/docs/server/mastra-server). If you're using a [server adapter](https://mastra.ai/docs/server/server-adapters) or [web framework](https://mastra.ai/docs/deployment/web-framework), deploy the way you normally would for that framework.
 
-> **Warning:** Multi-pod support relies on [durable agents](https://mastra.ai/docs/long-running-agents/durable-agents), which are currently in **beta**. APIs may change in minor versions. Read [Known limitations](#known-limitations) before you rely on this in production.
+> **Beta:** Multi-pod support relies on [durable agents](https://mastra.ai/docs/long-running-agents/durable-agents). Breaking changes may occur without a major version bump until the API is stable. Read [Known limitations](#known-limitations) before you rely on this in production.
 
 ## Before you begin
 
 You'll need:
 
-- A [Mastra application](https://mastra.ai/guides/getting-started/quickstart)
+- A [Mastra application](https://mastra.ai/docs)
 - A [Kubernetes](https://kubernetes.io/docs/setup/) cluster and [`kubectl`](https://kubernetes.io/docs/tasks/tools/)
 - A container registry your cluster can pull from
 - A shared [Redis](https://redis.io/) instance, reachable from every pod
@@ -295,6 +295,5 @@ The pod that handles the approval loads the suspended run from Postgres. It then
 - [PubSub](https://mastra.ai/docs/server/pubsub)
 - [Durable agents](https://mastra.ai/docs/long-running-agents/durable-agents)
 - [Workers](https://mastra.ai/docs/deployment/workers): Split background processing into separate containers on Kubernetes
-- [Worker deployment guide](https://mastra.ai/guides/deployment/mastra-workers): Full Kubernetes manifests for orchestration, scheduler, and background task workers
 - [Mastra server](https://mastra.ai/docs/server/mastra-server)
 - [Deployment overview](https://mastra.ai/docs/deployment/overview)

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

@@ -1,16 +1,16 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Deploy Mastra to Netlify
+# Netlify
 
 Use `@mastra/deployer-netlify` to deploy your Mastra server on Netlify. The deployer bundles your code and generates a `.netlify` directory conforming to Netlify's [Frameworks API](https://docs.netlify.com/build/frameworks/frameworks-api/), ready to deploy. You can deploy as serverless functions (default) or as [edge functions](https://docs.netlify.com/build/edge-functions/overview/) for lower latency and longer execution times.
 
-> **Info:** This guide covers deploying the [Mastra server](https://mastra.ai/docs/server/mastra-server). If you're using a [server adapter](https://mastra.ai/docs/server/server-adapters) or [web framework](https://mastra.ai/docs/deployment/web-framework), deploy the way you normally would for that framework.
+> **Note:** This guide covers deploying the [Mastra server](https://mastra.ai/docs/server/mastra-server). If you're using a [server adapter](https://mastra.ai/docs/server/server-adapters) or [web framework](https://mastra.ai/docs/deployment/web-framework), deploy the way you normally would for that framework.
 
 ## Before you begin
 
-You'll need a [Mastra application](https://mastra.ai/guides/getting-started/quickstart) and a [Netlify](https://www.netlify.com/) account.
+You'll need a [Mastra application](https://mastra.ai/docs) 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
 
@@ -87,7 +87,7 @@ After setting up your project, push it to your remote Git provider of choice (e.
 
    Since the [Mastra server](https://mastra.ai/docs/server/mastra-server) prefixes every API endpoint with `/api`, you have to add it to your URLs when making requests.
 
-   > **Info:** Netlify functions are typically deployed at `https://<random-slug>.netlify.app/.netlify/functions/api`. The `NetlifyDeployer` redirects any request from `/*` to `/.netlify/functions/api/:splat`, so you don't need to include the `.netlify/functions` prefix in your URLs.
+   > **Note:** Netlify functions are typically deployed at `https://<random-slug>.netlify.app/.netlify/functions/api`. The `NetlifyDeployer` redirects any request from `/*` to `/.netlify/functions/api/:splat`, so you don't need to include the `.netlify/functions` prefix in your URLs.
 
 4. You can now call your Mastra endpoints over HTTP.
 

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

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Temporal workflow
+# Temporal
 
 [Temporal](https://temporal.io/) is a durable execution platform for orchestrating long-running, fault-tolerant workflows. The `@mastra/temporal` package lets you author workflows with the standard Mastra API and run them on a Temporal cluster.
 

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

@@ -1,16 +1,16 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Deploy Mastra to Vercel
+# Vercel Deployer
 
 Use `@mastra/deployer-vercel` to deploy your Mastra server as serverless functions on Vercel. The deployer bundles your code and generates a `.vercel/output` directory conforming to Vercel's [Build Output API](https://vercel.com/docs/build-output-api/v3), ready to deploy with no additional configuration.
 
-> **Info:** This guide covers deploying the [Mastra server](https://mastra.ai/docs/server/mastra-server). If you're using a [server adapter](https://mastra.ai/docs/server/server-adapters) or [web framework](https://mastra.ai/docs/deployment/web-framework), deploy the way you normally would for that framework.
+> **Note:** This guide covers deploying the [Mastra server](https://mastra.ai/docs/server/mastra-server). If you're using a [server adapter](https://mastra.ai/docs/server/server-adapters) or [web framework](https://mastra.ai/docs/deployment/web-framework), deploy the way you normally would for that framework.
 
 ## Before you begin
 
-You'll need a [Mastra application](https://mastra.ai/guides/getting-started/quickstart) and a [Vercel](https://vercel.com/) account.
+You'll need a [Mastra application](https://mastra.ai/docs) 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/agentfs-filesystem.md → integrations/file-storage/agentfs.md}

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# AgentFSFilesystem
+# AgentFS
 
 Stores files in a Turso/SQLite database via the [AgentFS](https://github.com/nichochar/agentfs) SDK. Files are persisted across sessions in a local SQLite database, giving agents durable storage without external cloud services. For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
 

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

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# S3Filesystem
+# Amazon S3
 
 Stores files in Amazon S3 or S3-compatible storage services like Cloudflare R2, MinIO, DigitalOcean Spaces, and Tigris. For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
 
@@ -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}

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# ArchilFilesystem
+# Archil
 
 Stores files on [Archil](https://docs.archil.com) elastic, serverless disks. Combines an S3-compatible object API for fast reads/writes with `exec()` for POSIX shell operations and `grep()` for parallel server-side search. For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
 
@@ -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}

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# AzureBlobFilesystem
+# Azure Blob
 
 Stores files in Azure Blob Storage containers. For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
 
@@ -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}

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# GCSFilesystem
+# Google Cloud Storage
 
 Stores files in Google Cloud Storage. For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
 
@@ -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/google-drive-filesystem.md → integrations/file-storage/google-drive.md}

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# GoogleDriveFilesystem
+# Google Drive
 
 Stores files in a single Google Drive folder. Each directory maps to a Drive folder under the configured root, and paths use POSIX semantics (for example `/notes/todo.txt`). For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
 

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

@@ -1,12 +1,12 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# MesaFilesystem
+# Mesa
 
 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).
 
-> **Info:** `MesaFilesystem` runs in the Mastra process.
+> **Note:** `MesaFilesystem` runs in the Mastra process.
 >
 > [Mesa's POSIX mount](https://docs.mesa.dev/content/mesafs/posix-mount) (for using a Mesa filesystem within a sandbox) isn't yet part of the `@mastra/mesa` package. Support is coming soon.
 

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

@@ -1,10 +1,10 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# FilesSDKFilesystem
+# Vercel Files
 
 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

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Integrate Mastra in your Astro project
+# Astro
 
 In this guide, you'll build a tool-calling AI agent using Mastra, then connect it to Astro by importing and calling the agent directly from your routes.
 
@@ -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

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Integrate Mastra in your Electron project
+# Electron
 
 In this guide, you'll build a tool-calling AI agent using Mastra, then connect it to an Electron desktop app by calling the agent directly from Mastra's server.
 
@@ -60,7 +60,7 @@ Open `src/renderer/index.html` and update the `<meta http-equiv="Content-Securit
 />
 ```
 
-> **Info:** For production deployments you'll need to adjust this to match your actual server URL.
+> **Note:** For production deployments you'll need to adjust this to match your actual server URL.
 
 ### Edit `main.css`
 
@@ -165,7 +165,7 @@ export const mastra = new Mastra({
 })
 ```
 
-> **Info:** CORS is required because the Electron renderer loads from a different origin than the Mastra server. For production deployments, restrict the origin to your application's actual origin.
+> **Note:** CORS is required because the Electron renderer loads from a different origin than the Mastra server. For production deployments, restrict the origin to your application's actual origin.
 
 ## Add the chat UI
 
@@ -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}/express.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Integrate Mastra in your Express project
+# Express
 
 In this guide, you'll build a tool-calling AI agent using Mastra and Express. Using the [Express server adapter](https://mastra.ai/reference/server/express-adapter), you can expose your agents as HTTP endpoints without writing the routing yourself or running a separate Mastra server.
 

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

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Integrate Mastra in your Hono project
+# Hono
 
 In this guide, you'll build a tool-calling AI agent using Mastra and Hono. Using the [Hono server adapter](https://mastra.ai/reference/server/hono-adapter), you can expose your agents as HTTP endpoints without writing the routing yourself or running a separate Mastra server.
 

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

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Integrate Mastra in Your NestJS Project
+# NestJS
 
 In this guide, you'll build a tool-calling AI agent using Mastra and NestJS. The [NestJS server adapter](https://mastra.ai/reference/server/nestjs-adapter) registers Mastra's agent and workflow routes as a NestJS module, so they run inside your existing NestJS application.
 

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

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Integrate Mastra in your Next.js project
+# Next.js
 
 In this guide, you'll build a tool-calling AI agent using Mastra, then connect it to Next.js by importing and calling the agent directly from your routes.
 
@@ -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

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Integrate Mastra in your Nuxt project
+# Nuxt
 
 In this guide, you'll build a tool-calling AI agent using Mastra, then connect it to Nuxt by importing and calling the agent directly from your server routes.
 
@@ -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)