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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mastra/mcp-docs-server",
-  "version": "0.13.5-alpha.0",
+  "version": "0.13.6",
   "description": "MCP server for accessing Mastra.ai documentation, changelogs, and news.",
   "type": "module",
   "main": "dist/index.js",
@@ -22,7 +22,7 @@
   },
   "keywords": [],
   "author": "",
-  "license": "Elastic-2.0",
+  "license": "Apache-2.0",
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.13.0",
     "date-fns": "^4.1.0",
@@ -32,7 +32,8 @@
     "uuid": "^11.1.0",
     "zod": "^3.25.67",
     "zod-to-json-schema": "^3.24.5",
-    "@mastra/mcp": "^0.10.6-alpha.0"
+    "@mastra/core": "0.11.1",
+    "@mastra/mcp": "^0.10.7"
   },
   "devDependencies": {
     "@hono/node-server": "^1.14.4",
@@ -41,17 +42,14 @@
     "@types/turndown": "^5.0.5",
     "@wong2/mcp-cli": "^1.10.0",
     "cross-env": "^7.0.3",
-    "eslint": "^9.29.0",
+    "eslint": "^9.30.1",
     "hono": "^4.8.4",
     "tsup": "^8.5.0",
     "tsx": "^4.19.4",
     "typescript": "^5.8.3",
     "vitest": "^3.2.4",
-    "@internal/lint": "0.0.17",
-    "@mastra/core": "0.10.11-alpha.2"
-  },
-  "peerDependencies": {
-    "@mastra/core": "^0.10.0-alpha.0"
+    "@internal/lint": "0.0.22",
+    "@mastra/core": "0.11.1"
   },
   "scripts": {
     "prepare-docs": "cross-env PREPARE=true node dist/prepare-docs/prepare.js",

package/.docs/raw/deployment/custom-api-routes.mdx

@@ -1,55 +0,0 @@
----
-title: "Custom API Routes"
-description: "Expose additional HTTP endpoints from your Mastra server."
----
-
-# Custom API Routes
-
-By default Mastra automatically exposes registered agents and workflows via the
-server. For additional behaviour you can define your own HTTP routes.
-
-Routes are provided with a helper `registerApiRoute` from `@mastra/core/server`.
-Routes can live in the same file as the `Mastra` instance but separating them
-helps keep configuration concise.
-
-```typescript copy showLineNumbers
-import { Mastra } from "@mastra/core";
-import { registerApiRoute } from "@mastra/core/server";
-
-export const mastra = new Mastra({
-  server: {
-    apiRoutes: [
-      registerApiRoute("/my-custom-route", {
-        method: "GET",
-        handler: async (c) => {
-          const mastra = c.get("mastra");
-          const agents = await mastra.getAgent("my-agent");
-
-          return c.json({ message: "Hello, world!" });
-        },
-      }),
-    ],
-  },
-});
-```
-
-Each route's handler receives the Hono `Context`. Within the handler you can
-access the `Mastra` instance to fetch or call agents and workflows.
-
-To add route-specific middleware pass a `middleware` array when calling
-`registerApiRoute`.
-
-```typescript copy showLineNumbers
-registerApiRoute("/my-custom-route", {
-  method: "GET",
-  middleware: [
-    async (c, next) => {
-      console.log(`${c.req.method} ${c.req.url}`);
-      await next();
-    },
-  ],
-  handler: async (c) => {
-    return c.json({ message: "My route with custom middleware" });
-  },
-});
-```

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

@@ -1,116 +0,0 @@
----
-title: "Creating A Mastra Server"
-description: "Configure and customize the Mastra server with middleware and other options"
----
-
-# Creating A Mastra Server
-
-While developing or when you deploy a Mastra application, it runs as an HTTP server that exposes your agents, workflows, and other functionality as API endpoints. This page explains how to configure and customize the server behavior.
-
-## Server Architecture
-
-Mastra uses [Hono](https://hono.dev) as its underlying HTTP server framework. When you build a Mastra application using `mastra build`, it generates a Hono-based HTTP server in the `.mastra` directory.
-
-The server provides:
-
-- API endpoints for all registered agents
-- API endpoints for all registered workflows
-- Custom api route supports
-- Custom middleware support
-- Configuration of timeout
-- Configuration of port
-- Configuration of body limit
-
-See the [Middleware](/docs/deployment/middleware) and
-[Custom API Routes](/docs/deployment/custom-api-routes) pages for details on
-adding additional server behaviour.
-
-## Server configuration
-
-You can configure server `port` and `timeout` in the Mastra instance.
-
-```typescript copy showLineNumbers
-import { Mastra } from "@mastra/core";
-
-export const mastra = new Mastra({
-  server: {
-    port: 3000, // Defaults to 4111
-    timeout: 10000, // Defaults to 30000 (30s)
-  },
-});
-```
-
-The `method` option can be one of `"GET"`, `"POST"`, `"PUT"`,
-`"DELETE"` or `"ALL"`. Using `"ALL"` will cause the handler to be
-invoked for any HTTP method that matches the path.
-
-## Custom CORS Config
-
-Mastra allows you to configure CORS (Cross-Origin Resource Sharing) settings for your server.
-
-```typescript copy showLineNumbers
-import { Mastra } from "@mastra/core";
-
-export const mastra = new Mastra({
-  server: {
-    cors: {
-      origin: ["https://example.com"], // Allow specific origins or '*' for all
-      allowMethods: ["GET", "POST", "PUT", "DELETE", "OPTIONS"],
-      allowHeaders: ["Content-Type", "Authorization"],
-      credentials: false,
-    },
-  },
-});
-```
-
-## Deployment
-
-Since Mastra builds to a standard Node.js server, you can deploy to any platform that runs Node.js applications:
-
-- Cloud VMs (AWS EC2, DigitalOcean Droplets, GCP Compute Engine)
-- Container platforms (Docker, Kubernetes)
-- Platform as a Service (Heroku, Railway)
-- Self-hosted servers
-
-### Building
-
-Build the application:
-
-```bash copy
-# Build from current directory
-mastra build
-
-# Or specify a directory
-mastra build --dir ./my-project
-```
-
-The build process:
-
-1. Locates entry file (`src/mastra/index.ts` or `src/mastra/index.js`)
-2. Creates `.mastra` output directory
-3. Bundles code using Rollup with tree shaking and source maps
-4. Generates [Hono](https://hono.dev) HTTP server
-
-See [`mastra build`](/reference/cli/build) for all options.
-
-### Running the Server
-
-Start the HTTP server:
-
-```bash copy
-node .mastra/output/index.mjs
-```
-
-### Enable Telemetry for build output
-
-Load instrumentation for the build output like so:
-
-```bash copy
-node --import=./.mastra/output/instrumentation.mjs  .mastra/output/index.mjs
-```
-
-## Serverless Deployment
-
-Mastra also supports serverless deployment on Cloudflare Workers, Vercel, and Netlify.
-
-See our [Serverless Deployment](/docs/deployment/deployment) guide for setup instructions.

package/.docs/raw/frameworks/ai-sdk-v5.mdx

@@ -1,91 +0,0 @@
-# AI SDK v5 (beta) Migration Guide
-
-This guide covers Mastra-specific considerations when migrating from AI SDK v4 to v5 beta.
-
-Please add any feedback or bug reports to the [AI SDK v5 mega issue in Github.](https://github.com/mastra-ai/mastra/issues/5470)
-
-## Official Migration Guide
-
-**Follow the official [AI SDK v5 Migration Guide](https://v5.ai-sdk.dev/docs/migration-guides/migration-guide-5-0)** for all AI SDK core breaking changes, package updates, and API changes.
-
-This guide covers only the Mastra-specific aspects of the migration.
-
-## Warnings
-
-- **Data compatibility**: New data stored in v5 format will no longer work if you downgrade from the beta
-- **Backup recommendation**: Keep DB backups from before you upgrade to v5 beta
-- **Production use**: Wait for the AI SDK v5 stable release before using in production applications
-- **Prerelease status**: The Mastra `ai-v5` tag is a prerelease version and may have bugs
-
-## Memory Storage
-
-Your existing AI SDK v4 data will run through our internal `MessageList` class which handles converting to/from various message formats.
-This includes converting from AI SDK v4->v5. This means you don't need to run any DB migrations and your data will be translated on the fly and will just work when you upgrade.
-
-
-## Migration Strategy
-
-Migrating to AI SDK v5 with Mastra involves updating both your **backend** (Mastra server) and **frontend**.
-We provide a compatibility mode to handle stream format conversion during the transition.
-
-### Backend Upgrade
-
-Bump Mastra to the new `ai-v5` prerelease version for all Mastra packages:
-
-```bash npm2yarn copy
-npm i mastra@ai-v5 @mastra/core@ai-v5 @mastra/memory@ai-v5 [etc]
-```
-
-Then configure your Mastra instance with v4 compatibility so your existing frontend will continue to work:
-
-```typescript
-import { Mastra } from '@mastra/core';
-
-export const mastra = new Mastra({
-  agents: { myAgent },
-  aiSdkCompat: 'v4', // <- add this for compatibility
-});
-```
-
-#### Dependencies
-
-You will need to upgrade all AI SDK dependencies to use the new v5 beta versions in your backend when you bump to the Mastra `ai-v5` prerelease tag.
-
-In most cases this will only involve bumping your model provider packages. For example: `npm i @ai-sdk/openai@2.0.0-beta.1` - refer to the [AI SDK v5 documentation](https://v5.ai-sdk.dev/docs/migration-guides/migration-guide-5-0) for more info. Some model providers do not yet have V5 versions (Openrouter for example).
-
-Also note that you need to bump all your Mastra dependencies to the new `ai-v5` tag, and you must upgrade `zod` to the latest version if you have it installed.
-
-#### Using Stream Compatibility Manually
-
-If you have a frontend that calls Mastra agents in an endpoint, you can wrap the new `response.toUIMessageStreamResponse()` manually.
-
-```ts
-import { mastra } from "@/src/mastra";
-import { createV4CompatibleResponse } from "@mastra/core/agent";
-
-const myAgent = mastra.getAgent("weatherAgent");
-export async function POST(req: Request) {
-  const { messages } = await req.json();
-  const stream = await myAgent.stream(messages);
-
-  return createV4CompatibleResponse(stream.toUIMessageStreamResponse().body!);
-}
-```
-
-### Using Mastra Playground
-
-Currently playground is still an AI SDK v4 frontend. For now you need to set `aiSdkCompat: 'v4'` for it to work.
-We'll handle this automatically for you soon.
-
-### Frontend Upgrade
-
-When you're ready, remove the compatibility flag and upgrade your frontend:
-
-1. Remove `aiSdkCompat: 'v4'` from your Mastra configuration
-2. Follow the AI SDK guide on upgrading your frontend dependencies
-3. Update your frontend code for v5 breaking changes
-
-## Discussion and Bug Reports
-
-Please add any feedback or bug reports to the [AI SDK v5 mega issue in Github.](https://github.com/mastra-ai/mastra/issues/5470)
-