@mastra/mcp-docs-server 1.0.0-beta.9 → 1.0.0

package/.docs/raw/guides/build-your-ui/assistant-ui.mdx

@@ -44,7 +44,7 @@ project-root
 
 Bootstrap your Mastra server:
 
-```bash copy
+```bash
 npx create-mastra@beta
 ```
 
@@ -52,7 +52,7 @@ This command will launch an interactive wizard to help you scaffold a new Mastra
 
 Navigate to your newly created Mastra server directory:
 
-```bash copy
+```bash
 cd mastra-server # Replace with the actual directory name you provided
 ```
 
@@ -84,13 +84,13 @@ Ensure that you have set the appropriate environment variables for your LLM prov
 
 Create a chat route for the Assistant UI frontend by using the `chatRoute()` helper from `@mastra/ai-sdk`. Add it to your Mastra project:
 
-```bash copy
+```bash
 npm install @mastra/ai-sdk@beta
 ```
 
 In your `src/mastra/index.ts` file, register the chat route:
 
-```typescript copy title="src/mastra/index.ts" {2,7-13}
+```typescript title="src/mastra/index.ts" {2,7-13}
 import { Mastra } from '@mastra/core/mastra';
 import { chatRoute } from '@mastra/ai-sdk';
 // Rest of the imports...
@@ -115,7 +115,7 @@ This will make all agents available in AI SDK-compatible formats, including the
 
 Run the Mastra server using the following command:
 
-```bash copy
+```bash
 npm run dev
 ```
 
@@ -127,13 +127,13 @@ By default, the Mastra server will run on `http://localhost:4111`. Keep this ser
 
 Go up one directory to your project root.
 
-```bash copy
+```bash
 cd ..
 ```
 
 Create a new `assistant-ui` project with the following command.
 
-```bash copy
+```bash
 npx assistant-ui@latest create
 ```
 
@@ -175,7 +175,7 @@ Now, the Assistant UI frontend will send chat requests directly to your running
 
 You're ready to connect the pieces! Make sure both the Mastra server and the Assistant UI frontend are running. Start the Next.js development server:
 
-```bash copy
+```bash
 npm run dev
 ```
 

package/.docs/raw/guides/build-your-ui/copilotkit.mdx

@@ -48,7 +48,7 @@ project-root
 
 Bootstrap your Mastra server:
 
-```bash copy
+```bash
 npx create-mastra@latest
 ```
 
@@ -56,7 +56,7 @@ This command will launch an interactive wizard to help you scaffold a new Mastra
 
 Navigate to your newly created Mastra server directory:
 
-```bash copy
+```bash
 cd mastra-server # Replace with the actual directory name you provided
 ```
 
@@ -88,13 +88,13 @@ Ensure that you have set the appropriate environment variables for your LLM prov
 
 Create a chat route for the CopilotKit frontend by using the `registerCopilotKit()` helper from `@ag-ui/mastra`. Add it to your Mastra project (and its peer dependencies):
 
-```bash copy
+```bash
 npm install --legacy-peer-deps @ag-ui/mastra @copilotkit/runtime @ag-ui/core @ag-ui/client @ag-ui/encoder @ag-ui/langgraph @ag-ui/proto
 ```
 
 In your `src/mastra/index.ts` file, register the chat route:
 
-```typescript copy title="src/mastra/index.ts" {2,7-19}
+```typescript title="src/mastra/index.ts" {2,7-19}
 import { Mastra } from '@mastra/core/mastra';
 import { registerCopilotKit } from '@ag-ui/mastra/copilotkit';
 // Rest of the imports...
@@ -125,7 +125,7 @@ This will make the `weatherAgent` available at `/chat` in a CopilotKit-compatibl
 
 Run the Mastra server using the following command:
 
-```bash copy
+```bash
 npm run dev
 ```
 
@@ -137,19 +137,19 @@ By default, the Mastra server will run on `http://localhost:4111`. Keep this ser
 
 Go up one directory to your project root.
 
-```bash copy
+```bash
 cd ..
 ```
 
 Create a new Next.js project with the name `my-copilot-app`:
 
-```bash copy
+```bash
 npx create-next-app@latest my-copilot-app
 ```
 
 Navigate to your newly created Next.js project directory:
 
