@mastra/mcp-docs-server 0.13.2 → 0.13.3

package/.docs/organized/code-examples/workflow-with-memory.md

@@ -2,16 +2,6 @@
 ```json
 {
   "name": "examples-workflow-with-memory",
-  "type": "module",
-  "private": true,
-  "main": "index.js",
-  "scripts": {
-    "test": "echo \"Error: no test specified\" && exit 1"
-  },
-  "keywords": [],
-  "author": "",
-  "license": "MIT",
-  "description": "",
   "devDependencies": {
     "@types/node": "^20.17.57",
     "tsx": "^4.19.3",
@@ -23,18 +13,8 @@
     "@mastra/core": "latest",
     "@mastra/memory": "latest",
     "@mastra/pg": "latest"
-  },
-  "version": "0.0.1",
-  "pnpm": {
-    "overrides": {
-      "@mastra/core": "link:../../packages/core",
-      "@mastra/memory": "link:../../packages/memory",
-      "@mastra/pg": "link:../../stores/pg"
-    }
-  },
-  "packageManager": "pnpm@10.10.0+sha512.d615db246fe70f25dcfea6d8d73dee782ce23e2245e3c4f6f888249fb568149318637dca73c2c5c8ef2a4ca0d5657fb9567188bfab47f566d1ee6ce987815c39"
+  }
 }
-
 ```
 
 ### mastra/agents/index.ts

package/.docs/organized/code-examples/workflow-with-separate-steps.md

@@ -2,18 +2,6 @@
 ```json
 {
   "name": "examples-workflow-with-separate-steps",
-  "type": "module",
-  "private": true,
-  "main": "index.js",
-  "scripts": {
-    "test": "echo \"Error: no test specified\" && exit 1",
-    "dev": "mastra dev",
-    "start:workflow": "npx tsx src/index.ts"
-  },
-  "keywords": [],
-  "author": "",
-  "license": "MIT",
-  "description": "",
   "devDependencies": {
     "@types/node": "^20.17.57",
     "mastra": "latest",
@@ -23,17 +11,8 @@
   },
   "dependencies": {
     "@mastra/core": "latest"
-  },
-  "pnpm": {
-    "overrides": {
-      "@mastra/core": "link:../../packages/core",
-      "mastra": "link:../../packages/mastra"
-    }
-  },
-  "version": "0.0.1-alpha.2",
-  "packageManager": "pnpm@10.10.0+sha512.d615db246fe70f25dcfea6d8d73dee782ce23e2245e3c4f6f888249fb568149318637dca73c2c5c8ef2a4ca0d5657fb9567188bfab47f566d1ee6ce987815c39"
+  }
 }
-
 ```
 
 ### index.ts

package/.docs/raw/course/01-first-agent/11-creating-transactions-tool.md

