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

package/.docs/raw/server-db/server-adapters.mdx

@@ -3,20 +3,16 @@ title: "Server Adapters | Server & DB"
 description: "Manually configure a Mastra server using Hono or Express adapters."
 ---
 
-import PropertiesTable from "@site/src/components/PropertiesTable";
 import Tabs from "@theme/Tabs";
 import TabItem from "@theme/TabItem";
 
 # Server Adapters
 
-Server adapters let you run Mastra with your own HTTP server instead of using `mastra build`. While `mastra build` generates a standalone server for you, adapters give you full control over the server setup, letting you integrate Mastra into any Node.js application.
+Server adapters let you run Mastra with your own HTTP server instead of the Hono server generated by `mastra build`. They provide more control over the server setup, including custom middleware ordering, authentication, logging, and deployment configuration, while still letting you integrate Mastra into any Node.js application without changing how agents or workflows execute.
 
-Use adapters when you need to:
+## When to use server adapters
 
-- **Integrate Mastra into an existing application** - Add Mastra endpoints to an Express or Hono app you already have running
-- **Control middleware ordering** - Insert your own middleware before or after Mastra's authentication and routing
-- **Deploy to platforms requiring specific server setup** - Some platforms like Cloudflare Workers or custom Docker setups need direct access to the server instance
-- **Use Express instead of Hono** - `mastra build` uses Hono internally, but you may prefer Express for its ecosystem or team familiarity
+Use server adapters when you want Mastra’s endpoints added automatically to an existing application, when you need direct access to the server instance for custom configuration, or when your team prefers using Express instead of the Hono server created by `mastra build`.
 
 :::info
 
@@ -26,81 +22,85 @@ For simple deployments without custom server requirements, use `mastra build` in
 
 ## Available adapters
 
-- **[@mastra/hono](/reference/v1/server/hono-adapter)** - Hono framework adapter
-- **[@mastra/express](/reference/v1/server/express-adapter)** - Express framework adapter
-
-## Basic setup
-
-Both adapters follow the same pattern. The adapter wraps your framework's app instance and registers Mastra's routes and middleware onto it.
-
-1. **Create your framework's app instance** - Initialize Hono or Express as you normally would
-2. **Create a `MastraServer`** - Pass your app and Mastra instance to the adapter
-3. **Call `init()`** - This registers context middleware, authentication, and all API routes
-
-After `init()`, your app has all the Mastra endpoints (`/api/agents`, `/api/workflows`, etc.) and you can add your own routes before or after.
-
-See the [Hono Adapter](/reference/v1/server/hono-adapter) or [Express Adapter](/reference/v1/server/express-adapter) docs for framework-specific setup and code examples.
-
-## Constructor options
-
-Both adapters accept the same options:
-
-<PropertiesTable
-  content={[
-    {
-      name: "app",
-      type: "Hono | Application",
-      description: "Framework app instance",
-      isOptional: false,
-    },
-    {
-      name: "mastra",
-      type: "Mastra",
-      description: "Mastra instance",
-      isOptional: false,
-    },
-    {
-      name: "prefix",
-      type: "string",
-      description: "Route path prefix (e.g., `/api/v2`)",
-      isOptional: true,
-      defaultValue: "''",
-    },
-    {
-      name: "openapiPath",
-      type: "string",
-      description: "Path to serve OpenAPI spec (e.g., `/openapi.json`)",
-      isOptional: true,
-    },
-    {
-      name: "bodyLimitOptions",
-      type: "{ maxSize: number, onError: (err) => unknown }",
-      description: "Request body size limits",
-      isOptional: true,
-    },
-    {
-      name: "streamOptions",
-      type: "{ redact?: boolean }",
-      description: "Stream redaction config. When true, redacts sensitive data from streams.",
-      isOptional: true,
-      defaultValue: "{ redact: true }",
-    },
-    {
-      name: "customRouteAuthConfig",
-      type: "Map<string, boolean>",
-      description: "Per-route auth overrides. Keys are `METHOD:PATH` (e.g., `GET:/api/health`). Value `false` makes route public, `true` requires auth.",
-      isOptional: true,
-    },
-  ]}
-/>
+- [@mastra/express](/reference/v1/server/express-adapter): Express framework adapter.
+- [@mastra/hono](/reference/v1/server/hono-adapter): Hono framework adapter.
+
+## Installation
+
+Install the adapter for the framework you’re using.
+
+<Tabs>
+  <TabItem value="express" label="Express">
+
+```bash
+npm install @mastra/express@beta
+```
+  </TabItem>
+  <TabItem value="hono" label="Hono">
+
+```bash
+npm install @mastra/hono@beta
+```
+  </TabItem>
+</Tabs>
+
+## Configuration
+
+Initialize your Express or Hono app as usual, then create a `MastraServer` by passing in the `app` and your main `mastra` instance from `src/mastra`. Calling `init()` automatically registers Mastra middleware and all available endpoints. You can continue adding your own routes as normal, either before or after `init()`, and they’ll run alongside Mastra’s endpoints.
+
+<Tabs>
+  <TabItem value="express" label="Express">
+
+```typescript {8} title="express-server.ts" showLineNumbers
+import express from "express";
+import { MastraServer } from "@mastra/express";
+import { mastra } from "./mastra"; // src/mastra/index.ts
+
+const app = express();
+app.use(express.json());
+
+const server = new MastraServer({ app, mastra });
+
+await server.init();
+
+app.listen(4111, () => {
+  console.log('Server running on port 4111');
+});
+```
+
+  </TabItem>
+  <TabItem value="hono" label="Hono">
+
+```typescript {8} title="hono-server.ts" showLineNumbers
+import { Hono } from "hono";
+import { serve } from "@hono/node-server";
+import { HonoBindings, HonoVariables, MastraServer } from "@mastra/hono";
+import { mastra } from "./mastra"; // src/mastra/index.ts
+
+const app = new Hono<{ Bindings: HonoBindings; Variables: HonoVariables }>();
+
+const server = new MastraServer({ app, mastra });
+
+await server.init();
+
+serve({ fetch: app.fetch, port: 4111 }, () => {
+  console.log('Server running on port 4111');
+});
+```
+
+  </TabItem>
+</Tabs>
+
+> See the [Express Adapter](/reference/v1/server/express-adapter) or [Hono Adapter](/reference/v1/server/hono-adapter)  docs for full configuration options.
+
 
 ## Initialization flow
 
 Calling `init()` runs three steps in order. Understanding this flow helps when you need to insert your own middleware at specific points.
 
