@mastra/mcp-docs-server 0.13.37 → 0.13.38

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

@@ -1,10 +1,8 @@
 ---
-title: Monorepo Deployment
+title: "Monorepo Deployment | Deployment | Mastra Docs"
 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.
@@ -13,50 +11,42 @@ Deploying Mastra in a monorepo follows the same approach as deploying a standalo
 
 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>
+```
+apps/
+├── api/
+│   ├── src/
+│   │   └── mastra/
+│   │       ├── agents/
+│   │       ├── tools/
+│   │       ├── workflows/
+│   │       └── index.ts
+│   ├── package.json
+│   └── tsconfig.json
+└── web/
+packages/
+├── ui/
+└── utils/
+package.json
+```
 
 ## 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>
-
+```
+api/
+├── src/
+│   └── mastra/
+├── .env
+├── package.json
+└── tsconfig.json
+```
 
 ## 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.
+The image below shows how to select `apps/api` as the project root when deploying to [Mastra Cloud](../mastra-cloud/overview). While the interface may differ between providers, the configuration remains the same.
 
-![Deployment configuration](/image/monorepo/monorepo-mastra-cloud.jpg)
+![Deployment configuration](/img/monorepo/monorepo-mastra-cloud.jpg)
 
 ## Dependency management
 
@@ -75,7 +65,7 @@ Common issues to watch for when deploying Mastra in a monorepo:
 
 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
+```typescript title="src/mastra/index.ts" showLineNumbers copy
 import { Mastra } from "@mastra/core/mastra";
 
 export const mastra = new Mastra({
@@ -83,12 +73,12 @@ export const mastra = new Mastra({
   bundler: {
     transpilePackages: ["utils"],
     externals: ["ui"],
-    sourcemap: true
-  }
+    sourcemap: true,
+  },
 });
 ```
 
-> See [Mastra Class](../../reference/core/mastra-class.mdx) for more configuration options.
+> See [Mastra Class](/reference/core/mastra-class) for more configuration options.
 
 ## Supported monorepos
 

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

@@ -1,5 +1,5 @@
 ---
-title: Deployment Overview
+title: "Deployment Overview | Deployment | Mastra Docs"
 description: Learn about different deployment options for your Mastra applications
 ---
 
@@ -9,12 +9,12 @@ Mastra offers multiple deployment options to suit your application's needs, from
 
 ## 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  |
+| 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
 
@@ -23,7 +23,7 @@ Mastra offers multiple deployment options to suit your application's needs, from
 - Node.js `v20.0` or higher
 - Bun
 - Deno
-- [Cloudflare](../deployment/serverless-platforms/cloudflare-deployer.mdx)
+- [Cloudflare](../deployment/serverless-platforms/cloudflare-deployer)
 
 ### Mastra Cloud
 
@@ -35,18 +35,18 @@ Mastra Cloud is a deployment platform that connects to your GitHub repository, a
 - Comprehensive logs and traces
 - Custom domains for each project
 
-[View Mastra Cloud documentation →](../mastra-cloud/overview.mdx)
+[View Mastra Cloud documentation →](../mastra-cloud/overview)
 
 ### 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)
+- [With Next.js](../frameworks/web-frameworks/next-js)
+- [With Astro](../frameworks/web-frameworks/astro)
 
 When integrated with a framework, Mastra typically requires no additional configuration for deployment.
 
-[View Web Framework Integration →](./web-framework.mdx)
+[View Web Framework Integration →](./web-framework)
 
 ### With a Server
 
@@ -57,7 +57,7 @@ You can deploy Mastra as a standard Node.js HTTP server, which gives you full co
 - Deploy to VMs, containers, or PaaS platforms
 - Ideal for integrating with existing Node.js applications
 
-[Server deployment guide →](./server-deployment.mdx)
+[Server deployment guide →](./server-deployment)
 
 ### Serverless Platforms
 
@@ -68,7 +68,7 @@ Mastra provides platform-specific deployers for popular serverless platforms, en
 - Simplified deployment process
 - Automatic scaling through the platform
 
-[Serverless deployment guide →](./server-deployment.mdx)
+[Serverless deployment guide →](./server-deployment)
 
 ## Client Configuration
 
@@ -79,4 +79,4 @@ Once your Mastra application is deployed, you'll need to configure your client t
 - Retries and error handling
 - Support for streaming responses
 
-[Client configuration guide →](../server-db/mastra-client.mdx)
+[Client configuration guide →](/docs/server-db/mastra-client)

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

@@ -1,10 +1,8 @@
 ---
-title: "Deploy a Mastra Server"
+title: "Deploy a Mastra Server | Deployment | Mastra Docs"
 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.
