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

package/.docs/docs/auth/fga.md

@@ -22,9 +22,9 @@ FGA is designed for multi-tenant B2B products where permissions are contextual:
 Configure FGA in your Mastra server config alongside authentication and RBAC:
 
 ```typescript
-import { Mastra } from '@mastra/core/mastra';
-import { MastraFGAPermissions } from '@mastra/core/auth/ee';
-import { MastraAuthWorkos, MastraFGAWorkos } from '@mastra/auth-workos';
+import { Mastra } from '@mastra/core/mastra'
+import { MastraFGAPermissions } from '@mastra/core/auth/ee'
+import { MastraAuthWorkos, MastraFGAWorkos } from '@mastra/auth-workos'
 
 const mastra = new Mastra({
   server: {
@@ -35,8 +35,8 @@ const mastra = new Mastra({
     }),
     fga: new MastraFGAWorkos({
       resourceMapping: {
-        agent: { fgaResourceType: 'team', deriveId: (ctx) => ctx.user.teamId },
-        workflow: { fgaResourceType: 'team', deriveId: (ctx) => ctx.user.teamId },
+        agent: { fgaResourceType: 'team', deriveId: ctx => ctx.user.teamId },
+        workflow: { fgaResourceType: 'team', deriveId: ctx => ctx.user.teamId },
         thread: { fgaResourceType: 'workspace-thread', deriveId: ({ resourceId }) => resourceId },
       },
       permissionMapping: {
@@ -50,7 +50,7 @@ const mastra = new Mastra({
       scope: true,
     },
   },
-});
+})
 ```
 
 When using `MastraFGAWorkos`, set `fetchMemberships: true` on `MastraAuthWorkos`. WorkOS FGA checks need the user's organization memberships to resolve the correct membership ID for authorization.
@@ -117,7 +117,7 @@ const mastra = new Mastra({
       scope: true,
     },
   },
-});
+})
 ```
 
 With `scope: true`, Mastra reads `MASTRA_RESOURCE_ID_KEY` from the request context. `mapUserToResourceId()` sets this value after authentication. Stored resource handlers persist the scope in record metadata and filter list, read, update, publish, and delete operations by that scope.
@@ -155,7 +155,7 @@ const fga = new MastraFGAWorkos({
   validatePermissions: async permissions => {
     // Throw if a Mastra permission is missing from permissionMapping.
   },
-});
+})
 ```
 
 Set `auditProtectedRoutes: 'error'` to fail startup when protected routes are missing built-in FGA metadata. If `requireForProtectedRoutes` is enabled, Mastra logs this audit as a warning by default.
@@ -163,7 +163,7 @@ Set `auditProtectedRoutes: 'error'` to fail startup when protected routes are mi
 For custom routes, prefer route-level `fga` metadata. This keeps authorization policy next to the route:
 
 ```typescript
-import { createRoute } from '@mastra/server/server-adapter';
+import { createRoute } from '@mastra/server/server-adapter'
 
 export const getProjectRoute = createRoute({
   method: 'GET',
@@ -176,15 +176,15 @@ export const getProjectRoute = createRoute({
     permission: 'projects:read',
   },
   handler: async () => {
-    return { project: null };
+    return { project: null }
   },
-});
+})
 ```
 
 Use `resolveRouteFGA()` only when route metadata must be derived centrally from route, params, or request context. A route map scales better than string-prefix checks:
 
 ```typescript
-import type { FGARouteConfig, FGARouteResolver } from '@mastra/core/auth/ee';
+import type { FGARouteConfig, FGARouteResolver } from '@mastra/core/auth/ee'
 
 const routeFGA = {
   'GET /billing/:accountId': {
@@ -192,14 +192,14 @@ const routeFGA = {
     resourceIdParam: 'accountId',
     permission: 'billing:read',
   },
-} satisfies Record<string, FGARouteConfig>;
+} satisfies Record<string, FGARouteConfig>
 
-const resolveRouteFGA: FGARouteResolver = ({ route }) => routeFGA[`${route.method} ${route.path}`];
+const resolveRouteFGA: FGARouteResolver = ({ route }) => routeFGA[`${route.method} ${route.path}`]
 
 const fga = new MastraFGAWorkos({
   /* ... */
   resolveRouteFGA,
-});
+})
 ```
 
 ## Enforcement points