-1. **`registerContextMiddleware()`** - Attaches the Mastra instance, request context, tools, and abort signal to every request. This makes Mastra available to all subsequent middleware and route handlers.
-2. **`registerAuthMiddleware()`** - Adds authentication and authorization middleware, but only if `server.auth` is configured in your Mastra instance. Skipped entirely if no auth is configured.
-3. **`registerRoutes()`** - Registers all Mastra API routes for agents, workflows, and other features. Also registers MCP routes if MCP servers are configured.
+1. `registerContextMiddleware()`: Attaches the Mastra instance, request context, tools, and abort signal to every request. This makes Mastra available to all subsequent middleware and route handlers.
+2. `registerAuthMiddleware()`: Adds authentication and authorization middleware, but only if `server.auth` is configured in your Mastra instance. Skipped entirely if no auth is configured.
+3. `registerRoutes()`: Registers all Mastra API routes for agents, workflows, and other features. Also registers MCP routes if MCP servers are configured.
 
 ### Manual initialization
 
@@ -132,18 +132,19 @@ Use manual initialization when you need middleware that runs before Mastra's con
 
 ## Adding custom routes
 
-You can add your own routes to the app alongside Mastra's routes. Routes added after `init()` have access to the Mastra context (the Mastra instance, request context, authenticated user, etc.) through framework-specific mechanisms.
+You can add your own routes to the app alongside Mastra's routes.
+
+- Routes added **before** `init()` won't have Mastra context available.
+- Routes added **after** `init()` have access to the Mastra context (the Mastra instance, request context, authenticated user, etc.).
 