@@ -13,18 +11,16 @@ Mastra runs as a standard Node.js server and can be deployed across a wide range
 
 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>
+```
+src/
+└── mastra/
+    ├── agents/
+    ├── tools/
+    ├── workflows/
+    └── index.ts
+package.json
+tsconfig.json
+```
 
 ## Building
 
@@ -48,8 +44,8 @@ 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.
+   - **`.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.
@@ -58,12 +54,11 @@ The build process follows these steps:
 
 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>
+```
+.mastra/
+├── .build/
+└── output/
+```
 
 ### `public` folder
 

package/.docs/raw/deployment/serverless-platforms/cloudflare-deployer.mdx

@@ -1,13 +1,11 @@
 ---
-title: "Cloudflare Deployer"
+title: "CloudflareDeployer | Deployment | Mastra Docs"
 description: "Learn how to deploy a Mastra application to Cloudflare using the Mastra CloudflareDeployer"
 ---
 
-import { FileTree } from "nextra/components";
-
 # CloudflareDeployer
 
-The `CloudflareDeployer` class handles deployment of standalone Mastra applications to Cloudflare Workers. It manages configuration, deployment, and extends the base [Deployer](/reference/deployer/deployer) class with Cloudflare specific functionality.
+The `CloudflareDeployer` class handles deployment of standalone Mastra applications to Cloudflare Workers. It manages configuration, deployment, and extends the base [Deployer](/reference/deployer/) class with Cloudflare specific functionality.
 
 ## Installation
 
@@ -17,7 +15,7 @@ npm install @mastra/deployer-cloudflare@latest
 
 ## Usage example
 
-```typescript filename="src/mastra/index.ts" showLineNumbers copy
+```typescript title="src/mastra/index.ts" showLineNumbers copy
 import { Mastra } from "@mastra/core/mastra";
 import { CloudflareDeployer } from "@mastra/deployer-cloudflare";
 
@@ -56,15 +54,13 @@ npm run build && wrangler deploy --config .mastra/output/wrangler.json
 
 The build output for Mastra applications using the `CloudflareDeployer` includes all agents, tools, and workflows in your project, along with Mastra specific files required to run your application on Cloudflare.
 
-<FileTree>
-  <FileTree.Folder name=".mastra" defaultOpen>
-    <FileTree.Folder name="output" defaultOpen>
-      <FileTree.File name="index.mjs" />
-      <FileTree.File name="wrangler.json" />
-      </FileTree.Folder>
-  </FileTree.Folder>
-  <FileTree.File name="package.json" />
-</FileTree>
+```
+.mastra/
+└── output/
+    ├── index.mjs
+    └── wrangler.json
+package.json
+```
 
 The `CloudflareDeployer` automatically generates a `wrangler.json` configuration file in `.mastra/output` with the following settings:
 
@@ -73,15 +69,18 @@ The `CloudflareDeployer` automatically generates a `wrangler.json` configuration
   "name": "hello-mastra",
   "main": "./index.mjs",
   "compatibility_date": "2025-04-01",
-  "compatibility_flags": ["nodejs_compat", "nodejs_compat_populate_process_env"],
+  "compatibility_flags": [
+    "nodejs_compat",
+    "nodejs_compat_populate_process_env"
+  ],
   "observability": { "logs": { "enabled": true } },
   "vars": {
     "OPENAI_API_KEY": "...",
     "CLOUDFLARE_API_TOKEN": "..."
   }
 }
-
 ```
+
 ## Next steps
 
-- [Mastra Client SDK](/docs/client-js/overview)
+- [Mastra Client SDK](/reference/client-js/mastra-client)

package/.docs/raw/deployment/serverless-platforms/index.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Serverless Deployment"
+title: "Serverless Deployment | Deployment | Mastra Docs"
 description: "Build and deploy Mastra applications using platform-specific deployers or standard HTTP servers"
 ---
 
@@ -13,7 +13,7 @@ Standalone Mastra applications can be deployed to popular serverless platforms u
 
 Deployers **aren't** required when integrating Mastra with a framework. See [Web Framework Integration](/docs/deployment/web-framework) for more information.
 