-```bash copy
+```bash
 cd my-copilot-app
 ```
 
@@ -159,13 +159,13 @@ cd my-copilot-app
 
 Install the CopilotKit UI packages which you'll use to display a chat interface:
 
-```bash copy
+```bash
 npm install @copilotkit/react-ui @copilotkit/react-core
 ```
 
 Open the home route of the Next.js app (usually `app/page.tsx` or `src/app/page.tsx`) and replace the existing contents with the following code to set up a basic CopilotKit chat interface:
 
-```typescript copy title="app/page.tsx"
+```typescript title="app/page.tsx"
 import { CopilotChat } from "@copilotkit/react-ui";
 import { CopilotKit } from "@copilotkit/react-core";
 import "@copilotkit/react-ui/styles.css";
@@ -193,7 +193,7 @@ export default function Home() {
 
 You're ready to connect the pieces! Make sure both the Mastra server and the CopilotKit frontend are running. Start the Next.js development server:
 
-```bash copy
+```bash
 npm run dev
 ```
 
@@ -204,3 +204,24 @@ You should now be able to chat with your agent in the browser.
 </Steps>
 
 Congratulations! You have successfully integrated Mastra with CopilotKit using a separate server approach. Your CopilotKit frontend now communicates with a standalone Mastra agent server.
+
+## Deployment
+
+When deploying your Mastra server with CopilotKit, you must exclude `@copilotkit/runtime` from the bundle. This package contains dependencies that are not compatible with bundling and will cause 500 errors if included.
+
+:::note
+
+This issue doesn't occur during development with `mastra dev` since it doesn't require bundling. However, anyone running `mastra build` for deployment will encounter this issue.
+
+:::
+
+Add the `@copilotkit/runtime` package to your bundler externals configuration:
+
+```typescript title="src/mastra/index.ts" 
+export const mastra = new Mastra({
+  bundler: {
+    externals: ['@copilotkit/runtime'],
+  },
+ // Rest of the configuration...
+});
+```

package/.docs/raw/{deployment/cloud-providers → guides/deployment}/amazon-ec2.mdx

@@ -39,7 +39,7 @@ Connect to your EC2 instance and clone your repository:
 <Tabs>
   <TabItem value="public" label="Public Repository">
 
-```bash copy
+```bash
 git clone https://github.com/<your-username>/<your-repository>.git
 ```
 
@@ -47,7 +47,7 @@ git clone https://github.com/<your-username>/<your-repository>.git
 
   <TabItem value="private" label="Private Repository">
 
-```bash copy
+```bash
 git clone https://<your-username>:<your-personal-access-token>@github.com/<your-username>/<your-repository>.git
 ```
 
@@ -56,7 +56,7 @@ git clone https://<your-username>:<your-personal-access-token>@github.com/<your-
 
 Navigate to the repository directory:
 
-```bash copy
+```bash
 cd "<your-repository>"
 ```
 
@@ -66,7 +66,7 @@ cd "<your-repository>"
 
 Install dependencies:
 
-```bash copy
+```bash
 npm install
 ```
 
@@ -76,13 +76,13 @@ npm install
 
 Create a `.env` file and add your environment variables:
 
-```bash copy
+```bash
 touch .env
 ```
 
 Edit the `.env` file and add your environment variables:
 
-```bash copy
+```bash
 OPENAI_API_KEY=<your-openai-api-key>
 # Add other required environment variables
 ```
@@ -93,7 +93,7 @@ OPENAI_API_KEY=<your-openai-api-key>
 
 Build the application:
 
-```bash copy
+```bash
 npm run build
 ```
 
@@ -103,7 +103,7 @@ npm run build
 
 Run the application:
 
-```bash copy
+```bash
 node --env-file=".env" .mastra/output/index.mjs
 ```
 
@@ -121,7 +121,7 @@ You can now connect to your Mastra server from your client application using a `
 
 Refer to the [`MastraClient` documentation](/reference/v1/client-js/mastra-client) for more information.
 
-```typescript copy showLineNumbers
+```typescript
 import { MastraClient } from "@mastra/client-js";
 
 const mastraClient = new MastraClient({

package/.docs/raw/{deployment/cloud-providers → guides/deployment}/aws-lambda.mdx

@@ -29,18 +29,15 @@ Before deploying to AWS Lambda, ensure you have:
 
 ## Memory Configuration
 
-:::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.
+:::warning
+AWS Lambda uses an ephemeral file system, meaning that any files written to the file system are short-lived and may be lost. Remove any usage of [LibSQLStore](/reference/v1/storage/libsql) with file URLs from your Mastra configuration. Use in-memory storage (`:memory:`) or external storage providers like Turso, PostgreSQL, or Upstash.
 :::
 
 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 title="src/mastra/index.ts" copy showLineNumbers
+```typescript title="src/mastra/index.ts"
 import { LibSQLStore } from "@mastra/libsql";
 
 const storage = new LibSQLStore({
@@ -53,7 +50,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 title="src/mastra/index.ts" copy showLineNumbers
+```typescript title="src/mastra/index.ts"
 import { LibSQLStore } from "@mastra/libsql";
 
 const storage = new LibSQLStore({
@@ -69,7 +66,7 @@ For more memory configuration options, see the [Memory documentation](/docs/v1/m
 
 Create a `Dockerfile` in your Mastra project root directory:
 
-```dockerfile title="Dockerfile" copy showLineNumbers
+```dockerfile title="Dockerfile"
 FROM node:22-alpine
 
 WORKDIR /app
@@ -103,7 +100,7 @@ CMD ["node", ".mastra/output/index.mjs"]
 
 Set up your environment variables for the deployment process:
 
-```bash copy
+```bash
 export PROJECT_NAME="your-mastra-app"
 export AWS_REGION="us-east-1"
 export AWS_ACCOUNT_ID=$(aws sts get-caller-identity --query Account --output text)
@@ -115,7 +112,7 @@ export AWS_ACCOUNT_ID=$(aws sts get-caller-identity --query Account --output tex
 
 Build your Docker image locally:
 
-```bash copy
+```bash
 docker build -t "$PROJECT_NAME" .
 ```
 
@@ -125,7 +122,7 @@ docker build -t "$PROJECT_NAME" .
 
 Create an Amazon ECR repository to store your Docker image:
 
-```bash copy
+```bash
 aws ecr create-repository --repository-name "$PROJECT_NAME" --region "$AWS_REGION"
 ```
 
@@ -135,7 +132,7 @@ aws ecr create-repository --repository-name "$PROJECT_NAME" --region "$AWS_REGIO
 
 Log in to Amazon ECR:
 
-```bash copy
+```bash
 aws ecr get-login-password --region "$AWS_REGION" | docker login --username AWS --password-stdin "$AWS_ACCOUNT_ID.dkr.ecr.$AWS_REGION.amazonaws.com"
 ```
 
@@ -145,7 +142,7 @@ aws ecr get-login-password --region "$AWS_REGION" | docker login --username AWS
 
 Tag your image with the ECR repository URI and push it:
 
-```bash copy
+```bash
 docker tag "$PROJECT_NAME":latest "$AWS_ACCOUNT_ID.dkr.ecr.$AWS_REGION.amazonaws.com/$PROJECT_NAME":latest
 docker push "$AWS_ACCOUNT_ID.dkr.ecr.$AWS_REGION.amazonaws.com/$PROJECT_NAME":latest
 ```
@@ -189,7 +186,7 @@ Add your environment variables in the Lambda function configuration:
 2. Add the required variables for your Mastra application:
    - `OPENAI_API_KEY`: Your OpenAI API key (if using OpenAI)
    - `ANTHROPIC_API_KEY`: Your Anthropic API key (if using Anthropic)
-   - `TURSO_AUTH_TOKEN`: Your Turso auth token (if using LibSQL with Turso)
+   - `TURSO_AUTH_TOKEN`: Your Turso auth token (if using libSQL with Turso)
    - Other provider-specific API keys as needed
 
 </StepItem>
@@ -216,13 +213,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/v1/deployment/building-mastra).
+For more information about available API endpoints, see the [Server documentation](/docs/v1/deployment/mastra-server).
 
 ## Connecting your client
 
 Update your client application to use the Lambda function URL:
 
-```typescript title="src/client.ts" copy showLineNumbers
+```typescript title="src/client.ts"
 import { MastraClient } from "@mastra/client-js";
 
 const mastraClient = new MastraClient({

package/.docs/raw/{deployment/cloud-providers → guides/deployment}/azure-app-services.mdx

@@ -17,6 +17,10 @@ For more information on how to create a new Mastra application,
 refer to our [getting started guide](/guides/v1/getting-started/quickstart)
 :::
 
+:::warning
+Azure App Services uses an ephemeral filesystem for some pricing tiers. Remove any usage of [LibSQLStore](/reference/v1/storage/libsql) with file URLs from your Mastra configuration. Use in-memory storage (`:memory:`) or external storage providers like Turso, PostgreSQL, or Upstash.
+:::
+
 ## Prerequisites
 
 - An [Azure account](https://azure.microsoft.com/) with an active subscription
@@ -143,7 +147,7 @@ You can now connect to your Mastra server from your client application using a `
 
 Refer to the [`MastraClient` documentation](/reference/v1/client-js/mastra-client) for more information.
 
-```typescript copy showLineNumbers
+```typescript
 import { MastraClient } from "@mastra/client-js";
 
 const mastraClient = new MastraClient({
@@ -151,12 +155,6 @@ const mastraClient = new MastraClient({
 });
 ```
 
-:::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.
-:::
-
 ## Next steps
 
 - [Mastra Client SDK](/reference/v1/client-js/mastra-client)

package/.docs/raw/{deployment/cloud-providers → guides/deployment}/cloudflare-deployer.mdx

@@ -7,20 +7,23 @@ description: "Learn how to deploy a Mastra application to Cloudflare using the M
 
 The `CloudflareDeployer` class handles deployment of standalone Mastra applications to Cloudflare Workers. It manages configuration, deployment, and extends the base [Deployer](/reference/v1/deployer/) class with Cloudflare specific functionality.
 
+:::warning
+Cloudflare Workers do not support filesystem access. Remove any usage of [LibSQLStore](/reference/v1/storage/libsql) with file URLs from your Mastra configuration. Use in-memory storage (`:memory:`) or external storage providers like Turso, PostgreSQL, or Upstash.
+:::
+
 ## Installation
 
-```bash copy
+```bash
 npm install @mastra/deployer-cloudflare@beta
 ```
 
 ## Usage example
 
-```typescript title="src/mastra/index.ts" showLineNumbers copy
+```typescript title="src/mastra/index.ts"
 import { Mastra } from "@mastra/core";
 import { CloudflareDeployer } from "@mastra/deployer-cloudflare";
 
 export const mastra = new Mastra({
-  // ...
   deployer: new CloudflareDeployer({
     projectName: "hello-mastra",
     env: {
@@ -38,13 +41,13 @@ Manual deployments are also possible using the [Cloudflare Wrangler CLI](https:/
 
 With the Wrangler CLI installed, login and authenticate with your Cloudflare logins:
 
-```bash copy
+```bash
 npx wrangler login
 ```
 
 Run the following to build and deploy your application to Cloudflare
 
-```bash copy
+```bash
 npm run build && wrangler deploy --config .mastra/output/wrangler.json
 ```
 

package/.docs/raw/{deployment/cloud-providers → guides/deployment}/digital-ocean.mdx

@@ -19,18 +19,18 @@ For more information on how to create a new Mastra application,
 refer to our [getting started guide](/guides/v1/getting-started/quickstart)
 :::
 
+## Instructions
+
 <Tabs>
 
   <TabItem value="app-platform" label="App Platform">
 
-## App Platform
-
-### Prerequisites
+<h3>Prerequisites</h3>
 
 - 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
+<h3>Deployment Steps</h3>
 
 <Steps>
 
@@ -97,22 +97,17 @@ Deployment
 
 You can now access your deployed application at the URL provided by Digital Ocean.
 
-:::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.
+:::warning
+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. Remove any usage of [LibSQLStore](/reference/v1/storage/libsql) with file URLs from your Mastra configuration. Use in-memory storage (`:memory:`) or external storage providers like Turso, PostgreSQL, or Upstash.
 :::
 
   </TabItem>
 
   <TabItem value="droplets" label="Droplets">
 
-## Droplets
-
 Deploy your Mastra application to Digital Ocean's Droplets.
 
-### Prerequisites
+<h3>Prerequisites</h3>
 
 - A [Digital Ocean account](https://www.digitalocean.com/)
 - A [Droplet](https://docs.digitalocean.com/products/droplets/) running Ubuntu 24+
@@ -121,7 +116,7 @@ Deploy your Mastra application to Digital Ocean's Droplets.
 - SSL certificate configured (e.g., using [Let's Encrypt](https://letsencrypt.org/))
 - Node.js 22.13.0 or later installed on your droplet
 
-### Deployment Steps
+<h3>Deployment Steps</h3>
 
 <Steps>
 
@@ -134,7 +129,7 @@ Connect to your Droplet and clone your repository:
 <Tabs>
   <TabItem value="public" label="Public Repository">
 
-```bash copy
+```bash
 git clone https://github.com/<your-username>/<your-repository>.git
 ```
 
@@ -142,7 +137,7 @@ git clone https://github.com/<your-username>/<your-repository>.git
 
   <TabItem value="private" label="Private Repository">
 
-```bash copy
+```bash
 git clone https://<your-username>:<your-personal-access-token>@github.com/<your-username>/<your-repository>.git
 ```
 
@@ -151,7 +146,7 @@ git clone https://<your-username>:<your-personal-access-token>@github.com/<your-
 
 Navigate to the repository directory:
 
-```bash copy
+```bash
 cd "<your-repository>"
 ```
 
@@ -161,7 +156,7 @@ cd "<your-repository>"
 
 Install dependencies
 
-```bash copy
+```bash
 npm install
 ```
 
@@ -173,13 +168,13 @@ Set up environment variables
 
 Create a `.env` file and add your environment variables:
 
-```bash copy
+```bash
 touch .env
 ```
 
 Edit the `.env` file and add your environment variables:
 
-```bash copy
+```bash
 OPENAI_API_KEY=<your-openai-api-key>
 # Add other required environment variables
 ```
@@ -190,7 +185,7 @@ OPENAI_API_KEY=<your-openai-api-key>
 
 Build the application
 
-```bash copy
+```bash
 npm run build
 ```
 
@@ -200,7 +195,7 @@ npm run build
 
 Run the application
 
-```bash copy
+```bash
 node --env-file=".env" .mastra/output/index.mjs
 ```
 
@@ -220,9 +215,9 @@ Your Mastra application will run on port 4111 by default. Ensure your reverse pr
 
 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/v1/server-db/mastra-client) for more information.
+Refer to the [`MastraClient` documentation](/docs/v1/server/mastra-client) for more information.
 
-```typescript copy showLineNumbers
+```typescript
 import { MastraClient } from "@mastra/client-js";
 
 const mastraClient = new MastraClient({

package/.docs/raw/guides/deployment/index.mdx

@@ -0,0 +1,32 @@
+---
+title: "Cloud Providers | Deployment"
+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](/guides/v1/deployment/amazon-ec2)
+- [AWS Lambda](/guides/v1/deployment/aws-lambda)
+- [Azure App Services](/guides/v1/deployment/azure-app-services)
+- [Cloudflare](/guides/v1/deployment/cloudflare-deployer)
+- [Digital Ocean](/guides/v1/deployment/digital-ocean)
+- [Netlify](/guides/v1/deployment/netlify-deployer)
+- [Vercel](/guides/v1/deployment/vercel-deployer)
+
+For self-hosted Node.js server deployment, see the [Creating A Mastra Server](/docs/v1/deployment/mastra-server) guide.
+
+## Prerequisites
+
+Before deploying to a cloud provider, ensure you have:
+
+- A [Mastra application](/guides/v1/getting-started/quickstart)
+- Node.js `v22.13.0` or later
+- 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)
+
+:::warning
+`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, Netlify, Azure App Services, or Digital Ocean App Platform, you must remove all usage of [LibSQLStore](/reference/v1/storage/libsql) with file URLs. Use in-memory storage (`:memory:`) or external storage providers like Turso, PostgreSQL, or Upstash.
+:::