@mastra/mcp-docs-server 0.13.22-alpha.5 → 0.13.22-alpha.7

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

@@ -20,9 +20,10 @@ The dependency injection system allows you to:
 
 Agents can access `runtimeContext` via the `instructions` parameter, and retrieve variables using `runtimeContext.get()`. This allows agent behavior to adapt dynamically based on user input or external configuration, without changing the underlying implementation.
 
-```typescript {6-7,14} filename="src/mastra/agents/test-weather-agent.ts" showLineNumbers copy
+```typescript {7-8,15} filename="src/mastra/agents/test-weather-agent.ts" showLineNumbers copy
 import { openai } from "@ai-sdk/openai";
 import { Agent } from "@mastra/core/agent";
+import { testWeatherTool } from "../tools/test-weather-tool";
 
 export const testWeatherAgent = new Agent({
   name: "test-weather-agent",
@@ -38,7 +39,47 @@ export const testWeatherAgent = new Agent({
     - If no city is mentioned, ask for a city name
     `;
   },
-  model: openai("gpt-4o-mini")
+  model: openai("gpt-4o-mini"),
+  tools: { testWeatherTool }
+});
+```
+
+### Example tool
+
+This tool exports a `WeatherRuntimeContext` type, which can be used anywhere `RuntimeContext` is used to enable type-safe access to runtime configuration.
+
+```typescript {4-6} filename="src/mastra/tools/test-weather-tool.ts" showLineNumbers copy
+import { createTool } from "@mastra/core/tools";
+import { z } from "zod";
+
+export type WeatherRuntimeContext = {
+  "temperature-unit": "celsius" | "fahrenheit";
+};
+
+export const testWeatherTool = createTool({
+  id: "test-weather-tool",
+  description: "Get weather for a location",
+  inputSchema: z.object({
+    location: z.string()
+  }),
+  outputSchema: z.object({
+    metric: z.string(),
+    temperature: z.number(),
+    weather: z.string()
+  }),
+  execute: async ({ context, runtimeContext }) => {
+    const { location } = context;
+    const unit = runtimeContext.get("temperature-unit") as WeatherRuntimeContext["temperature-unit"];
+
+    const temperature = 30;
+    const weather = "Sunny";
+
+    return {
+      metric: unit === "celsius" ? "°C" : "°F",
+      temperature,
+      weather
+    };
+  }
 });
 ```
 
@@ -46,16 +87,13 @@ export const testWeatherAgent = new Agent({
 
 In this example, `temperature-unit` is set using `runtimeContext.set()` to either **celsius** or **fahrenheit**, allowing the agent to respond with temperatures in the appropriate unit.
 
-```typescript {12} filename="src/test-weather-agent.ts" showLineNumbers copy
+```typescript {9, 12} filename="src/test-weather-agent.ts" showLineNumbers copy
 import { mastra } from "./mastra";
 import { RuntimeContext } from "@mastra/core/runtime-context";
+import { WeatherRuntimeContext } from "./mastra/tools/test-weather-tool";
 
 const agent = mastra.getAgent("testWeatherAgent");
 
-export type WeatherRuntimeContext = {
-  "temperature-unit": "celsius" | "fahrenheit";
-};
-
 const runtimeContext = new RuntimeContext<WeatherRuntimeContext>();
 
 runtimeContext.set("temperature-unit", "fahrenheit");
@@ -71,14 +109,11 @@ console.log(response.text);
 
 You can populate `runtimeContext` 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 {2,12-21} filename="src/mastra/index.ts" showLineNumbers copy
+```typescript {2,4,9-18} filename="src/mastra/index.ts" showLineNumbers copy
 import { Mastra } from "@mastra/core/mastra";
 import { RuntimeContext } from "@mastra/core/runtime-context";
 import { testWeatherAgent } from "./agents/test-weather-agent";
-
-type WeatherRuntimeContext = {
-  "temperature-unit": "celsius" | "fahrenheit";
-};
+import { WeatherRuntimeContext } from "./mastra/tools/test-weather-tool";
 
 export const mastra = new Mastra({
   agents: { testWeatherAgent },

package/.docs/raw/frameworks/agentic-uis/cedar-os.mdx

@@ -8,19 +8,19 @@ import { Tabs, Steps } from "nextra/components";
 
 # Integrate Cedar-OS with Mastra
 
-Cedar-OS is an open-source agentic UI framework designed specifically for building the most ambitious AI-native applications. We built Cedar with Mastra in mind.
+Cedar-OS is an open-source agentic UI framework designed specifically for building the most ambitious AI-native applications. Cedar was built with Mastra in mind.
 
 ## Should you use Cedar?
 
-There are a few pillars we care about strongly that you can read more about [here](https://docs.cedarcopilot.com/introduction/philosophy):
+There are a few pillars Cedar cares about strongly that you can read more about [here](https://docs.cedarcopilot.com/introduction/philosophy):
 
 #### 1. Developer experience
 - **Every single component is downloaded shadcn-style** – You own all the code and can style it however you want
-- **Works out of the box** – Just drop in our chat component, and it'll work
+- **Works out of the box** – Just drop in the chat component, and it'll work
 - **Fully extensible** - Built on a [Zustand store architecture](https://docs.cedarcopilot.com/introduction/architecture) that you can customize completely. Every single internal function can be overridden in one line.
 
 #### 2. Enabling truly AI-native applications
-For the first time in history, products can come to life. We want to help you build something with life.
+For the first time in history, products can come to life. Cedar is aimed at helping you build something with life.
 - **[Spells](https://docs.cedarcopilot.com/spells/spells#what-are-spells)** - Users can trigger AI from keyboard shortcuts, mouse events, text selection, and other components
 - **[State Diff Management](https://docs.cedarcopilot.com/state-diff/using-state-diff)** - Give users control over accepting/rejecting agent outputs 
 - **[Voice Integration](https://docs.cedarcopilot.com/voice/voice-integration)** - Let users control your app with their voice
@@ -38,7 +38,7 @@ npx cedar-os-cli plant-seed
 If starting from scratch, select the **Mastra starter** template for a complete setup with both frontend and backend in a monorepo
 
 If you already have a Mastra backend, use the **blank frontend cedar repo** option instead.
-- This will give you the option to download components and download all dependencies for Cedar. We recommend at least downloading one of the chat components to get started. 
+- This will give you the option to download components and download all dependencies for Cedar. It is recommended to download at least one of the chat components to get started. 
 
 ### Wrap your app with CedarCopilot
 
@@ -101,8 +101,8 @@ Your backend and frontend are now linked! You're ready to start building AI-nati
 ## More information
 
 - Check out the [detailed Mastra integration guide](https://docs.cedarcopilot.com/agent-backend-connection/mastra#extending-mastra) for more configuration options (or for manual installation instructions if something goes wrong)
-- Explore Mastra-specific optimizations and features we've built
+- Explore Mastra-specific optimizations and features Cedar has built
   - **Seamless event streaming** - Automatic rendering of [Mastra streamed events](https://docs.cedarcopilot.com/chat/custom-message-rendering#mastra-event-renderer)
   - **Voice endpoint support** - Built-in [voice backend integration](https://docs.cedarcopilot.com/voice/agentic-backend#endpoint-configuration)
   - **End-to-End type safety** - [Types](https://docs.cedarcopilot.com/type-safety/typing-agent-requests) for communicating between your app and Mastra backend
-- [Join our Discord!](https://discord.gg/4AWawRjNdZ) We're excited to have you :)
+- [Join the Discord!](https://discord.gg/4AWawRjNdZ) The Cedar team is excited to have you :)

package/CHANGELOG.md

@@ -1,5 +1,22 @@
 # @mastra/mcp-docs-server
 
+## 0.13.22-alpha.7
+
+### Patch Changes
+
+- Updated dependencies [[`4f9ea8c`](https://github.com/mastra-ai/mastra/commit/4f9ea8c95ea74ba9abbf3b2ab6106c7d7bc45689)]:
+  - @mastra/core@0.17.0-alpha.7
+
+## 0.13.22-alpha.6
+
+### Patch Changes
+
+- dependencies updates: ([#7907](https://github.com/mastra-ai/mastra/pull/7907))
+  - Updated dependency [`turndown@^7.2.1` ↗︎](https://www.npmjs.com/package/turndown/v/7.2.1) (from `^7.2.0`, in `dependencies`)
+- Updated dependencies [[`197cbb2`](https://github.com/mastra-ai/mastra/commit/197cbb248fc8cb4bbf61bf70b770f1388b445df2), [`6590763`](https://github.com/mastra-ai/mastra/commit/65907630ef4bf4127067cecd1cb21b56f55d5f1b), [`c2eade3`](https://github.com/mastra-ai/mastra/commit/c2eade3508ef309662f065e5f340d7840295dd53), [`222965a`](https://github.com/mastra-ai/mastra/commit/222965a98ce8197b86673ec594244650b5960257), [`0324ceb`](https://github.com/mastra-ai/mastra/commit/0324ceb8af9d16c12a531f90e575f6aab797ac81), [`0f9d227`](https://github.com/mastra-ai/mastra/commit/0f9d227890a98db33865abbea39daf407cd55ef7), [`de056a0`](https://github.com/mastra-ai/mastra/commit/de056a02cbb43f6aa0380ab2150ea404af9ec0dd), [`c93532a`](https://github.com/mastra-ai/mastra/commit/c93532a340b80e4dd946d4c138d9381de5f70399), [`6cb1fcb`](https://github.com/mastra-ai/mastra/commit/6cb1fcbc8d0378ffed0d17784c96e68f30cb0272), [`2685a78`](https://github.com/mastra-ai/mastra/commit/2685a78f224b8b04e20d4fab5ac1adb638190071), [`239b5a4`](https://github.com/mastra-ai/mastra/commit/239b5a497aeae2e8b4d764f46217cfff2284788e)]:
+  - @mastra/core@0.17.0-alpha.6
+  - @mastra/mcp@0.13.0-alpha.2
+
 ## 0.13.22-alpha.5
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mastra/mcp-docs-server",
-  "version": "0.13.22-alpha.5",
+  "version": "0.13.22-alpha.7",
   "description": "MCP server for accessing Mastra.ai documentation, changelogs, and news.",
   "type": "module",
   "main": "dist/index.js",
@@ -29,28 +29,28 @@
     "date-fns": "^4.1.0",
     "exit-hook": "^4.0.0",
     "jsdom": "^26.1.0",
-    "turndown": "^7.2.0",
+    "turndown": "^7.2.1",
     "uuid": "^11.1.0",
     "zod": "^3.25.76",
     "zod-to-json-schema": "^3.24.6",
-    "@mastra/core": "0.17.0-alpha.5",
-    "@mastra/mcp": "^0.13.0-alpha.1"
+    "@mastra/mcp": "^0.13.0-alpha.2",
+    "@mastra/core": "0.17.0-alpha.7"
   },
   "devDependencies": {
-    "@hono/node-server": "^1.19.2",
+    "@hono/node-server": "^1.19.3",
     "@types/jsdom": "^21.1.7",
     "@types/node": "^20.19.0",
     "@types/turndown": "^5.0.5",
     "@wong2/mcp-cli": "^1.10.0",
     "cross-env": "^7.0.3",
-    "eslint": "^9.30.1",
-    "hono": "^4.9.6",
+    "eslint": "^9.35.0",
+    "hono": "^4.9.7",
     "tsup": "^8.5.0",
     "tsx": "^4.19.4",
     "typescript": "^5.8.3",
     "vitest": "^3.2.4",
     "@internal/lint": "0.0.39",
-    "@mastra/core": "0.17.0-alpha.5"
+    "@mastra/core": "0.17.0-alpha.7"
   },
   "homepage": "https://mastra.ai",
   "repository": {

package/.docs/raw/reference/networks/agent-network.mdx

@@ -1,165 +0,0 @@
----
-title: "AgentNetwork (Experimental)"
-description: "Reference documentation for the AgentNetwork class"
----
-
-# AgentNetwork (Experimental)
-
-> **Note:** The AgentNetwork feature is experimental and may change in future releases.
-
-The `AgentNetwork` class provides a way to create a network of specialized agents that can collaborate to solve complex tasks. Unlike Workflows, which require explicit control over execution paths, AgentNetwork uses an LLM-based router to dynamically determine which agent to call next.
-
-## Key Concepts
-
-- **LLM-based Routing**: AgentNetwork exclusively uses an LLM to figure out the best way to use your agents
-- **Agent Collaboration**: Multiple specialized agents can work together to solve complex tasks
-- **Dynamic Decision Making**: The router decides which agent to call based on the task requirements
-
-## Usage
-
-```typescript
-import { AgentNetwork } from "@mastra/core/network";
-import { openai } from "@mastra/openai";
-
-// Create specialized agents
-const webSearchAgent = new Agent({
-  name: "Web Search Agent",
-  instructions: "You search the web for information.",
-  model: openai("gpt-4o"),
-  tools: {
-    /* web search tools */
-  },
-});
-
-const dataAnalysisAgent = new Agent({
-  name: "Data Analysis Agent",
-  instructions: "You analyze data and provide insights.",
-  model: openai("gpt-4o"),
-  tools: {
-    /* data analysis tools */
-  },
-});
-
-// Create the network
-const researchNetwork = new AgentNetwork({
-  name: "Research Network",
-  instructions: "Coordinate specialized agents to research topics thoroughly.",
-  model: openai("gpt-4o"),
-  agents: [webSearchAgent, dataAnalysisAgent],
-});
-
-// Use the network
-const result = await researchNetwork.generate(
-  "Research the impact of climate change on agriculture",
-);
-console.log(result.text);
-```
-
-## Constructor
-
-```typescript
-constructor(config: AgentNetworkConfig)
-```
-
-### Parameters
-
-- `config`: Configuration object for the AgentNetwork
-  - `name`: Name of the network
-  - `instructions`: Instructions for the routing agent
-  - `model`: Language model to use for routing
-  - `agents`: Array of specialized agents in the network
-
-## Methods
-
-### generate()
-
-Generates a response using the agent network. This method has replaced the deprecated `run()` method for consistency with the rest of the codebase.
-
-```typescript
-async generate(
-  messages: string | string[] | CoreMessage[],
-  args?: AgentGenerateOptions
-): Promise<GenerateTextResult>
-```
-
-### stream()
-
-Streams a response using the agent network.
-
-```typescript
-async stream(
-  messages: string | string[] | CoreMessage[],
-  args?: AgentStreamOptions
-): Promise<StreamTextResult>
-```
-
-### getRoutingAgent()
-
-Returns the routing agent used by the network.
-
-```typescript
-getRoutingAgent(): Agent
-```
-
-### getAgents()
-
-Returns the array of specialized agents in the network.
-
-```typescript
-getAgents(): Agent[]
-```
-
-### getAgentHistory()
-
-Returns the history of interactions for a specific agent.
-
-```typescript
-getAgentHistory(agentId: string): Array<{
-  input: string;
-  output: string;
-  timestamp: string;
-}>
-```
-
-### getAgentInteractionHistory()
-
-Returns the history of all agent interactions that have occurred in the network.
-
-```typescript
-getAgentInteractionHistory(): Record<
-  string,
-  Array<{
-    input: string;
-    output: string;
-    timestamp: string;
-  }>
->
-```
-
-### getAgentInteractionSummary()
-
-Returns a formatted summary of agent interactions in chronological order.
-
-```typescript
-getAgentInteractionSummary(): string
-```
-
-## When to Use AgentNetwork vs Workflows
-
-- **Use AgentNetwork when:** You want the AI to figure out the best way to use your agents, with dynamic routing based on the task requirements.
-
-- **Use Workflows when:** You need explicit control over execution paths, with predetermined sequences of agent calls and conditional logic.
-
-## Internal Tools
-
-The AgentNetwork uses a special `transmit` tool that allows the routing agent to call specialized agents. This tool handles:
-
-- Single agent calls
-- Multiple parallel agent calls
-- Context sharing between agents
-
-## Limitations
-
-- The AgentNetwork approach may use more tokens than a well-designed Workflow for the same task
-- Debugging can be more challenging as the routing decisions are made by the LLM
-- Performance may vary based on the quality of the routing instructions and the capabilities of the specialized agents