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

package/.docs/raw/reference/streaming/workflows/stream.mdx

@@ -5,18 +5,22 @@ description: Documentation for the `Run.stream()` method in workflows, which ena
 
 # Run.stream()
 
-The `.stream()` method enables real-time streaming of responses from a workflow.
+The `.stream()` method enables real-time streaming of responses from a workflow. It returns a `ReadableStream` of events directly.
 
 ## Usage example
 
 ```typescript showLineNumbers copy
 const run = await workflow.createRun();
 
-const stream = run.stream({
+const stream = await run.stream({
   inputData: {
     value: "initial data",
   },
 });
+
+for await (const chunk of stream) {
+  console.log(chunk);
+}
 ```
 
 ## Parameters
@@ -129,35 +133,30 @@ const stream = run.stream({
 
 ## Returns
 
+Returns a `WorkflowRunOutput` object that implements the async iterable interface (can be used directly in `for await...of` loops) and provides access to the stream and workflow execution results.
+
 <PropertiesTable
   content={[
     {
-      name: "stream",
-      type: "MastraWorkflowStream<ChunkType>",
+      name: "fullStream",
+      type: "ReadableStream<WorkflowStreamEvent>",
       description:
-        "A custom stream that extends ReadableStream<ChunkType> with additional workflow-specific properties",
+        "A ReadableStream of workflow events that you can iterate over to track progress in real-time. You can also iterate over the WorkflowRunOutput object directly.",
     },
     {
-      name: "stream.status",
-      type: "Promise<RunStatus>",
-      description: "A promise that resolves to the current workflow run status",
-    },
-    {
-      name: "stream.result",
-      type: "Promise<WorkflowResult<TState, TOutput, TSteps>>",
+      name: "result",
+      type: "Promise<WorkflowResult<TState, TInput, TOutput, TSteps>>",
       description: "A promise that resolves to the final workflow result",
     },
     {
-      name: "stream.usage",
-      type: "Promise<{ inputTokens: number; outputTokens: number; totalTokens: number, reasoningTokens?: number, cacheInputTokens?: number }>",
-      description: "A promise that resolves to token usage statistics",
+      name: "status",
+      type: "WorkflowRunStatus",
+      description: "The current workflow run status ('running', 'suspended', 'success', 'failed', 'canceled', or 'tripwire')",
     },
     {
-      name: "stream.traceId",
-      type: "string",
-      isOptional: true,
-      description:
-        "The trace ID associated with this execution when Tracing is enabled.",
+      name: "usage",
+      type: "Promise<{ inputTokens: number; outputTokens: number; totalTokens: number, reasoningTokens?: number, cachedInputTokens?: number }>",
+      description: "A promise that resolves to token usage statistics",
     },
   ]}
 />
@@ -173,7 +172,21 @@ const stream = run.stream({
   },
 });
 
+// Iterate over stream events (you can iterate over stream directly or use stream.fullStream)
+for await (const chunk of stream) {
+  console.log(chunk);
+}
+
+// Access the final result
 const result = await stream.result;
+console.log("Final result:", result);
+
+// Access token usage
+const usage = await stream.usage;
+console.log("Token usage:", usage);
+
+// Check current status
+console.log("Status:", stream.status);
 ```
 
 ## Stream Events

package/.docs/raw/reference/tools/create-tool.mdx

@@ -63,6 +63,27 @@ export const tool = createTool({
         "A Zod schema defining the expected output structure of the tool's `execute` function.",
       isOptional: true,
     },
+    {
+      name: "suspendSchema",
+      type: "Zod schema",
+      description:
+        "A Zod schema defining the structure of the payload passed to `suspend()`. This payload is returned to the client when the tool suspends execution.",
+      isOptional: true,
+    },
+    {
+      name: "resumeSchema",
+      type: "Zod schema",
+      description:
+        "A Zod schema defining the expected structure of `resumeData` when the tool is resumed. Used by the agent to extract data from user messages when `autoResumeSuspendedTools` is enabled.",
+      isOptional: true,
+    },
+    {
+      name: "requireApproval",
+      type: "boolean",
+      description:
+        "When true, the tool requires explicit approval before execution. The agent will emit a `tool-call-approval` chunk and pause until approved or declined.",
+      isOptional: true,
+    },
     {
       name: "execute",
       type: "function",
@@ -284,5 +305,6 @@ Hook errors are caught and logged automatically, but do not prevent tool executi
 
 - [MCP Overview](/docs/v1/mcp/overview)
 - [Using Tools with Agents](/docs/v1/agents/using-tools)
+- [Agent Approval](/docs/v1/agents/agent-approval)
 - [Tool Streaming](/docs/v1/streaming/tool-streaming)
-- [Request Context](/docs/v1/server-db/request-context#accessing-values-with-tools)
+- [Request Context](/docs/v1/server/request-context#accessing-values-with-tools)

package/.docs/raw/reference/tools/graph-rag-tool.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Reference: createGraphRAGTool() | Tools & MCP"
-description: Documentation for the Graph RAG Tool in Mastra, which enhances RAG by building a graph of semantic relationships between documents.
+description: Documentation for the GraphRAG Tool in Mastra, which enhances RAG by building a graph of semantic relationships between documents.
 ---
 
 # createGraphRAGTool()
@@ -253,8 +253,8 @@ const response = await agent.generate(
 
 For more information on request context, please see:
 
-- [Agent Request Context](/docs/v1/server-db/request-context)
-- [Request Context](/docs/v1/server-db/request-context#accessing-values-with-tools)
+- [Agent Request Context](/docs/v1/server/request-context)
+- [Request Context](/docs/v1/server/request-context#accessing-values-with-tools)
 
 ## Related
 

package/.docs/raw/reference/tools/vector-query-tool.mdx

@@ -326,7 +326,7 @@ This agent-driven approach:
 
 For detailed filter syntax and store-specific capabilities, see the [Metadata Filters](../rag/metadata-filters) documentation.
 
-For an example of how agent-driven filtering works, see the [Agent-Driven Metadata Filtering](/examples/v1/rag/usage/filter-rag) example.
+For an example of how agent-driven filtering works, see the [Agent-Driven Metadata Filtering](https://github.com/mastra-ai/mastra/tree/main/examples/basics/rag/filter-rag) example.
 
 ## Example with Reranking
 
@@ -567,8 +567,8 @@ const response = await agent.generate(
 
 For more information on request context, please see:
 
-- [Agent Request Context](/docs/v1/server-db/request-context)
-- [Request Context](/docs/v1/server-db/request-context#accessing-values-with-tools)
+- [Agent Request Context](/docs/v1/server/request-context)
+- [Request Context](/docs/v1/server/request-context#accessing-values-with-tools)
 
 ## Usage Without a Mastra Server
 

package/.docs/raw/reference/workflows/run-methods/startAsync.mdx

@@ -0,0 +1,143 @@
+---
+title: "Reference: Run.startAsync() | Workflows"
+description: Documentation for the `Run.startAsync()` method in workflows, which starts a workflow run without waiting for completion (fire-and-forget).
+---
+
+# Run.startAsync()
+
+The `.startAsync()` method starts a workflow run without waiting for completion. It returns immediately with the `runId`, allowing the workflow to execute in the background. This is useful for long-running workflows, scheduled tasks, or when you want to avoid blocking on workflow completion.
+
+## Usage example
+
+```typescript showLineNumbers copy
+const run = await workflow.createRun();
+
+// Fire-and-forget - returns immediately
+const { runId } = await run.startAsync({
+  inputData: {
+    value: "initial data",
+  },
+});
+
+// Optionally poll for completion later
+const result = await workflow.getWorkflowRunExecutionResult(runId);
+```
+
+## Parameters
+
+<PropertiesTable
+  content={[
+    {
+      name: "inputData",
+      type: "z.infer<TInput>",
+      description: "Input data that matches the workflow's input schema",
+      isOptional: true,
+    },
+    {
+      name: "requestContext",
+      type: "RequestContext",
+      description: "Request Context data to use during workflow execution",
+      isOptional: true,
+    },
+    {
+      name: "initialState",
+      type: "z.infer<TState>",
+      description: "Initial state to use for the workflow execution",
+      isOptional: true,
+    },
+    {
+      name: "tracingOptions",
+      type: "TracingOptions",
+      isOptional: true,
+      description: "Options for Tracing configuration.",
+      properties: [
+        {
+          parameters: [
+            {
+              name: "metadata",
+              type: "Record<string, any>",
+              isOptional: true,
+              description:
+                "Metadata to add to the root trace span. Useful for adding custom attributes like user IDs, session IDs, or feature flags.",
+            },
+          ],
+        },
+        {
+          parameters: [
+            {
+              name: "traceId",
+              type: "string",
+              isOptional: true,
+              description:
+                "Trace ID to use for this execution (1-32 hexadecimal characters). If provided, this trace will be part of the specified trace.",
+            },
+          ],
+        },
+      ],
+    },
+    {
+      name: "outputOptions",
+      type: "OutputOptions",
+      isOptional: true,
+      description: "Options for output configuration.",
+      properties: [
+        {
+          parameters: [
+            {
+              name: "includeState",
+              type: "boolean",
+              isOptional: true,
+              description:
+                "Whether to include the workflow run state in the result.",
+            },
+          ],
+        },
+      ],
+    },
+  ]}
+/>
+
+## Returns
+
+<PropertiesTable
+  content={[
+    {
+      name: "runId",
+      type: "string",
+      description:
+        "The unique identifier for this workflow run. Use this to check status or retrieve results later.",
+    },
+  ]}
+/>
+
+## When to use startAsync()
+
+Use `startAsync()` instead of `start()` when:
+
+- **Long-running workflows**: The workflow may take minutes or hours to complete
+- **Scheduled/cron triggers**: You want to trigger a workflow without blocking the scheduler
+- **Avoiding polling failures**: With Inngest workflows, `start()` polls for completion which can fail and cause retries. `startAsync()` avoids this issue
+- **Background processing**: You want to queue work and handle results asynchronously
+
+## Checking workflow status
+
+After calling `startAsync()`, you can check the workflow status using:
+
+```typescript showLineNumbers copy
+// Get the execution result (including step outputs)
+const result = await workflow.getWorkflowRunExecutionResult(runId);
+
+if (result?.status === 'success') {
+  console.log('Workflow completed:', result.steps);
+} else if (result?.status === 'failed') {
+  console.log('Workflow failed:', result.error);
+} else if (result?.status === 'running') {
+  console.log('Workflow still running...');
+}
+```
+
+## Related
+
+- [Run.start()](./start) - Start a workflow and wait for completion
+- [Workflows overview](/docs/v1/workflows/overview)
+- [Workflow.createRun()](../workflow-methods/create-run)

package/.docs/raw/reference/workflows/workflow-methods/create-run.mdx

@@ -23,6 +23,18 @@ await workflow.createRun();
       description: "Optional custom identifier for the workflow run",
       isOptional: true,
     },
+    {
+      name: "resourceId",
+      type: "string",
+      description: "Optional identifier to associate the workflow run with a specific resource (e.g., user ID, tenant ID). This value is persisted with the workflow run and can be used for filtering and querying runs.",
+      isOptional: true,
+    },
+    {
+      name: "disableScorers",
+      type: "boolean",
+      description: "Optional flag to disable scorers for this workflow run",
+      isOptional: true,
+    },
   ]}
 />
 
@@ -53,6 +65,29 @@ const result = await run.start({
 });
 ```
 
+## Using resourceId
+
+The `resourceId` parameter associates a workflow run with a specific resource, such as a user or tenant. This is useful for multi-tenant applications or when you need to track which user initiated a workflow.
+
+```typescript showLineNumbers copy
+const workflow = mastra.getWorkflow("workflow");
+
+// Create a run associated with a specific user
+const run = await workflow.createRun({
+  resourceId: "user-123",
+});
+
+const result = await run.start({
+  inputData: {
+    value: 10,
+  },
+});
+
+// Later, retrieve the run and access the resourceId
+const storedRun = await workflow.getWorkflowRunById(run.runId);
+console.log(storedRun.resourceId); // "user-123"
+```
+
 ## Related
 
 - [Run Class](../run)

package/.docs/raw/reference/workflows/workflow.mdx

@@ -85,6 +85,20 @@ export const workflow = createWorkflow({
       isOptional: true,
       defaultValue: "() => true",
     },
+    {
+      name: "onFinish",
+      type: "(result: WorkflowFinishCallbackResult) => void | Promise<void>",
+      description:
+        "Callback invoked when workflow completes with any status (success, failed, suspended, tripwire). Receives the workflow result including status, output, error, and step results. Errors thrown in this callback are caught and logged, not propagated.",
+      isOptional: true,
+    },
+    {
+      name: "onError",
+      type: "(errorInfo: WorkflowErrorCallbackInfo) => void | Promise<void>",
+      description:
+        "Callback invoked only when workflow fails (failed or tripwire status). Receives error details and step results. Errors thrown in this callback are caught and logged, not propagated.",
+      isOptional: true,
+    },
   ]}
 />
 

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

