@mastra/mcp-docs-server 0.13.37 → 0.13.38

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

@@ -1,21 +1,22 @@
 ---
-title: "AWS Lambda"
+title: "AWS Lambda | Deployment | Mastra Docs"
 description: "Deploy your Mastra applications to AWS Lambda using Docker containers and the AWS Lambda Web Adapter."
 ---
 
-import { Callout, Steps } from "nextra/components";
+import Steps from "@site/src/components/Steps";
+import StepItem from "@site/src/components/StepItem";
 
 # 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.
 
-<Callout>
-  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](/docs/getting-started/installation)
-</Callout>
+:::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](/docs/getting-started/installation)
+:::
 
 ## Prerequisites
 
@@ -28,18 +29,18 @@ Before deploying to AWS Lambda, ensure you have:
 
 ## Memory Configuration
 
-<Callout>
-  AWS Lambda uses an ephemeral file system,
-  meaning that any files written to the file system are short-lived and may be lost.
-  Avoid using a Mastra storage provider that uses the file system,
-  such as `LibSQLStore` with a file URL.
-</Callout>
+:::note
+AWS Lambda uses an ephemeral file system,
+meaning that any files written to the file system are short-lived and may be lost.
+Avoid using a Mastra storage provider that uses the file system,
+such as `LibSQLStore` with a file URL.
+:::
 
 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 filename="src/mastra/index.ts" copy showLineNumbers
+```typescript title="src/mastra/index.ts" copy showLineNumbers
 import { LibSQLStore } from "@mastra/libsql";
 
 const storage = new LibSQLStore({
@@ -51,7 +52,7 @@ const storage = new LibSQLStore({
 
 For persistent memory across Lambda invocations, use external storage providers like `LibSQLStore` with Turso or other storage providers like `PostgreStore`:
 
-```typescript filename="src/mastra/index.ts" copy showLineNumbers
+```typescript title="src/mastra/index.ts" copy showLineNumbers
 import { LibSQLStore } from "@mastra/libsql";
 
 const storage = new LibSQLStore({
@@ -66,7 +67,7 @@ For more memory configuration options, see the [Memory documentation](/docs/memo
 
 Create a `Dockerfile` in your Mastra project root directory:
 
-```dockerfile filename="Dockerfile" copy showLineNumbers
+```dockerfile title="Dockerfile" copy showLineNumbers
 FROM node:22-alpine
 
 WORKDIR /app
@@ -96,7 +97,7 @@ CMD ["node", "--import=./.mastra/output/instrumentation.mjs", ".mastra/output/in
 
 <Steps>
 
-### Set up environment variables
+<StepItem>
 
 Set up your environment variables for the deployment process:
 
@@ -106,7 +107,9 @@ export AWS_REGION="us-east-1"
 export AWS_ACCOUNT_ID=$(aws sts get-caller-identity --query Account --output text)
 ```
 
-### Build the Docker image
+</StepItem>
+
+<StepItem>
 
 Build your Docker image locally:
 
