@mastra/mcp-docs-server 0.0.0-error-handler-fix-20251020202607 → 0.0.0-execa-dynamic-import-20260304221256

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

@@ -1,137 +0,0 @@
----
-title: "Azure App Services"
-description: "Deploy your Mastra applications to Azure App Services."
----
-
-import { Callout, Steps } from "nextra/components";
-
-# 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>
-
-## 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
-
-<Steps>
-
-### 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
-
-- **Subscription**: Select your Azure subscription
-- **Resource Group**: Create a new resource group or select an existing one
-- **Instance name**: Enter a unique name for your app (this will be part of your URL)
-- **Publish**: Select **Code**
-- **Runtime stack**: Select **Node 22 LTS**
-- **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**
-
-### Wait for deployment
-
-- Wait for the deployment to complete
-- Once finished, click **Go to resource** under the next steps section
-
-### Configure environment variables
-
-Before setting up deployment, configure your environment variables:
-
-- Navigate to **Settings** > **Environment variables** in the left sidebar
-- Add your required environment variables such as:
-  - Model provider API keys (e.g., `OPENAI_API_KEY`)
-  - Database connection strings
-  - Any other configuration values your Mastra application requires
-- Click **Apply** to save the changes
-
-### Set up GitHub deployment
-
-- 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)
-
-### Modify the GitHub workflow
-
-<Callout type="warning">
-The default workflow generated by Azure will fail for Mastra applications and needs to be modified.
-</Callout>
-
-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.
-
-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 .)
-   ```
-
-   This ensures only the build outputs from `.mastra/output` are included in the deployment package.
-
-### 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
-
-- 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`
-
-</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.
-
-```typescript copy showLineNumbers
-import { MastraClient } from "@mastra/client-js";
-
-const mastraClient = new MastraClient({
-  baseUrl: "https://<your-app-name>.azurewebsites.net",
-});
-```
-
-<Callout>
-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)
-- [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,206 +0,0 @@
----
-title: "Digital Ocean"
-description: "Deploy your Mastra applications to Digital Ocean."
----
-
-import { Callout, Steps, Tabs } from "nextra/components";
-
-# 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>
-
-<Tabs items={["App Platform", "Droplets"]}>
-
-<Tabs.Tab>
-
-## App Platform
-
-### 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
-
-<Steps>
-
-### 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
-
-- 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
-
-- 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>
-
-- Add any required environment variables for your Mastra application. This includes API keys, database URLs, and other configuration values.
-- You may choose to configure the size of your resource here.
-- 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
-
-- Your app will be built and deployed automatically.
-- Digital Ocean will provide you with a URL to access your deployed application.
-
-</Steps>
-
-You can now access your deployed application at the URL provided by Digital Ocean.
-
-<Callout>
-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>
-
-<Tabs.Tab>
-
-## Droplets
-
-Deploy your Mastra application to Digital Ocean's Droplets.
-
-### Prerequisites [#droplets-prerequisites]
-
-- A [Digital Ocean account](https://www.digitalocean.com/)
-- A [Droplet](https://docs.digitalocean.com/products/droplets/) running Ubuntu 24+
-- A domain name with an A record pointing to your droplet
-- A reverse proxy configured (e.g., using [nginx](https://nginx.org/))
-- SSL certificate configured (e.g., using [Let's Encrypt](https://letsencrypt.org/))
-- Node.js 18+ installed on your droplet
-
-### Deployment Steps
-
-<Steps>
-
-### Clone your Mastra application
-
-Connect to your Droplet and clone your repository:
-
-<Tabs items={["Public Repository", "Private Repository"]}>
-<Tabs.Tab>
-
-```bash copy
-git clone https://github.com/<your-username>/<your-repository>.git
-```
-
-</Tabs.Tab>
-
-<Tabs.Tab>
-
-```bash copy
-git clone https://<your-username>:<your-personal-access-token>@github.com/<your-username>/<your-repository>.git
-```
-
-</Tabs.Tab>
-</Tabs>
-
-Navigate to the repository directory:
-
-```bash copy
-cd "<your-repository>"
-```
-
-### Install dependencies
-
-```bash copy
-npm install
-```
-
-### Set up environment variables
-
-Create a `.env` file and add your environment variables:
-
-```bash copy
-touch .env
-```
-
-Edit the `.env` file and add your environment variables:
-
-```bash copy
-OPENAI_API_KEY=<your-openai-api-key>
-# Add other required environment variables
-```
-
-### Build the application
-
-```bash copy
-npm run build
-```
-
-### Run the application
-
-```bash copy
-node --import=./.mastra/output/instrumentation.mjs --env-file=".env" .mastra/output/index.mjs
-```
-
-<Callout>
-Your Mastra application will run on port 4111 by default. Ensure your reverse proxy is configured to forward requests to this port.
-</Callout>
-
-</Steps>
-
-</Tabs.Tab>
-
-</Tabs>
-
-## 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/server-db/mastra-client) for more information.
-
-```typescript copy showLineNumbers
-import { MastraClient } from "@mastra/client-js";
-
-const mastraClient = new MastraClient({
-  baseUrl: "https://<your-domain-name>",
-});
-```
-
-## Next steps
-
-- [Mastra Client SDK](/docs/client-js/overview)
-- [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,52 +0,0 @@
----
-title: "Cloud Providers"
-description: "Deploy your Mastra applications to popular cloud providers."
----
-
-## Cloud Providers
-
-Standalone Mastra applications can be deployed to popular cloud providers, see one of the following guides for more information:
-
-- [Amazon EC2](/docs/deployment/cloud-providers/amazon-ec2)
-- [AWS Lambda](/docs/deployment/cloud-providers/aws-lambda)
-- [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.
-
-## Prerequisites
-
-Before deploying to a cloud provider, ensure you have:
-
-- A [Mastra application](/docs/getting-started/installation)
-- Node.js `v20.0` or higher
-- A GitHub repository for your application (required for most CI/CD setups)
-- Domain name management access (for SSL and HTTPS)
-- Basic familiarity with server setup (e.g. Nginx, environment variables)
-
-## LibSQLStore
-
-`LibSQLStore` writes to the local filesystem, which is not supported in cloud environments that use ephemeral file systems. If you're deploying to platforms like **AWS Lambda**, **Azure App Services**, or **Digital Ocean App Platform**, you **must remove** all usage of `LibSQLStore`.
-
-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
-export const mastra = new Mastra({
-  // ...
-  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 --]
-});
-```
-
-```typescript filename="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 --]
-});
-```

package/.docs/raw/deployment/monorepo.mdx

@@ -1,107 +0,0 @@
----
-title: Monorepo Deployment
-description: Learn how to deploy Mastra applications that are part of a monorepo setup
----
-
-import { FileTree } from "nextra/components";
-
-# Monorepo Deployment
-
-Deploying Mastra in a monorepo follows the same approach as deploying a standalone application. While some [Cloud](./cloud-providers/) or [Serverless Platform](./serverless-platforms/) providers may introduce extra requirements, the core setup is the same.
-
-## Example monorepo
-
-In this example, the Mastra application is located at `apps/api`.
-
-<FileTree>
-  <FileTree.Folder name="apps" defaultOpen>
-    <FileTree.Folder name="api" defaultOpen>
-      <FileTree.Folder name="src" defaultOpen>
-        <FileTree.Folder name="mastra" defaultOpen>
-          <FileTree.Folder name="agents" />
-          <FileTree.Folder name="tools" />
-          <FileTree.Folder name="workflows" />
-          <FileTree.File name="index.ts" />
-        </FileTree.Folder>
-      </FileTree.Folder>
-      <FileTree.File name="package.json" />
-      <FileTree.File name="tsconfig.json" />
-    </FileTree.Folder>
-    <FileTree.Folder name="web" />
-  </FileTree.Folder>
-  <FileTree.Folder name="packages" defaultOpen>
-    <FileTree.Folder name="ui" />
-    <FileTree.Folder name="utils" />
-  </FileTree.Folder>
-  <FileTree.File name="package.json" />
-</FileTree>
-
-## Environment variables
-
-Environment variables like `OPENAI_API_KEY` should be stored in an `.env` file at the root of the Mastra application `(apps/api)`, for example:
-
-<FileTree>
-  <FileTree.Folder name="api" defaultOpen>
-    <FileTree.Folder name="src" defaultOpen>
-      <FileTree.Folder name="mastra" />
-    </FileTree.Folder>
-    <FileTree.File name=".env" />
-    <FileTree.File name="package.json" />
-    <FileTree.File name="tsconfig.json" />
-  </FileTree.Folder>
-</FileTree>
-
-
-## Deployment configuration
-
-The image below shows how to select `apps/api` as the project root when deploying to [Mastra Cloud](../mastra-cloud/overview.mdx). While the interface may differ between providers, the configuration remains the same.
-
-![Deployment configuration](/image/monorepo/monorepo-mastra-cloud.jpg)
-
-## Dependency management
-
-In a monorepo, keep dependencies consistent to avoid version conflicts and build errors.
-
-- Use a **single lockfile** at the project root so all packages resolve the same versions.
-- Align versions of **shared libraries** (like Mastra or frameworks) to prevent duplicates.
-
-## Deployment pitfalls
-
-Common issues to watch for when deploying Mastra in a monorepo:
-
-- **Wrong project root**: make sure the correct package (e.g. `apps/api`) is selected as the deploy target.
-
-## Bundler options
-
-Use `transpilePackages` to compile TypeScript workspace packages or libraries. List package names exactly as they appear in each `package.json`. Use `externals` to exclude dependencies resolved at runtime, and `sourcemap` to emit readable stack traces.
-
-```typescript filename="src/mastra/index.ts" showLineNumbers copy
-import { Mastra } from "@mastra/core/mastra";
-
-export const mastra = new Mastra({
-  // ...
-  bundler: {
-    transpilePackages: ["utils"],
-    externals: ["ui"],
-    sourcemap: true
-  }
-});
-```
-
-> See [Mastra Class](../../reference/core/mastra-class.mdx) for more configuration options.
-
-## Supported monorepos
-
-Mastra works with:
-
-- npm workspaces
-- pnpm workspaces
-- Yarn workspaces
-- Turborepo
-
-Known limitations:
-
-- Bun workspaces — partial support; known issues
-- Nx — You can use Nx's [supported dependency strategies](https://nx.dev/concepts/decisions/dependency-management) but you need to have `package.json` files inside your workspace packages
-
-> If you are experiencing issues with monorepos see our: [Monorepos Support mega issue](https://github.com/mastra-ai/mastra/issues/6852).

package/.docs/raw/deployment/overview.mdx

@@ -1,82 +0,0 @@
----
-title: Deployment Overview
-description: Learn about different deployment options for your Mastra applications
----
-
-# Deployment Overview
-
-Mastra offers multiple deployment options to suit your application's needs, from fully-managed solutions to self-hosted options, and web framework integrations. This guide will help you understand the available deployment paths and choose the right one for your project.
-
-## Choosing a Deployment Option
-
-| Option                   | Best For                                                      | Key Benefits                                                    |
-| ------------------------ | ------------------------------------------------------------- | -------------------------------------------------------------- |
-| **Mastra Cloud**         | Teams wanting to ship quickly without infrastructure concerns | Fully-managed, automatic scaling, built-in observability       |
-| **Framework Deployment** | Teams already using Next.js, Astro etc                          | Simplify deployment with a unified codebase for frontend and backend  |
-| **Server Deployment**    | Teams needing maximum control and customization               | Full control, custom middleware, integrate with existing apps  |
-| **Serverless Platforms** | Teams already using Vercel, Netlify, or Cloudflare             | Platform integration, simplified deployment, automatic scaling  |
-
-## Deployment Options
-
-### Runtime support
-
-- Node.js `v20.0` or higher
-- Bun
-- Deno
-- [Cloudflare](../deployment/serverless-platforms/cloudflare-deployer.mdx)
-
-### Mastra Cloud
-
-Mastra Cloud is a deployment platform that connects to your GitHub repository, automatically deploys on code changes, and provides monitoring tools. It includes:
-
-- GitHub repository integration
-- Deployment on git push
-- Agent testing interface
-- Comprehensive logs and traces
-- Custom domains for each project
-
-[View Mastra Cloud documentation →](../mastra-cloud/overview.mdx)
-
-### With a Web Framework
-
-Mastra can be integrated with a variety of web frameworks. For example, see one of the following for a detailed guide.
-
-- [With Next.js](../frameworks/web-frameworks/next-js.mdx)
-- [With Astro](../frameworks/web-frameworks/astro.mdx)
-
-When integrated with a framework, Mastra typically requires no additional configuration for deployment.
-
-[View Web Framework Integration →](./web-framework.mdx)
-
-### With a Server
-
-You can deploy Mastra as a standard Node.js HTTP server, which gives you full control over your infrastructure and deployment environment.
-
-- Custom API routes and middleware
-- Configurable CORS and authentication
-- Deploy to VMs, containers, or PaaS platforms
-- Ideal for integrating with existing Node.js applications
-
-[Server deployment guide →](./server-deployment.mdx)
-
-### Serverless Platforms
-
-Mastra provides platform-specific deployers for popular serverless platforms, enabling you to deploy your application with minimal configuration.
-
-- Deploy to Cloudflare Workers, Vercel, or Netlify
-- Platform-specific optimizations
-- Simplified deployment process
-- Automatic scaling through the platform
-
-[Serverless deployment guide →](./server-deployment.mdx)
-
-## Client Configuration
-
-Once your Mastra application is deployed, you'll need to configure your client to communicate with it. The Mastra Client SDK provides a simple and type-safe interface for interacting with your Mastra server.
-
-- Type-safe API interactions
-- Authentication and request handling
-- Retries and error handling
-- Support for streaming responses
-
-[Client configuration guide →](../server-db/mastra-client.mdx)

package/.docs/raw/deployment/server-deployment.mdx

@@ -1,86 +0,0 @@
----
-title: "Deploy a Mastra Server"
-description: "Learn how to deploy a Mastra server with build settings and deployment options."
----
-
-import { FileTree } from "nextra/components";
-
-# Deploy a Mastra Server
-
-Mastra runs as a standard Node.js server and can be deployed across a wide range of environments.
-
-## Default project structure
-
-The [getting started guide](/docs/getting-started/installation) scaffolds a project with sensible defaults to help you begin quickly. By default, the CLI organizes application files under the `src/mastra/` directory, resulting in a structure similar to the following:
-
-<FileTree>
-  <FileTree.Folder name="src" defaultOpen>
-    <FileTree.Folder name="mastra" defaultOpen>
-      <FileTree.Folder name="agents" />
-      <FileTree.Folder name="tools" />
-      <FileTree.Folder name="workflows" />
-      <FileTree.File name="index.ts" />
-    </FileTree.Folder>
-  </FileTree.Folder>
-  <FileTree.File name="package.json" />
-  <FileTree.File name="tsconfig.json" />
-</FileTree>
-
-## Building
-
-The `mastra build` command starts the build process:
-
-```bash copy
-mastra build
-```
-
-### Customizing the input directory
-
-If your Mastra files are located elsewhere, use the `--dir` flag to specify the custom location. The `--dir` flag tells Mastra where to find your entry point file (`index.ts` or `index.js`) and related directories.
-
-```bash copy
-mastra build --dir ./my-project/mastra
-```
-
-## Build process
-
-The build process follows these steps:
-
-1. **Locates entry file**: Finds `index.ts` or `index.js` in your specified directory (default: `src/mastra/`).
-2. **Creates build directory**: Generates a `.mastra/` directory containing:
-    - **`.build`**: Contains dependency analysis, bundled dependencies, and build configuration files.
-    - **`output`**: Contains the production-ready application bundle with `index.mjs`, `instrumentation.mjs`, and project-specific files.
-3. **Copies static assets**: Copies the `public/` folder contents to the `output` directory for serving static files.
-4. **Bundles code**: Uses Rollup with tree shaking and source maps for optimization.
-5. **Generates server**: Creates a [Hono](https://hono.dev) HTTP server ready for deployment.
-
-### Build output structure
-
-After building, Mastra creates a `.mastra/` directory with the following structure:
-
-<FileTree>
-  <FileTree.Folder name=".mastra" defaultOpen>
-    <FileTree.Folder name=".build" />
-    <FileTree.Folder name="output" />
-  </FileTree.Folder>
-</FileTree>
-
-### `public` folder
-
-If a `public` folder exists in `src/mastra`, its contents are copied into the `.build/output` directory during the build process.
-
-## Running the Server
-
-Start the HTTP server:
-
-```bash copy
-node .mastra/output/index.mjs
-```
-
-## Enable Telemetry
-
-To enable telemetry and observability, load the instrumentation file:
-
-```bash copy
-node --import=./.mastra/output/instrumentation.mjs .mastra/output/index.mjs
-```