-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 you begin, 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 --]
 });
 ```

package/.docs/raw/deployment/serverless-platforms/netlify-deployer.mdx

@@ -1,13 +1,11 @@
 ---
-title: "Netlify Deployer"
+title: "NetlifyDeployer | Deployment | Mastra Docs"
 description: "Learn how to deploy a Mastra application to Netlify using the Mastra NetlifyDeployer"
 ---
 
-import { FileTree } from "nextra/components";
-
 # NetlifyDeployer
 
-The `NetlifyDeployer` class handles deployment of standalone Mastra applications to Netlify. It manages configuration, deployment, and extends the base [Deployer](/reference/deployer/deployer) class with Netlify specific functionality.
+The `NetlifyDeployer` class handles deployment of standalone Mastra applications to Netlify. It manages configuration, deployment, and extends the base [Deployer](/reference/deployer/) class with Netlify specific functionality.
 
 ## Installation
 
@@ -17,13 +15,13 @@ npm install @mastra/deployer-netlify@latest
 
 ## Usage example
 
-```typescript filename="src/mastra/index.ts" showLineNumbers copy
+```typescript title="src/mastra/index.ts" showLineNumbers copy
 import { Mastra } from "@mastra/core/mastra";
 import { NetlifyDeployer } from "@mastra/deployer-netlify";
 
 export const mastra = new Mastra({
   // ...
-  deployer: new NetlifyDeployer()
+  deployer: new NetlifyDeployer(),
 });
 ```
 
