@mastra/mcp-docs-server 1.0.0-beta.11 → 1.0.0-beta.14

package/.docs/raw/{server-db → server}/server-adapters.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Server Adapters | Server & DB"
+title: "Server Adapters | Server"
 description: "Manually configure a Mastra server using Hono or Express adapters."
 ---
 
@@ -18,7 +18,7 @@ Server adapters let you run Mastra with your own HTTP server instead of the Hono
 
 :::tip
 
-For simple deployments without custom server requirements, use `mastra build` instead. It configures server setup, registers middleware, and applies deployment settings based on your project configuration. See [Server Configuration](/docs/v1/server-db/mastra-server).
+For deployments without custom server requirements, use `mastra build` instead. It configures server setup, registers middleware, and applies deployment settings based on your project configuration. See [Server Configuration](/docs/v1/server/mastra-server).
 
 :::
 
@@ -29,7 +29,7 @@ Mastra currently provides two official server adapters:
 - [@mastra/express](/reference/v1/server/express-adapter): Express framework adapter
 - [@mastra/hono](/reference/v1/server/hono-adapter): Hono framework adapter
 
-You can build your own adapter, read [Custom Adapters](/docs/v1/server-db/custom-adapters) for details.
+You can build your own adapter, read [Custom Adapters](/docs/v1/server/custom-adapters) for details.
 
 ## Installation
 
@@ -115,7 +115,7 @@ Calling `init()` runs three steps in order. Understanding this flow helps when y
 
 For custom middleware ordering, call each method separately instead of `init()`. This is useful when you need middleware that runs before Mastra's context is set up, or when you need to insert logic between the initialization steps.
 
-```typescript title="server.ts" copy
+```typescript title="server.ts"
 const server = new MastraServer({ app, mastra });
 
 // Your middleware first