@@ -170,7 +170,7 @@ 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.
+> See [Mastra Client SDK](/docs/v1/server/mastra-client) for more configuration options.
 
 ### Making authenticated requests
 

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

@@ -93,7 +93,7 @@ export const mastraClient = new MastraClient({
 ```
 
 > **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.
+> See [Mastra Client SDK](/docs/v1/server/mastra-client) for more configuration options.
 
 ### Making authenticated requests
 

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

@@ -190,7 +190,7 @@ export const createMastraClient = (idToken: string) => {
 
 > **Note:** The ID token must be prefixed with `Bearer` in the Authorization header.
 
-> See [Mastra Client SDK](/docs/v1/server-db/mastra-client) for more configuration options.
+> See [Mastra Client SDK](/docs/v1/server/mastra-client) for more configuration options.
 
 ### Making authenticated requests
 

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

@@ -11,9 +11,9 @@ You can start with simple shared secret JWT authentication and switch to provide
 
 ## Available providers
 
-- [JSON Web Token (JWT)](/docs/v1/auth/jwt)
-- [Clerk](/docs/v1/auth/clerk)
-- [Supabase](/docs/v1/auth/supabase)
-- [Firebase](/docs/v1/auth/firebase)
-- [WorkOS](/docs/v1/auth/workos)
-- [Auth0](/docs/v1/auth/auth0)
+- [JSON Web Token (JWT)](/docs/v1/server/auth/jwt)
+- [Clerk](/docs/v1/server/auth/clerk)
+- [Supabase](/docs/v1/server/auth/supabase)
+- [Firebase](/docs/v1/server/auth/firebase)
+- [WorkOS](/docs/v1/server/auth/workos)
+- [Auth0](/docs/v1/server/auth/auth0)

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

@@ -51,7 +51,7 @@ export const mastraClient = new MastraClient({
 });
 ```
 
-> See [Mastra Client SDK](/docs/v1/server-db/mastra-client) for more configuration options.
+> See [Mastra Client SDK](/docs/v1/server/mastra-client) for more configuration options.
 
 ### Making authenticated requests
 

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

@@ -90,7 +90,7 @@ export const mastraClient = new MastraClient({
 
 > **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.
+> See [Mastra Client SDK](/docs/v1/server/mastra-client) for more configuration options.
 
 ### Making authenticated requests
 

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

@@ -152,7 +152,7 @@ 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.
+> See [Mastra Client SDK](/docs/v1/server/mastra-client) for more configuration options.
 
 ### Making authenticated requests
 

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."
 ---
 
@@ -296,7 +296,7 @@ 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
 
@@ -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."
 ---
 

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
 

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,8 +27,8 @@ 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
@@ -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."
 ---
 
@@ -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.
 ---
 
@@ -99,7 +99,7 @@ export const mastra = new Mastra({
 });
 ```
 
-> See [Middleware](/docs/v1/server-db/middleware) for how to use server middleware.
+> See [Middleware](/docs/v1/server/middleware) for how to use server middleware.
 
 ## Accessing values with agents
 
@@ -190,4 +190,4 @@ export const weatherTool = createTool({
 - [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)

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
 
@@ -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/tools-mcp/overview.mdx

@@ -56,7 +56,7 @@ 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
 export type UserTier = {
@@ -81,7 +81,7 @@ export const testTool = createTool({
 });
 ```
 
-> See [Request Context](/docs/v1/server-db/request-context) for more information.
+> See [Request Context](/docs/v1/server/request-context) for more information.
 
 ## Testing with Studio