@mastra/mcp-docs-server 0.13.19-alpha.0 → 0.13.19-alpha.2

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

@@ -93,5 +93,5 @@ The `createTool()` function returns a `Tool` object.
 
 - [Tools Overview](/docs/tools-mcp/overview.mdx)
 - [Using Tools with Agents](/docs/agents/using-tools-and-mcp.mdx)
-- [Dynamic Tool Context](/docs/tools-mcp/dynamic-context.mdx)
+- [Tool Runtime Context](/docs/tools-mcp/runtime-context.mdx)
 - [Advanced Tool Usage](/docs/tools-mcp/advanced-usage.mdx)

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

@@ -253,8 +253,8 @@ const response = await agent.generate(
 
 For more information on runtime context, please see:
 
-- [Runtime Variables](../../docs/agents/runtime-variables.mdx)
-- [Dynamic Context](../../docs/tools-mcp/dynamic-context.mdx)
+- [Agent Runtime Context](../../docs/agents/runtime-context.mdx)
+- [Tool Runtime Context](../../docs/tools-mcp/runtime-context.mdx)
 
 ## Related
 

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

@@ -558,8 +558,8 @@ const response = await agent.generate(
 
 For more information on runtime context, please see:
 
-- [Runtime Variables](../../docs/agents/runtime-variables.mdx)
-- [Dynamic Context](../../docs/tools-mcp/dynamic-context.mdx)
+- [Agent Runtime Context](../../docs/agents/runtime-context.mdx)
+- [Tool Runtime Context](../../docs/tools-mcp/runtime-context.mdx)
 
 ## Usage Without a Mastra Server
 

package/.docs/raw/tools-mcp/runtime-context.mdx

@@ -0,0 +1,63 @@
+---
+title: "Runtime context | Tools & MCP | Mastra Docs"
+description: Learn how to use Mastra's RuntimeContext to provide dynamic, request-specific configuration to tools.
+---
+
+import { Callout } from "nextra/components";
+
+# Tool Runtime Context
+
+Mastra provides `RuntimeContext`, a dependency injection system that lets you configure tools with runtime variables. If you find yourself creating multiple tools that perform similar tasks, runtime context allows you to consolidate them into a single, more flexible tool.
+
+## Overview
+
+The dependency injection system allows you to:
+
+1. Pass runtime configuration variables to tools through a type-safe `runtimeContext`.
+2. Access these variables within tool execution context.
+3. Modify tool behavior without changing the underlying code.
+4. Share configuration across multiple tools within the same agent.
+
+<Callout>
+  **Note:** `RuntimeContext` is primarily used for passing data *into* tool
+  executions. It's distinct from agent memory, which handles conversation
+  history and state persistence across multiple calls.
+</Callout>
+
+
+## Accessing `runtimeContext` in tools
+
+Tools can access the same `runtimeContext` used by their parent agent, allowing them to adjust behavior based on runtime configuration. In this example, the `temperature-unit` is retrieved within the tool’s `execute` function to ensure consistent formatting with the agent’s instructions.
+
+```typescript {14-15} filename="src/mastra/tools/test-weather-tool" showLineNumbers copy
+import { createTool } from "@mastra/core/tools";
+import { z } from "zod";
+
+type WeatherRuntimeContext = {
+  "temperature-unit": "celsius" | "fahrenheit";
+};
+
+export const testWeatherTool = createTool({
+  id: "getWeather",
+  description: "Get the current weather for a location",
+  inputSchema: z.object({
+    location: z.string().describe("The location to get weather for")
+  }),
+  execute: async ({ context, runtimeContext }) => {
+    const temperatureUnit = runtimeContext.get("temperature-unit") as WeatherRuntimeContext["temperature-unit"];
+
+    const weather = await fetchWeather(context.location, temperatureUnit);
+
+    return { result: weather };
+  }
+});
+
+async function fetchWeather(location: string, temperatureUnit: WeatherRuntimeContext["temperature-unit"]) {
+  // ...
+}
+```
+
+
+## Related
+
+[Agent Runtime Context](../agents/runtime-context.mdx)

package/.docs/raw/workflows/control-flow.mdx

@@ -53,7 +53,7 @@ export const testWorkflow = createWorkflow({...})
 
 This executes `step1` and `step2` concurrently, then continues to `step3` after both complete.
 
-> See [Parallel Execution with Steps](/examples/workflows/parallel-steps) for more information.
+> See [Parallel Execution with Steps](../../examples/workflows/parallel-steps.mdx) for more information.
 
 > 📹 Watch: How to run steps in parallel and optimize your Mastra workflow → [YouTube (3 minutes)](https://youtu.be/pTSOSWbreE0)
 
@@ -80,7 +80,7 @@ export const testWorkflow = createWorkflow({...})
 
 Branch conditions are evaluated sequentially, but steps with matching conditions are executed in parallel.
 
-> See [Workflow with Conditional Branching](/examples/workflows/conditional-branching) for more information.
+> See [Workflow with Conditional Branching](../../examples/workflows/conditional-branching.mdx) for more information.
 
 ## Looping steps
 

package/.docs/raw/workflows/overview.mdx

@@ -46,7 +46,7 @@ Steps are the building blocks of workflows. Create a step using `createStep`:
 const step1 = createStep({...});
 ```
 
-> See [createStep](/reference/workflows/step) for more information.
+> See [createStep](../../reference/workflows/step.mdx) for more information.
 
 ### Create workflow
 
@@ -72,7 +72,7 @@ export const testWorkflow = createWorkflow({
   .commit();
 ```
 
-> See [workflow](/reference/workflows/workflow) for more information.
+> See [workflow](../../reference/workflows/workflow.mdx) for more information.
 
 #### Composing steps
 
@@ -100,7 +100,7 @@ export const testWorkflow = createWorkflow({
   .commit();
 ```
 
-> Steps can be composed using a number of different methods. See [Control Flow](/docs/workflows/control-flow)  for more information.
+> Steps can be composed using a number of different methods. See [Control Flow](./control-flow.mdx)  for more information.
 
 #### Cloning steps
 
@@ -163,7 +163,7 @@ There are two ways to run and test workflows.
 
 With the Mastra Dev Server running you can run the workflow from the Mastra Playground by visiting [http://localhost:4111/workflows](http://localhost:4111/workflows) in your browser.
 
-> For more information, see the [Local Dev Playground](/docs/server-db/local-dev-playground) documentation.
+> For more information, see the [Local Dev Playground](../server-db/local-dev-playground.mdx) documentation.
 
 ### Command line
 
@@ -188,7 +188,7 @@ if (result.status === 'success') {
   console.log(result.result.output);
 }
 ```
-> see [createRunAsync](../../reference/workflows/create-run.mdx) and [start](../../reference/workflows/run-methods/start.mdx) for more information.
+> see [createRunAsync](../../reference/workflows/run.mdx) and [start](../../reference/workflows/run-methods/start.mdx) for more information.
 
 To trigger this workflow, run the following:
 
@@ -286,7 +286,7 @@ for await (const chunk of result.stream) {
 }
 ```
 
-> See [stream](/reference/workflows/run-methods/stream) and [messages](/reference/workflows/run-methods/stream#messages) for more information.
+> See [stream](../../reference/workflows/run-methods/stream.mdx) for more information.
 
 ## Watch Workflow
 
@@ -308,7 +308,7 @@ const result = await run.start({
 });
 ```
 
-> See [watch](/reference/workflows/run-methods/watch) for more information.
+> See [watch](../../reference/workflows/run-methods/watch.mdx) for more information.
 
 ## Related
 
@@ -321,5 +321,5 @@ const result = await run.start({
 
 ## Workflows (Legacy)
 
-For legacy workflow documentation, see [Workflows (Legacy)](/docs/workflows-legacy/overview).
+For legacy workflow documentation, see [Workflows (Legacy)](../workflows-legacy/overview.mdx).
 

package/.docs/raw/workflows/suspend-and-resume.mdx

@@ -60,7 +60,7 @@ export const testWorkflow = createWorkflow({
   .commit();
 ```
 
-> For more details, check out the [Suspend workflow example](/examples/workflows/human-in-the-loop#suspend-workflow).
+> For more details, check out the [Suspend workflow example](../../examples/workflows/human-in-the-loop.mdx#suspend-workflow).
 
 ### Identifying suspended steps
 
@@ -89,8 +89,6 @@ if (result.status === "suspended") {
 }
 ```
 
-> See [Run Workflow Results](/docs/workflows/overview#run-workflow-results) for more details.
-
 In this case, the logic resumes the first step listed in the `suspended` array. A `step` can also be defined using it's `id`, for example: 'step-1'.
 
 ```json
@@ -111,6 +109,8 @@ In this case, the logic resumes the first step listed in the `suspended` array.
 }
 ```
 
+> See [Run Workflow Results](./overview.mdx#run-workflow-results) for more details.
+
 ## Providing user feedback with suspend
 
 When a workflow is suspended, feedback can be surfaced to the user through the `suspendSchema`. Include a reason in the `suspend` payload to explain why the workflow paused.
@@ -168,7 +168,7 @@ In this case, the reason provided explains that the user must confirm to continu
 }
 ```
 
-> See [Run Workflow Results](/docs/workflows/overview#run-workflow-results) for more details.
+> See [Run Workflow Results](./overview.mdx#run-workflow-results) for more details.
 
 ## Resuming a workflow with `resume()`
 

package/CHANGELOG.md

@@ -1,5 +1,22 @@
 # @mastra/mcp-docs-server
 
+## 0.13.19-alpha.2
+
+### Patch Changes
+
+- Updated dependencies [[`827d876`](https://github.com/mastra-ai/mastra/commit/827d8766f36a900afcaf64a040f7ba76249009b3), [`7eaf1d1`](https://github.com/mastra-ai/mastra/commit/7eaf1d1cec7e828d7a98efc2a748ac395bbdba3b), [`f3427cd`](https://github.com/mastra-ai/mastra/commit/f3427cdaf9eecd63360dfc897a4acbf5f4143a4e), [`05f13b8`](https://github.com/mastra-ai/mastra/commit/05f13b8fb269ccfc4de98e9db58dbe16eae55a5e)]:
+  - @mastra/core@0.16.1-alpha.2
+
+## 0.13.19-alpha.1
+
+### Patch Changes
+
+- dependencies updates: ([#7527](https://github.com/mastra-ai/mastra/pull/7527))
+  - Updated dependency [`@modelcontextprotocol/sdk@^1.17.5` ↗︎](https://www.npmjs.com/package/@modelcontextprotocol/sdk/v/1.17.5) (from `^1.17.3`, in `dependencies`)
+- Updated dependencies [[`0f7b8c0`](https://github.com/mastra-ai/mastra/commit/0f7b8c0c22d2a677a0f71c35ad1bc2d60b063d39), [`47b6dc9`](https://github.com/mastra-ai/mastra/commit/47b6dc94f4976d4f3d3882e8f19eb365bbc5976c), [`565d65f`](https://github.com/mastra-ai/mastra/commit/565d65fc16314a99f081975ec92f2636dff0c86d), [`4da3d68`](https://github.com/mastra-ai/mastra/commit/4da3d68a778e5c4d5a17351ef223289fe2f45a45), [`0b0bbb2`](https://github.com/mastra-ai/mastra/commit/0b0bbb24f4198ead69792e92b68a350f52b45cf3), [`d951f41`](https://github.com/mastra-ai/mastra/commit/d951f41771e4e5da8da4b9f870949f9509e38756), [`8049e2e`](https://github.com/mastra-ai/mastra/commit/8049e2e8cce80a00353c64894c62b695ac34e35e)]:
+  - @mastra/mcp@0.12.0-alpha.1
+  - @mastra/core@0.16.1-alpha.1
+
 ## 0.13.19-alpha.0
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mastra/mcp-docs-server",
-  "version": "0.13.19-alpha.0",
+  "version": "0.13.19-alpha.2",
   "description": "MCP server for accessing Mastra.ai documentation, changelogs, and news.",
   "type": "module",
   "main": "dist/index.js",
@@ -25,7 +25,7 @@
   "author": "",
   "license": "Apache-2.0",
   "dependencies": {
-    "@modelcontextprotocol/sdk": "^1.17.3",
+    "@modelcontextprotocol/sdk": "^1.17.5",
     "date-fns": "^4.1.0",
     "exit-hook": "^4.0.0",
     "jsdom": "^26.1.0",
@@ -33,8 +33,8 @@
     "uuid": "^11.1.0",
     "zod": "^3.25.76",
     "zod-to-json-schema": "^3.24.6",
-    "@mastra/core": "0.16.1-alpha.0",
-    "@mastra/mcp": "^0.12.0-alpha.0"
+    "@mastra/mcp": "^0.12.0-alpha.1",
+    "@mastra/core": "0.16.1-alpha.2"
   },
   "devDependencies": {
     "@hono/node-server": "^1.17.1",
@@ -50,7 +50,7 @@
     "typescript": "^5.8.3",
     "vitest": "^3.2.4",
     "@internal/lint": "0.0.36",
-    "@mastra/core": "0.16.1-alpha.0"
+    "@mastra/core": "0.16.1-alpha.2"
   },
   "homepage": "https://mastra.ai",
   "repository": {

package/.docs/raw/agents/runtime-variables.mdx

@@ -1,116 +0,0 @@
----
-title: "Runtime context | Agents | Mastra Docs"
-description: Learn how to use Mastra's dependency injection system to provide runtime configuration to agents and tools.
----
-
-# Agent Runtime Context
-
-Mastra provides runtime context, which is a system based on dependency injection that enables you to configure your agents and tools with runtime variables. If you find yourself creating several different agents that do very similar things, runtime context allows you to combine them into one agent.
-
-## Overview
-
-The dependency injection system allows you to:
-
-1. Pass runtime configuration variables to agents through a type-safe runtimeContext
-2. Access these variables within tool execution contexts
-3. Modify agent behavior without changing the underlying code
-4. Share configuration across multiple tools within the same agent
-
-## Basic Usage
-
-```typescript
-const agent = mastra.getAgent("weatherAgent");
-
-// Define your runtimeContext's type structure
-type WeatherRuntimeContext = {
-  "temperature-scale": "celsius" | "fahrenheit";
-};
-
-const runtimeContext = new RuntimeContext<WeatherRuntimeContext>();
-runtimeContext.set("temperature-scale", "celsius");
-
-const response = await agent.generate("What's the weather like today?", {
-  runtimeContext,
-});
-
-console.log(response.text);
-```
-
-## Using with REST API
-
-Here's how to dynamically set temperature units based on a user's location using the Cloudflare `CF-IPCountry` header:
-
-```typescript filename="src/index.ts"
-import { Mastra } from "@mastra/core";
-import { RuntimeContext } from "@mastra/core/di";
-import { agent as weatherAgent } from "./agents/weather";
-
-// Define RuntimeContext type with clear, descriptive types
-type WeatherRuntimeContext = {
-  "temperature-scale": "celsius" | "fahrenheit";
-};
-
-export const mastra = new Mastra({
-  agents: {
-    weather: weatherAgent,
-  },
-  server: {
-    middleware: [
-      async (c, next) => {
-        const country = c.req.header("CF-IPCountry");
-        const runtimeContext = c.get<WeatherRuntimeContext>("runtimeContext");
-
-        // Set temperature scale based on country
-        runtimeContext.set(
-          "temperature-scale",
-          country === "US" ? "fahrenheit" : "celsius",
-        );
-
-        await next(); // Don't forget to call next()
-      },
-    ],
-  },
-});
-```
-
-## Creating Tools with Variables
-
-Tools can access runtimeContext variables and must conform to the agent's runtimeContext type:
-
-```typescript
-import { createTool } from "@mastra/core/tools";
-import { z } from "zod";
-
-export const weatherTool = createTool({
-  id: "getWeather",
-  description: "Get the current weather for a location",
-  inputSchema: z.object({
-    location: z.string().describe("The location to get weather for"),
-  }),
-  execute: async ({ context, runtimeContext }) => {
-    // Type-safe access to runtimeContext variables
-    const temperatureUnit = runtimeContext.get("temperature-scale");
-
-    const weather = await fetchWeather(context.location, {
-      temperatureUnit,
-    });
-
-    return { result: weather };
-  },
-});
-
-async function fetchWeather(
-  location: string,
-  { temperatureUnit }: { temperatureUnit: "celsius" | "fahrenheit" },
-): Promise<WeatherResponse> {
-  // Implementation of weather API call
-  const response = await weatherApi.fetch(location, temperatureUnit);
-
-  return {
-    location,
-    temperature: "72°F",
-    conditions: "Sunny",
-    unit: temperatureUnit,
-  };
-}
-```

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

@@ -1,131 +0,0 @@
----
-title: "Reference: Workflow.execute() | Workflows | Mastra Docs"
-description: Documentation for the `Workflow.execute()` method in workflows, which executes a workflow directly and returns the output.
----
-
-# Workflow.execute()
-
-The `.execute()` method executes a workflow directly and returns the output, allowing you to run a workflow without creating a separate run instance.
-
-## Usage example
-
-```typescript showLineNumbers copy
-await workflow.execute({
-  inputData: {
-    value: "hello world"
-  }
-});
-```
-
-## Parameters
-
-<PropertiesTable
-  content={[
-    {
-      name: "inputData",
-      type: "z.infer<TInput>",
-      description: "Input data that matches the workflow's input schema",
-      isOptional: false,
-    },
-    {
-      name: "resumeData",
-      type: "any",
-      description: "Data for resuming a suspended workflow",
-      isOptional: true,
-    },
-    {
-      name: "suspend",
-      type: "(suspendPayload: any) => Promise<any>",
-      description: "Function to suspend workflow execution",
-      isOptional: false,
-    },
-    {
-      name: "resume",
-      type: "object",
-      description: "Configuration for resuming workflow execution",
-      isOptional: true,
-      properties: [
-        {
-          name: "steps",
-          type: "string[]",
-          description: "Steps to resume",
-          isOptional: false,
-        },
-        {
-          name: "resumePayload",
-          type: "any",
-          description: "Payload data for resuming",
-          isOptional: false,
-        },
-        {
-          name: "runId",
-          type: "string",
-          description: "ID of the run to resume",
-          isOptional: true,
-        },
-      ],
-    },
-    {
-      name: "emitter",
-      type: "object",
-      description: "Event emitter object for workflow events",
-      isOptional: false,
-      properties: [
-        {
-          name: "emit",
-          type: "(event: string, data: any) => void",
-          description: "Function to emit events",
-          isOptional: false,
-        },
-      ],
-    },
-    {
-      name: "mastra",
-      type: "Mastra",
-      description: "Mastra instance",
-      isOptional: false,
-    },
-    {
-      name: "runtimeContext",
-      type: "RuntimeContext",
-      description: "Runtime context data to use during workflow execution",
-      isOptional: true,
-    },
-    {
-      name: "abort",
-      type: "() => any",
-      description: "Function to abort workflow execution",
-      isOptional: false,
-    },
-    {
-      name: "abortSignal",
-      type: "AbortSignal",
-      description: "Abort signal for workflow execution",
-      isOptional: false,
-    },
-    {
-      name: "runCount",
-      type: "number",
-      description: "Number of times the workflow has been run",
-      isOptional: true,
-    },
-  ]}
-/>
-
-## Returns
-
-<PropertiesTable
-  content={[
-    {
-      name: "result",
-      type: "Promise<z.infer<TOutput>>",
-      description: "A promise that resolves to the output of the executed workflow",
-    },
-  ]}
-/>
-
-## Related
-
-- [Workflow.createRunAsync()](./create-run.mdx) - Alternative method for creating workflow runs
-- [WorkflowRun.start()](./run-methods/start.mdx) - Starting workflow execution
-- [Workflows overview](../../docs/workflows/overview.mdx#run-workflow)

package/.docs/raw/tools-mcp/dynamic-context.mdx

@@ -1,131 +0,0 @@
----
-title: "Dynamic Tool Context | Tools & MCP | Mastra Docs"
-description: Learn how to use Mastra's RuntimeContext to provide dynamic, request-specific configuration to tools.
----
-
-import { Callout } from "nextra/components";
-
-# Dynamic Tool Context
-
-Mastra provides `RuntimeContext`, a system based on dependency injection, that allows you to pass dynamic, request-specific configuration to your tools during execution. This is useful when a tool's behavior needs to change based on user identity, request headers, or other runtime factors, without altering the tool's core code.
-
-<Callout>
-  **Note:** `RuntimeContext` is primarily used for passing data *into* tool
-  executions. It's distinct from agent memory, which handles conversation
-  history and state persistence across multiple calls.
-</Callout>
-
-## Basic Usage
-
-To use `RuntimeContext`, first define a type structure for your dynamic configuration. Then, create an instance of `RuntimeContext` typed with your definition and set the desired values. Finally, include the `runtimeContext` instance in the options object when calling `agent.generate()` or `agent.stream()`.
-
-```typescript
-import { RuntimeContext } from "@mastra/core/di";
-// Assume 'agent' is an already defined Mastra Agent instance
-
-// Define the context type
-type WeatherRuntimeContext = {
-  "temperature-scale": "celsius" | "fahrenheit";
-};
-
-// Instantiate RuntimeContext and set values
-const runtimeContext = new RuntimeContext<WeatherRuntimeContext>();
-runtimeContext.set("temperature-scale", "celsius");
-
-// Pass to agent call
-const response = await agent.generate("What's the weather like today?", {
-  runtimeContext, // Pass the context here
-});
-
-console.log(response.text);
-```
-
-## Accessing Context in Tools
-
-Tools receive the `runtimeContext` as part of the second argument to their `execute` function. You can then use the `.get()` method to retrieve values.
-
-```typescript filename="src/mastra/tools/weather-tool.ts"
-import { createTool } from "@mastra/core/tools";
-import { z } from "zod";
-// Assume WeatherRuntimeContext is defined as above and accessible here
-
-// Dummy fetch function
-async function fetchWeather(
-  location: string,
-  options: { temperatureUnit: "celsius" | "fahrenheit" },
-): Promise<any> {
-  console.log(`Fetching weather for ${location} in ${options.temperatureUnit}`);
-  // Replace with actual API call
-  return { temperature: options.temperatureUnit === "celsius" ? 20 : 68 };
-}
-
-export const weatherTool = createTool({
-  id: "getWeather",
-  description: "Get the current weather for a location",
-  inputSchema: z.object({
-    location: z.string().describe("The location to get weather for"),
-  }),
-  // The tool's execute function receives runtimeContext
-  execute: async ({ context, runtimeContext }) => {
-    // Type-safe access to runtimeContext variables
-    const temperatureUnit = runtimeContext.get("temperature-scale");
-
-    // Use the context value in the tool logic
-    const weather = await fetchWeather(context.location, {
-      temperatureUnit,
-    });
-
-    return {
-      result: `The temperature is ${weather.temperature}°${temperatureUnit === "celsius" ? "C" : "F"}`,
-    };
-  },
-});
-```
-
-When the agent uses `weatherTool`, the `temperature-scale` value set in the `runtimeContext` during the `agent.generate()` call will be available inside the tool's `execute` function.
-
-## Using with Server Middleware
-
-In server environments (like Express or Next.js), you can use middleware to automatically populate `RuntimeContext` based on incoming request data, such as headers or user sessions.
-
-Here's an example using Mastra's built-in server middleware support (which uses Hono internally) to set the temperature scale based on the Cloudflare `CF-IPCountry` header:
-
-```typescript filename="src/mastra/index.ts"
-import { Mastra } from "@mastra/core";
-import { RuntimeContext } from "@mastra/core/di";
-import { weatherAgent } from "./agents/weather"; // Assume agent is defined elsewhere
-
-// Define RuntimeContext type
-type WeatherRuntimeContext = {
-  "temperature-scale": "celsius" | "fahrenheit";
-};
-
-export const mastra = new Mastra({
-  agents: {
-    weather: weatherAgent,
-  },
-  server: {
-    middleware: [
-      async (c, next) => {
-        // Get the RuntimeContext instance
-        const runtimeContext =
-          c.get<RuntimeContext<WeatherRuntimeContext>>("runtimeContext");
-
-        // Get country code from request header
-        const country = c.req.header("CF-IPCountry");
-
-        // Set temperature scale based on country
-        runtimeContext.set(
-          "temperature-scale",
-          country === "US" ? "fahrenheit" : "celsius",
-        );
-
-        // Continue request processing
-        await next();
-      },
-    ],
-  },
-});
-```
-
-With this middleware in place, any agent call handled by this Mastra server instance will automatically have the `temperature-scale` set in its `RuntimeContext` based on the user's inferred country, and tools like `weatherTool` will use it accordingly.