@@ -156,7 +156,7 @@ Visit "Adding custom routes" for [Express](/reference/v1/server/express-adapter#
 
 By default, Mastra routes are registered at `/api/agents`, `/api/workflows`, etc. Use the `prefix` option to change this. This is useful for API versioning or when integrating with an existing app that has its own `/api` routes.
 
-```typescript copy
+```typescript
 const server = new MastraServer({
   app,
   mastra,
@@ -170,7 +170,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
+```typescript
 const server = new MastraServer({
   app,
   mastra,
@@ -193,7 +193,7 @@ This redaction happens at the HTTP boundary, so internal callbacks like `onStepF
 
 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
+```typescript
 const server = new MastraServer({
   app,
   mastra,
@@ -215,7 +215,7 @@ When authentication is configured on your Mastra instance, all routes require au
 
 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
+```typescript
 const server = new MastraServer({
   app,
   mastra,
@@ -244,7 +244,7 @@ See [MastraServer](/reference/v1/server/mastra-server) for full configuration op
 
 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
+```typescript
 // Via the MastraServer instance
 const app = server.getApp();
 
@@ -305,8 +305,8 @@ See [MCP](/docs/v1/mcp/overview) for configuration details and how to set up MCP
 
 - [Hono Adapter](/reference/v1/server/hono-adapter) - Hono-specific setup
 - [Express Adapter](/reference/v1/server/express-adapter) - Express-specific setup
-- [Custom Adapters](/docs/v1/server-db/custom-adapters) - Building adapters for other frameworks
-- [Server Configuration](/docs/v1/server-db/mastra-server) - Using `mastra build` instead
-- [Authentication](/docs/v1/auth) - Configuring auth for your server
+- [Custom Adapters](/docs/v1/server/custom-adapters) - Building adapters for other frameworks
+- [Server Configuration](/docs/v1/server/mastra-server) - Using `mastra build` instead
+- [Authentication](/docs/v1/server/auth) - Configuring auth for your server
 - [MastraServer Reference](/reference/v1/server/mastra-server) - Full API reference
 - [createRoute() Reference](/reference/v1/server/create-route) - Creating type-safe custom routes

package/.docs/raw/streaming/events.mdx

@@ -44,7 +44,7 @@ When using `agent.network()` for multi-agent collaboration, additional event typ
 
 Iterate over the `stream` with a `for await` loop to inspect all emitted event chunks.
 
-```typescript {3,7} showLineNumbers copy
+```typescript
 const testAgent = mastra.getAgent("testAgent");
 
 const stream = await testAgent.stream([
@@ -56,7 +56,11 @@ for await (const chunk of stream) {
 }
 ```
 
-> See [Agent.stream()](/reference/v1/streaming/agents/stream) for more information.
+:::info
+
+Visit [Agent.stream()](/reference/v1/streaming/agents/stream) for more information.
+
+:::
 
 ### Example agent output
 
@@ -91,7 +95,7 @@ Below is an example of events that may be emitted. Each event always includes a
 
 Iterate over the `stream` with a `for await` loop to inspect all emitted event chunks.
 
-```typescript {5,11} showLineNumbers copy
+```typescript {5,11}
 const testWorkflow = mastra.getWorkflow("testWorkflow");
 
 const run = await testWorkflow.createRun();
@@ -136,7 +140,7 @@ Below is an example of events that may be emitted. Each event always includes a
 
 When using multi-agent collaboration with `agent.network()`, iterate over the stream to track how tasks are delegated and executed across agents, workflows, and tools.
 
-```typescript {3,5} showLineNumbers copy
+```typescript {3,5}
 const networkAgent = mastra.getAgent("networkAgent");
 
 const networkStream = await networkAgent.network(
@@ -148,7 +152,11 @@ for await (const chunk of networkStream) {
 }
 ```
 
-> See [Agent.network()](/reference/v1/agents/network) for more information.
+:::info
+
+Visit [Agent.network()](/reference/v1/agents/network) for more information.
+
+:::
 
 ### Example network output
 
@@ -195,14 +203,13 @@ Network streams emit events that track the orchestration flow. Each iteration be
     }
   }
 }
-// ...more events
 ```
 
 ### Filtering network events
 
 You can filter events by type to track specific aspects of the network execution:
 
-```typescript {5-8,11-13,16-18} showLineNumbers copy
+```typescript {5-8,11-13,16-18}
 const networkStream = await networkAgent.network(
   "Analyze data and create visualization",
 );

package/.docs/raw/streaming/overview.mdx

@@ -22,7 +22,7 @@ You can pass a single string for simple prompts, an array of strings when provid
 
 A `textStream` breaks the response into chunks as it's generated, allowing output to stream progressively instead of arriving all at once. Iterate over the `textStream` using a `for await` loop to inspect each stream chunk.
 
-```typescript {3,7} showLineNumbers copy
+```typescript {3,7}
 const testAgent = mastra.getAgent("testAgent");
 
 const stream = await testAgent.stream([
@@ -34,7 +34,11 @@ for await (const chunk of stream.textStream) {
 }
 ```
 
-> See [Agent.stream()](/reference/v1/streaming/agents/stream) for more information.
+:::info
+
+Visit [Agent.stream()](/reference/v1/streaming/agents/stream) for more information.
+
+:::
 
 ### Output from `Agent.stream()`
 
@@ -62,7 +66,7 @@ AI SDK v5 uses `LanguageModelV2` for the model providers. If you are getting an
 
 For integration with AI SDK v5, use the `toAISdkV5Stream()` utility from `@mastra/ai-sdk` to convert Mastra streams to AI SDK-compatible format:
 
-```typescript {2,9-12} showLineNumbers copy
+```typescript {2,9-12}
 import { toAISdkV5Stream } from "@mastra/ai-sdk";
 
 const testAgent = mastra.getAgent("testAgent");
@@ -79,7 +83,7 @@ const aiSDKStream = toAISdkV5Stream(stream, { from: "agent" });
 
 For converting messages to AI SDK v5 format, use the `toAISdkV5Messages()` utility from `@mastra/ai-sdk/ui`:
 
-```typescript {1,4} showLineNumbers copy
+```typescript {1,4}
 import { toAISdkV5Messages } from "@mastra/ai-sdk/ui";
 
 const messages = [{ role: "user", content: "Hello" }];
@@ -92,7 +96,7 @@ The `network()` method enables multi-agent collaboration by executing a network
 
 > **Note**: This method is experimental and requires memory to be configured on the agent.
 
-```typescript {3,5-7} showLineNumbers copy
+```typescript {3,5-7}
 const testAgent = mastra.getAgent("testAgent");
 
 const networkStream = await testAgent.network("Help me organize my day");
@@ -102,7 +106,11 @@ for await (const chunk of networkStream) {
 }
 ```
 
-> See [Agent.network()](/reference/v1/agents/network) for more information.
+:::info
+
+Visit [Agent.network()](/reference/v1/agents/network) for more information.
+
+:::
 
 #### Network stream properties
 
@@ -112,7 +120,7 @@ The network stream provides access to execution information:
 - **`networkStream.result`**: Promise resolving to the complete execution results
 - **`networkStream.usage`**: Promise resolving to token usage information
 
-```typescript {9-11} showLineNumbers copy
+```typescript {9-11}
 const testAgent = mastra.getAgent("testAgent");
 
 const networkStream = await testAgent.network(
@@ -136,7 +144,7 @@ Streaming from a workflow returns a sequence of structured events describing the
 
 The `stream()` method returns a `ReadableStream` of events directly.
 
-```typescript {3,9} showLineNumbers copy
+```typescript {3,9}
 const run = await testWorkflow.createRun();
 
 const stream = await run.stream({
@@ -150,14 +158,17 @@ for await (const chunk of stream) {
 }
 ```
 
-> See [Run.stream()](/reference/v1/streaming/workflows/stream) method documentation for more information.
+:::info
+
+Visit [Run.stream()](/reference/v1/streaming/workflows/stream) for more information.
+
+:::
 
 ### Output from `Run.stream()`
 
 The event structure includes `runId` and `from` at the top level, making it easier to identify and track workflow runs without digging into the payload.
 
 ```typescript
-// ...
 {
   type: 'workflow-start',
   runId: '1eeaf01a-d2bf-4e3f-8d1b-027795ccd3df',

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

@@ -18,7 +18,7 @@ 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 {2,9} showLineNumbers copy
+```typescript {2,9}
 import { Agent } from "@mastra/core/agent";
 import { testTool } from "../tools/test-tool";
 
@@ -41,7 +41,7 @@ You must `await` the call to `writer.write()` or else you will lock the stream a
 
 :::
 
-```typescript {4,7,14} showLineNumbers copy
+```typescript {4,7,14}
 import { createTool } from "@mastra/core/tools";
 
 export const testTool = createTool({
@@ -70,7 +70,7 @@ export const testTool = createTool({
 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 {4,7,14} showLineNumbers copy
+```typescript {4,7,14}
 import { createTool } from "@mastra/core/tools";
 
 export const testTool = createTool({
@@ -100,7 +100,7 @@ export const testTool = createTool({
 
 Events written to the stream are included in the emitted chunks. These chunks can be inspected to access any custom fields, such as event types, intermediate values, or tool-specific data.
 
-```typescript showLineNumbers copy
+```typescript
 const stream = await testAgent.stream([
   "What is the weather in London?",
   "Use the testTool",
@@ -119,7 +119,7 @@ Tools support lifecycle hooks that allow you to monitor different stages of tool
 
 ### Example: Using onInputAvailable and onOutput
 
-```typescript showLineNumbers copy
+```typescript
 import { createTool } from "@mastra/core/tools";
 import { z } from "zod";
 
@@ -161,7 +161,7 @@ For detailed documentation on all lifecycle hooks, see the [createTool() referen
 
 Pipe an agent's `fullStream` to the tool's `writer`. This streams partial output, and Mastra automatically aggregates the agent's usage into the tool run.
 
-```typescript showLineNumbers copy
+```typescript
 import { createTool } from "@mastra/core/tools";
 import { z } from "zod";
 

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

@@ -24,13 +24,12 @@ You must `await` the call to `writer.write(...)` or else you will lock the strea
 
 :::
 
-```typescript {5,8,15} showLineNumbers copy
+```typescript {5,7,14}
 import { createStep } from "@mastra/core/workflows";
 
 export const testStep = createStep({
-  // ...
   execute: async ({ inputData, writer }) => {
-     const { value } = inputData;
+    const { value } = inputData;
 
     await writer?.write({
       type: "custom-event",
@@ -39,7 +38,7 @@ export const testStep = createStep({
 
     const response = await fetch(...);
 
-   await writer?.write({
+    await writer?.write({
       type: "custom-event",
       status: "success"
     });
@@ -55,7 +54,7 @@ export const testStep = createStep({
 
 Events written to the stream are included in the emitted chunks. These chunks can be inspected to access any custom fields, such as event types, intermediate values, or step-specific data.
 
-```typescript showLineNumbers copy
+```typescript
 const testWorkflow = mastra.getWorkflow("testWorkflow");
 
 const run = await testWorkflow.createRun();
@@ -86,7 +85,7 @@ if (result!.status === "suspended") {
 
 If a workflow stream is closed or interrupted for any reason, you can resume it with the `resumeStream` method. This will return a new `ReadableStream` that you can use to observe the workflow events.
 
-```typescript showLineNumbers copy
+```typescript
 const newStream = await run.resumeStream();
 
 for await (const chunk of newStream) {
@@ -98,12 +97,11 @@ for await (const chunk of newStream) {
 
 Pipe an agent's `textStream` to the workflow step's `writer`. This streams partial output, and Mastra automatically aggregates the agent's usage into the workflow run.
 
-```typescript showLineNumbers copy
+```typescript
 import { createStep } from "@mastra/core/workflows";
 import { z } from "zod";
 
 export const testStep = createStep({
-  // ...
   execute: async ({ inputData, mastra, writer }) => {
     const { city } = inputData;
 

package/.docs/raw/tools-mcp/advanced-usage.mdx

@@ -82,13 +82,13 @@ Mastra maintains compatibility with the tool format used by the Vercel AI SDK (`
 
 First, ensure you have the `ai` package installed:
 
-```bash npm2yarn copy
+```bash npm2yarn
 npm install ai
 ```
 
 Here's an example of a tool defined using the Vercel AI SDK format:
 
-```typescript title="src/mastra/tools/vercelWeatherTool.ts" copy
+```typescript title="src/mastra/tools/vercelWeatherTool.ts"
 import { tool } from "ai";
 import { z } from "zod";
 

package/.docs/raw/tools-mcp/mcp-overview.mdx

@@ -29,7 +29,7 @@ npm install @mastra/mcp@beta
 
 The `MCPClient` connects Mastra primitives to external MCP servers, which can be local packages (invoked using `npx`) or remote HTTP(S) endpoints. Each server must be configured with either a `command` or a `url`, depending on how it's hosted.
 
-```typescript title="src/mastra/mcp/test-mcp-client.ts" showLineNumbers copy
+```typescript title="src/mastra/mcp/test-mcp-client.ts"
 import { MCPClient } from "@mastra/mcp";
 
 export const testMcpClient = new MCPClient({
@@ -48,13 +48,17 @@ export const testMcpClient = new MCPClient({
 });
 ```
 
-> See [MCPClient](/reference/v1/tools/mcp-client) for a full list of configuration options.
+:::info
+
+Visit [MCPClient](/reference/v1/tools/mcp-client) for a full list of configuration options.
+
+:::
 
 ## Using `MCPClient` with an agent
 
 To use tools from an MCP server in an agent, import your `MCPClient` and call `.listTools()` in the `tools` parameter. This loads from the defined MCP servers, making them available to the agent.
 
-```typescript {3,15} title="src/mastra/agents/test-agent.ts" showLineNumbers copy
+```typescript {3,15} title="src/mastra/agents/test-agent.ts"
 import { Agent } from "@mastra/core/agent";
 
 import { testMcpClient } from "../mcp/test-mcp-client";
@@ -74,13 +78,17 @@ export const testAgent = new Agent({
 });
 ```
 
-> See the [Agent Class](/reference/v1/agents/agent) for a full list of configuration options.
+:::info
+
+Visit [Agent Class](/reference/v1/agents/agent) for a full list of configuration options.
+
+:::
 
 ## Configuring `MCPServer`
 
 To expose agents, tools, and workflows from your Mastra application to external systems over HTTP(S) use the `MCPServer` class. This makes them accessible to any system or agent that supports the protocol.
 
-```typescript title="src/mastra/mcp/test-mcp-server.ts" showLineNumbers copy
+```typescript title="src/mastra/mcp/test-mcp-server.ts"
 import { MCPServer } from "@mastra/mcp";
 
 import { testAgent } from "../agents/test-agent";
@@ -97,7 +105,11 @@ export const testMcpServer = new MCPServer({
 });
 ```
 
-> See [MCPServer](/reference/v1/tools/mcp-server) for a full list of configuration options.
+:::info
+
+Visit [MCPServer](/reference/v1/tools/mcp-server) for a full list of configuration options.
+
+:::
 
 ### Serverless deployments
 
@@ -109,13 +121,12 @@ export const testMcpServer = new MCPServer({
 
 To make an MCP server available to other systems or agents that support the protocol, register it in the main `Mastra` instance using `mcpServers`.
 
-```typescript title="src/mastra/index.ts" showLineNumbers copy
+```typescript title="src/mastra/index.ts"
 import { Mastra } from "@mastra/core";
 
 import { testMcpServer } from "./mcp/test-mcp-server";
 
 export const mastra = new Mastra({
-  // ...
   mcpServers: {
     testMcpServer,  // Registry key: 'testMcpServer'
   },
@@ -141,9 +152,13 @@ mastra.getMCPServerById('test-mcp-server');    // By intrinsic ID
 
 Use the `.listTools()` method to fetch tools from all configured MCP servers. This is suitable when configuration (such as API keys) is static and consistent across users or requests. Call it once and pass the result to the `tools` property when defining your agent.
 
-> See [listTools()](/reference/v1/tools/mcp-client#listtools) for more information.
+:::info
+
+Visit [listTools()](/reference/v1/tools/mcp-client#listtools) for more information.
+
+:::
 
-```typescript {7} title="src/mastra/agents/test-agent.ts" showLineNumbers copy
+```typescript {7} title="src/mastra/agents/test-agent.ts"
 import { Agent } from "@mastra/core/agent";
 
 import { testMcpClient } from "../mcp/test-mcp-client";
@@ -158,7 +173,7 @@ export const testAgent = new Agent({
 
 Use the `.listToolsets()` method when tool configuration may vary by request or user, such as in a multi-tenant system where each user provides their own API key. This method returns toolsets that can be passed to the `toolsets` option in the agent's `.generate()` or `.stream()` calls.
 
-```typescript {5-16,21} showLineNumbers copy
+```typescript {5-16,21}
 import { MCPClient } from "@mastra/mcp";
 import { mastra } from "./mastra";
 
@@ -190,7 +205,11 @@ async function handleRequest(userPrompt: string, userApiKey: string) {
 }
 ```
 
-> See [listToolsets()](/reference/v1/tools/mcp-client#listtoolsets) for more information.
+:::info
+
+Visit [listToolsets()](/reference/v1/tools/mcp-client#listtoolsets) for more information.
+
+:::
 
 ## Connecting to an MCP registry
 

package/.docs/raw/tools-mcp/overview.mdx

@@ -18,7 +18,7 @@ Each tool typically defines:
 
 In Mastra, you create tools using the [`createTool`](/reference/v1/tools/create-tool) function from the `@mastra/core/tools` package.
 
-```typescript title="src/mastra/tools/weatherInfo.ts" copy
+```typescript title="src/mastra/tools/weatherInfo.ts"
 import { createTool } from "@mastra/core/tools";
 import { z } from "zod";
 
@@ -56,23 +56,18 @@ To make tools available to an agent, you configure them in the agent's definitio
 
 ## Using `RequestContext`
 
-Use [RequestContext](/docs/v1/server-db/request-context) to access request-specific values. This lets you conditionally adjust behavior based on the context of the request.
+Use [RequestContext](/docs/v1/server/request-context) to access request-specific values. This lets you conditionally adjust behavior based on the context of the request.
 
-```typescript title="src/mastra/tools/test-tool.ts" showLineNumbers
+```typescript title="src/mastra/tools/test-tool.ts"
 export type UserTier = {
   "user-tier": "enterprise" | "pro";
 };
 
-const advancedTools = () => {
-  // ...
-};
+const advancedTools = () => {};
 
-const baseTools = () => {
-  // ...
-};
+const baseTools = () => {};
 
 export const testTool = createTool({
-  // ...
   execute: async ({ requestContext }) => {
     const userTier = requestContext.get("user-tier") as UserTier["user-tier"];
 
@@ -81,7 +76,11 @@ export const testTool = createTool({
 });
 ```
 
-> See [Request Context](/docs/v1/server-db/request-context) for more information.
+:::info
+
+Visit [Request Context](/docs/v1/server/request-context) for more information.
+
+:::
 
 ## Testing with Studio
 

package/.docs/raw/voice/overview.mdx

@@ -917,7 +917,7 @@ const voiceAgent = new Agent({
   id: "aisdk-voice-agent",
   name: "AI SDK Voice Agent",
   instructions: "You are a helpful assistant with voice capabilities.",
-  model: openai("gpt-5.1"),
+  model: "openai/gpt-5.1",
   voice,
 });
 ```