-The timing matters: routes added before `init()` won't have Mastra context available, while routes added after `init()` will. See the framework-specific docs for syntax and examples:
+> See adding custom routes for [Express](/reference/v1/server/express-adapter#adding-custom-routes) and [Hono](/reference/v1/server/hono-adapter#adding-custom-routes) for more information.
 
-- [Hono: Adding custom routes](/reference/v1/server/hono-adapter#adding-custom-routes)
-- [Express: Adding custom routes](/reference/v1/server/express-adapter#adding-custom-routes)
 
 ## Route prefixes
 
 By default, Mastra routes are registered at `/api/agents`, `/api/workflows`, etc. Use the `prefix` option to change this, which is useful for API versioning or when integrating with an existing app that has its own `/api` routes.
 
-```typescript copy showLineNumbers
+```typescript showLineNumbers copy
 const server = new MastraServer({
   app,
   mastra,
@@ -157,7 +158,7 @@ With this prefix, Mastra routes become `/api/v2/agents`, `/api/v2/workflows`, et
 
 Mastra can generate an OpenAPI specification for all registered routes. This is useful for documentation, client generation, or integration with API tools. Enable it by setting the `openapiPath` option:
 
-```typescript copy showLineNumbers
+```typescript showLineNumbers copy
 const server = new MastraServer({
   app,
   mastra,
@@ -178,9 +179,9 @@ When streaming agent responses over HTTP, the HTTP streaming layer redacts sensi
 
 This redaction happens at the HTTP boundary, so internal callbacks like `onStepFinish` still have access to the full request data for debugging and observability purposes.
 
-By default, redaction is enabled. Configure this behavior via `streamOptions`:
+By default, redaction is enabled. Configure this behavior via `streamOptions`. Set `redact: false` only for internal services or debugging scenarios where you need access to the full request data in stream responses.
 
-```typescript copy showLineNumbers
+```typescript showLineNumbers copy
 const server = new MastraServer({
   app,
   mastra,
@@ -190,15 +191,15 @@ const server = new MastraServer({
 });
 ```
 
-Set `redact: false` only for internal services or debugging scenarios where you need access to the full request data in stream responses.
+> See [MastraServer](/reference/v1/server/mastra-server) for full configuration options.
 
 ## Per-route auth overrides
 
 When authentication is configured on your Mastra instance, all routes require authentication by default. Sometimes you need exceptions: public health check endpoints, webhook receivers, or admin routes that need stricter controls.
 
-Use `customRouteAuthConfig` to override authentication behavior for specific routes:
+Use `customRouteAuthConfig` to override authentication behavior for specific routes. Keys follow the format `METHOD:PATH` where method is `GET`, `POST`, `PUT`, `DELETE`, or `ALL`. Paths support wildcards (`*`) for matching multiple routes. Setting a value to `false` makes the route public, while `true` requires authentication.
 
-```typescript copy showLineNumbers
+```typescript showLineNumbers copy
 const server = new MastraServer({
   app,
   mastra,
@@ -212,13 +213,15 @@ const server = new MastraServer({
 });
 ```
 
-Keys follow the format `METHOD:PATH` where method is `GET`, `POST`, `PUT`, `DELETE`, or `ALL`. Paths support wildcards (`*`) for matching multiple routes. Setting a value to `false` makes the route public, while `true` requires authentication.
+
+
+> See [MastraServer](/reference/v1/server/mastra-server) for full configuration options.
 
 ## Accessing the app
 
-After creating the adapter, you may need to access the underlying framework app instance—for example, to pass it to a platform's serve function or to add routes programmatically from another module.
+After creating the adapter, you may still need access to the underlying framework app. This is useful when passing it to a platform’s `serve` function or when adding routes from another module.
 
-```typescript copy showLineNumbers
+```typescript showLineNumbers copy
 // Via the MastraServer instance
 const app = server.getApp();
 

package/.docs/raw/streaming/tool-streaming.mdx

@@ -18,9 +18,8 @@ By combining writable tool streams with agent streaming, you gain fine grained c
 
 Agent streaming can be combined with tool calls, allowing tool outputs to be written directly into the agent’s streaming response. This makes it possible to surface tool activity as part of the overall interaction.
 
-```typescript {3,9} showLineNumbers copy
+```typescript {2,9} showLineNumbers copy
 import { Agent } from "@mastra/core/agent";
-
 import { testTool } from "../tools/test-tool";
 
 export const testAgent = new Agent({
@@ -34,30 +33,29 @@ export const testAgent = new Agent({
 
 ### Using `context.writer`
 
-The `context.writer` object is available in a tool's `execute` function and can be used to emit custom events, data, or values into the active stream. This enables tools to provide intermediate results or status updates while execution is still in progress.
+The `context.writer` object is available in a tool's `execute()` function and can be used to emit custom events, data, or values into the active stream. This enables tools to provide intermediate results or status updates while execution is still in progress.
 
 :::warning
 
-You must `await` the call to `writer.write(...)` or else you will lock the stream and get a `WritableStream is locked` error.
+You must `await` the call to `writer.write()` or else you will lock the stream and get a `WritableStream is locked` error.
 
 :::
 
-```typescript {5,8,15} showLineNumbers copy
+```typescript {4,7,14} showLineNumbers copy
 import { createTool } from "@mastra/core/tools";
 
 export const testTool = createTool({
-  // ...
   execute: async (inputData, context) => {
     const { value } = inputData;
 
-   await context?.writer?.write({
+    await context?.writer?.write({
       type: "custom-event",
       status: "pending"
     });
 
     const response = await fetch(...);
 
-   await context?.writer?.write({
+    await context?.writer?.write({
       type: "custom-event",
       status: "success"
     });
@@ -69,14 +67,13 @@ export const testTool = createTool({
 });
 ```
 
-You can also use `writer.custom` if you want to emit top level stream chunks, This useful and relevant when
+You can also use `writer.custom()` if you want to emit top level stream chunks, This useful and relevant when
 integrating with UI Frameworks
 
-```typescript {5,8,15} showLineNumbers copy
+```typescript {4,7,14} showLineNumbers copy
 import { createTool } from "@mastra/core/tools";
 
 export const testTool = createTool({
-  // ...
   execute: async (inputData, context) => {
     const { value } = inputData;
 
@@ -169,12 +166,11 @@ import { createTool } from "@mastra/core/tools";
 import { z } from "zod";
 
 export const testTool = createTool({
-  // ...
   execute: async (inputData, context) => {
     const { city } = inputData;
 
-    const testAgent = context?.mastra?.getAgent("testAgent");
-    const stream = await testAgent?.stream(`What is the weather in ${city}?`);
+    const agent = context?.mastra?.getAgent("testAgent");
+    const stream = await agent?.stream(`What is the weather in ${city}?`);
 
     await stream!.fullStream.pipeTo(context?.writer!);
 

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # @mastra/mcp-docs-server
 
+## 1.0.0-beta.9
+
+### Patch Changes
+
+- Updated dependencies [[`72df8ae`](https://github.com/mastra-ai/mastra/commit/72df8ae595584cdd7747d5c39ffaca45e4507227), [`9198899`](https://github.com/mastra-ai/mastra/commit/91988995c427b185c33714b7f3be955367911324), [`653e65a`](https://github.com/mastra-ai/mastra/commit/653e65ae1f9502c2958a32f47a5a2df11e612a92), [`c6fd6fe`](https://github.com/mastra-ai/mastra/commit/c6fd6fedd09e9cf8004b03a80925f5e94826ad7e), [`fdf5a82`](https://github.com/mastra-ai/mastra/commit/fdf5a822716b2fd7ba2e50bd4c1521851e208cd9), [`0bed332`](https://github.com/mastra-ai/mastra/commit/0bed332843f627202c6520eaf671771313cd20f3)]:
+  - @mastra/core@1.0.0-beta.9
+  - @mastra/mcp@1.0.0-beta.6
+
 ## 1.0.0-beta.8
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mastra/mcp-docs-server",
-  "version": "1.0.0-beta.8",
+  "version": "1.0.0-beta.9",
   "description": "MCP server for accessing Mastra.ai documentation, changelogs, and news.",
   "type": "module",
   "main": "dist/index.js",
@@ -28,8 +28,8 @@
     "@modelcontextprotocol/sdk": "^1.17.5",
     "jsdom": "^26.1.0",
     "zod": "^3.25.76",
-    "@mastra/core": "1.0.0-beta.8",
-    "@mastra/mcp": "^1.0.0-beta.5"
+    "@mastra/core": "1.0.0-beta.9",
+    "@mastra/mcp": "^1.0.0-beta.6"
   },
   "devDependencies": {
     "@hono/node-server": "^1.19.6",
@@ -46,7 +46,7 @@
     "typescript": "^5.8.3",
     "vitest": "4.0.12",
     "@internal/lint": "0.0.53",
-    "@mastra/core": "1.0.0-beta.8"
+    "@mastra/core": "1.0.0-beta.9"
   },
   "homepage": "https://mastra.ai",
   "repository": {