package/.docs/docs/evals/custom-scorers.md

@@ -319,13 +319,12 @@ const customScorer = createScorer({
   id: 'recent-output',
   description: 'Scores only the last response',
   type: 'agent',
-  prepareRun: (run) => ({
+  prepareRun: run => ({
     ...run,
     output: run.output.slice(-1), // Keep only the last message
     requestContext: undefined,
   }),
-})
-.generateScore(({ run }) => {
+}).generateScore(({ run }) => {
   return run.output.length > 0 ? 1 : 0
 })
 ```

package/.docs/docs/evals/overview.md

@@ -80,35 +80,35 @@ export const evaluatedAgent = new Agent({
 You can also add scorers to individual workflow steps to evaluate outputs at specific points in your process. Each scorer receives that step's own input and output, so you can measure quality at each step instead of only scoring the final answer:
 
 ```typescript
-import { createWorkflow, createStep } from "@mastra/core/workflows";
-import { z } from "zod";
-import { customStepScorer } from "../scorers/custom-step-scorer";
+import { createWorkflow, createStep } from '@mastra/core/workflows'
+import { z } from 'zod'
+import { customStepScorer } from '../scorers/custom-step-scorer'
 
 const contentStep = createStep({
-  id: "content-step",
+  id: 'content-step',
   inputSchema: z.object({ topic: z.string() }),
   outputSchema: z.object({ content: z.string() }),
   scorers: {
     customStepScorer: {
       scorer: customStepScorer(),
       sampling: {
-        type: "ratio",
+        type: 'ratio',
         rate: 1, // Score every step execution
       },
     },
   },
   execute: async ({ inputData }) => {
-    return { content: await generateContent(inputData.topic) };
+    return { content: await generateContent(inputData.topic) }
   },
-});
+})
 
 export const contentWorkflow = createWorkflow({
-  id: "content-workflow",
+  id: 'content-workflow',
   inputSchema: z.object({ topic: z.string() }),
   outputSchema: z.object({ content: z.string() }),
 })
   .then(contentStep)
