@mastra/mcp-docs-server 0.13.7-alpha.3 → 0.13.7-alpha.5

package/.docs/organized/changelogs/%40mastra%2Fvoice-sarvam.md

@@ -1,5 +1,12 @@
 # @mastra/voice-sarvam
 
+## 0.10.6-alpha.0
+
+### Patch Changes
+
+- f42c4c2: update peer deps for packages to latest core range
+  - @mastra/core@0.12.0-alpha.5
+
 ## 0.10.5
 
 ### Patch Changes
@@ -291,12 +298,5 @@
 
 ### Patch Changes
 
-- Updated dependencies [e450778]
-- Updated dependencies [8902157]
-- Updated dependencies [ca0dc88]
-- Updated dependencies [9cd1a46]
-- Updated dependencies [70dbf51]
-  - @mastra/core@0.9.3-alpha.1
-
 
-... 639 more lines hidden. See full changelog in package directory.
+... 646 more lines hidden. See full changelog in package directory.

package/.docs/organized/changelogs/%40mastra%2Fvoice-speechify.md

@@ -1,5 +1,12 @@
 # @mastra/voice-speechify
 
+## 0.10.6-alpha.0
+
+### Patch Changes
+
+- f42c4c2: update peer deps for packages to latest core range
+  - @mastra/core@0.12.0-alpha.5
+
 ## 0.10.5
 
 ### Patch Changes
@@ -291,12 +298,5 @@
 
 ## 0.1.17
 
-### Patch Changes
-
-- Updated dependencies [e450778]
-- Updated dependencies [8902157]
-- Updated dependencies [ca0dc88]
-- Updated dependencies [526c570]
-- Updated dependencies [d7a6a33]
 
-... 993 more lines hidden. See full changelog in package directory.
+... 1000 more lines hidden. See full changelog in package directory.

package/.docs/organized/changelogs/mastra.md

@@ -1,5 +1,16 @@
 # mastra
 
+## 0.10.16-alpha.3
+
+### Patch Changes
+
+- f42c4c2: update peer deps for packages to latest core range
+- Updated dependencies [f42c4c2]
+  - @mastra/deployer@0.12.0-alpha.5
+  - @mastra/loggers@0.10.5-alpha.0
+  - @mastra/mcp@0.10.8-alpha.0
+  - @mastra/core@0.12.0-alpha.5
+
 ## 0.10.16-alpha.2
 
 ### Patch Changes
@@ -287,16 +298,5 @@
 - Updated dependencies [626b0f4]
 - Updated dependencies [c22a91f]
 - Updated dependencies [f7403ab]
-- Updated dependencies [6c89d7f]
-  - @mastra/deployer@0.10.15-alpha.0
-  - @mastra/core@0.10.15-alpha.0
-
-## 0.10.12
-
-### Patch Changes
-
-- 640f47e: move agent model settings into agent settings
-- 5d0c163: Scaffold create-mastra projects with zod@^3 to prevent package version conflicts during install
-- 53e3f58: Add support for custom instrumentation files
 
-... 4594 more lines hidden. See full changelog in package directory.
+... 4605 more lines hidden. See full changelog in package directory.

package/.docs/organized/code-examples/agent.md

@@ -462,7 +462,12 @@ import { Memory } from '@mastra/memory';
 import { Agent, InputProcessor } from '@mastra/core/agent';
 import { cookingTool } from '../tools/index.js';
 import { myWorkflow } from '../workflows/index.js';
-import { PIIDetector, LanguageDetector, PromptInjectionDetector } from '@mastra/core/agent/input-processor/processors';
+import {
+  PIIDetector,
+  LanguageDetector,
+  PromptInjectionDetector,
+  ModerationInputProcessor,
+} from '@mastra/core/agent/input-processor/processors';
 import { MCPClient } from '@mastra/mcp';
 
 const memory = new Memory();
@@ -577,13 +582,9 @@ const promptInjectionDetector = new PromptInjectionDetector({
   strategy: 'block',
 });
 
