@mastra/mcp-docs-server 1.0.0-beta.13 → 1.0.0-beta.15

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

@@ -25,7 +25,7 @@ The `MastraServer` abstract class from `@mastra/server/server-adapter` provides
 
 The class takes three type parameters that represent your framework's types:
 
-```typescript title="my-framework-adapter.ts" copy
+```typescript title="my-framework-adapter.ts"
 import { MastraServer } from '@mastra/server/server-adapter';
 
 export class MyFrameworkServer extends MastraServer<
@@ -50,7 +50,7 @@ You must implement these six abstract methods. Each handles a specific part of t
 
 This method runs first and attaches Mastra context to every incoming request. Route handlers need access to the Mastra instance, tools, and other context to function. How you attach this context depends on your framework — Express uses `res.locals`, Hono uses `c.set()`, and other frameworks have their own patterns.
 
-```typescript copy
+```typescript
 registerContextMiddleware(): void {
   this.app.use('*', (req, res, next) => {
     // Attach context to your framework's request/response
@@ -77,7 +77,7 @@ Context to attach:
 
 Register authentication and authorization middleware. This method should check if authentication is configured on the Mastra instance and skip registration entirely if not. When auth is configured, you'll typically register two middleware functions: one for authentication (validating tokens and setting the user) and one for authorization (checking if the user can access the requested resource).
 
-```typescript copy
+```typescript
 registerAuthMiddleware(): void {
   const authConfig = this.mastra.getServer()?.auth;
   if (!authConfig) return;
@@ -113,7 +113,7 @@ registerAuthMiddleware(): void {
 
 Register a single route with your framework. This method is called once for each Mastra route during initialization. It receives a `ServerRoute` object containing the path, HTTP method, handler function, and Zod schemas for validation. Your implementation should wire this up to your framework's routing system.
 
-```typescript copy
+```typescript
 async registerRoute(
   app: MyApp,
   route: ServerRoute,
@@ -160,7 +160,7 @@ async registerRoute(
 
 Extract URL parameters, query parameters, and request body from the incoming request. Different frameworks expose these values in different ways—Express uses `req.params`, `req.query`, and `req.body`, while other frameworks may use different property names or require method calls. This method normalizes the extraction for your framework.
 
-```typescript copy
+```typescript
 async getParams(
   route: ServerRoute,
   request: MyRequest
@@ -184,7 +184,7 @@ async getParams(
 
 Send the response back to the client based on the route's response type. Mastra routes can return different response types: JSON for most API responses, streams for agent generation, and special types for MCP transports. Your implementation should handle each type appropriately for your framework.
 
-```typescript copy
+```typescript
 async sendResponse(
   route: ServerRoute,
   response: MyResponse,
@@ -219,7 +219,7 @@ async sendResponse(
 
 Handle streaming responses for agent generation. When an agent generates a response, it produces a stream of chunks that should be sent to the client as they become available. This method reads from the stream, optionally applies redaction to hide sensitive data, and writes chunks to the response in the appropriate format (SSE or newline-delimited JSON).
 
-```typescript copy
+```typescript
 async stream(
   route: ServerRoute,
   response: MyResponse,
@@ -282,7 +282,7 @@ The `parse*` methods use Zod schemas defined on each route to validate input and
 
 Your adapter's constructor should accept the same options as the base class and pass them to `super()`. You can add additional framework-specific options if needed:
 
-```typescript copy
+```typescript
 constructor(options: {
   app: MyApp;
   mastra: Mastra;
@@ -302,7 +302,7 @@ See [Server Adapters](/docs/v1/server/server-adapters#constructor-options) for f
 
 Here's a skeleton implementation showing all the required methods. This uses pseudocode for framework-specific parts—replace with your framework's actual APIs:
 
-```typescript title="my-framework-adapter.ts" copy
+```typescript title="my-framework-adapter.ts"
 import { MastraServer, ServerRoute } from '@mastra/server/server-adapter';
 import type { Mastra } from '@mastra/core';
 
@@ -359,7 +359,7 @@ export class MyFrameworkServer extends MastraServer<MyApp, MyRequest, MyResponse
 
 Once your adapter is implemented, use it the same way as the provided adapters:
 
-```typescript title="server.ts" copy
+```typescript title="server.ts"
 import { MyFrameworkServer } from './my-framework-adapter';
 import { mastra } from './mastra';
 

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

@@ -9,12 +9,11 @@ By default, Mastra automatically exposes registered agents and workflows via its
 
 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 title="src/mastra/index.ts" copy
+```typescript title="src/mastra/index.ts"
 import { Mastra } from "@mastra/core";
 import { registerApiRoute } from "@mastra/core/server";
 
 export const mastra = new Mastra({
-  // ...
   server: {
     apiRoutes: [
       registerApiRoute("/my-custom-route", {
@@ -41,12 +40,11 @@ Each route's handler receives the Hono `Context`. Within the handler you can acc
 
 To add route-specific middleware pass a `middleware` array when calling `registerApiRoute()`.
 
-```typescript title="src/mastra/index.ts" copy
+```typescript title="src/mastra/index.ts"
 import { Mastra } from "@mastra/core";
 import { registerApiRoute } from "@mastra/core/server";
 
 export const mastra = new Mastra({
-  // ...
   server: {
     apiRoutes: [
       registerApiRoute("/my-custom-route", {

package/.docs/raw/server/mastra-client.mdx

@@ -61,7 +61,7 @@ To use the Mastra Client SDK, install the required dependencies:
 
 Once initialized with a `baseUrl`, `MastraClient` exposes a type-safe interface for calling agents, tools, and workflows.
 
-```typescript title="lib/mastra-client.ts" showLineNumbers copy
+```typescript title="lib/mastra-client.ts"
 import { MastraClient } from "@mastra/client-js";
 
 export const mastraClient = new MastraClient({
@@ -85,7 +85,7 @@ The Mastra Client SDK exposes all resources served by the Mastra Server
 
 Call `.generate()` with an array of message objects that include `role` and `content`:
 
-```typescript showLineNumbers copy
+```typescript
 import { mastraClient } from "lib/mastra-client";
 
 const testAgent = async () => {
@@ -108,13 +108,17 @@ const testAgent = async () => {
 };
 ```
 
-> See [.generate()](/reference/v1/client-js/agents#generate-response) for more information.
+:::info
+
+Visit [.generate()](/reference/v1/client-js/agents#generate-response) for more information.
+
+:::
 
 ## Streaming responses
 
 Use `.stream()` for real-time responses with an array of message objects that include `role` and `content`:
 
-```typescript showLineNumbers copy
+```typescript
 import { mastraClient } from "lib/mastra-client";
 
 const testAgent = async () => {
@@ -141,17 +145,20 @@ const testAgent = async () => {
 };
 ```
 
-> See [.stream()](/reference/v1/client-js/agents#stream-response) for more information.
+:::info
+
+Visit [.stream()](/reference/v1/client-js/agents#stream-response) for more information.
+
+:::
 
 ## Configuration options
 
 `MastraClient` accepts optional parameters like `retries`, `backoffMs`, and `headers` to control request behavior. These parameters are useful for controlling retry behavior and including diagnostic metadata.
 
-```typescript title="lib/mastra-client.ts" showLineNumbers copy
+```typescript title="lib/mastra-client.ts"
 import { MastraClient } from "@mastra/client-js";
 
 export const mastraClient = new MastraClient({
-  // ...
   retries: 3,
   backoffMs: 300,
   maxBackoffMs: 5000,
@@ -161,7 +168,11 @@ export const mastraClient = new MastraClient({
 });
 ```
 
-> See [MastraClient](/reference/v1/client-js/mastra-client) for more configuration options.
+:::info
+
+Visit [MastraClient](/reference/v1/client-js/mastra-client) for more configuration options.
+
+:::
 
 ## Adding request cancelling
 
@@ -169,7 +180,7 @@ export const mastraClient = new MastraClient({
 
 Pass an `AbortSignal` to the client constructor to enable cancellation across all requests.
 
-```typescript {3,7} title="lib/mastra-client.ts" showLineNumbers copy
+```typescript {3,7} title="lib/mastra-client.ts"
 import { MastraClient } from "@mastra/client-js";
 
 export const controller = new AbortController();
@@ -184,7 +195,7 @@ export const mastraClient = new MastraClient({
 
 Calling `.abort()` will cancel any ongoing requests tied to that signal.
 
-```typescript {4} showLineNumbers copy
+```typescript {4}
 import { mastraClient, controller } from "lib/mastra-client";
 
 const handleAbort = () => {
@@ -198,7 +209,7 @@ Define tools directly in client-side applications using the `createTool()` funct
 
 This lets agents trigger browser-side functionality such as DOM manipulation, local storage access, or other Web APIs, enabling tool execution in the user's environment rather than on the server.
 
-```typescript {27} showLineNumbers copy
+```typescript {27}
 import { createTool } from "@mastra/client-js";
 import { z } from "zod";
 
@@ -239,7 +250,7 @@ const handleClientTool = async () => {
 
 This is a standard Mastra [agent](../agents/overview#setting-up-agents) configured to return hex color codes, intended to work with the browser-based client tool defined above.
 
-```typescript title="src/mastra/agents/color-agent" showLineNumbers copy
+```typescript title="src/mastra/agents/color-agent"
 import { Agent } from "@mastra/core/agent";
 
 export const colorAgent = new Agent({
@@ -256,7 +267,7 @@ export const colorAgent = new Agent({
 
 You can also use `MastraClient` in server-side environments such as API routes, serverless functions or actions. The usage will broadly remain the same but you may need to recreate the response to your client:
 
-```typescript {8} showLineNumbers
+```typescript {8}
 export async function action() {
   const agent = mastraClient.getAgent("testAgent");
 

package/.docs/raw/server/mastra-server.mdx

@@ -35,7 +35,7 @@ adding additional server behaviour.
 
 You can configure server `port`, `host`, `studioBase`, and `timeout` in the Mastra instance.
 
-```typescript title="src/mastra/index.ts" copy
+```typescript title="src/mastra/index.ts"
 import { Mastra } from "@mastra/core";
 
 export const mastra = new Mastra({
@@ -54,7 +54,7 @@ The `studioBase` option allows you to host Mastra Studio on a sub-path of your e
 
 Mastra requires `module` and `moduleResolution` values that support modern Node.js versions. Older settings like `CommonJS` or `node` are incompatible with Mastra’s packages and will cause resolution errors.
 
-```json {4-5} title="tsconfig.json" copy
+```json {4-5} title="tsconfig.json"
 {
   "compilerOptions": {
     "target": "ES2022",
@@ -77,7 +77,7 @@ Mastra requires `module` and `moduleResolution` values that support modern Node.
 
 Mastra allows you to configure CORS (Cross-Origin Resource Sharing) settings for your server.
 
-```typescript title="src/mastra/index.ts" copy
+```typescript title="src/mastra/index.ts"
 import { Mastra } from "@mastra/core";
 
 export const mastra = new Mastra({

package/.docs/raw/server/middleware.mdx

@@ -13,7 +13,7 @@ A middleware receives the [Hono](https://hono.dev) `Context` (`c`) and a `next`
 function. If it returns a `Response` the request is short-circuited. Calling
 `next()` continues processing the next middleware or route handler.
 
-```typescript copy showLineNumbers
+```typescript
 import { Mastra } from "@mastra/core";
 
 export const mastra = new Mastra({
@@ -44,7 +44,7 @@ export const mastra = new Mastra({
 To attach middleware to a single route pass the `middleware` option to
 `registerApiRoute`:
 
-```typescript copy showLineNumbers
+```typescript
 registerApiRoute("/my-custom-route", {
   method: "GET",
   middleware: [
@@ -68,7 +68,7 @@ registerApiRoute("/my-custom-route", {
 
 You can populate `RequestContext` dynamically in server middleware by extracting information from the request. In this example, the `temperature-unit` is set based on the Cloudflare `CF-IPCountry` header to ensure responses match the user's locale.
 
-```typescript title="src/mastra/index.ts" showLineNumbers copy
+```typescript title="src/mastra/index.ts"
 import { Mastra } from "@mastra/core";
 import { RequestContext } from "@mastra/core/request-context";
 import { testWeatherAgent } from "./agents/test-weather-agent";
@@ -95,7 +95,7 @@ export const mastra = new Mastra({
 
 ### Authentication
 
-```typescript copy
+```typescript
 {
   handler: async (c, next) => {
     const authHeader = c.req.header('Authorization');
@@ -112,7 +112,7 @@ export const mastra = new Mastra({
 
 ### CORS support
 
-```typescript copy
+```typescript
 {
   handler: async (c, next) => {
     c.header('Access-Control-Allow-Origin', '*');
@@ -136,7 +136,7 @@ export const mastra = new Mastra({
 
 ### Request logging
 
-```typescript copy
+```typescript
 {
   handler: async (c, next) => {
     const start = Date.now();
@@ -152,7 +152,7 @@ export const mastra = new Mastra({
 When integrating with Mastra Cloud or custom clients the following headers can
 be inspected by middleware to tailor behavior:
 
-```typescript copy
+```typescript
 {
   handler: async (c, next) => {
     const isFromMastraCloud = c.req.header('x-mastra-cloud') === 'true';

package/.docs/raw/server/request-context.mdx

@@ -28,7 +28,7 @@ The `.set()` method takes two arguments:
 1. **key**: The name used to identify the value.
 2. **value**: The data to associate with that key.
 
-```typescript showLineNumbers
+```typescript
 import { RequestContext } from "@mastra/core/request-context";
 
 export type UserTier = {
@@ -74,7 +74,7 @@ await weatherTool.execute({
 
 You can populate `requestContext` dynamically in server middleware by extracting information from the request. In this example, the `temperature-unit` is set based on the Cloudflare `CF-IPCountry` header to ensure responses match the user's locale.
 
-```typescript title="src/mastra/index.ts" showLineNumbers copy
+```typescript title="src/mastra/index.ts"
 import { Mastra } from "@mastra/core";
 import { RequestContext } from "@mastra/core/request-context";
 import { testWeatherAgent } from "./agents/test-weather-agent";
@@ -99,13 +99,17 @@ export const mastra = new Mastra({
 });
 ```
 
-> See [Middleware](/docs/v1/server/middleware) for how to use server middleware.
+:::info
+
+Visit [Middleware](/docs/v1/server/middleware) for how to use server middleware.
+
+:::
 
 ## Accessing values with agents
 
 You can access the `requestContext` argument from any supported configuration options in agents. These functions can be sync or `async`. Use the `.get()` method to read values from `requestContext`.
 
-```typescript {7-8,15,18,21} title="src/mastra/agents/weather-agent.ts" showLineNumbers
+```typescript title="src/mastra/agents/weather-agent.ts"
 export type UserTier = {
   "user-tier": "enterprise" | "pro";
 };
@@ -116,32 +120,27 @@ export const weatherAgent = new Agent({
   instructions: async ({ requestContext }) => {
     const userTier = requestContext.get("user-tier") as UserTier["user-tier"];
 
-    if (userTier === "enterprise") {
-      // ...
-    }
-    // ...
-  },
-  model: ({ requestContext }) => {
-    // ...
-  },
-  tools: ({ requestContext }) => {
-    // ...
-  },
-  memory: ({ requestContext }) => {
-    // ...
+    if (userTier === "enterprise") {}
   },
+  model: ({ requestContext }) => {},
+  tools: ({ requestContext }) => {},
+  memory: ({ requestContext }) => {},
 });
 ```
 
 You can also use `requestContext` with other options like `agents`, `workflows`, `scorers`, `inputProcessors`, and `outputProcessors`.
 
-> See [Agent](/reference/v1/agents/agent) for a full list of configuration options.
+:::info
+
+Visit [Agent](/reference/v1/agents/agent) for a full list of configuration options.
+
+:::
 
 ## Accessing values from workflow steps
 
 You can access the `requestContext` argument from a workflow step's `execute` function. This function can be sync or async. Use the `.get()` method to read values from `requestContext`.
 
-```typescript {7-8} title="src/mastra/workflows/weather-workflow.ts" showLineNumbers copy
+```typescript title="src/mastra/workflows/weather-workflow.ts"
 export type UserTier = {
   "user-tier": "enterprise" | "pro";
 };
@@ -151,21 +150,22 @@ const stepOne = createStep({
   execute: async ({ requestContext }) => {
     const userTier = requestContext.get("user-tier") as UserTier["user-tier"];
 
-    if (userTier === "enterprise") {
-      // ...
-    }
-    // ...
+    if (userTier === "enterprise") {}
   },
 });
 ```
 
-> See [createStep()](/reference/v1/workflows/step) for a full list of configuration options.
+:::info
+
+Visit [createStep()](/reference/v1/workflows/step) for a full list of configuration options.
+
+:::
 
 ## Accessing values with tools
 
 You can access the `requestContext` argument from a tool’s `execute` function. This function is `async`. Use the `.get()` method to read values from `requestContext`.
 
-```typescript {7-8} title="src/mastra/tools/weather-tool.ts" showLineNumbers
+```typescript title="src/mastra/tools/weather-tool.ts"
 export type UserTier = {
   "user-tier": "enterprise" | "pro";
 };
@@ -175,15 +175,16 @@ export const weatherTool = createTool({
   execute: async ({ requestContext }) => {
     const userTier = requestContext.get("user-tier") as UserTier["user-tier"];
 
-    if (userTier === "enterprise") {
-      // ...
-    }
-    // ...
+    if (userTier === "enterprise") {}
   },
 });
 ```
 
-> See [createTool()](/reference/v1/tools/create-tool) for a full list of configuration options.
+:::info
+
+Visit [createTool()](/reference/v1/tools/create-tool) for a full list of configuration options.
+
+:::
 
 ## Related
 

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

@@ -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();
 

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',