-  .commit();
+  .commit()
 ```
 
 For the step-level `scorers` API, see the [Step class reference](https://mastra.ai/reference/workflows/step).

package/.docs/docs/memory/semantic-recall.md

@@ -14,8 +14,6 @@ Semantic recall is RAG-based search that helps agents maintain context across lo
 
 It uses vector embeddings of messages for similarity search and integrates with vector stores, plus has configurable context windows around retrieved messages.
 
-![Diagram showing Mastra Memory semantic recall](/assets/images/semantic-recall-fd7b9336a6d0d18019216cb6d3dbe710.png)
-
 When it's enabled, new messages are used to query a vector DB for semantically similar messages.
 
 After getting a response from the LLM, all new messages (user, assistant, and tool calls/results) are inserted into the vector DB to be recalled in later interactions.

package/.docs/docs/observability/feedback.md

@@ -166,7 +166,7 @@ Feedback flows through the observability event bus, so exporters that support fe
 ## Related
 
 - [Observability overview](https://mastra.ai/docs/observability/overview)
-- [Tracing overview](https://mastra.ai/docs/observability/tracing/overview)
+- [Traces usage](https://mastra.ai/docs/observability/tracing/overview)
 - [Metrics overview](https://mastra.ai/docs/observability/metrics/overview)
 - [Client SDK observability reference](https://mastra.ai/reference/client-js/observability)
 - [Feedback reference](https://mastra.ai/reference/observability/feedback)

package/.docs/docs/observability/integrations/exporters/mastra-storage.md

@@ -248,7 +248,7 @@ new MastraStorageExporter({
 
 ## Related
 
-- [Tracing Overview](https://mastra.ai/docs/observability/tracing/overview)
+- [Traces usage](https://mastra.ai/docs/observability/tracing/overview)
 - [MastraPlatformExporter](https://mastra.ai/docs/mastra-platform/observability)
 - [Composite Storage](https://mastra.ai/reference/storage/composite): Combine multiple storage providers
 - [Storage Configuration](https://mastra.ai/docs/storage)

package/.docs/docs/observability/metrics/overview.md

@@ -104,5 +104,5 @@ In production, always include a timestamp range in metric queries. Time bounds l
 ## Related
 
 - [Observability overview](https://mastra.ai/docs/observability/overview)
-- [Tracing overview](https://mastra.ai/docs/observability/tracing/overview)
+- [Traces usage](https://mastra.ai/docs/observability/tracing/overview)
 - [MastraStorageExporter](https://mastra.ai/docs/observability/integrations/exporters/mastra-storage)

package/.docs/docs/observability/overview.md

@@ -4,14 +4,16 @@
 
 # Observability
 
-Mastra's observability system gives you visibility into every agent run, workflow step, tool call, and model interaction. Agent behavior depends on model responses, prompts, tools, memory, and workflow state, so observability helps you inspect runtime decisions from day one. It captures complementary signals that work together to help you understand what your application is doing and why.
+Mastra's observability system gives you visibility into every agent run, workflow step, tool call, and model interaction. Agent behavior depends on model responses, prompts, tools, memory, and workflow state, so observability helps you inspect runtime decisions from day one.
 
-- [**Configuration**](#configuration): Configure observability once for traces, logs, metrics, and feedback.
-- [**Storage**](#storage): Choose storage backends for persisted traces, logs, metrics aggregation, and feedback queries.
-- [**Tracing**](https://mastra.ai/docs/observability/tracing/overview): Records every operation as a hierarchical timeline of spans, capturing inputs, outputs, token usage, and timing.
-- [**Logging**](https://mastra.ai/docs/observability/logging): Forwards structured log entries from your application and Mastra internals to observability storage, correlated to traces automatically.
-- [**Metrics**](https://mastra.ai/docs/observability/metrics/overview): Extracts trace usage and cost data. No additional instrumentation is required.
-- [**Feedback**](https://mastra.ai/docs/observability/feedback): Stores ratings, comments, corrections, and other review signals linked to traces and spans.
+Start with the trace-correlated pages:
+
+- [**Usage**](https://mastra.ai/docs/observability/tracing/overview): Inspect the span hierarchy, inputs, outputs, token usage, timing, and trace context for an execution.
+- [**Logging**](https://mastra.ai/docs/observability/logging): Forward structured log entries from your application and Mastra internals, correlated to traces automatically.
+- [**Feedback**](https://mastra.ai/docs/observability/feedback): Store ratings, comments, corrections, and other review signals linked to traces and spans.
+- [**Storage**](#storage): Choose backends for persisted traces, logs, metrics aggregation, and feedback queries.
+
+Use [**Metrics**](https://mastra.ai/docs/observability/metrics/overview) to analyze aggregate usage, performance, and cost data derived from spans. No additional instrumentation is required. Use [**Configuration**](#configuration) to enable the signals and exporters your application needs.
 
 ## When to use observability
 
@@ -23,15 +25,15 @@ Mastra's observability system gives you visibility into every agent run, workflo
 
 ## How the pieces fit together
 
-Tracing is the foundation. When observability is configured, every agent run, workflow execution, tool call, and model interaction produces a [span](https://opentelemetry.io/docs/concepts/signals/traces/#spans). Spans are organized into traces that show the full request lifecycle as a hierarchical timeline.
+When observability is configured, every agent run, workflow execution, tool call, and model interaction produces a [span](https://opentelemetry.io/docs/concepts/signals/traces/#spans). Mastra organizes related spans into traces that show the full request lifecycle as a hierarchical timeline.
 
-Metrics are derived from traces automatically. When a span ends, Mastra extracts duration, token counts, and cost estimates without any extra code. These metrics power the dashboards in [Studio](https://mastra.ai/docs/studio/observability).
+When a span ends, Mastra extracts duration, token counts, and cost estimates without any extra code. These metrics power the aggregate dashboards in [Studio](https://mastra.ai/docs/studio/observability).
 
-Logs are correlated to traces automatically. Every `logger.info()`, `logger.warn()`, or `logger.error()` call within a traced context is tagged with the current trace and span IDs. You can move through from a log entry directly to the trace that produced it.
+Every `logger.info()`, `logger.warn()`, or `logger.error()` call within a traced context is tagged with the current trace and span IDs. You can move from a log entry directly to the trace that produced it.
 
 Feedback records human review signals such as ratings, comments, and corrections. Feedback can be linked to traces and spans, then queried with the same observability store used for metrics.
 
-These signals share correlation IDs such as trace ID, span ID, entity type, and entity name. You can use them to move from a metric spike to its traces, logs, and related feedback.
+These records share correlation fields such as trace ID, span ID, entity type, and entity name. You can use them to move from a metric spike to its traces, logs, and related feedback.
 
 ## Quickstart
 

package/.docs/docs/observability/tracing/overview.md

@@ -2,7 +2,7 @@
 
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Traces
+# Usage
 
 Tracing is the observability signal that records how a request moves through agents, workflows, tools, and model calls. Mastra represents each operation as a span and groups related spans into a trace so you can inspect the full execution path.
 
@@ -660,8 +660,8 @@ export const mastra = new Mastra({
       default: {
         serviceName: 'my-service',
         serializationOptions: {
-          maxStringLength: 2048, // Maximum length for string values (default: 1024)
-          maxDepth: 10, // Maximum depth for nested objects (default: 6)
+          maxStringLength: 2048, // Maximum length for string values (default: 131072)
+          maxDepth: 10, // Maximum depth for nested objects (default: 8)
           maxArrayLength: 100, // Maximum number of items in arrays (default: 50)
           maxObjectKeys: 75, // Maximum number of keys in objects (default: 50)
         },
@@ -674,12 +674,12 @@ export const mastra = new Mastra({
 
 ### Available options
 
-| Option            | Default | Description                                                      |
-| ----------------- | ------- | ---------------------------------------------------------------- |
-| `maxStringLength` | 1024    | Maximum length for string values. Longer strings are truncated.  |
-| `maxDepth`        | 6       | Maximum depth for nested objects. Deeper levels are omitted.     |
-| `maxArrayLength`  | 50      | Maximum number of items in arrays. Additional items are omitted. |
-| `maxObjectKeys`   | 50      | Maximum number of keys in objects. Additional keys are omitted.  |
+| Option            | Default         | Description                                                      |
+| ----------------- | --------------- | ---------------------------------------------------------------- |
+| `maxStringLength` | 131072 (128 KB) | Maximum length for string values. Longer strings are truncated.  |
+| `maxDepth`        | 8               | Maximum depth for nested objects. Deeper levels are omitted.     |
+| `maxArrayLength`  | 50              | Maximum number of items in arrays. Additional items are omitted. |
+| `maxObjectKeys`   | 50              | Maximum number of keys in objects. Additional keys are omitted.  |
 
 ### Use cases
 
@@ -687,9 +687,9 @@ export const mastra = new Mastra({
 
 ```ts
 serializationOptions: {
-  maxStringLength: 8192,  // Capture longer text content
-  maxDepth: 12,           // Handle deeply nested JSON responses
-  maxArrayLength: 200,    // Keep more items from large lists
+  maxStringLength: 262144, // Capture longer text content (256 KB)
+  maxDepth: 12,            // Handle deeply nested JSON responses
+  maxArrayLength: 200,     // Keep more items from large lists
 }
 ```
 

package/.docs/docs/studio/observability.md

@@ -102,7 +102,7 @@ Above the trace list, open **Columns** to show or hide input, entity, duration,
 
 Token and estimated cost columns require an observability store that supports metrics. These columns stay hidden in the **Branches** view because several branch rows can belong to the same trace.
 
-Tracing filters out low-level framework details so your traces stay focused and readable. Visit the [tracing overview](https://mastra.ai/docs/observability/tracing/overview) for more details.
+Tracing filters out low-level framework details so your traces stay focused and readable. Visit [Traces usage](https://mastra.ai/docs/observability/tracing/overview) for more details.
 
 To export a trace, select **Download trace JSON** in the trace panel header. This saves the entire trace as a `trace-<id>.json` file, with every span and its full input, output, metadata, and attributes. Use it to share a trace or attach it to a bug report, or alternatively build an evaluation dataset offline.
 
@@ -116,6 +116,6 @@ Log forwarding is enabled by default when you configure observability. See [logg
 
 - [Observability overview](https://mastra.ai/docs/observability/overview)
 - [Metrics overview](https://mastra.ai/docs/observability/metrics/overview)
-- [Tracing overview](https://mastra.ai/docs/observability/tracing/overview)
+- [Traces usage](https://mastra.ai/docs/observability/tracing/overview)
 - [Logging](https://mastra.ai/docs/observability/logging)
 - [Mastra platform observability](https://mastra.ai/docs/mastra-platform/observability)

package/.docs/docs/workflows/agents-and-tools.md

@@ -41,8 +41,6 @@ const step1 = createStep({
 
 Compose an agent as a step using `createStep()` when you don't need to modify the agent call. Use `.map()` to transform the previous step's output into a `prompt` the agent can use.
 
-![Agent as step](/assets/images/workflows-agent-tools-agent-step-b2f5be22552ce514f7f8cd785ffc5604.jpg)
-
 ```typescript
 import { testAgent } from '../agents/test-agent'
 const step1 = createStep(testAgent)