@@ -29,7 +29,7 @@ export const getTransactionsTool = createTool({
 const getTransactions = async () => {
   // This URL points to a public Google Sheet with transaction data
   const url =
-    "https://docs.google.com/spreadsheets/d/e/2PACX-1vTQWaCzJAFsF4owWRHQRLo4G0-ERv31c74OOZFnqLiTLaP7NweoiX7IXvzQud2H6bdUPnIqZEA485Ux/pubhtml?gid=0&single=true";
+    "https://docs.google.com/spreadsheets/d/e/2PACX-1vTQWaCzJAFsF4owWRHQRLo4G0-ERv31c74OOZFnqLiTLaP7NweoiX7IXvzQud2H6bdUPnIqZEA485Ux/pub?gid=0&single=true&output=csv";
   const response = await fetch(url);
   const data = await response.text();
   return {

package/.docs/raw/course/03-agent-memory/24-working-memory-in-practice.md

@@ -12,17 +12,14 @@ By using working memory effectively, you can create agents that feel more person
 Here are some best practices for using working memory effectively:
 
 1. **Be selective about what goes into working memory**
-
    - Focus on information that will be relevant across multiple conversations
    - Don't overload working memory with transient details
 
 2. **Use clear instructions**
-
    - Give your agent explicit guidance on when and how to update working memory
    - Instruct it to check memory before asking for information the user has already provided
 
 3. **Design a thoughtful template**
-
    - Structure your template based on the specific needs of your agent
    - Include sections for different types of information
    - Use clear labels and organization to make information easy to find

package/.docs/raw/course/03-agent-memory/29-memory-best-practices.md

@@ -3,32 +3,26 @@
 As you build memory-enhanced agents, keep these best practices in mind:
 
 1. **Be selective about what goes into working memory**
-
    - Focus on information that will be relevant across multiple conversations
    - Don't overload working memory with transient details
 
 2. **Use clear instructions**
-
    - Give your agent explicit guidance on when and how to update working memory
    - Instruct it to check memory before asking for information the user has already provided
 
 3. **Choose appropriate memory parameters**
-
    - Adjust `lastMessages`, `topK`, and `messageRange` based on your use case
    - More isn't always better - larger context windows can dilute focus
 
 4. **Consider privacy implications**
-
    - Be transparent with users about what information is being stored
    - Implement appropriate security measures for sensitive information
 
 5. **Test thoroughly**
-
    - Verify that your agent correctly recalls information across different scenarios
    - Test edge cases like conflicting information or corrections
 
 6. **Design thoughtful templates**
-
    - Structure your working memory templates based on your agent's specific needs
    - Include clear sections and organization to make information easy to find
 

package/.docs/raw/deployment/cloud-providers/amazon-ec2.mdx

@@ -0,0 +1,81 @@
+---
+title: "Amazon EC2"
+description: "Deploy your Mastra applications to Amazon EC2."
+---
+
+import { Callout, Steps } from "nextra/components";
+import ServerConfig from "@/components/content-blocks/server-config.mdx";
+
+## Amazon EC2
+
+Deploy your Mastra applications to Amazon EC2 (Elastic Cloud Compute).
+
+<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>
+
+### Setting up EC2
+
+<Steps>
+
+#### Log into your AWS console
+
+Navigate to the [AWS Management Console](https://aws.amazon.com/console/) and sign in to your account.
+
+#### Navigate to EC2
+
+Head over to **All services** in the left side navigation. Under **Compute**, click on **EC2**.
+
+#### Launch a virtual server instance
+
+Click on **Launch instance** to create a new EC2 instance.
+
+#### Configure your instance details
+
+Add the following details for your instance:
+
+- **Name**: Give your instance a descriptive name
+- **Application and OS Images**: For this example, we'll use the **Amazon Linux** environment
+- **Instance type**: Select **t3.micro** (eligible for free tier)
+- **Key pair**: Select an existing key pair or create a new one for secure login
+- **Network settings**: Ensure to **allow HTTPS and HTTP traffic from the internet** by checking the appropriate boxes
+
+#### Launch your instance
+
+Review your configuration and click **Launch instance**.
+
+#### Connect to your instance
+
+You'll be redirected to a next steps page. You can connect to your instance either:
+
+- **Through the browser**: Click the **Connect** button for browser-based access
+- **Via SSH**: Use your key pair to SSH into the instance (instructions available when you click **Connect**)
+
+</Steps>
+
+### Server Configuration
+
+Once you have access to your EC2 instance (either via SSH or browser), follow these steps to set up your server environment:
+
+<ServerConfig />
+
+### 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-domain-name>",
+});
+```
+
+## Next steps
+
+- [Mastra Client SDK](/docs/client-js/overview)

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

@@ -0,0 +1,136 @@
+---
+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 with an active subscription
+- A GitHub repository 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** 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 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"
+   - Remove the `npm test` command from the run section
+
+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)
+

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

@@ -12,4 +12,6 @@ Deploy your Mastra applicaitons to popular cloud providers.
 
 <CardGrid>
   <CardGridItem title="Digital Ocean" description="Deploy your Mastra applications to Digital Ocean" href="./cloud-providers/digital-ocean" />
+  <CardGridItem title="Amazon EC2" description="Deploy your Mastra applications to Amazon EC2" href="./cloud-providers/amazon-ec2" />
+  <CardGridItem title="Azure App Services" description="Deploy your Mastra applications to Azure App Services" href="./cloud-providers/azure-app-services" />
 </CardGrid>

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

@@ -0,0 +1,111 @@
+---
+title: "Cloudflare Deployer"
+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.
+
+## Installation
+
+```bash copy
+npm install @mastra/deployer-cloudflare@latest
+```
+
+## Usage example
+
+```typescript filename="src/mastra/index.ts" showLineNumbers copy
+import { Mastra } from "@mastra/core/mastra";
+import { CloudflareDeployer } from "@mastra/deployer-cloudflare";
+
+export const mastra = new Mastra({
+  // ...
+  deployer: new CloudflareDeployer({
+    projectName: "hello-mastra",
+    scope: "",
+    auth: {
+      apiToken: process.env.CLOUDFLARE_API_TOKEN!,
+      apiEmail: "name@email.com"
+    }
+  })
+});
+```
+
+> See the [CloudflareDeployer](/reference/deployer/cloudflare) API reference for all available configuration options.
+
+### Cloudflare API token
+
+In your Cloudflare dashboard, navigate to **Profile** > **API Tokens**, then select **Edit Cloudflare Workers** and click **Use template** to create a token for the `CloudflareDeployer`.
+
+> To learn how to create a Cloudflare API token, see [Create API token](https://developers.cloudflare.com/fundamentals/api/get-started/create-token/) in the Cloudflare docs.
+
+## Continuous integration
+In the Cloudflare dashboard, navigate to **Workers** > **Import a repository**. After importing your Mastra project's Git repository, create an application and configure the build settings with:
+
+- **Build command**: `npm run build`
+- **Deploy command**: `cd .mastra/output && npx wrangler deploy`
+
+- **Build command**: `npm run build` (optional)
+
+## Manual deployment
+
+Manual deployments are also possible using the [Cloudflare Wrangler CLI](https://developers.cloudflare.com/workers/wrangler/install-and-update/). With the Wrangler CLI installed run the following from your project root to deploy your application.
+
+```bash copy
+npm run build && wrangler deploy --config .mastra/output/wrangler.json
+```
+
+> You can also run `wrangler dev --config .mastra/output/wrangler.json` from your project root to test your Mastra application locally.
+
+## Cloudflare secrets
+
+To add secrets to your Cloudflare Workers application, use the Wrangler CLI. Secrets are environment variables that are encrypted and stored securely.
+
+
+For example, to add an API key:
+
+```bash copy
+npx wrangler secret put OPENAI_API_KEY
+```
+
+When prompted, enter the secret value. The secret will be encrypted and stored securely in your Cloudflare account.
+
+> For more details on managing secrets, see [Environment Variables and Secrets](https://developers.cloudflare.com/workers/configuration/secrets/) in the Cloudflare documentation.
+
+## Build output
+
+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>
+
+The `CloudflareDeployer` automatically generates a `wrangler.json` configuration file in `.mastra/output` with the following settings:
+
+```json
+{
+  "name": "hello-mastra",
+  "main": "./index.mjs",
+  "compatibility_date": "2025-04-01",
+  "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)

package/.docs/raw/deployment/{deployment.mdx → serverless-platforms/index.mdx}

@@ -5,7 +5,11 @@ description: "Build and deploy Mastra applications using platform-specific deplo
 
 # Serverless Deployment
 
-This guide covers deploying standalone Mastra applications to Cloudflare Workers, Vercel, and Netlify using platform-specific deployers.
+Standalone Mastra applications can be deployed to popular serverless platforms using one of our deployer packages:
+
+- [Cloudflare](/docs/deployment/serverless-platforms/cloudflare-deployer)
+- [Netlify](/docs/deployment/serverless-platforms/netlify-deployer)
+- [Vercel](/docs/deployment/serverless-platforms/vercel-deployer)
 
 Deployers **aren't** required when integrating Mastra with a framework. See [Web Framework Integration](/docs/deployment/web-framework) for more information.
 
@@ -47,12 +51,3 @@ export const weatherAgent = new Agent({
 -  })
 });
 ```
-
-## Serverless Platform Deployers
-
-Platform-specific deployers handle configuration and deployment for:
-
-- **[Cloudflare Workers](/reference/deployer/cloudflare)**
-- **[Vercel](/reference/deployer/vercel)**
-- **[Netlify](/reference/deployer/netlify)**
-- **[Mastra Cloud](/docs/mastra-cloud/overview)** _(beta)_. You can join the [cloud waitlist](https://mastra.ai/cloud-beta) for early access.

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

@@ -0,0 +1,94 @@
+---
+title: "Netlify Deployer"
+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.
+
+## Installation
+
+```bash copy
+npm install @mastra/deployer-netlify@latest
+```
+
+## Usage example
+
+```typescript filename="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()
+});
+```
+
+> See the [NetlifyDeployer](/reference/deployer/netlify) API reference for all available configuration options.
+
+## Continuous integration
+
+After connecting your Mastra project’s Git repository to Netlify, update the project settings. In the Netlify dashboard, go to **Project configuration** > **Build & deploy** > **Continuous deployment**, and under **Build settings**, set the following:
+
+- **Build command**: `npm run build` (optional)
+
+### Environment variables
+
+Before your first deployment, make sure to add any environment variables used by your application. For example, if you're using OpenAI as the LLM, you'll need to set `OPENAI_API_KEY` in your Netlify project settings.
+
+> 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.
+
+```bash copy
+netlify deploy --prod
+```
+
+> You can also run `netlify dev` from your project root to test your Mastra application locally.
+
+## Build output
+
+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>
+
+
+The `NetlifyDeployer` automatically generates a `config.json` configuration file in `.netlify/v1` with the following settings:
+
+```json
+{
+  "redirects": [
+    {
+      "force": true,
+      "from": "/*",
+      "to": "/.netlify/functions/api/:splat",
+      "status": 200
+    }
+  ]
+}
+```
+
+## Next steps
+
+- [Mastra Client SDK](/docs/client-js/overview)