-const mcpInstance = new MCPClient({
-  id: 'myMcpServerTwo',
-  servers: {
-    myMcpServerTwo: {
-      url: new URL(`http://localhost:4111/api/mcp/myMcpServerTwo/mcp`),
-    },
-  },
+const moderationDetector = new ModerationInputProcessor({
+  model: google('gemini-2.0-flash-001'),
+  strategy: 'block',
 });
 
 export const chefAgentResponses = new Agent({
@@ -596,7 +597,6 @@ export const chefAgentResponses = new Agent({
   model: openai.responses('gpt-4o'),
   tools: async () => {
     return {
-      ...(await mcpInstance.getTools()),
       web_search_preview: openai.tools.webSearchPreview(),
     };
   },
@@ -604,10 +604,11 @@ export const chefAgentResponses = new Agent({
     myWorkflow,
   },
   inputProcessors: [
-    piiDetector,
-    vegetarianProcessor,
+    // piiDetector,
+    // vegetarianProcessor,
     languageDetector,
-    promptInjectionDetector,
+    // promptInjectionDetector,
+    // moderationDetector,
     {
       name: 'no-soup-for-you',
       process: async ({ messages, abort }) => {

package/.docs/raw/agents/input-processors.mdx

@@ -153,7 +153,7 @@ import { LanguageDetector } from "@mastra/core/agent/input-processor/processors"
 const agent = new Agent({
   inputProcessors: [
     new LanguageDetector({
-      model: openai("gpt-4o"),
+      model: openai("gpt-4o-mini"),
       targetLanguages: ['English', 'en'], // Accept English content
       strategy: 'translate', // Auto-translate non-English content
       threshold: 0.8, // High confidence threshold
@@ -210,7 +210,7 @@ const secureAgent = new Agent({
 You can create custom processors by implementing the `InputProcessor` interface.
 
 ```typescript copy showLineNumbers {4-19,23-26}
-import type { InputProcessor, MastraMessageV2 } from "@mastra/core/agent";
+import type { InputProcessor, MastraMessageV2, TripWire } from "@mastra/core/agent";
 
 class MessageLengthLimiter implements InputProcessor {
   readonly name = 'message-length-limiter';
@@ -222,14 +222,21 @@ class MessageLengthLimiter implements InputProcessor {
     abort: (reason?: string) => never 
   }): MastraMessageV2[] {
     // Check total message length
-    const totalLength = messages.reduce((sum, msg) => {
-      return sum + msg.content.parts
-        .filter(part => part.type === 'text')
-        .reduce((partSum, part) => partSum + (part as any).text.length, 0);
-    }, 0);
-    
-    if (totalLength > this.maxLength) {
-      abort(`Message too long: ${totalLength} characters (max: ${this.maxLength})`);
+    try {
+      const totalLength = messages.reduce((sum, msg) => {
+        return sum + msg.content.parts
+          .filter(part => part.type === 'text')
+          .reduce((partSum, part) => partSum + (part as any).text.length, 0);
+      }, 0);
+      
+      if (totalLength > this.maxLength) {
+        abort(`Message too long: ${totalLength} characters (max: ${this.maxLength})`); // throws a TripWire error
+      }
+    } catch (error) {
+      if (error instanceof TripWire) {
+        throw error; // Re-throw tripwire errors
+      }
+      throw new Error(`Length validation failed: ${error instanceof Error ? error.message : 'Unknown error'}`); // application level throw a standard error
     }
     
     return messages;
@@ -246,9 +253,10 @@ const agent = new Agent({
 
 When creating custom processors:
 - Always return the `messages` array (potentially modified)
-- Use `abort(reason)` to terminate processing early
-- Mutate the input messages directly
+- Use `abort(reason)` to terminate processing early. Abort is used to simulate blocking a message. errors thrown with `abort` will be an instance of TripWire. For code/application level errors, throw standard errors.
+- Mutate the input messages directly, make sure to mutate both the parts and content of a message.
 - Keep processors focused on a single responsibility
+- If using an agent inside your processor, use a fast model, limit the size of the response from it as much as possible (every token slows down the response exponentially), and make the system prompt as concise as possible, these are both latency bottlenecks.
 
 ## Integration with Agent Methods
 
@@ -265,4 +273,4 @@ for await (const chunk of stream.textStream) {
 }
 ```
 
-If any processor calls `abort()`, the request terminates immediately and subsequent processors are not executed. The agent returns an error response with details about why the request was blocked. 
+If any processor calls `abort()`, the request terminates immediately and subsequent processors are not executed. The agent returns a 200 response with details (`result.tripwireReason`) about why the request was blocked. 

package/.docs/raw/evals/custom-eval.mdx

@@ -3,8 +3,12 @@ title: "Create a custom eval"
 description: "Mastra allows you to create your own evals, here is how."
 ---
 
+import { ScorerCallout } from '@/components/scorer-callout'
+
 # Create a Custom Eval
 
+<ScorerCallout />
+
 Create a custom eval by extending the `Metric` class and implementing the `measure` method. This gives you full control over how scores are calculated and what information is returned. For LLM-based evaluations, extend the `MastraAgentJudge` class to define how the model reasons and scores output.
 
 ## Native JavaScript evaluation

package/.docs/raw/evals/overview.mdx

@@ -3,8 +3,12 @@ title: "Overview"
 description: "Understanding how to evaluate and measure AI agent quality using Mastra evals."
 ---
 
+import { ScorerCallout } from '@/components/scorer-callout'
+
 # Testing your agents with evals
 
+<ScorerCallout />
+
 While traditional software tests have clear pass/fail conditions, AI outputs are non-deterministic — they can vary with the same input. Evals help bridge this gap by providing quantifiable metrics for measuring agent quality.
 
 Evals are automated tests that evaluate Agents outputs using model-graded, rule-based, and statistical methods. Each eval returns a normalized score between 0-1 that can be logged and compared. Evals can be customized with your own prompts and scoring functions.

package/.docs/raw/evals/running-in-ci.mdx

@@ -3,8 +3,12 @@ title: "Running in CI"
 description: "Learn how to run Mastra evals in your CI/CD pipeline to monitor agent quality over time."
 ---
 
+import { ScorerCallout } from '@/components/scorer-callout'
+
 # Running Evals in CI
 
+<ScorerCallout />
+
 Running evals in your CI pipeline helps bridge this gap by providing quantifiable metrics for measuring agent quality over time.
 
 ## Setting Up CI Integration

package/.docs/raw/evals/textual-evals.mdx

@@ -3,8 +3,12 @@ title: "Textual Evals"
 description: "Understand how Mastra uses LLM-as-judge methodology to evaluate text quality."
 ---
 
+import { ScorerCallout } from '@/components/scorer-callout'
+
 # Textual Evals
 
+<ScorerCallout />
+
 Textual evals use an LLM-as-judge methodology to evaluate agent outputs. This approach leverages language models to assess various aspects of text quality, similar to how a teaching assistant might grade assignments using a rubric.
 
 Each eval focuses on specific quality aspects and returns a score between 0 and 1, providing quantifiable metrics for non-deterministic AI outputs.

package/.docs/raw/reference/evals/answer-relevancy.mdx

@@ -3,8 +3,12 @@ title: "Reference: Answer Relevancy | Metrics | Evals | Mastra Docs"
 description: Documentation for the Answer Relevancy Metric in Mastra, which evaluates how well LLM outputs address the input query.
 ---
 
+import { ScorerCallout } from '@/components/scorer-callout'
+
 # AnswerRelevancyMetric
 
+<ScorerCallout />
+
 The `AnswerRelevancyMetric` class evaluates how well an LLM's output answers or addresses the input query. It uses a judge-based system to determine relevancy and provides detailed scoring and reasoning.
 
 ## Basic Usage

package/.docs/raw/reference/evals/bias.mdx

@@ -3,8 +3,12 @@ title: "Reference: Bias | Output Metrics | Evals | Mastra Docs"
 description: Documentation for the Bias Metric in Mastra, which evaluates LLM outputs for various forms of bias, including gender, political, racial/ethnic, or geographical bias.
 ---
 
+import { ScorerCallout } from '@/components/scorer-callout'
+
 # BiasMetric
 
+<ScorerCallout />
+
 The `BiasMetric` class evaluates whether an LLM's output contains various forms of bias, including gender, political, racial/ethnic, or geographical bias. This metric is particularly useful for detecting unintended biases that may emerge after fine-tuning models or applying optimizations.
 
 ## Basic Usage

package/.docs/raw/reference/evals/completeness.mdx

@@ -3,8 +3,12 @@ title: "Reference: Completeness | Metrics | Evals | Mastra Docs"
 description: Documentation for the Completeness Metric in Mastra, which evaluates how thoroughly LLM outputs cover key elements present in the input.
 ---
 
+import { ScorerCallout } from '@/components/scorer-callout'
+
 # CompletenessMetric
 
+<ScorerCallout />
+
 The `CompletenessMetric` class evaluates how thoroughly an LLM's output covers the key elements present in the input. It analyzes nouns, verbs, topics, and terms to determine coverage and provides a detailed completeness score.
 
 ## Basic Usage

package/.docs/raw/reference/evals/content-similarity.mdx

@@ -3,8 +3,12 @@ title: "Reference: Content Similarity | Evals | Mastra Docs"
 description: Documentation for the Content Similarity Metric in Mastra, which measures textual similarity between strings and provides a matching score.
 ---
 
+import { ScorerCallout } from '@/components/scorer-callout'
+
 # ContentSimilarityMetric
 
+<ScorerCallout />
+
 The `ContentSimilarityMetric` class measures the textual similarity between two strings, providing a score that indicates how closely they match. It supports configurable options for case sensitivity and whitespace handling.
 
 ## Basic Usage

package/.docs/raw/reference/evals/context-position.mdx

@@ -3,8 +3,12 @@ title: "Reference: Context Position | Metrics | Evals | Mastra Docs"
 description: Documentation for the Context Position Metric in Mastra, which evaluates the ordering of context nodes based on their relevance to the query and output.
 ---
 
+import { ScorerCallout } from '@/components/scorer-callout'
+
 # ContextPositionMetric
 
+<ScorerCallout />
+
 The `ContextPositionMetric` class evaluates how well context nodes are ordered based on their relevance to the query and output. It uses position-weighted scoring to emphasize the importance of having the most relevant context pieces appear earlier in the sequence.
 
 ## Basic Usage

package/.docs/raw/reference/evals/context-precision.mdx

@@ -3,8 +3,12 @@ title: "Reference: Context Precision | Metrics | Evals | Mastra Docs"
 description: Documentation for the Context Precision Metric in Mastra, which evaluates the relevance and precision of retrieved context nodes for generating expected outputs.
 ---
 
+import { ScorerCallout } from '@/components/scorer-callout'
+
 # ContextPrecisionMetric
 
+<ScorerCallout />
+
 The `ContextPrecisionMetric` class evaluates how relevant and precise the retrieved context nodes are for generating the expected output. It uses a judge-based system to analyze each context piece's contribution and provides weighted scoring based on position.
 
 ## Basic Usage

package/.docs/raw/reference/evals/context-relevancy.mdx

@@ -3,8 +3,12 @@ title: "Reference: Context Relevancy | Evals | Mastra Docs"
 description: Documentation for the Context Relevancy Metric, which evaluates the relevance of retrieved context in RAG pipelines.
 ---
 
+import { ScorerCallout } from '@/components/scorer-callout'
+
 # ContextRelevancyMetric
 
+<ScorerCallout />
+
 The `ContextRelevancyMetric` class evaluates the quality of your RAG (Retrieval-Augmented Generation) pipeline's retriever by measuring how relevant the retrieved context is to the input query. It uses an LLM-based evaluation system that first extracts statements from the context and then assesses their relevance to the input.
 
 ## Basic Usage

package/.docs/raw/reference/evals/contextual-recall.mdx

@@ -3,8 +3,12 @@ title: "Reference: Contextual Recall | Metrics | Evals | Mastra Docs"
 description: Documentation for the Contextual Recall Metric, which evaluates the completeness of LLM responses in incorporating relevant context.
 ---
 
+import { ScorerCallout } from '@/components/scorer-callout'
+
 # ContextualRecallMetric
 
+<ScorerCallout />
+
 The `ContextualRecallMetric` class evaluates how effectively an LLM's response incorporates all relevant information from the provided context. It measures whether important information from the reference documents was successfully included in the response, focusing on completeness rather than precision.
 
 ## Basic Usage

package/.docs/raw/reference/evals/faithfulness.mdx

@@ -3,8 +3,12 @@ title: "Reference: Faithfulness | Metrics | Evals | Mastra Docs"
 description: Documentation for the Faithfulness Metric in Mastra, which evaluates the factual accuracy of LLM outputs compared to the provided context.
 ---
 
+import { ScorerCallout } from '@/components/scorer-callout'
+
 # FaithfulnessMetric Reference
 
+<ScorerCallout />
+
 The `FaithfulnessMetric` in Mastra evaluates how factually accurate an LLM's output is compared to the provided context. It extracts claims from the output and verifies them against the context, making it essential to measure RAG pipeline responses' reliability.
 
 ## Basic Usage

package/.docs/raw/reference/evals/hallucination.mdx

@@ -3,8 +3,12 @@ title: "Reference: Hallucination | Metrics | Evals | Mastra Docs"
 description: Documentation for the Hallucination Metric in Mastra, which evaluates the factual correctness of LLM outputs by identifying contradictions with provided context.
 ---
 
+import { ScorerCallout } from '@/components/scorer-callout'
+
 # HallucinationMetric
 
+<ScorerCallout />
+
 The `HallucinationMetric` evaluates whether an LLM generates factually correct information by comparing its output against the provided context. This metric measures hallucination by identifying direct contradictions between the context and the output.
 
 ## Basic Usage

package/.docs/raw/reference/evals/keyword-coverage.mdx

@@ -3,8 +3,12 @@ title: "Reference: Keyword Coverage | Metrics | Evals | Mastra Docs"
 description: Documentation for the Keyword Coverage Metric in Mastra, which evaluates how well LLM outputs cover important keywords from the input.
 ---
 
+import { ScorerCallout } from '@/components/scorer-callout'
+
 # KeywordCoverageMetric
 
+<ScorerCallout />
+
 The `KeywordCoverageMetric` class evaluates how well an LLM's output covers the important keywords from the input. It analyzes keyword presence and matches while ignoring common words and stop words.
 
 ## Basic Usage

package/.docs/raw/reference/evals/prompt-alignment.mdx

@@ -3,8 +3,12 @@ title: "Reference: Prompt Alignment | Metrics | Evals | Mastra Docs"
 description: Documentation for the Prompt Alignment Metric in Mastra, which evaluates how well LLM outputs adhere to given prompt instructions.
 ---
 
+import { ScorerCallout } from '@/components/scorer-callout'
+
 # PromptAlignmentMetric
 
+<ScorerCallout />
+
 The `PromptAlignmentMetric` class evaluates how strictly an LLM's output follows a set of given prompt instructions. It uses a judge-based system to verify each instruction is followed exactly and provides detailed reasoning for any deviations.
 
 ## Basic Usage

package/.docs/raw/reference/evals/summarization.mdx

@@ -3,9 +3,12 @@ title: "Reference: Summarization | Metrics | Evals | Mastra Docs"
 description: Documentation for the Summarization Metric in Mastra, which evaluates the quality of LLM-generated summaries for content and factual accuracy.
 ---
 
+import { ScorerCallout } from '@/components/scorer-callout'
+
 # SummarizationMetric
 
-,
+<ScorerCallout />
+
 The `SummarizationMetric` evaluates how well an LLM's summary captures the original text's content while maintaining factual accuracy. It combines two aspects: alignment (factual correctness) and coverage (inclusion of key information), using the minimum scores to ensure both qualities are necessary for a good summary.
 
 ## Basic Usage

package/.docs/raw/reference/evals/textual-difference.mdx

@@ -3,8 +3,12 @@ title: "Reference: Textual Difference | Evals | Mastra Docs"
 description: Documentation for the Textual Difference Metric in Mastra, which measures textual differences between strings using sequence matching.
 ---
 
+import { ScorerCallout } from '@/components/scorer-callout'
+
 # TextualDifferenceMetric
 
+<ScorerCallout />
+
 The `TextualDifferenceMetric` class uses sequence matching to measure the textual differences between two strings. It provides detailed information about changes, including the number of operations needed to transform one text into another.
 
 ## Basic Usage

package/.docs/raw/reference/evals/tone-consistency.mdx

@@ -3,8 +3,12 @@ title: "Reference: Tone Consistency | Metrics | Evals | Mastra Docs"
 description: Documentation for the Tone Consistency Metric in Mastra, which evaluates emotional tone and sentiment consistency in text.
 ---
 
+import { ScorerCallout } from '@/components/scorer-callout'
+
 # ToneConsistencyMetric
 
+<ScorerCallout />
+
 The `ToneConsistencyMetric` class evaluates the text's emotional tone and sentiment consistency. It can operate in two modes: comparing tone between input/output pairs or analyzing tone stability within a single text.
 
 ## Basic Usage

package/.docs/raw/reference/evals/toxicity.mdx

@@ -3,8 +3,12 @@ title: "Reference: Toxicity | Metrics | Evals | Mastra Docs"
 description: Documentation for the Toxicity Metric in Mastra, which evaluates LLM outputs for racist, biased, or toxic elements.
 ---
 
+import { ScorerCallout } from '@/components/scorer-callout'
+
 # ToxicityMetric
 
+<ScorerCallout />
+
 The `ToxicityMetric` class evaluates whether an LLM's output contains racist, biased, or toxic elements. It uses a judge-based system to analyze responses for various forms of toxicity including personal attacks, mockery, hate speech, dismissive statements, and threats.
 
 ## Basic Usage

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

@@ -50,10 +50,10 @@ All commands install the same @mastra/client-js package but use different packag
 
 To get started you'll need to initialize your MastraClient with necessary parameters:
 
-```typescript
+```typescript filename="lib/mastra-client.ts" showLineNumbers copy
 import { MastraClient } from "@mastra/client-js";
 
-const client = new MastraClient({
+export const mastraClient = new MastraClient({
   baseUrl: "http://localhost:4111", // Default Mastra development server port
 });
 ```
@@ -62,8 +62,10 @@ const client = new MastraClient({
 
 You can customize the client with various options:
 
-```typescript
-const client = new MastraClient({
+```typescript filename="lib/mastra-client.ts" showLineNumbers copy
+import { MastraClient } from "@mastra/client-js";
+
+export const mastraClient = new MastraClient({
   // Required
   baseUrl: "http://localhost:4111",
 
@@ -82,10 +84,12 @@ const client = new MastraClient({
 
 The Mastra Client SDK supports request cancellation using the standard Web API `AbortSignal`. Pass an `AbortSignal` to the client constructor to enable cancellation for all requests:
 
-```typescript
+```typescript filename="lib/mastra-client.ts" showLineNumbers copy
+import { MastraClient } from "@mastra/client-js";
+
 const controller = new AbortController();
 
-const client = new MastraClient({
+export const mastraClient = new MastraClient({
   baseUrl: "http://localhost:4111",
   abortSignal: controller.signal,
 });

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

@@ -37,7 +37,7 @@ Execute steps simultaneously using `.parallel()`:
 
 ![Concurrent steps with .parallel()](/image/workflows/workflows-control-flow-parallel.jpg)
 
-```typescript {8,4-5} filename="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
+```typescript {9,4-5} filename="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
 import { createWorkflow, createStep } from "@mastra/core/workflows";
 import { z } from "zod";
 
@@ -70,8 +70,8 @@ const greaterThanStep = createStep({...});
 
 export const testWorkflow = createWorkflow({...})
   .branch([
-    [async ({ inputData: { value } }) => (value < 9), lessThanStep],
-    [async ({ inputData: { value } }) => (value >= 9), greaterThanStep]
+    [async ({ inputData: { value } }) => value <= 10, lessThanStep],
+    [async ({ inputData: { value } }) => value > 10, greaterThanStep]
   ])
   .commit();
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mastra/mcp-docs-server",
-  "version": "0.13.7-alpha.3",
+  "version": "0.13.7-alpha.5",
   "description": "MCP server for accessing Mastra.ai documentation, changelogs, and news.",
   "type": "module",
   "main": "dist/index.js",
@@ -32,8 +32,8 @@
     "uuid": "^11.1.0",
     "zod": "^3.25.67",
     "zod-to-json-schema": "^3.24.5",
-    "@mastra/core": "0.12.0-alpha.3",
-    "@mastra/mcp": "^0.10.7"
+    "@mastra/core": "0.12.0-alpha.5",
+    "@mastra/mcp": "^0.10.8-alpha.0"
   },
   "devDependencies": {
     "@hono/node-server": "^1.17.1",
@@ -49,7 +49,7 @@
     "typescript": "^5.8.3",
     "vitest": "^3.2.4",
     "@internal/lint": "0.0.23",
-    "@mastra/core": "0.12.0-alpha.3"
+    "@mastra/core": "0.12.0-alpha.5"
   },
   "scripts": {
     "prepare-docs": "cross-env PREPARE=true node dist/prepare-docs/prepare.js",