@@ -114,7 +117,9 @@ Build your Docker image locally:
 docker build -t "$PROJECT_NAME" .
 ```
 
-### Create an ECR repository
+</StepItem>
+
+<StepItem>
 
 Create an Amazon ECR repository to store your Docker image:
 
@@ -122,7 +127,9 @@ 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
+</StepItem>
+
+<StepItem>
 
 Log in to Amazon ECR:
 
@@ -130,7 +137,9 @@ 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
+</StepItem>
+
+<StepItem>
 
 Tag your image with the ECR repository URI and push it:
 
@@ -139,7 +148,9 @@ 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
+</StepItem>
+
+<StepItem>
 
 Create a Lambda function using the AWS Console:
 
@@ -151,7 +162,9 @@ 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
+</StepItem>
+
+<StepItem>
 
 Enable Function URL for external access:
 
@@ -164,7 +177,9 @@ Enable Function URL for external access:
    - **Allow-Methods**: `*` (audit and restrict in production)
 5. Click **Save**
 
-### Configure environment variables
+</StepItem>
+
+<StepItem>
 
 Add your environment variables in the Lambda function configuration:
 
@@ -175,7 +190,9 @@ 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
+</StepItem>
+
+<StepItem>
 
 Configure the function's memory and timeout settings:
 
@@ -185,6 +202,8 @@ Configure the function's memory and timeout settings:
    - **Timeout**: 30 seconds (adjust based on your application needs)
    - **Ephemeral storage**: 512 MB (optional, for temporary files)
 
+</StepItem>
+
 </Steps>
 
 ## Testing your deployment
@@ -195,13 +214,13 @@ Once deployed, test your Lambda function:
 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](/docs/deployment/server).
+For more information about available API endpoints, see the [Server documentation](/docs/deployment/server-deployment).
 
 ## Connecting your client
 
 Update your client application to use the Lambda function URL:
 
-```typescript filename="src/client.ts" copy showLineNumbers
+```typescript title="src/client.ts" copy showLineNumbers
 import { MastraClient } from "@mastra/client-js";
 
 const mastraClient = new MastraClient({
@@ -268,6 +287,6 @@ For production deployments:
 
 ## Next steps
 
-- [Mastra Client SDK](/docs/client-js/overview)
+- [Mastra Client SDK](/reference/client-js/mastra-client)
 - [AWS Lambda documentation](https://docs.aws.amazon.com/lambda/)
 - [AWS Lambda Web Adapter](https://github.com/awslabs/aws-lambda-web-adapter)

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

@@ -1,20 +1,21 @@
 ---
-title: "Azure App Services"
+title: "Azure App Services | Deployment | Mastra Docs"
 description: "Deploy your Mastra applications to Azure App Services."
 ---
 
-import { Callout, Steps } from "nextra/components";
+import Steps from "@site/src/components/Steps";
+import StepItem from "@site/src/components/StepItem";
 
 # Azure App Services
 
 Deploy your Mastra applications to Azure App Services.
 
-<Callout>
-  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](/docs/getting-started/installation)
-</Callout>
+:::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](/docs/getting-started/installation)
+:::
 
 ## Prerequisites
 
@@ -26,14 +27,20 @@ Deploy your Mastra applications to Azure App Services.
 
 <Steps>
 
-### Create a new App Service
+<StepItem>
+
+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
+</StepItem>
+
+<StepItem>
+
+Configure app service settings:
 
 - **Subscription**: Select your Azure subscription
 - **Resource Group**: Create a new resource group or select an existing one
@@ -46,12 +53,18 @@ Deploy your Mastra applications to Azure App Services.
 - Click **Review + Create**
 - Wait for validation to complete, then click **Create**
 
-### Wait for deployment
+</StepItem>
+
+<StepItem>
+
+Wait for deployment:
 
 - Wait for the deployment to complete
 - Once finished, click **Go to resource** under the next steps section
 
-### Configure environment variables
+</StepItem>
+
+<StepItem>
 
 Before setting up deployment, configure your environment variables:
 
@@ -62,7 +75,11 @@ 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
+</StepItem>
+
+<StepItem>
+
+Setup GitHub deployment:
 
 - Navigate to **Deployment Center** in the left sidebar
 - Select **GitHub** as your source
@@ -72,14 +89,16 @@ 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
+</StepItem>
 
-<Callout type="warning">
-The default workflow generated by Azure will fail for Mastra applications and needs to be modified.
-</Callout>
+<StepItem>
 
 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:
@@ -94,25 +113,35 @@ 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
+</StepItem>
+
+<StepItem>
+
+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
+</StepItem>
+
+<StepItem>
+
+Access your deployed 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
 - Your application will be available at `https://<your-app-name>.azurewebsites.net`
 
+</StepItem>
+
 </Steps>
 
 ## 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.
 
-Refer to the [`MastraClient` documentation](/docs/client-js/overview) for more information.
+Refer to the [`MastraClient` documentation](/reference/client-js/mastra-client) for more information.
 
 ```typescript copy showLineNumbers
 import { MastraClient } from "@mastra/client-js";
@@ -122,16 +151,15 @@ const mastraClient = new MastraClient({
 });
 ```
 
-<Callout>
+:::note
 Azure App Services uses an ephemeral file system for some pricing tiers.
 For production applications, avoid using Mastra storage providers that rely on the local file system,
 such as `LibSQLStore` with a file URL. Consider using cloud-based storage solutions instead.
-</Callout>
+:::
 
 ## Next steps
 
