@mastra/mcp-docs-server 1.1.7 → 1.1.8

package/.docs/guides/deployment/aws-lambda.md

@@ -1,84 +1,64 @@
-# AWS Lambda
+# Deploy Mastra to AWS Lambda
 
-Deploy your Mastra applications to AWS Lambda using Docker containers and the AWS Lambda Web Adapter. This approach allows you to run your Mastra server as a containerized Lambda function with automatic scaling.
+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.
 
-> **Note:** This guide assumes your Mastra application has been created using the default `npx create-mastra@latest` command. For more information on how to create a new Mastra application, refer to our [getting started guide](https://mastra.ai/guides/getting-started/quickstart)
+> **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.
 
-## Prerequisites
+## Before you begin
 
-Before deploying to AWS Lambda, ensure you have:
+You'll need:
 
-- [AWS CLI](https://aws.amazon.com/cli/) installed and configured
-- [Docker](https://www.docker.com/) installed and running
-- An AWS account with appropriate permissions for Lambda, ECR, and IAM
-- Your Mastra application configured with appropriate memory storage
+- A [Mastra application](https://mastra.ai/guides/getting-started/quickstart)
+- 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
 
-## Memory Configuration
+> **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:** AWS Lambda uses an ephemeral file system, meaning that any files written to the file system are short-lived and may be lost. Remove any usage of [LibSQLStore](https://mastra.ai/reference/storage/libsql) with file URLs from your Mastra configuration. Use in-memory storage (`:memory:`) or external storage providers like Turso, PostgreSQL, or Upstash.
+## Create a Dockerfile
 
-Lambda functions have limitations with file system storage. Configure your Mastra application to use either in-memory or external storage providers:
-
-### Option 1: In-Memory (Simplest)
-
-```typescript
-import { LibSQLStore } from '@mastra/libsql'
-
-const storage = new LibSQLStore({
-  id: 'mastra-storage',
-  url: ':memory:', // in-memory storage
-})
-```
-
-### Option 2: External Storage Providers
-
-For persistent memory across Lambda invocations, use external storage providers like `LibSQLStore` with Turso or other storage providers like `PostgreStore`:
-
-```typescript
-import { LibSQLStore } from '@mastra/libsql'
-
-const storage = new LibSQLStore({
-  id: 'mastra-storage',
-  url: 'libsql://your-database.turso.io', // External Turso database
-  authToken: process.env.TURSO_AUTH_TOKEN,
-})
-```
-
-For more memory configuration options, see the [Memory documentation](https://mastra.ai/docs/memory/overview).
-
-## Creating a Dockerfile
-
-Create a `Dockerfile` in your Mastra project root directory:
+Create a `Dockerfile` in your project root:
 
 ```dockerfile
 FROM node:22-alpine
 
 WORKDIR /app
+
+# Install dependencies
 COPY package*.json ./
 RUN npm ci
+
+# Copy source and build Mastra
 COPY src ./src
 RUN npx mastra build
+
+# Alpine compatibility for some native deps
 RUN apk add --no-cache gcompat
 
-COPY --from=public.ecr.aws/awsguru/aws-lambda-adapter:0.9.0 /lambda-adapter /opt/extensions/lambda-adapter
+# Add the Lambda Web Adapter
+COPY --from=public.ecr.aws/awsguru/aws-lambda-adapter:0.9.1 /lambda-adapter /opt/extensions/lambda-adapter
+
+# Run as non-root
 RUN addgroup -g 1001 -S nodejs && \
   adduser -S mastra -u 1001 && \
   chown -R mastra:nodejs /app
 
 USER mastra
 
+# Adapter / app configuration
 ENV PORT=8080
 ENV NODE_ENV=production
-ENV READINESS_CHECK_PATH="/api"
-
-EXPOSE 8080
+ENV AWS_LWA_READINESS_CHECK_PATH="/api"
 
+# Start the Mastra server
 CMD ["node", ".mastra/output/index.mjs"]
 ```
 
-## Building and Deploying
+> **Note:** This Dockerfile uses npm. If you're using pnpm, yarn, or another package manager, adjust the commands accordingly (e.g. `npm ci` won't work with pnpm lockfiles).
 
-1. Set up your environment variables for the deployment process:
+## Build and push the Docker image
+
+1. Set up environment variables for the deployment. Use the same region for all AWS services (ECR, Lambda) to avoid issues with resources not appearing across regions:
 
    ```bash
    export PROJECT_NAME="your-mastra-app"
@@ -86,12 +66,15 @@ CMD ["node", ".mastra/output/index.mjs"]
    export AWS_ACCOUNT_ID=$(aws sts get-caller-identity --query Account --output text)
    ```
 
-2. Build your Docker image locally:
+2. Build your Docker image. Disable BuildKit to ensure the image is compatible with Lambda's container runtime:
 
    ```bash
-   docker build -t "$PROJECT_NAME" .
+   export DOCKER_BUILDKIT=0
+   docker build --platform linux/arm64 -t "$PROJECT_NAME" .
    ```
 
+   > **Note:** BuildKit's default image format can cause compatibility issues with Lambda. Setting `DOCKER_BUILDKIT=0` uses the classic builder, which produces images in a format Lambda reliably accepts.
+
 3. Create an Amazon ECR repository to store your Docker image:
 
    ```bash
@@ -101,148 +84,76 @@ CMD ["node", ".mastra/output/index.mjs"]
 4. Log in to Amazon ECR:
 
    ```bash
-   aws ecr get-login-password --region "$AWS_REGION" | docker login --username AWS --password-stdin "$AWS_ACCOUNT_ID.dkr.ecr.$AWS_REGION.amazonaws.com"
+   aws ecr get-login-password --region "$AWS_REGION" | \
+     docker login --username AWS --password-stdin \
+     "$AWS_ACCOUNT_ID.dkr.ecr.$AWS_REGION.amazonaws.com"
    ```
 
-5. Tag your image with the ECR repository URI and push it:
+5. Tag your image and push it to ECR:
 
    ```bash
-   docker tag "$PROJECT_NAME":latest "$AWS_ACCOUNT_ID.dkr.ecr.$AWS_REGION.amazonaws.com/$PROJECT_NAME":latest
-   docker push "$AWS_ACCOUNT_ID.dkr.ecr.$AWS_REGION.amazonaws.com/$PROJECT_NAME":latest
-   ```
-
-6. Create a Lambda function using the AWS Console:
-
-   1. Navigate to the [AWS Lambda Console](https://console.aws.amazon.com/lambda/)
-
-   2. Click **Create function**
-
-   3. Select **Container image**
-
-   4. Configure the function:
-
-      - **Function name**: Your function name (e.g., `mastra-app`)
-      - **Container image URI**: Click **Browse images** and select your ECR repository, then choose the `latest` tag
-      - **Architecture**: Select the architecture that matches your Docker build (typically `x86_64`)
+   docker tag "$PROJECT_NAME":latest \
+     "$AWS_ACCOUNT_ID.dkr.ecr.$AWS_REGION.amazonaws.com/$PROJECT_NAME":latest
 
-7. Enable Function URL for external access:
-
-   1. In the Lambda function configuration, go to **Configuration** > **Function URL**
-
-   2. Click **Create function URL**
-
-   3. Set **Auth type** to **NONE** (for public access)
-
-   4. Configure **CORS** settings:
-
-      - **Allow-Origin**: `*` (restrict to your domain in production)
-      - **Allow-Headers**: `content-type` (`x-amzn-request-context` is also required when used with services like Cloudfront/API Gateway)
-      - **Allow-Methods**: `*` (audit and restrict in production)
-
-   5. Click **Save**
-
-8. Add your environment variables in the Lambda function configuration:
-
-   1. Go to **Configuration** > **Environment variables**
-
-   2. Add the required variables for your Mastra application:
-
-      - `OPENAI_API_KEY`: Your OpenAI API key (if using OpenAI)
-      - `ANTHROPIC_API_KEY`: Your Anthropic API key (if using Anthropic)
-      - `TURSO_AUTH_TOKEN`: Your Turso auth token (if using libSQL with Turso)
-      - Other provider-specific API keys as needed
-
-9. Configure the function's memory and timeout settings:
-
-   1. Go to **Configuration** > **General configuration**
-
-   2. Set the following recommended values:
-
-      - **Memory**: 512 MB (adjust based on your application needs)
-      - **Timeout**: 30 seconds (adjust based on your application needs)
-      - **Ephemeral storage**: 512 MB (optional, for temporary files)
-
-## Testing your deployment
-
-Once deployed, test your Lambda function:
-
-1. Copy the **Function URL** from the Lambda console
-2. Visit the URL in your browser to see your Mastra's server home screen
-3. Test your agents and workflows using the generated API endpoints
-
-For more information about available API endpoints, see the [Server documentation](https://mastra.ai/docs/deployment/mastra-server).
-
-## Connecting your client
-
-Update your client application to use the Lambda function URL:
-
-```typescript
-import { MastraClient } from '@mastra/client-js'
+   docker push \
+     "$AWS_ACCOUNT_ID.dkr.ecr.$AWS_REGION.amazonaws.com/$PROJECT_NAME":latest
+   ```
 
-const mastraClient = new MastraClient({
-  baseUrl: 'https://your-function-url.lambda-url.us-east-1.on.aws',
-})
-```
+## Create the Lambda function
 
-## Troubleshooting
+1. Navigate to the [AWS Lambda Console](https://console.aws.amazon.com/lambda/) and click **Create function**. Make sure you have the same region selected as where you created your ECR repository.
 
-### Function timeout errors
+2. Select **Container image** and configure the function:
 
-If your Lambda function times out:
+   - **Function name**: Enter a name (e.g. `mastra-app`)
+   - **Container image URI**: Click **Browse images**, select your ECR repository, and choose the `latest` tag
+   - **Architecture**: Select **arm64**
 
-- Increase the timeout value in **Configuration** > **General configuration**
-- Optimize your Mastra application for faster cold starts
-- Consider using provisioned concurrency for consistent performance
+   Click **Create function** to create the Lambda function.
 
-### Memory issues
+3. Configure memory and timeout. Go to **Configuration** > **General configuration** and click **Edit**:
 
-If you encounter memory-related errors:
+   - **Memory**: 512 MB (adjust based on your application needs)
+   - **Timeout**: 1 minute or higher (the default 3 seconds is too low for most Mastra applications)
 
-- Increase the memory allocation in **Configuration** > **General configuration**
-- Monitor memory usage in CloudWatch Logs
-- Optimize your application's memory usage
+   Click **Save**.
 
-### CORS issues
+4. Add environment variables. Go to **Configuration** > **Environment variables** and click **Edit**. Add the variables your Mastra application needs:
 
-If you encounter CORS errors when accessing endpoints but not the home page:
+   - `OPENAI_API_KEY`: Your OpenAI API key (if using OpenAI)
+   - `ANTHROPIC_API_KEY`: Your Anthropic API key (if using Anthropic)
+   - Other provider-specific API keys as needed (e.g. `TURSO_DATABASE_URL` and `TURSO_AUTH_TOKEN` if using LibSQL with Turso)
 
-- Verify CORS headers are properly set in your Mastra server configuration
-- Check the Lambda Function URL CORS configuration
-- Ensure your client is making requests to the correct URL
+   Click **Save**.
 
-### Container image issues
+5. Enable a Function URL for external access. Go to **Configuration** > **Function URL** and click **Create function URL**:
 
-If the Lambda function fails to start:
+   - **Auth type**: Select **NONE** for public access
 
-- Verify the Docker image builds successfully locally
-- Check that the `CMD` instruction in your Dockerfile is correct
-- Review CloudWatch Logs for container startup errors
-- Ensure the Lambda Web Adapter is properly installed in the container
+   - Under **Additional settings**, check **Configure cross-origin resource sharing (CORS)**, then configure:
 
-## Production considerations
+     - **Allow origin**: `*`
+     - **Allow headers**: `content-type` (`x-amzn-request-context` is also required when used with services like CloudFront/API Gateway)
+     - **Allow methods**: `*`
 
-For production deployments:
+   Click **Save**.
 
-### Security
+## Verify your deployment
 
-- Restrict CORS origins to your trusted domains
-- Use AWS IAM roles for secure access to other AWS services
-- Store sensitive environment variables in AWS Secrets Manager or Parameter Store
+1. Copy the **Function URL** from the Lambda console and visit `<your-function-url>/api/agents` in your browser. You should see a JSON list of your agents.
 
-### Monitoring
+2. You can now call your Mastra endpoints over HTTP.
 
-- Enable CloudWatch monitoring for your Lambda function
-- Set up CloudWatch alarms for errors and performance metrics
-- Use AWS X-Ray for distributed tracing
+   > **Warning:** For production deployments, set up [authentication](https://mastra.ai/docs/server/auth) before exposing your endpoints publicly, restrict CORS origins to your trusted domains, use AWS IAM roles for secure access to other AWS services, and store sensitive environment variables in AWS Secrets Manager or Parameter Store.
 
-### Scaling
+## Next steps
 
-- Configure provisioned concurrency for predictable performance
-- Monitor concurrent executions and adjust limits as needed
-- Consider using Application Load Balancer for more complex routing needs
+This guide provides a quickstart for deploying Mastra to AWS Lambda. For production workloads, consider enabling [CloudWatch monitoring](https://docs.aws.amazon.com/lambda/latest/dg/monitoring-cloudwatchlogs.html) for your Lambda function, setting up [AWS X-Ray](https://docs.aws.amazon.com/lambda/latest/dg/services-xray.html) for distributed tracing, and configuring [provisioned concurrency](https://docs.aws.amazon.com/lambda/latest/dg/provisioned-concurrency.html) for consistent performance.
 
-## Next steps
+## Related
 
-- [Mastra Client SDK](https://mastra.ai/reference/client-js/mastra-client)
+- [Deployment overview](https://mastra.ai/docs/deployment/overview)
+- [Mastra server](https://mastra.ai/docs/server/mastra-server)
+- [Server adapters](https://mastra.ai/docs/server/server-adapters)
 - [AWS Lambda documentation](https://docs.aws.amazon.com/lambda/)
 - [AWS Lambda Web Adapter](https://github.com/awslabs/aws-lambda-web-adapter)

package/.docs/guides/deployment/azure-app-services.md

@@ -1,27 +1,26 @@
-# Azure App Services
+# Deploy Mastra to Azure App Services
 
 Deploy your Mastra applications to Azure App Services.
 
-> **Note:** This guide assumes your Mastra application has been created using the default `npx create-mastra@latest` command. For more information on how to create a new Mastra application, refer to our [getting started guide](https://mastra.ai/guides/getting-started/quickstart)
+> **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.
 
-> **Warning:** Azure App Services uses an ephemeral filesystem for some pricing tiers. Remove any usage of [LibSQLStore](https://mastra.ai/reference/storage/libsql) with file URLs from your Mastra configuration. Use in-memory storage (`:memory:`) or external storage providers like Turso, PostgreSQL, or Upstash.
+## Before you begin
 
-## Prerequisites
+You'll need:
 
+- A [Mastra application](https://mastra.ai/guides/getting-started/quickstart)
 - An [Azure account](https://azure.microsoft.com/) with an active subscription
 - A [GitHub repository](https://github.com/) containing your Mastra application
-- Your Mastra application should be created using `npx create-mastra@latest`
 
-## Deployment Steps
+> **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.
 
-1. Create a new App service:
+## Create a new app service
 
-   - Log in to the [Azure Portal](https://portal.azure.com)
-   - Navigate to **[App Services](https://docs.microsoft.com/en-us/azure/app-service/)** or search for it in the top search bar
-   - Click **Create** to create a new App Service
-   - In the drop-down, select **Web App**
+In these steps you'll learn how to create a new Azure App Service for hosting your Mastra application. This will set up the necessary infrastructure and environment for your application to run.
 
-2. Configure app service settings:
+1. Log in to the [Azure Portal](https://portal.azure.com) and navigate to **[App Services](https://docs.microsoft.com/en-us/azure/app-service/)** or search for it in the top search bar. Select **Create** to create a new App Service, and in the drop-down, select **Web App**.
+
+2. Configure the app service settings:
 
    - **Subscription**: Select your Azure subscription
    - **Resource Group**: Create a new resource group or select an existing one
@@ -31,80 +30,58 @@ Deploy your Mastra applications to Azure App Services.
    - **Operating System**: Select **Linux**
    - **Region**: Choose a region close to your users
    - **Linux Plan**: You may have the option of choosing a plan depending on the region you chose, pick an appropriate one for your needs.
-   - Click **Review + Create**
-   - Wait for validation to complete, then click **Create**
+   - Select **Review + Create** and wait for validation to complete, then select **Create**.
 
-3. Wait for deployment:
+3. A new deployment has been triggered. Wait for the deployment to complete, then select **Go to resource** under the next steps section.
 
-   - Wait for the deployment to complete
-   - Once finished, click **Go to resource** under the next steps section
+4. Before setting up GitHub deployment, configure your environment variables. Navigate to **Settings** > **Environment variables** in the left sidebar. Add your required environment variables, such as:
 
-4. Before setting up deployment, configure your environment variables:
+   - Model provider API keys (e.g., `OPENAI_API_KEY`)
+   - Database connection strings
+   - Any other configuration values your Mastra application requires
 
-   - Navigate to **Settings** > **Environment variables** in the left sidebar
+   Select **Apply** to save the changes.
 
-   - Add your required environment variables such as:
+## GitHub deployment
 
-     - Model provider API keys (e.g., `OPENAI_API_KEY`)
-     - Database connection strings
-     - Any other configuration values your Mastra application requires
+In these steps, you'll connect your Azure App Service to your GitHub repository to enable continuous deployment. This means that every time you push changes to your repository, Azure will automatically build and deploy your application.
 
-   - Click **Apply** to save the changes
+1. Navigate to **Deployment Center** in the left sidebar and select **GitHub** as your source. Sign in to GitHub if you're not already authenticated with Azure.
 
-5. Setup GitHub deployment:
+   In this example, you'll keep [GitHub Actions](https://docs.github.com/en/actions) as your provider. Select your organization, repository, and branch.
 
-   - Navigate to **Deployment Center** in the left sidebar
-   - Select **GitHub** as your source
-   - Sign in to GitHub if you're not already authenticated with Azure
-   - In this example, we will keep [GitHub Actions](https://docs.github.com/en/actions) as our provider
-   - Select your organization, repository, and branch
-   - Azure will generate a GitHub workflow file and you can preview it before proceeding
-   - Click **Save** (the save button is located at the top of the page)
+   Azure will generate a GitHub workflow file and you can preview it before proceeding. Select **Save** (the save button is located at the top of the page).
 
-6. After Azure creates the workflow, it will trigger a GitHub Actions run and merge the workflow file into your branch. **Cancel this initial run** as it will fail without the necessary modifications.
+2. After Azure creates the workflow, it will trigger a GitHub Actions run and merge the workflow file into your branch. **Cancel this initial run** as it will fail without the necessary modifications.
 
    > **Warning:** The default workflow generated by Azure will fail for Mastra applications and needs to be modified.
 
    Pull the latest changes to your local repository and modify the generated workflow file (`.github/workflows/main_<your-app-name>.yml`):
 
-   1. **Update the build step**: Find the step named "npm install, build, and test" and:
-
-      - Change the step name to "npm install and build"
-      - If you haven't set up proper tests in your Mastra application, remove the `npm test` command from the run section as the default test script will fail and disrupt deployment. If you have working tests, you can keep the test command.
-
-   2. **Update the zip artifact step**: Find the "Zip artifact for deployment" step and replace the zip command with:
-
-      ```yaml
-      run: (cd .mastra/output && zip ../../release.zip -r .)
-      ```
+3. Find the step named "npm install, build, and test" and:
 
-      This ensures only the build outputs from `.mastra/output` are included in the deployment package.
+   - Change the step name to "npm install and build"
+   - If you haven't set up proper tests in your Mastra application, remove the `npm test` command from the run section as the default test script will fail and disrupt deployment. If you have working tests, you can keep the test command.
 
-7. Deploy your changes:
+4. Find the "Zip artifact for deployment" step and replace the zip command with:
 
-   - Commit and push your workflow modifications
-   - The build will be automatically triggered in the **Deployment Center** in your Azure dashboard
-   - Monitor the deployment progress until it completes successfully
+   ```yaml
+   run: (cd .mastra/output && zip ../../release.zip -r .)
+   ```
 
-8. Access your deployed application:
+   This ensures only the build outputs from `.mastra/output` are included in the deployment package.
 
-   - Once the build is successful, wait a few moments for the application to start
-   - Access your deployed application using the default URL provided in the **Overview** tab in the Azure portal
-   - Your application will be available at `https://<your-app-name>.azurewebsites.net`
+5. Commit and push your workflow modifications. The build will be automatically triggered in the **Deployment Center** in your Azure dashboard. Monitor the deployment progress until it completes successfully.
 
-## Connect to your Mastra server
+## Verify your deployment
 
-You can now connect to your Mastra server from your client application using a `MastraClient` from the `@mastra/client-js` package.
+Once the build is successful, wait a few moments for the application to start. You can access your deployed application using the default URL provided in the **Overview** tab in the Azure portal. Your application will be available at `https://<your-app-name>.azurewebsites.net`.
 
-Refer to the [`MastraClient` documentation](https://mastra.ai/reference/client-js/mastra-client) for more information.
+Copy the URL from the Azure portal and visit `https://<your-app-name>.azurewebsites.net/api/agents` in your browser. You should see a JSON list of your agents.
 
-```typescript
-import { MastraClient } from '@mastra/client-js'
+You can now call your Mastra endpoints over HTTP.
 
-const mastraClient = new MastraClient({
-  baseUrl: 'https://<your-app-name>.azurewebsites.net',
-})
-```
+> **Warning:** Set up [authentication](https://mastra.ai/docs/server/auth) before exposing your endpoints publicly.
 
 ## Next steps
 

package/.docs/guides/deployment/cloudflare.md

@@ -8,7 +8,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.
 
-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/reference/storage/libsql) with a file URL, switch to a remotely hosted database.
 
 ## Installation
 

package/.docs/guides/deployment/netlify.md

@@ -8,7 +8,7 @@ Use `@mastra/deployer-netlify` to deploy your Mastra server as serverless functi
 
 You'll need a [Mastra application](https://mastra.ai/guides/getting-started/quickstart) and a [Netlify](https://www.netlify.com/) account.
 
-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/reference/storage/libsql) with a file URL, switch to a remotely hosted database.
 
 ## Installation
 

package/.docs/guides/deployment/vercel.md

@@ -8,7 +8,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.
 
-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/reference/storage/libsql) with a file URL, switch to a remotely hosted database.
 
 ## Installation
 

package/.docs/models/gateways/netlify.md

@@ -1,6 +1,6 @@
 # Netlify
 
-Netlify AI Gateway provides unified access to multiple providers with built-in caching and observability. Access 56 models through Mastra's model router.
+Netlify AI Gateway provides unified access to multiple providers with built-in caching and observability. Access 60 models through Mastra's model router.
 
 Learn more in the [Netlify documentation](https://docs.netlify.com/build/ai-gateway/overview/).
 
@@ -88,6 +88,10 @@ ANTHROPIC_API_KEY=ant-...
 | `openai/gpt-5.2-pro-2025-12-11`                |
 | `openai/gpt-5.3-chat-latest`                   |
 | `openai/gpt-5.3-codex`                         |
+| `openai/gpt-5.4`                               |
+| `openai/gpt-5.4-2026-03-05`                    |
+| `openai/gpt-5.4-pro`                           |
+| `openai/gpt-5.4-pro-2026-03-05`                |
 | `openai/o3`                                    |
 | `openai/o3-mini`                               |
 | `openai/o4-mini`                               |

package/.docs/models/index.md

@@ -1,6 +1,6 @@
 # Model Providers
 
-Mastra provides a unified interface for working with LLMs across multiple providers, giving you access to 2609 models from 88 providers through a single API.
+Mastra provides a unified interface for working with LLMs across multiple providers, giving you access to 2613 models from 88 providers through a single API.
 
 ## Features
 

package/.docs/models/providers/anthropic.md

@@ -105,23 +105,23 @@ const response = await agent.generate("Hello!", {
 
 ### Available Options
 
-**sendReasoning?:** (`boolean | undefined`)
+**sendReasoning** (`boolean | undefined`)
 
-**structuredOutputMode?:** (`"outputFormat" | "jsonTool" | "auto" | undefined`)
+**structuredOutputMode** (`"outputFormat" | "jsonTool" | "auto" | undefined`)
 
-**thinking?:** (`{ type: "adaptive"; } | { type: "enabled"; budgetTokens?: number | undefined; } | { type: "disabled"; } | undefined`)
+**thinking** (`{ type: "adaptive"; } | { type: "enabled"; budgetTokens?: number | undefined; } | { type: "disabled"; } | undefined`)
 
-**disableParallelToolUse?:** (`boolean | undefined`)
+**disableParallelToolUse** (`boolean | undefined`)
 
-**cacheControl?:** (`{ type: "ephemeral"; ttl?: "5m" | "1h" | undefined; } | undefined`)
+**cacheControl** (`{ type: "ephemeral"; ttl?: "5m" | "1h" | undefined; } | undefined`)
 
-**container?:** (`{ id?: string | undefined; skills?: { type: "anthropic" | "custom"; skillId: string; version?: string | undefined; }[] | undefined; } | undefined`)
+**container** (`{ id?: string | undefined; skills?: { type: "anthropic" | "custom"; skillId: string; version?: string | undefined; }[] | undefined; } | undefined`)
 
-**effort?:** (`"low" | "medium" | "high" | "max" | undefined`)
+**effort** (`"low" | "medium" | "high" | "max" | undefined`)
 
-**speed?:** (`"fast" | undefined`)
+**speed** (`"fast" | undefined`)
 
-**contextManagement?:** (`{ edits: ({ type: "clear_01"; trigger?: { type: "input_tokens"; value: number; } | undefined; keep?: "all" | { type: "thinking_turns"; value: number; } | undefined; } | { type: "compact_20260112"; trigger?: { ...; } | undefined; pauseAfterCompaction?: boolean | undefined; instructions?: string | undefined; })[]; } |...`)
+**contextManagement** (`{ edits: ({ type: "clear_01"; trigger?: { type: "input_tokens"; value: number; } | undefined; keep?: "all" | { type: "thinking_turns"; value: number; } | undefined; } | { type: "compact_20260112"; trigger?: { ...; } | undefined; pauseAfterCompaction?: boolean | undefined; instructions?: string | undefined; })[]; } |...`)
 
 ## Direct Provider Installation
 

package/.docs/models/providers/deepseek.md

@@ -85,4 +85,4 @@ const response = await agent.generate("Hello!", {
 
 ### Available Options
 
-**thinking?:** (`{ type?: "enabled" | "disabled" | undefined; } | undefined`)
+**thinking** (`{ type?: "enabled" | "disabled" | undefined; } | undefined`)

package/.docs/models/providers/google.md

@@ -110,27 +110,27 @@ const response = await agent.generate("Hello!", {
 
 ### Available Options
 
-**responseModalities?:** (`("TEXT" | "IMAGE")[] | undefined`)
+**responseModalities** (`("TEXT" | "IMAGE")[] | undefined`)
 
-**thinkingConfig?:** (`{ thinkingBudget?: number | undefined; includeThoughts?: boolean | undefined; thinkingLevel?: "minimal" | "low" | "medium" | "high" | undefined; } | undefined`)
+**thinkingConfig** (`{ thinkingBudget?: number | undefined; includeThoughts?: boolean | undefined; thinkingLevel?: "minimal" | "low" | "medium" | "high" | undefined; } | undefined`)
 
-**cachedContent?:** (`string | undefined`)
+**cachedContent** (`string | undefined`)
 
-**structuredOutputs?:** (`boolean | undefined`)
+**structuredOutputs** (`boolean | undefined`)
 
-**safetySettings?:** (`{ category: "HARM_CATEGORY_UNSPECIFIED" | "HARM_CATEGORY_HATE_SPEECH" | "HARM_CATEGORY_DANGEROUS_CONTENT" | "HARM_CATEGORY_HARASSMENT" | "HARM_CATEGORY_SEXUALLY_EXPLICIT" | "HARM_CATEGORY_CIVIC_INTEGRITY"; threshold: "HARM_BLOCK_THRESHOLD_UNSPECIFIED" | ... 4 more ... | "OFF"; }[] | undefined`)
+**safetySettings** (`{ category: "HARM_CATEGORY_UNSPECIFIED" | "HARM_CATEGORY_HATE_SPEECH" | "HARM_CATEGORY_DANGEROUS_CONTENT" | "HARM_CATEGORY_HARASSMENT" | "HARM_CATEGORY_SEXUALLY_EXPLICIT" | "HARM_CATEGORY_CIVIC_INTEGRITY"; threshold: "HARM_BLOCK_THRESHOLD_UNSPECIFIED" | ... 4 more ... | "OFF"; }[] | undefined`)
 
-**threshold?:** (`"HARM_BLOCK_THRESHOLD_UNSPECIFIED" | "BLOCK_LOW_AND_ABOVE" | "BLOCK_MEDIUM_AND_ABOVE" | "BLOCK_ONLY_HIGH" | "BLOCK_NONE" | "OFF" | undefined`)
+**threshold** (`"HARM_BLOCK_THRESHOLD_UNSPECIFIED" | "BLOCK_LOW_AND_ABOVE" | "BLOCK_MEDIUM_AND_ABOVE" | "BLOCK_ONLY_HIGH" | "BLOCK_NONE" | "OFF" | undefined`)
 
-**audioTimestamp?:** (`boolean | undefined`)
+**audioTimestamp** (`boolean | undefined`)
 
-**labels?:** (`Record<string, string> | undefined`)
+**labels** (`Record<string, string> | undefined`)
 
-**mediaResolution?:** (`"MEDIA_RESOLUTION_UNSPECIFIED" | "MEDIA_RESOLUTION_LOW" | "MEDIA_RESOLUTION_MEDIUM" | "MEDIA_RESOLUTION_HIGH" | undefined`)
+**mediaResolution** (`"MEDIA_RESOLUTION_UNSPECIFIED" | "MEDIA_RESOLUTION_LOW" | "MEDIA_RESOLUTION_MEDIUM" | "MEDIA_RESOLUTION_HIGH" | undefined`)
 
-**imageConfig?:** (`{ aspectRatio?: "1:1" | "2:3" | "3:2" | "3:4" | "4:3" | "4:5" | "5:4" | "9:16" | "16:9" | "21:9" | undefined; imageSize?: "1K" | "2K" | "4K" | undefined; } | undefined`)
+**imageConfig** (`{ aspectRatio?: "1:1" | "2:3" | "3:2" | "3:4" | "4:3" | "4:5" | "5:4" | "9:16" | "16:9" | "21:9" | undefined; imageSize?: "1K" | "2K" | "4K" | undefined; } | undefined`)
 
-**retrievalConfig?:** (`{ latLng?: { latitude: number; longitude: number; } | undefined; } | undefined`)
+**retrievalConfig** (`{ latLng?: { latitude: number; longitude: number; } | undefined; } | undefined`)
 
 ## Direct Provider Installation