@mastra/mcp-docs-server 1.0.0-beta.1 → 1.0.0-beta.10

package/dist/stdio.js

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-import { fromPackageRoot, prepare, getMatchingPaths, blogPostSchema } from './chunk-5NJC7NRO.js';
+import { fromPackageRoot, prepare, getMatchingPaths, blogPostSchema } from './chunk-4CM2BQNP.js';
 import * as fs from 'fs';
 import { existsSync, mkdirSync } from 'fs';
 import * as os2 from 'os';
@@ -112,7 +112,7 @@ var migrationPrompts = [
     arguments: [
       {
         name: "area",
-        description: "Optional: Focus on a specific area (agents, tools, workflows, memory, evals, mcp, vectors, syncs). If not provided, gives an overview of all changes.",
+        description: "Optional: Focus on a specific area (e.g., agent, tools, workflows, memory, storage, voice). The tool will check if a migration guide exists for this area and suggest alternatives if not found. If not provided, gives an overview of all changes.",
         required: false
       }
     ]
@@ -141,24 +141,21 @@ var migrationPromptMessages = {
 };
 function getUpgradeToV1Messages(area) {
   if (area) {
-    const validAreas = ["agents", "tools", "workflows", "memory", "evals", "mcp", "vectors", "syncs"];
-    if (!validAreas.includes(area.toLowerCase())) {
-      return [
-        {
-          role: "user",
-          content: {
-            type: "text",
-            text: `Invalid area: ${area}. Valid areas are: ${validAreas.join(", ")}`
-          }
-        }
-      ];
-    }
     return [
       {
         role: "user",
         content: {
           type: "text",
-          text: `I need help migrating my Mastra ${area} code from v0.x to v1.0. Use the mastraMigration tool to get the specific migration guide for "${area}" and walk me through the changes step by step.`
+          text: `I need help migrating my Mastra ${area} code from v0.x to v1.0. Use the mastraMigration tool to:
+
+1. If packages aren't already at the 'beta' tag, upgrade packages to the 'beta' tag and do an install of the new packages.
+2. First, try to get the specific migration guide for "${area}" using path: "upgrade-to-v1/${area}"
+3. If that doesn't exist, try the alternate form (singular/plural):
+   - If "${area}" ends with 's', try without the 's' (e.g., "agents" \u2192 "agent")
+   - If "${area}" doesn't end with 's', try adding 's' (e.g., "agent" \u2192 "agents")
+4. If the guide exists, walk me through the changes step by step
+5. If neither form exists, list available migration guides in "upgrade-to-v1/" and suggest which ones might be relevant to "${area}"
+6. After you find the guide, collect all the codemod calls to run to codemods. These callouts are marked with ":::tip[Codemod]" in the docs. Run the codemods with "npx @mastra/codemod@beta <codemod-name> <path>" to automate all those changes. Afterwards, help me with any remaining manual changes needed.`
         }
       }
     ];
@@ -170,12 +167,13 @@ function getUpgradeToV1Messages(area) {
         type: "text",
         text: `I need to migrate my Mastra project from v0.x to v1.0. Use the mastraMigration tool to:
 
-1. First, list all available migration guides with path: "upgrade-to-v1/"
+1. If packages aren't already at the 'beta' tag, upgrade packages to the 'beta' tag and do an install of the new packages.
+2. First, list all available migration guides with path: "upgrade-to-v1/"
 2. Give me a high-level overview of what changed in each area
-3. Ask me which areas I'm using in my project so we can focus on relevant changes
-4. After I decided on the areas, check the migration guides for callouts to codemods. These callouts are marked with ":::tip[Codemod]" in the docs. Run the codemods with "npx @mastra/codemod@beta v1" to automate all those changes. Afterwards, help me with any remaining manual changes needed.
+3. Find relevant migration areas to focus on based on my project's codebase and confirm the list with me
+4. After the areas are confirmed, check the migration guides for callouts to codemods. These callouts are marked with ":::tip[Codemod]" in the docs. Run the codemods with "npx @mastra/codemod@beta v1" to automate all those changes. Afterwards, help me with any remaining manual changes needed.
 
-After I tell you which areas I use, we'll go through each one systematically.`
+After the areas are confirmed, we'll go through each one systematically.`
       }
     }
   ];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mastra/mcp-docs-server",
-  "version": "1.0.0-beta.1",
+  "version": "1.0.0-beta.10",
   "description": "MCP server for accessing Mastra.ai documentation, changelogs, and news.",
   "type": "module",
   "main": "dist/index.js",
@@ -26,31 +26,27 @@
   "license": "Apache-2.0",
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.17.5",
-    "date-fns": "^4.1.0",
-    "exit-hook": "^4.0.0",
     "jsdom": "^26.1.0",
-    "turndown": "^7.2.1",
-    "uuid": "^11.1.0",
     "zod": "^3.25.76",
-    "zod-to-json-schema": "^3.24.6",
-    "@mastra/core": "1.0.0-beta.1",
-    "@mastra/mcp": "^1.0.0-beta.0"
+    "@mastra/mcp": "^1.0.0-beta.6",
+    "@mastra/core": "1.0.0-beta.10"
   },
   "devDependencies": {
     "@hono/node-server": "^1.19.6",
     "@types/jsdom": "^21.1.7",
-    "@types/node": "^20.19.0",
-    "@types/turndown": "^5.0.5",
-    "@wong2/mcp-cli": "^1.10.0",
+    "@types/node": "22.13.17",
+    "@vitest/coverage-v8": "4.0.12",
+    "@vitest/ui": "4.0.12",
+    "@wong2/mcp-cli": "^1.13.0",
     "cross-env": "^10.1.0",
     "eslint": "^9.37.0",
-    "hono": "^4.9.7",
+    "hono": "^4.10.5",
     "tsup": "^8.5.0",
     "tsx": "^4.19.4",
     "typescript": "^5.8.3",
-    "vitest": "^3.2.4",
-    "@internal/lint": "0.0.53",
-    "@mastra/core": "1.0.0-beta.1"
+    "vitest": "4.0.12",
+    "@mastra/core": "1.0.0-beta.10",
+    "@internal/lint": "0.0.53"
   },
   "homepage": "https://mastra.ai",
   "repository": {

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

@@ -1,58 +0,0 @@
----
-title: "Serverless Deployment | Deployment | Mastra Docs"
-description: "Build and deploy Mastra applications using platform-specific deployers or standard HTTP servers"
----
-
-# Serverless Deployment
-
-Standalone Mastra applications can be deployed to popular serverless platforms using one of our deployer packages:
-
-- [Cloudflare](/docs/v1/deployment/serverless-platforms/cloudflare-deployer)
-- [Netlify](/docs/v1/deployment/serverless-platforms/netlify-deployer)
-- [Vercel](/docs/v1/deployment/serverless-platforms/vercel-deployer)
-
-Deployers **aren't** required when integrating Mastra with a framework. See [Web Framework Integration](/docs/v1/deployment/web-framework) for more information.
-
-For self-hosted Node.js server deployment, see the [Creating A Mastra Server](/docs/v1/deployment/server-deployment) guide.
-
-## Prerequisites
-
-Before you begin, ensure you have:
-
-- Node.js `v22.13.0` or later
-- If using a platform-specific deployer:
-  - An account with your chosen platform
-  - Required API keys or credentials
-
-## LibSQLStore
-
-`LibSQLStore` writes to the local filesystem, which is not supported in serverless environments due to their ephemeral nature. If you're deploying to a platform like Vercel, Netlify or Cloudflare, 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 title="src/mastra/index.ts" showLineNumbers
-export const mastra = new Mastra({
-  // ...
-  storage: new LibSQLStore({
-    id: 'mastra-storage',
-    // [!code --]
-    // stores telemetry, scorer results, ... into memory storage, if it needs to persist, change to file:../mastra.db // [!code --]
-    url: ":memory:", // [!code --]
-  }), //[!code --]
-});
-```
-
-```typescript title="src/mastra/agents/weather-agent.ts" showLineNumbers
-export const weatherAgent = new Agent({
-  id: "weather-agent",
-  // ..
-  memory: new Memory({
-    // [!code --]
-    storage: new LibSQLStore({
-      id: 'mastra-storage',
-      // [!code --]
-      url: "file:../mastra.db", // path is relative to the .mastra/output directory // [!code --]
-    }), // [!code --]
-  }), //  [!code --]
-});
-```