@@ -41,10 +39,8 @@ Before your first deployment, make sure to add any environment variables used by
 
 > See [Environment variables overview](https://docs.netlify.com/environment-variables/overview/) for more details.
 
-
 Your project is now configured with automatic deployments which occur whenever you push to the configured branch of your GitHub repository.
 
-
 ## Manual deployment
 
 Manual deployments are also possible using the [Netlify CLI](https://docs.netlify.com/cli/get-started/). With the Netlify CLI installed run the following from your project root to deploy your application.
@@ -59,20 +55,15 @@ netlify deploy --prod
 
 The build output for Mastra applications using the `NetlifyDeployer` includes all agents, tools, and workflows in your project, along with Mastra specific files required to run your application on Netlify.
 
-<FileTree>
-  <FileTree.Folder name=".netlify" defaultOpen>
-    <FileTree.Folder name="v1" defaultOpen>
-      <FileTree.Folder name="functions" defaultOpen>
-        <FileTree.Folder name="api" defaultOpen>
-          <FileTree.File name="index.mjs" />
-        </FileTree.Folder>
-      </FileTree.Folder>
-    <FileTree.File name="config.json" />
-    </FileTree.Folder>
-  </FileTree.Folder>
-  <FileTree.File name="package.json" />
-</FileTree>
-
+```
+.netlify/
+└── v1/
+    ├── functions/
+    │   └── api/
+    │       └── index.mjs
+    └── config.json
+package.json
+```
 
 The `NetlifyDeployer` automatically generates a `config.json` configuration file in `.netlify/v1` with the following settings:
 
@@ -91,4 +82,4 @@ The `NetlifyDeployer` automatically generates a `config.json` configuration file
 
 ## Next steps
 
-- [Mastra Client SDK](/docs/client-js/overview)
+- [Mastra Client SDK](/reference/client-js/mastra-client)

package/.docs/raw/deployment/serverless-platforms/vercel-deployer.mdx

@@ -1,13 +1,11 @@
 ---
-title: "Vercel Deployer"
+title: "VercelDeployer | Deployment | Mastra Docs"
 description: "Learn how to deploy a Mastra application to Vercel using the Mastra VercelDeployer"
 ---
 
-import { FileTree } from "nextra/components";
-
 # VercelDeployer
 
-The `VercelDeployer` class handles deployment of standalone Mastra applications to Vercel. It manages configuration, deployment, and extends the base [Deployer](/reference/deployer/deployer) class with Vercel specific functionality.
+The `VercelDeployer` class handles deployment of standalone Mastra applications to Vercel. It manages configuration, deployment, and extends the base [Deployer](/reference/deployer/) class with Vercel specific functionality.
 
 ## Installation
 
@@ -17,13 +15,13 @@ npm install @mastra/deployer-vercel@latest
 
 ## Usage example
 
-```typescript filename="src/mastra/index.ts" showLineNumbers copy
+```typescript title="src/mastra/index.ts" showLineNumbers copy
 import { Mastra } from "@mastra/core/mastra";
 import { VercelDeployer } from "@mastra/deployer-vercel";
 
 export const mastra = new Mastra({
   // ...
-  deployer: new VercelDeployer()
+  deployer: new VercelDeployer(),
 });
 ```
 
@@ -39,12 +37,12 @@ The Vercel deployer can write a few high‑value settings into the Vercel Output
 
 Example:
 
-```ts filename="src/mastra/index.ts" showLineNumbers copy
+```ts title="src/mastra/index.ts" showLineNumbers copy
 deployer: new VercelDeployer({
   maxDuration: 600,
   memory: 1536,
   regions: ["sfo1", "iad1"],
-})
+});
 ```
 
 ## Continuous integration
@@ -75,20 +73,15 @@ npm run build && vercel --prod --prebuilt --archive=tgz
 
 The build output for Mastra applications using the `VercelDeployer` includes all agents, tools, and workflows in your project, along with Mastra specific files required to run your application on Vercel.
 
-<FileTree>
-  <FileTree.Folder name=".vercel" defaultOpen>
-    <FileTree.Folder name="output" defaultOpen>
-      <FileTree.Folder name="functions" defaultOpen>
-        <FileTree.Folder name="index.func" defaultOpen>
-          <FileTree.File name="index.mjs" />
-        </FileTree.Folder>
-      </FileTree.Folder>
-      <FileTree.File name="config.json" />
-    </FileTree.Folder>
-  </FileTree.Folder>
-  <FileTree.File name="package.json" />
-</FileTree>
-
+```
+.vercel/
+├── output/
+│   ├── functions/
+│   │   └── index.func/
+│   │       └── index.mjs
+│   └── config.json
+└── package.json
+```
 
 The `VercelDeployer` automatically generates a `config.json` configuration file in `.vercel/output` with the following settings:
 
@@ -106,4 +99,4 @@ The `VercelDeployer` automatically generates a `config.json` configuration file
 
 ## Next steps
 
-- [Mastra Client SDK](/docs/client-js/overview)
+- [Mastra Client SDK](/reference/client-js/mastra-client)

package/.docs/raw/deployment/web-framework.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Deploying Mastra with a Web Framework"
+title: "Web Framework Integration | Deployment | Mastra Docs"
 description: "Learn how Mastra can be deployed when integrated with a Web Framework"
 ---
 
@@ -16,9 +16,9 @@ When integrated with a framework, Mastra typically requires no additional config
 
 If you've integrated Mastra with Next.js [by following our guide](/docs/frameworks/web-frameworks/next-js) and plan to deploy to Vercel, no additional setup is required.
 
-The only thing to verify is that you've added the following to your `next.config.ts` and removed any usage of [LibSQLStore](/docs/deployment/deployment#libsqlstore), which is not supported in serverless environments:
+The only thing to verify is that you've added the following to your `next.config.ts` and removed any usage of [LibSQLStore](/docs/deployment/overview), which is not supported in serverless environments:
 
-```typescript {4} filename="next.config.ts" showLineNumbers copy
+```typescript {4} title="next.config.ts" showLineNumbers copy
 import type { NextConfig } from "next";
 
 const nextConfig: NextConfig = {
@@ -32,32 +32,32 @@ export default nextConfig;
 
 If you've integrated Mastra with Astro [by following our guide](/docs/frameworks/web-frameworks/astro) and plan to deploy to Vercel, no additional setup is required.
 
-The only thing to verify is that you've added the following to your `astro.config.mjs` and removed any usage of [LibSQLStore](/docs/deployment/deployment#libsqlstore), which is not supported in serverless environments:
+The only thing to verify is that you've added the following to your `astro.config.mjs` and removed any usage of [LibSQLStore](/docs/deployment/overview), which is not supported in serverless environments:
 
-```javascript {2,6,7} filename="astro.config.mjs" showLineNumbers copy
-import { defineConfig } from 'astro/config';
-import vercel from '@astrojs/vercel';
+```javascript {2,6,7} title="astro.config.mjs" showLineNumbers copy
+import { defineConfig } from "astro/config";
+import vercel from "@astrojs/vercel";
 
 export default defineConfig({
   // ...
   adapter: vercel(),
-  output: "server"
+  output: "server",
 });
 ```
 
 ## With Astro on Netlify
 
-If you've integrated Mastra with Astro [by following our guide](/docs/frameworks/web-frameworks/astro) and plan to deploy to Vercel, no additional setup is required.
+If you've integrated Mastra with Astro [by following our guide](/docs/frameworks/web-frameworks/astro) and plan to deploy to Netlify, no additional setup is required.
 
-The only thing to verify is that you've added the following to your `astro.config.mjs` and removed any usage of [LibSQLStore](/docs/deployment/deployment#libsqlstore), which is not supported in serverless environments:
+The only thing to verify is that you've added the following to your `astro.config.mjs` and removed any usage of [LibSQLStore](/docs/deployment/overview), which is not supported in serverless environments:
 
-```javascript {2,6,7} filename="astro.config.mjs" showLineNumbers copy
-import { defineConfig } from 'astro/config';
-import vercel from '@astrojs/netlify';
+```javascript {2,6,7} title="astro.config.mjs" showLineNumbers copy
+import { defineConfig } from "astro/config";
+import netlify from "@astrojs/netlify";
 
 export default defineConfig({
   // ...
   adapter: netlify(),
-  output: "server"
+  output: "server",
 });
 ```