-- [Mastra Client SDK](/docs/client-js/overview)
+- [Mastra Client SDK](/reference/client-js/mastra-client)
 - [Configure custom domains](https://docs.microsoft.com/en-us/azure/app-service/app-service-web-tutorial-custom-domain)
 - [Enable HTTPS](https://docs.microsoft.com/en-us/azure/app-service/configure-ssl-bindings)
 - [Azure App Service documentation](https://docs.microsoft.com/en-us/azure/app-service/)
-

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

@@ -1,28 +1,31 @@
 ---
-title: "Digital Ocean"
+title: "Digital Ocean | Deployment | Mastra Docs"
 description: "Deploy your Mastra applications to Digital Ocean."
 ---
 
-import { Callout, Steps, Tabs } from "nextra/components";
+import Steps from "@site/src/components/Steps";
+import StepItem from "@site/src/components/StepItem";
+import Tabs from "@theme/Tabs";
+import TabItem from "@theme/TabItem";
 
 # Digital Ocean
 
 Deploy your Mastra applications to Digital Ocean's App Platform and Droplets.
 
-<Callout>
-  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](./../../getting-started/installation.mdx)
-</Callout>
+:::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](./../../getting-started/installation)
+:::
 
-<Tabs items={["App Platform", "Droplets"]}>
+<Tabs>
 
-<Tabs.Tab>
+  <TabItem value="app-platform" label="App Platform">
 
 ## App Platform
 
-### Prerequisites [#app-platform-prerequisites]
+### 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/)
@@ -31,45 +34,47 @@ Deploy your Mastra applications to Digital Ocean's App Platform and Droplets.
 
 <Steps>
 
-### Create a new App
+<StepItem>
+
+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
+</StepItem>
+
+<StepItem>
+
+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
+</StepItem>
+
+<StepItem>
+
+Configure Resource Settings and Environment Variables
 
 - A Node.js build should be detected automatically.
 - **Configure Build Command**: You need to add a custom build command for the app platform to build your Mastra project successfully. Set the build command based on your package manager:
 
-<Tabs items={["npm", "pnpm", "yarn", "bun"]}>
-  <Tabs.Tab>
-    ```
-    npm run build
-    ```
-  </Tabs.Tab>
-  <Tabs.Tab>
-    ```
-    pnpm build
-    ```
-  </Tabs.Tab>
-  <Tabs.Tab>
-    ```
-    yarn build
-    ```
-  </Tabs.Tab>
-  <Tabs.Tab>
-    ```
-    bun run build
-    ```
-  </Tabs.Tab>
+<Tabs>
+  <TabItem value="npm" label="npm">
+    ``` npm run build ```
+  </TabItem>
+  <TabItem value="pnpm" label="pnpm">
+    ``` pnpm build ```
+  </TabItem>
+  <TabItem value="yarn" label="yarn">
+    ``` yarn build ```
+  </TabItem>
+  <TabItem value="bun" label="bun">
+    ``` bun run build ```
+  </TabItem>
 </Tabs>
 
 - Add any required environment variables for your Mastra application. This includes API keys, database URLs, and other configuration values.
@@ -77,31 +82,37 @@ 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
+</StepItem>
+
+<StepItem>
+
+Deployment
 
 - Your app will be built and deployed automatically.
 - Digital Ocean will provide you with a URL to access your deployed application.
 
+</StepItem>
+
 </Steps>
 
 You can now access your deployed application at the URL provided by Digital Ocean.
 
-<Callout>
+:::note
 The Digital Ocean App Platform uses an ephemeral file system,
 meaning that any files written to the file system are short-lived and may be lost.
 Avoid using a Mastra storage provider that uses the file system,
 such as `LibSQLStore` with a file URL.
-</Callout>
+:::
 
-</Tabs.Tab>
+  </TabItem>
 
-<Tabs.Tab>
+  <TabItem value="droplets" label="Droplets">
 
 ## Droplets
 
 Deploy your Mastra application to Digital Ocean's Droplets.
 
-### Prerequisites [#droplets-prerequisites]
+### Prerequisites
 
 - A [Digital Ocean account](https://www.digitalocean.com/)
 - A [Droplet](https://docs.digitalocean.com/products/droplets/) running Ubuntu 24+
@@ -114,26 +125,28 @@ Deploy your Mastra application to Digital Ocean's Droplets.
 
 <Steps>
 
-### Clone your Mastra application
+<StepItem>
+
+Clone your Mastra application
 
 Connect to your Droplet and clone your repository:
 
-<Tabs items={["Public Repository", "Private Repository"]}>
-<Tabs.Tab>
+<Tabs>
+  <TabItem value="public" label="Public Repository">
 
 ```bash copy
 git clone https://github.com/<your-username>/<your-repository>.git
 ```
 
-</Tabs.Tab>
+  </TabItem>
 
-<Tabs.Tab>
+  <TabItem value="private" label="Private Repository">
 
 ```bash copy
 git clone https://<your-username>:<your-personal-access-token>@github.com/<your-username>/<your-repository>.git
 ```
 
-</Tabs.Tab>
+  </TabItem>
 </Tabs>
 
 Navigate to the repository directory:
@@ -142,13 +155,21 @@ Navigate to the repository directory:
 cd "<your-repository>"
 ```
 
-### Install dependencies
+</StepItem>
+
+<StepItem>
+
+Install dependencies
 
 ```bash copy
 npm install
 ```
 
-### Set up environment variables
+</StepItem>
+
+<StepItem>
+
+Set up environment variables
 
 Create a `.env` file and add your environment variables:
 
@@ -163,25 +184,35 @@ OPENAI_API_KEY=<your-openai-api-key>
 # Add other required environment variables
 ```
 
-### Build the application
+</StepItem>
+
+<StepItem>
+
+Build the application
 
 ```bash copy
 npm run build
 ```
 
-### Run the application
+</StepItem>
+
+<StepItem>
+
+Run the application
 
 ```bash copy
 node --import=./.mastra/output/instrumentation.mjs --env-file=".env" .mastra/output/index.mjs
 ```
 
-<Callout>
+:::note
 Your Mastra application will run on port 4111 by default. Ensure your reverse proxy is configured to forward requests to this port.
-</Callout>
+:::
+
+</StepItem>
 
 </Steps>
 
-</Tabs.Tab>
+</TabItem>
 
 </Tabs>
 
@@ -201,6 +232,6 @@ const mastraClient = new MastraClient({
 
 ## Next steps
 
-- [Mastra Client SDK](/docs/client-js/overview)
+- [Mastra Client SDK](/reference/client-js/mastra-client)
 - [Digital Ocean App Platform documentation](https://docs.digitalocean.com/products/app-platform/)
 - [Digital Ocean Droplets documentation](https://docs.digitalocean.com/products/droplets/)

package/.docs/raw/deployment/cloud-providers/index.mdx

@@ -1,9 +1,9 @@
 ---
-title: "Cloud Providers"
+title: "Cloud Providers | Deployment | Mastra Docs"
 description: "Deploy your Mastra applications to popular cloud providers."
 ---
 
-## Cloud Providers
+# Cloud Providers
 
 Standalone Mastra applications can be deployed to popular cloud providers, see one of the following guides for more information:
 
@@ -12,7 +12,7 @@ Standalone Mastra applications can be deployed to popular cloud providers, see o
 - [Digital Ocean](/docs/deployment/cloud-providers/digital-ocean)
 - [Azure App Services](/docs/deployment/cloud-providers/azure-app-services)
 
-For self-hosted Node.js server deployment, see the [Creating A Mastra Server](/docs/deployment/server) guide.
+For self-hosted Node.js server deployment, see the [Creating A Mastra Server](/docs/deployment/server-deployment) guide.
 
 ## Prerequisites
 
@@ -30,23 +30,26 @@ Before deploying to a cloud provider, ensure you have:
 
 Specifically, ensure you've removed it from both `src/mastra/index.ts` and `src/mastra/agents/weather-agent.ts`:
 
-```typescript filename="src/mastra/index.ts" showLineNumbers
+```typescript title="src/mastra/index.ts" showLineNumbers
 export const mastra = new Mastra({
   // ...
-  storage: new LibSQLStore({ // [!code --]
+  storage: new LibSQLStore({
+    // [!code --]
     // stores telemetry, evals, ... into memory storage, if it needs to persist, change to file:../mastra.db // [!code --]
     url: ":memory:", // [!code --]
-  })//[!code --]
+  }), //[!code --]
 });
 ```
 
-```typescript filename="src/mastra/agents/weather-agent.ts" showLineNumbers
+```typescript title="src/mastra/agents/weather-agent.ts" showLineNumbers
 export const weatherAgent = new Agent({
- // ..
- memory: new Memory({  // [!code --]
-   storage: new LibSQLStore({ // [!code --]
-      url: "file:../mastra.db" // path is relative to the .mastra/output directory // [!code --]
-   }) // [!code --]
- })//  [!code --]
+  // ..
+  memory: new Memory({
+    // [!code --]
+    storage: new LibSQLStore({
+      // [!code --]
+      url: "file:../mastra.db", // path is relative to the .mastra/output directory // [!code --]
+    }), // [!code --]
+  }), //  [!code --]
 });
 ```