@mastra/mcp-docs-server 0.13.11 → 0.13.12-alpha.1

package/.docs/raw/deployment/cloud-providers/aws-lambda.mdx

@@ -5,7 +5,7 @@ description: "Deploy your Mastra applications to AWS Lambda using Docker contain
 
 import { Callout, Steps } from "nextra/components";
 
-## AWS Lambda
+# 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.
@@ -17,7 +17,7 @@ This approach allows you to run your Mastra server as a containerized Lambda fun
   refer to our [getting started guide](/docs/getting-started/installation)
 </Callout>
 
-### Prerequisites
+## Prerequisites
 
 Before deploying to AWS Lambda, ensure you have:
 
@@ -26,7 +26,7 @@ Before deploying to AWS Lambda, ensure you have:
 - An AWS account with appropriate permissions for Lambda, ECR, and IAM
 - Your Mastra application configured with appropriate memory storage
 
-### Memory Configuration
+## Memory Configuration
 
 <Callout>
   AWS Lambda uses an ephemeral file system,
@@ -37,7 +37,7 @@ Before deploying to AWS Lambda, ensure you have:
 
 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)
+### Option 1: In-Memory (Simplest)
 
 ```typescript filename="src/mastra/index.ts" copy showLineNumbers
 import { LibSQLStore } from "@mastra/libsql";
@@ -47,7 +47,7 @@ const storage = new LibSQLStore({
 });
 ```
 
-#### Option 2: External Storage Providers
+### 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`:
 