@@ -155,8 +153,6 @@ const step2 = createStep({
 
 Compose a tool as a step using `createStep()` when the previous step's output matches the tool's input context. You can use `.map()` to transform the previous step's output if they don't.
 
-![Tool as step](/assets/images/workflows-agent-tools-tool-step-cfd56227ce83c2d03a8c8d0496faeeef.jpg)
-
 ```typescript
 import { testTool } from '../tools/test-tool'
 

package/.docs/docs/workflows/control-flow.md

@@ -212,8 +212,6 @@ Visit [Choosing the right pattern](#choosing-the-right-pattern) to understand wh
 
 Use `.branch()` to choose which step to run based on a condition. All steps in a branch need the same `inputSchema` and `outputSchema` because branching requires consistent schemas so workflows can follow different paths.
 
-![Conditional branching with .branch()](/assets/images/workflows-control-flow-branch-1913ef107ba0198d73aa3c0a65145b7a.jpg)
-
 ```typescript
 const step1 = createStep({...})
 

package/.docs/models/gateways/netlify.md

@@ -4,7 +4,7 @@
 
 # Netlify
 
-Netlify AI Gateway provides unified access to multiple providers with built-in caching and observability. Access 233 models through Mastra's model router.
+Netlify AI Gateway provides unified access to multiple providers with built-in caching and observability. Access 234 models through Mastra's model router.
 
 Learn more in the [Netlify documentation](https://docs.netlify.com/build/ai-gateway/overview/).
 
@@ -132,6 +132,7 @@ ANTHROPIC_API_KEY=ant-...
 | `openrouter/deepseek/deepseek-v3.2-exp`                               |
 | `openrouter/deepseek/deepseek-v4-flash`                               |
 | `openrouter/deepseek/deepseek-v4-flash-0731`                          |
+| `openrouter/deepseek/deepseek-v4-flash-vision-exp`                    |
 | `openrouter/deepseek/deepseek-v4-pro`                                 |
 | `openrouter/deepseek/deepseek-v4-pro-0813`                            |
 | `openrouter/google/gemma-2-27b-it`                                    |

package/.docs/models/index.md

@@ -4,7 +4,7 @@
 
 # Model Providers
 
-Mastra provides a unified interface for working with LLMs across multiple providers, giving you access to 7044 models from 199 providers through a single API.
+Mastra provides a unified interface for working with LLMs across multiple providers, giving you access to 7046 models from 199 providers through a single API.
 
 ## Features
 

package/.docs/models/providers/crossmodel.md

@@ -4,7 +4,7 @@
 
 # ![CrossModel logo](https://models.dev/logos/crossmodel.svg)CrossModel
 
-Access 55 CrossModel models through Mastra's model router. Authentication is handled automatically using the `CROSSMODEL_API_KEY` environment variable.
+Access 56 CrossModel models through Mastra's model router. Authentication is handled automatically using the `CROSSMODEL_API_KEY` environment variable.
 
 Learn more in the [CrossModel documentation](https://www.crossmodel.ai/docs).
 
@@ -80,6 +80,7 @@ for await (const chunk of stream) {
 | `crossmodel/qwen/qwen3.8-flash`                    | 1.0M    |       |           |       |       |       | $0.13      | $0.43       |
 | `crossmodel/qwen/qwen3.8-max`                      | 1.0M    |       |           |       |       |       | $2         | $6          |
 | `crossmodel/tencent/hy3`                           | 262K    |       |           |       |       |       | $0.16      | $0.64       |
+| `crossmodel/tencent/hy4-preview`                   | 1.0M    |       |           |       |       |       | $0.96      | $3          |
 | `crossmodel/x-ai/grok-4.3`                         | 1.0M    |       |           |       |       |       | $1         | $3          |
 | `crossmodel/x-ai/grok-4.5`                         | 500K    |       |           |       |       |       | $2         | $6          |
 | `crossmodel/x-ai/grok-4.6`                         | 500K    |       |           |       |       |       | $2         | $6          |

package/.docs/models/providers/empiriolabs.md

@@ -4,7 +4,7 @@
 
 # ![EmpirioLabs AI logo](https://models.dev/logos/empiriolabs.svg)EmpirioLabs AI
 
-Access 57 EmpirioLabs AI models through Mastra's model router. Authentication is handled automatically using the `EMPIRIOLABS_API_KEY` environment variable.
+Access 56 EmpirioLabs AI models through Mastra's model router. Authentication is handled automatically using the `EMPIRIOLABS_API_KEY` environment variable.
 
 Learn more in the [EmpirioLabs AI documentation](https://docs.empiriolabs.ai).
 
@@ -62,7 +62,6 @@ for await (const chunk of stream) {
 | `empiriolabs/minimax-m2-7`             | 200K    |       |           |       |       |       | $0.15      | $0.60       |
 | `empiriolabs/minimax-m2-7-highspeed`   | 200K    |       |           |       |       |       | $0.30      | $1          |
 | `empiriolabs/minimax-m3`               | 1.0M    |       |           |       |       |       | $0.23      | $0.90       |
-| `empiriolabs/mistral-medium-3`         | 130K    |       |           |       |       |       | —          | —           |
 | `empiriolabs/mistral-small-4`          | 256K    |       |           |       |       |       | $0.15      | $0.60       |
 | `empiriolabs/muse-glimmer-30b`         | 131K    |       |           |       |       |       | $0.20      | $0.80       |
 | `empiriolabs/muse-spark-1-1`           | 1.0M    |       |           |       |       |       | $1         | $4          |

package/.docs/models/providers/kilo.md

@@ -158,7 +158,7 @@ for await (const chunk of stream) {
 | `kilo/meta-llama/llama-3.2-1b-instruct`                         | 60K     |       |           |       |       |       | $0.03      | $0.20       |
 | `kilo/meta-llama/llama-3.2-3b-instruct`                         | 131K    |       |           |       |       |       | $0.05      | $0.33       |
 | `kilo/meta-llama/llama-3.3-70b-instruct`                        | 128K    |       |           |       |       |       | $0.10      | $0.32       |
-| `kilo/meta-llama/llama-4-maverick`                              | 1.0M    |       |           |       |       |       | $0.20      | $0.70       |
+| `kilo/meta-llama/llama-4-maverick`                              | 128K    |       |           |       |       |       | $0.20      | $0.70       |
 | `kilo/meta-llama/llama-4-scout`                                 | 131K    |       |           |       |       |       | $0.10      | $0.30       |
 | `kilo/meta-llama/llama-guard-4-12b`                             | 164K    |       |           |       |       |       | $0.18      | $0.18       |
 | `kilo/meta/muse-glimmer-30b`                                    | 131K    |       |           |       |       |       | $0.30      | $1          |
@@ -365,7 +365,7 @@ for await (const chunk of stream) {
 | `kilo/tencent/hy-mt2-1.8b`                                      | 8K      |       |           |       |       |       | $0.04      | $0.18       |
 | `kilo/tencent/hy-mt2-30b-a3b`                                   | 8K      |       |           |       |       |       | $0.07      | $0.29       |
 | `kilo/tencent/hy-mt2-7b`                                        | 8K      |       |           |       |       |       | $0.07      | $0.29       |
-| `kilo/tencent/hy3`                                              | 262K    |       |           |       |       |       | $0.08      | $0.33       |
+| `kilo/tencent/hy3`                                              | 262K    |       |           |       |       |       | $0.14      | $0.58       |
 | `kilo/tencent/hy3-preview`                                      | 262K    |       |           |       |       |       | $0.18      | $0.60       |
 | `kilo/tencent/hy3:free`                                         | 262K    |       |           |       |       |       | —          | —           |
 | `kilo/tencent/hy4-preview`                                      | 1.0M    |       |           |       |       |       | $0.83      | $3          |

package/.docs/models/providers/nano-gpt.md

@@ -4,7 +4,7 @@
 
 # ![NanoGPT logo](https://models.dev/logos/nano-gpt.svg)NanoGPT
 
-Access 605 NanoGPT models through Mastra's model router. Authentication is handled automatically using the `NANO_GPT_API_KEY` environment variable.
+Access 606 NanoGPT models through Mastra's model router. Authentication is handled automatically using the `NANO_GPT_API_KEY` environment variable.
 
 Learn more in the [NanoGPT documentation](https://docs.nano-gpt.com).
 
@@ -544,6 +544,7 @@ for await (const chunk of stream) {
 | `nano-gpt/TEE/glm-5.1-thinking`                                  | 203K    |       |           |       |       |       | $2         | $5          |
 | `nano-gpt/TEE/glm-5.2`                                           | 1.0M    |       |           |       |       |       | $1         | $5          |
 | `nano-gpt/TEE/glm-5.2:thinking`                                  | 1.0M    |       |           |       |       |       | $1         | $5          |
+| `nano-gpt/TEE/glm-5.3`                                           | 1.0M    |       |           |       |       |       | $1         | $4          |
 | `nano-gpt/TEE/glm-5.3-flash`                                     | 1.0M    |       |           |       |       |       | $0.15      | $0.50       |
 | `nano-gpt/TEE/gpt-oss-120b`                                      | 131K    |       |           |       |       |       | $2         | $2          |
 | `nano-gpt/TEE/gpt-oss-20b`                                       | 131K    |       |           |       |       |       | $0.20      | $0.80       |

package/.docs/reference/observability/tracing/configuration.md

@@ -61,9 +61,9 @@ interface ObservabilityInstanceConfig {
 
 **serializationOptions** (`SerializationOptions`): Options for controlling serialization of span data (input/output/attributes)
 
-**serializationOptions.maxStringLength** (`number`): Maximum length for string values (default: 1024)
+**serializationOptions.maxStringLength** (`number`): Maximum length for string values (default: 131072)
 
-**serializationOptions.maxDepth** (`number`): Maximum depth for nested objects (default: 6)
+**serializationOptions.maxDepth** (`number`): Maximum depth for nested objects (default: 8)
 
 **serializationOptions.maxArrayLength** (`number`): Maximum number of items in arrays (default: 50)
 

package/.docs/reference/workflows/workflow-methods/agent.md

@@ -12,9 +12,9 @@ Unlike wrapping an agent with `createStep()`, `.agent()` records a declarative e
 
 ```typescript
 workflow
-  .map({ prompt: mapVariable({ initData: workflow, path: "topic" }) })
+  .map({ prompt: mapVariable({ initData: workflow, path: 'topic' }) })
   .agent(testAgent)
-  .commit();
+  .commit()
 ```
 
 ## Parameters
@@ -42,7 +42,7 @@ workflow
       }),
     },
   })
-  .commit();
+  .commit()
 ```
 
 ## Referencing an agent by ID
@@ -50,7 +50,7 @@ workflow
 Pass a string to reference a registered agent without importing it. The agent must be registered on the Mastra instance when the workflow runs:
 
 ```typescript
-workflow.agent("test-agent", { maxSteps: 3 }).commit();
+workflow.agent('test-agent', { maxSteps: 3 }).commit()
 ```
 
 ## Persisting agent steps

package/.docs/reference/workflows/workflow-methods/tool.md

@@ -11,7 +11,7 @@ Unlike wrapping a tool with `createStep()`, `.tool()` records a declarative entr
 ## Usage example
 
 ```typescript
-workflow.tool(testTool).commit();
+workflow.tool(testTool).commit()
 ```
 
 ## Parameters
@@ -31,7 +31,7 @@ workflow.tool(testTool).commit();
 Pass a string to reference a registered tool without importing it. The tool must be registered on the Mastra instance when the workflow runs:
 
 ```typescript
-workflow.tool("lookup-customer", { retries: 2 }).commit();
+workflow.tool('lookup-customer', { retries: 2 }).commit()
 ```
 
 ## Persisting tool steps

package/CHANGELOG.md

@@ -1,5 +1,12 @@
 # @mastra/mcp-docs-server
 
+## 1.2.23-alpha.4
+
+### Patch Changes
+
+- Updated dependencies [[`a3606a0`](https://github.com/mastra-ai/mastra/commit/a3606a09f3deaeef17caf04b9c6a0d7cd6b80fe6), [`4095752`](https://github.com/mastra-ai/mastra/commit/40957529233d202446ebecab1f59c76e99910230), [`a3606a0`](https://github.com/mastra-ai/mastra/commit/a3606a09f3deaeef17caf04b9c6a0d7cd6b80fe6)]:
+  - @mastra/core@1.63.3-alpha.1
+
 ## 1.2.23-alpha.0
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mastra/mcp-docs-server",
-  "version": "1.2.23-alpha.3",
+  "version": "1.2.23-alpha.5",
   "description": "MCP server for accessing Mastra.ai documentation, changelogs, and news.",
   "type": "module",
   "main": "dist/index.js",
@@ -28,7 +28,7 @@
     "jsdom": "^26.1.0",
     "local-pkg": "^1.1.2",
     "zod": "^4.4.3",
-    "@mastra/core": "1.63.3-alpha.0",
+    "@mastra/core": "1.63.3-alpha.1",
     "@mastra/mcp": "^1.17.2"
   },
   "devDependencies": {
@@ -45,9 +45,9 @@
     "tsx": "^4.23.1",
     "typescript": "^7.0.2",
     "vitest": "4.1.10",
-    "@mastra/core": "1.63.3-alpha.0",
+    "@internal/types-builder": "0.0.104",
     "@internal/lint": "0.0.129",
-    "@internal/types-builder": "0.0.104"
+    "@mastra/core": "1.63.3-alpha.1"
   },
   "homepage": "https://mastra.ai",
   "repository": {