@mastra/mcp-docs-server 0.13.5 → 0.13.7-alpha.0

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

@@ -1,17 +1,52 @@
 ---
 title: "Cloud Providers"
 description: "Deploy your Mastra applications to popular cloud providers."
-asIndexPage: true
 ---
 
-import { CardGrid, CardGridItem } from "@/components/cards/card-grid";
-
 ## Cloud Providers
 
-Deploy your Mastra applicaitons to popular 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 --]
+});
+```
 
-<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>
+```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/serverless-platforms/cloudflare-deployer.mdx

@@ -24,6 +24,7 @@ import { CloudflareDeployer } from "@mastra/deployer-cloudflare";
 export const mastra = new Mastra({
   // ...
   deployer: new CloudflareDeployer({
+    scope: "your-account-id",
     projectName: "hello-mastra",
     scope: "",
     auth: {
@@ -36,44 +37,23 @@ export const mastra = new Mastra({
 
 > 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.
 
+With the Wrangler CLI installed, login and authenticate with your Cloudflare logins:
+
 ```bash copy
-npm run build && wrangler deploy --config .mastra/output/wrangler.json
+npx wrangler login
 ```
 
-> 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:
+Run the following to build and deploy your application to Cloudflare
 
 ```bash copy
-npx wrangler secret put OPENAI_API_KEY
+npm run build && wrangler deploy --config .mastra/output/wrangler.json
 ```
 
-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.
+> You can also run `wrangler dev --config .mastra/output/wrangler.json` from your project root to test your Mastra application locally.
 
 ## Build output
 
@@ -99,13 +79,12 @@ The `CloudflareDeployer` automatically generates a `wrangler.json` configuration
   "compatibility_flags": ["nodejs_compat", "nodejs_compat_populate_process_env"],
   "observability": { "logs": { "enabled": true } },
   "vars": {
-    "OPENAI_API_KEY": "..",
+    "OPENAI_API_KEY": "...",
     "CLOUDFLARE_API_TOKEN": "..."
   }
 }
-```
-
 
+```
 ## Next steps
 
 - [Mastra Client SDK](/docs/client-js/overview)

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

@@ -19,7 +19,7 @@ For self-hosted Node.js server deployment, see the [Creating A Mastra Server](/d
 
 Before you begin, ensure you have:
 
-- **Node.js** installed (version 18 or higher is recommended)
+- Node.js `v20.0` or higher
 - If using a platform-specific deployer:
   - An account with your chosen platform
   - Required API keys or credentials
@@ -30,23 +30,23 @@ 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`:
 
-```diff filename="src/mastra/index.ts" showLineNumbers
+```typescript filename="src/mastra/index.ts" showLineNumbers
 export const mastra = new Mastra({
   // ...
--  storage: new LibSQLStore({
--    // stores telemetry, evals, ... into memory storage, if it needs to persist, change to file:../mastra.db
--    url: ":memory:",
--  })
+  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 --]
 });
 ```
 
-``` diff filename="src/mastra/agents/weather-agent.ts" showLineNumbers
+```typescript filename="src/mastra/agents/weather-agent.ts" showLineNumbers
 export const weatherAgent = new Agent({
-  // ..
--  memory: new Memory({
--    storage: new LibSQLStore({
--      url: "file:../mastra.db" // path is relative to the .mastra/output directory
--    })
--  })
+ // ..
+ 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/evals/custom-eval.mdx

@@ -1,22 +1,22 @@
 ---
-title: "Create your own Eval"
-description: "Mastra allows so create your own evals, here is how."
+title: "Create a custom eval"
+description: "Mastra allows you to create your own evals, here is how."
 ---
 
-# Create your own Eval
+# Create a Custom Eval
 
-Creating your own eval is as easy as creating a new function. You simply create a class that extends the `Metric` class and implement the `measure` method.
+Create a custom eval by extending the `Metric` class and implementing the `measure` method. This gives you full control over how scores are calculated and what information is returned. For LLM-based evaluations, extend the `MastraAgentJudge` class to define how the model reasons and scores output.
 
-## Basic example
+## Native JavaScript evaluation
 
-For a simple example of creating a custom metric that checks if the output contains certain words, see our [Word Inclusion example](/examples/evals/word-inclusion).
+You can write lightweight custom metrics using plain JavaScript/TypeScript. These are ideal for simple string comparisons, pattern checks, or other rule-based logic.
 
-## Creating a custom LLM-Judge
+See our [Word Inclusion example](/examples/evals/custom-native-javascript-eval.mdx), which scores responses based on the number of reference words found in the output.
 
-A custom LLM judge helps evaluate specific aspects of your AI's responses. Think of it like having an expert reviewer for your particular use case:
+## LLM as a judge evaluation
+
+For more complex evaluations, you can build a judge powered by an LLM. This lets you capture more nuanced criteria, like factual accuracy, tone, or reasoning.
+
+See the [Real World Countries example](/examples/evals/custom-llm-judge-eval.mdx) for a complete walkthrough of building a custom judge and metric that evaluates real-world factual accuracy.
 
-- Medical Q&A → Judge checks for medical accuracy and safety
-- Customer Service → Judge evaluates tone and helpfulness
-- Code Generation → Judge verifies code correctness and style
 
-For a practical example, see how we evaluate [Chef Michel's](/docs/guides/chef-michel) recipes for gluten content in our [Gluten Checker example](/examples/evals/custom-eval).