@@ -62,11 +62,7 @@ const storage = new LibSQLStore({
 
 For more memory configuration options, see the [Memory documentation](/docs/memory/overview).
 
-### Creating a Dockerfile
-
-<Steps>
-
-#### Create a Dockerfile in your project root
+## Creating a Dockerfile
 
 Create a `Dockerfile` in your Mastra project root directory:
 
@@ -96,13 +92,11 @@ EXPOSE 8080
 CMD ["node", "--import=./.mastra/output/instrumentation.mjs", ".mastra/output/index.mjs"]
 ```
 
-</Steps>
-
-### Building and Deploying
+## Building and Deploying
 
 <Steps>
 
-#### Set up environment variables
+### Set up environment variables
 
 Set up your environment variables for the deployment process:
 
@@ -112,7 +106,7 @@ export AWS_REGION="us-east-1"
 export AWS_ACCOUNT_ID=$(aws sts get-caller-identity --query Account --output text)
 ```
 
-#### Build the Docker image
+### Build the Docker image
 
 Build your Docker image locally:
 
@@ -120,7 +114,7 @@ Build your Docker image locally:
 docker build -t "$PROJECT_NAME" .
 ```
 
-#### Create an ECR repository
+### Create an ECR repository
 
 Create an Amazon ECR repository to store your Docker image:
 
@@ -128,7 +122,7 @@ Create an Amazon ECR repository to store your Docker image:
 aws ecr create-repository --repository-name "$PROJECT_NAME" --region "$AWS_REGION"
 ```
 
-#### Authenticate Docker with ECR
+### Authenticate Docker with ECR
 
 Log in to Amazon ECR:
 
@@ -136,7 +130,7 @@ Log in to Amazon ECR:
 aws ecr get-login-password --region "$AWS_REGION" | docker login --username AWS --password-stdin "$AWS_ACCOUNT_ID.dkr.ecr.$AWS_REGION.amazonaws.com"
 ```
 
-#### Tag and push the image
+### Tag and push the image
 
 Tag your image with the ECR repository URI and push it:
 
@@ -145,7 +139,7 @@ docker tag "$PROJECT_NAME":latest "$AWS_ACCOUNT_ID.dkr.ecr.$AWS_REGION.amazonaws
 docker push "$AWS_ACCOUNT_ID.dkr.ecr.$AWS_REGION.amazonaws.com/$PROJECT_NAME":latest
 ```
 
-#### Create the Lambda function
+### Create the Lambda function
 
 Create a Lambda function using the AWS Console:
 
@@ -157,7 +151,7 @@ Create a Lambda function using the AWS Console:
    - **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`)
 
-#### Configure Function URL
+### Configure Function URL
 
 Enable Function URL for external access:
 
@@ -170,7 +164,7 @@ Enable Function URL for external access:
    - **Allow-Methods**: `*` (audit and restrict in production)
 5. Click **Save**
 
-#### Configure environment variables
+### Configure environment variables
 
 Add your environment variables in the Lambda function configuration:
 
@@ -181,7 +175,7 @@ Add your environment variables in the Lambda function configuration:
    - `TURSO_AUTH_TOKEN`: Your Turso auth token (if using LibSQL with Turso)
    - Other provider-specific API keys as needed
 
-#### Adjust function settings
+### Adjust function settings
 
 Configure the function's memory and timeout settings:
 
@@ -193,7 +187,7 @@ Configure the function's memory and timeout settings:
 
 </Steps>
 
-### Testing your deployment
+## Testing your deployment
 
 Once deployed, test your Lambda function:
 
@@ -203,7 +197,7 @@ Once deployed, test your Lambda function:
 
 For more information about available API endpoints, see the [Server documentation](/docs/deployment/server).
 
-### Connecting your client
+## Connecting your client
 
 Update your client application to use the Lambda function URL:
 
@@ -215,9 +209,9 @@ const mastraClient = new MastraClient({
 });
 ```
 
-### Troubleshooting
+## Troubleshooting
 
-#### Function timeout errors
+### Function timeout errors
 
 If your Lambda function times out:
 
@@ -225,7 +219,7 @@ If your Lambda function times out:
 - Optimize your Mastra application for faster cold starts
 - Consider using provisioned concurrency for consistent performance
 
-#### Memory issues
+### Memory issues
 
 If you encounter memory-related errors:
 
@@ -233,7 +227,7 @@ If you encounter memory-related errors:
 - Monitor memory usage in CloudWatch Logs
 - Optimize your application's memory usage
 
-#### CORS issues
+### CORS issues
 
 If you encounter CORS errors when accessing endpoints but not the home page:
 
@@ -241,7 +235,7 @@ If you encounter CORS errors when accessing endpoints but not the home page:
 - Check the Lambda Function URL CORS configuration
 - Ensure your client is making requests to the correct URL
 
-#### Container image issues
+### Container image issues
 
 If the Lambda function fails to start:
 
@@ -250,23 +244,23 @@ If the Lambda function fails to start:
 - Review CloudWatch Logs for container startup errors
 - Ensure the Lambda Web Adapter is properly installed in the container
 
-### Production considerations
+## Production considerations
 
 For production deployments:
 
-#### Security
+### Security
 
 - 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
 
-#### Monitoring
+### Monitoring
 
 - Enable CloudWatch monitoring for your Lambda function
 - Set up CloudWatch alarms for errors and performance metrics
 - Use AWS X-Ray for distributed tracing
 
-#### Scaling
+### Scaling
 
 - Configure provisioned concurrency for predictable performance
 - Monitor concurrent executions and adjust limits as needed

package/.docs/raw/deployment/cloud-providers/azure-app-services.mdx

@@ -5,7 +5,7 @@ description: "Deploy your Mastra applications to Azure App Services."
 
 import { Callout, Steps } from "nextra/components";
 
-## Azure App Services
+# Azure App Services
 
 Deploy your Mastra applications to Azure App Services.
 
@@ -16,24 +16,24 @@ Deploy your Mastra applications to Azure App Services.
   refer to our [getting started guide](/docs/getting-started/installation)
 </Callout>
 
-### Prerequisites
+## Prerequisites
 
 - 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
+## Deployment Steps
 
 <Steps>
 
-#### 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**
 
-#### Configure App Service settings
+### Configure App Service settings
 
 - **Subscription**: Select your Azure subscription
 - **Resource Group**: Create a new resource group or select an existing one
@@ -46,12 +46,12 @@ Deploy your Mastra applications to Azure App Services.
 - Click **Review + Create**
 - Wait for validation to complete, then click **Create**
 
-#### Wait for deployment
+### Wait for deployment
 
 - Wait for the deployment to complete
 - Once finished, click **Go to resource** under the next steps section
 
-#### Configure environment variables
+### Configure environment variables
 
 Before setting up deployment, configure your environment variables:
 
@@ -62,7 +62,7 @@ Before setting up deployment, configure your environment variables:
   - Any other configuration values your Mastra application requires
 - Click **Apply** to save the changes
 
-#### Set up GitHub deployment
+### Set up GitHub deployment
 
 - Navigate to **Deployment Center** in the left sidebar
 - Select **GitHub** as your source
@@ -72,7 +72,7 @@ Before setting up deployment, configure your environment variables:
 - 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)
 
-#### Modify the GitHub workflow
+### Modify the GitHub workflow
 
 <Callout type="warning">
 The default workflow generated by Azure will fail for Mastra applications and needs to be modified.
@@ -94,13 +94,13 @@ Pull the latest changes to your local repository and modify the generated workfl
 
    This ensures only the build outputs from `.mastra/output` are included in the deployment package.
 
-#### Deploy your changes
+### Deploy your changes
 
 - 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
 
-#### Access your application
+### Access your application
 
 - 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
@@ -108,7 +108,7 @@ Pull the latest changes to your local repository and modify the generated workfl
 
 </Steps>
 
-### Connect to your Mastra server
+## Connect to your Mastra server
 
 You can now connect to your Mastra server from your client application using a `MastraClient` from the `@mastra/client-js` package.
 

package/.docs/raw/deployment/cloud-providers/digital-ocean.mdx

@@ -5,7 +5,7 @@ description: "Deploy your Mastra applications to Digital Ocean."
 
 import { Callout, Steps, Tabs } from "nextra/components";
 
-## Digital Ocean
+# Digital Ocean
 
 Deploy your Mastra applications to Digital Ocean's App Platform and Droplets.
 
@@ -20,31 +20,31 @@ Deploy your Mastra applications to Digital Ocean's App Platform and Droplets.
 
 <Tabs.Tab>
 
-### App Platform
+## App Platform
 
-#### Prerequisites [#app-platform-prerequisites]
+### Prerequisites [#app-platform-prerequisites]
 
 - A Git repository containing your Mastra application. This can be a [GitHub](https://github.com/) repository, [GitLab](https://gitlab.com/) repository, or any other compatible source provider.
 - A [Digital Ocean account](https://www.digitalocean.com/)
 
-#### Deployment Steps
+### Deployment Steps
 
 <Steps>
 
-#### Create a new App
+### Create a new App
 
 - Log in to your [Digital Ocean dashboard](https://cloud.digitalocean.com/).
 - Navigate to the [App Platform](https://docs.digitalocean.com/products/app-platform/) service.
 - Select your source provider and create a new app.
 
-#### Configure Deployment Source
+### Configure Deployment Source
 
 - Connect and select your repository. You may also choose a container image or a sample app.
 - Select the branch you want to deploy from.
 - Configure the source directory if necessary. If your Mastra application uses the default directory structure, no action is required here.
 - Head to the next step.
 
-#### Configure Resource Settings and Environment Variables
+### Configure Resource Settings and Environment Variables
 
 - A Node.js build should be detected automatically.
 - Add any required environment variables for your Mastra application. This includes API keys, database URLs, and other configuration values.
@@ -52,7 +52,7 @@ Deploy your Mastra applications to Digital Ocean's App Platform and Droplets.
 - Other things you may optionally configure include, the region of your resource, the unique app name, and what project the resource belongs to.
 - Once you're done, you may create the app after reviewing your configuration and pricing estimates.
 
-#### Deployment
+### Deployment
 
 - Your app will be built and deployed automatically.
 - Digital Ocean will provide you with a URL to access your deployed application.
@@ -72,11 +72,11 @@ such as `LibSQLStore` with a file URL.
 
 <Tabs.Tab>
 
-### Droplets
+## Droplets
 
 Deploy your Mastra application to Digital Ocean's Droplets.
 
-#### Prerequisites [#droplets-prerequisites]
+### Prerequisites [#droplets-prerequisites]
 
 - A [Digital Ocean account](https://www.digitalocean.com/)
 - A [Droplet](https://docs.digitalocean.com/products/droplets/) running Ubuntu 24+
@@ -85,11 +85,11 @@ Deploy your Mastra application to Digital Ocean's Droplets.
 - SSL certificate configured (e.g., using [Let's Encrypt](https://letsencrypt.org/))
 - Node.js 18+ installed on your droplet
 
-#### Deployment Steps
+### Deployment Steps
 
 <Steps>
 
-#### Clone your Mastra application
+### Clone your Mastra application
 
 Connect to your Droplet and clone your repository:
 
@@ -117,13 +117,13 @@ Navigate to the repository directory:
 cd "<your-repository>"
 ```
 
-#### Install dependencies
+### Install dependencies
 
 ```bash copy
 npm install
 ```
 
-#### Set up environment variables
+### Set up environment variables
 
 Create a `.env` file and add your environment variables:
 
@@ -138,13 +138,13 @@ OPENAI_API_KEY=<your-openai-api-key>
 # Add other required environment variables
 ```
 
-#### Build the application
+### Build the application
 
 ```bash copy
 npm run build
 ```
 
-#### Run the application
+### Run the application
 
 ```bash copy
 node --import=./.mastra/output/instrumentation.mjs --env-file=".env" .mastra/output/index.mjs
@@ -160,7 +160,7 @@ Your Mastra application will run on port 4111 by default. Ensure your reverse pr
 
 </Tabs>
 
-### Connect to your Mastra server
+## Connect to your Mastra server
 
 You can now connect to your Mastra server from your client application using a `MastraClient` from the `@mastra/client-js` package.
 

package/.docs/raw/getting-started/templates.mdx

@@ -83,7 +83,7 @@ After installation:
 
 ## Available Templates
 
-Browse available templates in the [templates directory](https://github.com/mastra-ai/mastra/tree/main/templates) on GitHub.
+Browse available templates in the [templates directory](https://mastra.ai/templates).
 
 ## Next Steps
 

package/.docs/raw/rag/vector-databases.mdx

@@ -114,7 +114,15 @@ await store.upsert({
 ```ts filename="vector-store.ts" showLineNumbers copy
 import { ChromaVector } from '@mastra/chroma'
 
-const store = new ChromaVector()
+// Running Chroma locally
+// const store = new ChromaVector()
+
+// Running on Chroma Cloud
+const store = new ChromaVector({
+  apiKey: process.env.CHROMA_API_KEY,
+  tenant: process.env.CHROMA_TENANT,
+  database: process.env.CHROMA_DATABASE
+})
 
 await store.createIndex({
   indexName: "myCollection",

package/.docs/raw/reference/agents/agent.mdx

@@ -13,7 +13,7 @@ The `Agent` class is the foundation for creating AI agents in Mastra. It provide
 import { openai } from "@ai-sdk/openai";
 import { Agent } from "@mastra/core/agent";
 
-const agent = new Agent({
+export const agent = new Agent({
   name: "test-agent",
   instructions: 'message for agent',
   model: openai("gpt-4o")
@@ -116,9 +116,15 @@ const agent = new Agent({
     },
     {
       name: "inputProcessors",
-      type: "InputProcessor[] | ({ runtimeContext: RuntimeContext }) => InputProcessor[] | Promise<InputProcessor[]>",
+      type: "Processor[] | ({ runtimeContext: RuntimeContext }) => Processor[] | Promise<Processor[]>",
       isOptional: true,
-      description: "Input processors that can modify or validate messages before they are processed by the agent.",
+      description: "Input processors that can modify or validate messages before they are processed by the agent. Must implement the `processInput` function.",
+    },
+    {
+      name: "outputProcessors",
+      type: "Processor[] | ({ runtimeContext: RuntimeContext }) => Processor[] | Promise<Processor[]>",
+      isOptional: true,
+      description: "Output processors that can modify or validate messages from the agent, before it is sent to the client. Must implement either (or both) of the `processOutputResult` and `processOutputStream` functions.",
     },
   ]}
 />

package/.docs/raw/reference/agents/generate.mdx

@@ -48,12 +48,72 @@ await agent.generate("message for agent");
       isOptional: true,
       description: "Additional context messages to provide to the agent.",
     },
+    {
+      name: "structuredOutput",
+      type: "StructuredOutputOptions<S extends ZodTypeAny = ZodTypeAny>",
+      isOptional: true,
+      description: "Enables structured output generation with better developer experience. Automatically creates and uses a StructuredOutputProcessor internally.",
+      properties: [
+        {
+          parameters: [{
+            name: "schema",
+            type: "z.ZodSchema<S>",
+            isOptional: false,
+            description: "Zod schema to validate the output against."
+          }]
+        },
+        {
+          parameters: [{
+            name: "model",
+            type: "MastraLanguageModel",
+            isOptional: false,
+            description: "Model to use for the internal structuring agent."
+          }]
+        },
+        {
+          parameters: [{
+            name: "errorStrategy",
+            type: "'strict' | 'warn' | 'fallback'",
+            isOptional: true,
+            description: "Strategy when parsing or validation fails. Defaults to 'strict'."
+          }]
+        },
+        {
+          parameters: [{
+            name: "fallbackValue",
+            type: "<S extends ZodTypeAny>",
+            isOptional: true,
+            description: "Fallback value when errorStrategy is 'fallback'."
+          }]
+        },
+        {
+          parameters: [{
+            name: "instructions",
+            type: "string",
+            isOptional: true,
+            description: "Custom instructions for the structuring agent."
+          }]
+        },
+      ]
+    },
+    {
+      name: "outputProcessors",
+      type: "Processor[]",
+      isOptional: true,
+      description: "Overrides the output processors set on the agent. Output processors that can modify or validate messages from the agent before they are returned to the user. Must implement either (or both) of the `processOutputResult` and `processOutputStream` functions.",
+    },
+    {
+      name: "inputProcessors",
+      type: "Processor[]",
+      isOptional: true,
+      description: "Overrides the input processors set on the agent. Input processors that can modify or validate messages before they are processed by the agent. Must implement the `processInput` function.",
+    },
     {
       name: "experimental_output",
       type: "Zod schema | JsonSchema7",
       isOptional: true,
       description:
-        "Enables structured output generation alongside text generation and tool calls. The model will generate responses that conform to the provided schema.",
+        "Note, the preferred route is to use the `structuredOutput` property. Enables structured output generation alongside text generation and tool calls. The model will generate responses that conform to the provided schema.",
     },
     {
       name: "instructions",
@@ -344,7 +404,7 @@ await agent.generate("message for agent");
       name: "object",
       type: "object",
       isOptional: true,
-      description: "The generated structured response. Present when a schema is provided via `output` or `experimental_output`.",
+      description: "The generated structured response. Present when a schema is provided via `output`, `structuredOutput`, or `experimental_output`.",
     },
     {
       name: "toolCalls",
@@ -376,6 +436,9 @@ await agent.generate("message for agent");
 ## Extended usage example
 
 ```typescript showLineNumbers copy
+import { z } from "zod";
+import { ModerationProcessor, TokenLimiterProcessor } from "@mastra/core/processors";
+
 await agent.generate(
   [
     { role: "user", content: "message for agent" },
@@ -406,7 +469,21 @@ await agent.generate(
       openai: {
         reasoningEffort: "high"
       }
-    }
+    },
+    // Structured output with better DX
+    structuredOutput: {
+      schema: z.object({
+        sentiment: z.enum(['positive', 'negative', 'neutral']),
+        confidence: z.number(),
+      }),
+      model: openai("gpt-4o-mini"),
+      errorStrategy: 'warn',
+    },
+    // Output processors for response validation
+    outputProcessors: [
+      new ModerationProcessor({ model: openai("gpt-4.1-nano") }),
+      new TokenLimiterProcessor({ maxTokens: 1000 }),
+    ],
   }
 );
 ```

package/.docs/raw/reference/agents/getDefaultGenerateOptions.mdx

@@ -5,7 +5,7 @@ description: "Documentation for the `Agent.getDefaultGenerateOptions()` method i
 
 # Agent.getDefaultGenerateOptions()
 
-The `.getDefaultGenerateOptions()` method retrieves the default generation options configured for an agent, resolving them if they're a function. These options are used as the base configuration for all `generate()` calls unless overridden.
+Agents can be configured with default generation options for controlling model behavior, output formatting and tool and workflow calls. The `.getDefaultGenerateOptions()` method retrieves these defaults, resolving them if they are functions. These options apply to all `generate()`calls unless overridden and are useful for inspecting an agent’s unknown defaults.
 
 ## Usage example
 

package/.docs/raw/reference/agents/getDefaultStreamOptions.mdx

@@ -5,7 +5,7 @@ description: "Documentation for the `Agent.getDefaultStreamOptions()` method in
 
 # Agent.getDefaultStreamOptions()
 
-The `.getDefaultStreamOptions()` method retrieves the default streaming options configured for an agent, resolving them if they're a function. These options are used as the base configuration for all `stream()` calls unless overridden.
+Agents can be configured with default streaming options for memory usage, output format, and iteration steps. The `.getDefaultStreamOptions()` method returns these defaults, resolving them if they are functions. These options apply to all `stream()` calls unless overridden and are useful for inspecting an agent’s unknown defaults.
 
 ## Usage example
 

package/.docs/raw/reference/agents/getDefaultVNextStreamOptions.mdx

@@ -5,7 +5,7 @@ description: "Documentation for the `Agent.getDefaultVNextStreamOptions()` metho
 
 # Agent.getDefaultVNextStreamOptions()
 
-The `.getDefaultVNextStreamOptions()` method retrieves the default vNext streaming options configured for an agent, resolving them if they're a function. These options are used as the base configuration for all `streamVNext()` calls unless overridden.
+Agents can be configured with default streaming options for memory usage, output format, and iteration steps. The `.getDefaultVNextStreamOptions()` method returns these defaults, resolving them if they are functions. These options apply to all `streamVNext()` calls unless overridden and are useful for inspecting an agent’s unknown defaults.
 
 ## Usage example
 

package/.docs/raw/reference/agents/getLLM.mdx

@@ -33,7 +33,7 @@ await agent.getLLM();
   content={[
     {
       name: "llm",
-      type: "MastraLLMBase | Promise<MastraLLMBase>",
+      type: "MastraLLMV1 | Promise<MastraLLMV1>",
       description: "The language model instance configured for the agent, either as a direct instance or a promise that resolves to the LLM.",
     },
   ]}