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

package/.docs/raw/{auth → server/auth}/workos.mdx

@@ -19,7 +19,7 @@ This example uses WorkOS authentication. Make sure to:
 3. Configure your redirect URIs and allowed origins
 4. Set up Organizations and configure user roles as needed
 
-```env title=".env" copy
+```env title=".env"
 WORKOS_API_KEY=sk_live_...
 WORKOS_CLIENT_ID=client_...
 ```
@@ -32,7 +32,7 @@ WORKOS_CLIENT_ID=client_...
 
 Before you can use the `MastraAuthWorkos` class you have to install the `@mastra/auth-workos` package.
 
-```bash copy
+```bash
 npm install @mastra/auth-workos@beta
 ```
 
@@ -40,12 +40,11 @@ npm install @mastra/auth-workos@beta
 
 ### Basic usage with environment variables
 
-```typescript {2,7} title="src/mastra/index.ts" showLineNumbers copy
+```typescript {2,6} title="src/mastra/index.ts"
 import { Mastra } from "@mastra/core";
 import { MastraAuthWorkos } from "@mastra/auth-workos";
 
 export const mastra = new Mastra({
-  // ..
   server: {
     auth: new MastraAuthWorkos(),
   },
@@ -54,12 +53,11 @@ export const mastra = new Mastra({
 
 ### Custom configuration
 
-```typescript {2,7-10} title="src/mastra/index.ts" showLineNumbers copy
+```typescript {2,6-9} title="src/mastra/index.ts"
 import { Mastra } from "@mastra/core";
 import { MastraAuthWorkos } from "@mastra/auth-workos";
 
 export const mastra = new Mastra({
-  // ..
   server: {
     auth: new MastraAuthWorkos({
       apiKey: process.env.WORKOS_API_KEY,
@@ -82,7 +80,7 @@ By default, `MastraAuthWorkos` checks whether the authenticated user has an 'adm
 
 To customize user authorization, provide a custom `authorizeUser` function:
 
-```typescript title="src/mastra/auth.ts" showLineNumbers copy
+```typescript title="src/mastra/auth.ts"
 import { MastraAuthWorkos } from "@mastra/auth-workos";
 
 const workosAuth = new MastraAuthWorkos({
@@ -94,7 +92,11 @@ const workosAuth = new MastraAuthWorkos({
 });
 ```
 
-> See the [MastraAuthWorkos](/reference/v1/auth/workos) API reference for all available configuration options.
+:::info
+
+Visit [MastraAuthWorkos](/reference/v1/auth/workos) for all available configuration options.
+
+:::
 
 ## Client-side setup
 
@@ -104,7 +106,7 @@ When using WorkOS auth, you'll need to implement the WorkOS authentication flow
 
 First, install the WorkOS SDK in your application:
 
-```bash copy
+```bash
 npm install @workos-inc/node
 ```
 
@@ -112,7 +114,7 @@ npm install @workos-inc/node
 
 After users complete the WorkOS authentication flow and return with an authorization code, exchange it for an access token:
 
-```typescript title="lib/auth.ts" showLineNumbers copy
+```typescript title="lib/auth.ts"
 import { WorkOS } from "@workos-inc/node";
 
 const workos = new WorkOS(process.env.WORKOS_API_KEY);
@@ -137,7 +139,7 @@ export const authenticateWithWorkos = async (
 
 When `auth` is enabled, all requests made with `MastraClient` must include a valid WorkOS access token in the `Authorization` header:
 
-```typescript title="lib/mastra/mastra-client.ts" showLineNumbers copy
+```typescript title="lib/mastra/mastra-client.ts"
 import { MastraClient } from "@mastra/client-js";
 
 export const createMastraClient = (accessToken: string) => {
@@ -152,7 +154,11 @@ export const createMastraClient = (accessToken: string) => {
 
 > **Note:** The access token must be prefixed with `Bearer` in the Authorization header.
 
-> See [Mastra Client SDK](/docs/v1/server-db/mastra-client) for more configuration options.
+:::info
+
+Visit [Mastra Client SDK](/docs/v1/server/mastra-client) for more configuration options.
+
+:::
 
 ### Making authenticated requests
 
@@ -160,7 +166,7 @@ Once `MastraClient` is configured with the WorkOS access token, you can send aut
 
 <Tabs>
   <TabItem value="react" label="React">
-    ```typescript title="src/api/agents.ts" showLineNumbers copy
+    ```typescript title="src/api/agents.ts" copy
     import { WorkOS } from '@workos-inc/node';
     import { MastraClient } from '@mastra/client-js';
 

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

@@ -1,5 +1,5 @@
 ---
-title: "Custom Adapters | Server & DB"
+title: "Custom Adapters | Server"
 description: "Create a custom server adapter for frameworks other than Hono or Express."
 ---
 
@@ -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;
@@ -296,13 +296,13 @@ constructor(options: {
 }
 ```
 
-See [Server Adapters](/docs/v1/server-db/server-adapters#constructor-options) for full documentation on each option.
+See [Server Adapters](/docs/v1/server/server-adapters#constructor-options) for full documentation on each option.
 
 ## Full example
 
 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';
 
@@ -379,7 +379,7 @@ The existing [@mastra/hono](https://github.com/mastra-ai/mastra/blob/main/server
 
 ## Related
 
-- [Server Adapters](/docs/v1/server-db/server-adapters) - Overview and shared concepts
+- [Server Adapters](/docs/v1/server/server-adapters) - Overview and shared concepts
 - [Hono Adapter](/reference/v1/server/hono-adapter) - Reference implementation
 - [Express Adapter](/reference/v1/server/express-adapter) - Reference implementation
 - [MastraServer Reference](/reference/v1/server/mastra-server) - Full API reference

package/.docs/raw/{server-db → server}/custom-api-routes.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Custom API Routes | Server & DB"
+title: "Custom API Routes | Server"
 description: "Expose additional HTTP endpoints from your Mastra server."
 ---
 
@@ -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-db → server}/mastra-client.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Mastra Client SDK | Server & DB"
+title: "Mastra Client SDK | Server"
 description: "Learn how to set up and use the Mastra Client SDK"
 ---
 
@@ -8,7 +8,7 @@ import TabItem from "@theme/TabItem";
 
 # Mastra Client SDK
 
-The Mastra Client SDK provides a simple and type-safe interface for interacting with your [Mastra Server](/docs/v1/server-db/mastra-server) from your client environment.
+The Mastra Client SDK provides a simple and type-safe interface for interacting with your [Mastra Server](/docs/v1/server/mastra-server) from your client environment.
 
 ## Prerequisites
 
@@ -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-db → server}/mastra-server.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Server Configuration | Server & DB"
+title: "Server Configuration | Server"
 description: "Configure the Mastra server with custom settings for port, timeout, CORS, and more."
 ---
 
@@ -9,7 +9,7 @@ When deploying your Mastra application to production, it runs as an HTTP server
 
 :::info
 
-This page covers the `server` configuration options passed to the `Mastra` constructor. For running Mastra with your own HTTP server (Hono, Express, etc.), see [Server Adapters](/docs/v1/server-db/server-adapters).
+This page covers the `server` configuration options passed to the `Mastra` constructor. For running Mastra with your own HTTP server (Hono, Express, etc.), see [Server Adapters](/docs/v1/server/server-adapters).
 
 :::
 
@@ -27,15 +27,15 @@ The server provides:
 - Configuration of port
 - Configuration of body limit
 
-See the [Middleware](/docs/v1/server-db/middleware) and
-[Custom API Routes](/docs/v1/server-db/custom-api-routes) pages for details on
+See the [Middleware](/docs/v1/server/middleware) and
+[Custom API Routes](/docs/v1/server/custom-api-routes) pages for details on
 adding additional server behaviour.
 
 ## Server configuration
 
 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({
@@ -96,4 +96,4 @@ export const mastra = new Mastra({
 
 When streaming agent responses, the HTTP streaming layer redacts system prompts, tool definitions, API keys, and similar data from each chunk before sending it to clients. This is enabled by default.
 
-If you're using server adapters directly, you can configure redaction behavior. See [Stream data redaction](/docs/v1/server-db/server-adapters#stream-data-redaction) in the Server Adapters docs.
+If you're using server adapters directly, you can configure redaction behavior. See [Stream data redaction](/docs/v1/server/server-adapters#stream-data-redaction) in the Server Adapters docs.

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

@@ -1,5 +1,5 @@
 ---
-title: "Middleware | Server & DB"
+title: "Middleware | Server"
 description: "Apply custom middleware functions to intercept requests."
 ---
 
@@ -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';
@@ -174,4 +174,4 @@ be inspected by middleware to tailor behavior:
 
 # Related
 
-- [Request Context](/docs/v1/server-db/request-context)
+- [Request Context](/docs/v1/server/request-context)

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

@@ -1,5 +1,5 @@
 ---
-title: "Request Context | Server & DB"
+title: "Request Context | Server"
 description: Learn how to use Mastra's RequestContext to provide dynamic, request-specific configuration to agents.
 ---
 
@@ -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-db/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,19 +175,20 @@ 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
 
 - [Agent Request Context](/docs/v1/agents/overview#using-requestcontext)
 - [Workflow Request Context](../workflows/overview#using-requestcontext)
 - [Tool Request Context](../mcp/overview#using-requestcontext)
-- [Server Middleware](/docs/v1/server-db/middleware)
+- [Server Middleware](/docs/v1/server/middleware)