@mastra/mcp-docs-server 0.13.37 → 0.13.38

package/.docs/raw/observability/ai-tracing/processors/sensitive-data-filter.mdx

@@ -3,8 +3,6 @@ title: "Sensitive Data Filter | Processors | Observability | Mastra Docs"
 description: "Protect sensitive information in your AI traces with automatic data redaction"
 ---
 
-import { Callout } from "nextra/components";
-
 # Sensitive Data Filter
 
 The Sensitive Data Filter is a span processor that automatically redacts sensitive information from your AI traces before they're exported. This ensures that passwords, API keys, tokens, and other confidential data never leave your application or get stored in observability platforms.
@@ -13,7 +11,7 @@ The Sensitive Data Filter is a span processor that automatically redacts sensiti
 
 By default, the Sensitive Data Filter is automatically enabled when you use the standard Mastra configuration:
 
-```ts filename="src/mastra/index.ts" showLineNumbers copy
+```ts title="src/mastra/index.ts" showLineNumbers copy
 export const mastra = new Mastra({
   observability: {
     default: { enabled: true }, // Automatically includes SensitiveDataFilter
@@ -42,9 +40,11 @@ With the default configuration, the filter automatically redacts these common se
 - `refresh`
 - `ssn`
 
-<Callout>
+:::note
+
 Field matching is case-insensitive and normalizes separators. For example, `api-key`, `api_key`, and `Api Key` are all treated as `apikey`.
-</Callout>
+
+:::
 
 ## How It Works
 
@@ -62,30 +62,38 @@ When a sensitive field is detected, its value is replaced with `[REDACTED]` by d
 
 You can customize which fields are redacted and how redaction appears:
 
-```ts filename="src/mastra/index.ts" showLineNumbers copy
-import { SensitiveDataFilter, DefaultExporter } from '@mastra/core/ai-tracing';
+```ts title="src/mastra/index.ts" showLineNumbers copy
+import { SensitiveDataFilter, DefaultExporter } from "@mastra/core/ai-tracing";
 
 export const mastra = new Mastra({
   observability: {
     configs: {
       production: {
-        serviceName: 'my-service',
+        serviceName: "my-service",
         exporters: [new DefaultExporter()],
         processors: [
           new SensitiveDataFilter({
             // Add custom sensitive fields
             sensitiveFields: [
               // Default fields
-              'password', 'token', 'secret', 'key', 'apikey',
+              "password",
+              "token",
+              "secret",
+              "key",
+              "apikey",
               // Custom fields for your application
-              'creditCard', 'bankAccount', 'routingNumber',
-              'email', 'phoneNumber', 'dateOfBirth',
+              "creditCard",
+              "bankAccount",
+              "routingNumber",
+              "email",
+              "phoneNumber",
+              "dateOfBirth",
             ],
             // Custom redaction token
-            redactionToken: '***SENSITIVE***',
+            redactionToken: "***SENSITIVE***",
             // Redaction style
-            redactionStyle: 'full', // or 'partial'
-          })
+            redactionStyle: "full", // or 'partial'
+          }),
         ],
       },
     },
@@ -121,8 +129,8 @@ Shows the first and last 3 characters, useful for debugging without exposing ful
 
 ```ts
 new SensitiveDataFilter({
-  redactionStyle: 'partial'
-})
+  redactionStyle: "partial",
+});
 ```
 
 ```json
@@ -201,12 +209,12 @@ The Sensitive Data Filter is designed to be lightweight and efficient:
 
 If you need to disable sensitive data filtering (not recommended for production):
 
-```ts filename="src/mastra/index.ts" showLineNumbers copy
+```ts title="src/mastra/index.ts" showLineNumbers copy
 export const mastra = new Mastra({
   observability: {
     configs: {
       debug: {
-        serviceName: 'debug-service',
+        serviceName: "debug-service",
         processors: [], // No processors, including no SensitiveDataFilter
         exporters: [new DefaultExporter()],
       },
@@ -215,9 +223,11 @@ export const mastra = new Mastra({
 });
 ```
 
-<Callout type="warning">
+:::warning
+
 Only disable sensitive data filtering in controlled environments. Never disable it when sending traces to external services or shared storage.
-</Callout>
+
+:::
 
 ## Common Use Cases
 
@@ -227,13 +237,17 @@ Only disable sensitive data filtering in controlled environments. Never disable
 new SensitiveDataFilter({
   sensitiveFields: [
     // HIPAA-related fields
-    'ssn', 'socialSecurityNumber',
-    'medicalRecordNumber', 'mrn',
-    'healthInsuranceNumber',
-    'diagnosisCode', 'icd10',
-    'prescription', 'medication',
-  ]
-})
+    "ssn",
+    "socialSecurityNumber",
+    "medicalRecordNumber",
+    "mrn",
+    "healthInsuranceNumber",
+    "diagnosisCode",
+    "icd10",
+    "prescription",
+    "medication",
+  ],
+});
 ```
 
 ### Financial Services
@@ -242,13 +256,21 @@ new SensitiveDataFilter({
 new SensitiveDataFilter({
   sensitiveFields: [
     // PCI compliance fields
-    'creditCard', 'ccNumber', 'cardNumber',
-    'cvv', 'cvc', 'securityCode',
-    'expirationDate', 'expiry',
-    'bankAccount', 'accountNumber',
-    'routingNumber', 'iban', 'swift',
-  ]
-})
+    "creditCard",
+    "ccNumber",
+    "cardNumber",
+    "cvv",
+    "cvc",
+    "securityCode",
+    "expirationDate",
+    "expiry",
+    "bankAccount",
+    "accountNumber",
+    "routingNumber",
+    "iban",
+    "swift",
+  ],
+});
 ```
 
 ## Error Handling
@@ -270,5 +292,4 @@ This ensures that processing errors don't prevent traces from being exported or
 ## Related
 
 - [SensitiveDataFilter API](/reference/observability/ai-tracing/processors/sensitive-data-filter)
-- [Basic AI Tracing Example](/examples/observability/basic-ai-tracing) 
-
+- [Basic AI Tracing Example](/examples/observability/basic-ai-tracing)

package/.docs/raw/observability/logging.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Logging | Mastra Observability Documentation"
+title: "Logging | Observability | Mastra Docs"
 description: Learn how to use logging in Mastra to monitor execution, capture application behavior, and improve the accuracy of AI applications.
 ---
 
@@ -7,26 +7,26 @@ description: Learn how to use logging in Mastra to monitor execution, capture ap
 
 Mastra's logging system captures function execution, input data, and output responses in a structured format.
 
-When deploying to Mastra Cloud, logs are shown on the [Logs](../mastra-cloud/observability.mdx) page. In self-hosted or custom environments, logs can be directed to files or external services depending on the configured transports.
+When deploying to Mastra Cloud, logs are shown on the [Logs](../mastra-cloud/observability) page. In self-hosted or custom environments, logs can be directed to files or external services depending on the configured transports.
 
 ## PinoLogger
 
-When [initializing a new Mastra project](../getting-started/installation.mdx) using the CLI, `PinoLogger` is included by default.
+When [initializing a new Mastra project](../getting-started/installation) using the CLI, `PinoLogger` is included by default.
 
-```typescript filename="src/mastra/index.ts" showLineNumbers copy
-import { Mastra } from '@mastra/core/mastra';
-import { PinoLogger } from '@mastra/loggers';
+```typescript title="src/mastra/index.ts" showLineNumbers copy
+import { Mastra } from "@mastra/core/mastra";
+import { PinoLogger } from "@mastra/loggers";
 
 export const mastra = new Mastra({
   // ...
   logger: new PinoLogger({
-    name: 'Mastra',
-    level: 'info',
+    name: "Mastra",
+    level: "info",
   }),
 });
 ```
 
-> See the [PinoLogger](../../reference/observability/logger.mdx) API reference for all available configuration options.
+> See the [PinoLogger](/reference/observability/logging/pino-logger) API reference for all available configuration options.
 
 ## Logging from workflows and tools
 
@@ -36,8 +36,7 @@ Mastra provides access to a logger instance via the `mastra.getLogger()` method,
 
 Within a workflow step, access the logger via the `mastra` parameter inside the `execute` function. This allows you to log messages relevant to the step’s execution.
 
-
-```typescript {8-9} filename="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
+```typescript {8-9} title="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
 import { createWorkflow, createStep } from "@mastra/core/workflows";
 import { z } from "zod";
 
@@ -63,32 +62,30 @@ export const testWorkflow = createWorkflow({...})
 
 Similarly, tools have access to the logger instance via the `mastra` parameter. Use this to log tool specific activity during execution.
 
-```typescript {8-9} filename="src/mastra/tools/test-tool.ts" showLineNumbers copy
+```typescript {8-9} title="src/mastra/tools/test-tool.ts" showLineNumbers copy
 import { createTool } from "@mastra/core/tools";
 import { z } from "zod";
 
 export const testTool = createTool({
   // ...
   execute: async ({ mastra }) => {
-
     const logger = mastra?.getLogger();
     logger?.info("tool info log");
 
     return {
-      output: ""
+      output: "",
     };
-  }
+  },
 });
 ```
 
-
 ## Logging with additional data
 
 Logger methods accept an optional second argument for additional data. This can be any value, such as an object, string, or number.
 
 In this example, the log message includes an object with a key of `agent` and a value of the `testAgent` instance.
 
-```typescript {11} filename="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
+```typescript {11} title="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
 import { createWorkflow, createStep } from "@mastra/core/workflows";
 import { z } from "zod";
 

package/.docs/raw/observability/nextjs-tracing.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Next.js Tracing | Mastra Observability Documentation"
+title: "Next.js Tracing | Observability | Mastra Docs"
 description: "Set up OpenTelemetry tracing for Next.js applications"
 ---
 
@@ -11,7 +11,7 @@ Next.js requires additional configuration to enable OpenTelemetry tracing.
 
 Start by enabling the instrumentation hook in your Next.js config:
 
-```ts filename="next.config.ts" showLineNumbers copy
+```ts title="next.config.ts" showLineNumbers copy
 import type { NextConfig } from "next";
 
 const nextConfig: NextConfig = {
@@ -27,7 +27,7 @@ export default nextConfig;
 
 Configure your Mastra instance:
 
-```typescript filename="mastra.config.ts" copy
+```typescript title="mastra.config.ts" copy
 import { Mastra } from "@mastra/core";
 
 export const mastra = new Mastra({
@@ -55,7 +55,7 @@ npm install @opentelemetry/api langfuse-vercel
 
 2. Create an instrumentation file:
 
-```ts filename="instrumentation.ts" copy
+```ts title="instrumentation.ts" copy
 import {
   NodeSDK,
   ATTR_SERVICE_NAME,
@@ -91,7 +91,7 @@ npm install @opentelemetry/api @vercel/otel
 
 2. Create an instrumentation file at the root of your project (or in the src folder if using one):
 
-```ts filename="instrumentation.ts" copy
+```ts title="instrumentation.ts" copy
 import { registerOTel } from "@vercel/otel";
 
 export function register() {

package/.docs/raw/observability/otel-tracing.mdx

@@ -1,10 +1,8 @@
 ---
-title: "OTEL Tracing | Mastra Observability Documentation"
+title: "OTEL Tracing | Observability | Mastra Docs"
 description: "Set up OpenTelemetry tracing for Mastra applications"
 ---
 
-import Image from "next/image";
-
 # OTEL Tracing
 
 Mastra supports the OpenTelemetry Protocol (OTLP) for tracing and monitoring your application. When telemetry is enabled, Mastra automatically traces all core primitives including agent operations, LLM interactions, tool executions, integration calls, workflow runs, and database operations. Your telemetry data can then be exported to any OTEL collector.
@@ -13,7 +11,7 @@ Mastra supports the OpenTelemetry Protocol (OTLP) for tracing and monitoring you
 
 Here's a simple example of enabling telemetry:
 
-```ts filename="mastra.config.ts" showLineNumbers copy
+```ts title="mastra.config.ts" showLineNumbers copy
 export const mastra = new Mastra({
   // ... other config
   telemetry: {
@@ -60,20 +58,20 @@ type OtelConfig = {
 };
 ```
 
-See the [OtelConfig reference documentation](../../reference/observability/otel-config.mdx) for more details.
+See the inline type definition above for more details.
 
 ### Environment Variables
 
 You can configure the OTLP endpoint and headers through environment variables:
 
-```env filename=".env" copy
+```env title=".env" copy
 OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4318
 OTEL_EXPORTER_OTLP_HEADERS=x-api-key=your-api-key
 ```
 
 Then in your config:
 
-```ts filename="mastra.config.ts" showLineNumbers copy
+```ts title="mastra.config.ts" showLineNumbers copy
 export const mastra = new Mastra({
   // ... other config
   telemetry: {
@@ -92,7 +90,7 @@ export const mastra = new Mastra({
 Here's what a traced agent interaction looks like in [SigNoz](https://signoz.io):
 
 <img
-  src="/image/signoz-telemetry-demo.png"
+  src="/img/signoz-telemetry-demo.png"
   alt="Agent interaction trace showing spans, LLM calls, and tool executions"
   style={{ maxWidth: "800px", width: "100%", margin: "8px 0" }}
   className="nextra-image rounded-md"
@@ -103,7 +101,7 @@ Here's what a traced agent interaction looks like in [SigNoz](https://signoz.io)
 
 ### Other Supported Providers
 
-For a complete list of supported observability providers and their configuration details, see the [Observability Providers reference](../../reference/observability/providers/).
+Mastra supports any OTLP-compatible observability platform including Datadog, New Relic, Jaeger, and others. Configure them using the same OTLP endpoint pattern shown above.
 
 ### Custom Instrumentation files
 
@@ -112,20 +110,21 @@ You can define custom instrumentation files in your Mastra project by placing th
 #### Supported File Types
 
 Mastra looks for instrumentation files with these extensions:
+
 - `instrumentation.js`
-- `instrumentation.ts` 
+- `instrumentation.ts`
 - `instrumentation.mjs`
 
 #### Example
 
-```ts filename="/mastra/instrumentation.ts" showLineNumbers copy
-import { NodeSDK } from '@opentelemetry/sdk-node';
-import { getNodeAutoInstrumentations } from '@opentelemetry/auto-instrumentations-node';
-import { OTLPTraceExporter } from '@opentelemetry/exporter-trace-otlp-http';
+```ts title="/mastra/instrumentation.ts" showLineNumbers copy
+import { NodeSDK } from "@opentelemetry/sdk-node";
+import { getNodeAutoInstrumentations } from "@opentelemetry/auto-instrumentations-node";
+import { OTLPTraceExporter } from "@opentelemetry/exporter-trace-otlp-http";
 
 const sdk = new NodeSDK({
   traceExporter: new OTLPTraceExporter({
-    url: 'http://localhost:4318/v1/traces',
+    url: "http://localhost:4318/v1/traces",
   }),
   instrumentations: [getNodeAutoInstrumentations()],
 });
@@ -154,9 +153,9 @@ export const mastra = new Mastra({
 2. Create an instrumentation file in your project (e.g., `instrumentation.mjs`):
 
 ```typescript
-import { NodeSDK } from '@opentelemetry/sdk-node';
-import { getNodeAutoInstrumentations } from '@opentelemetry/auto-instrumentations-node';
-import { OTLPTraceExporter } from '@opentelemetry/exporter-trace-otlp-http';
+import { NodeSDK } from "@opentelemetry/sdk-node";
+import { getNodeAutoInstrumentations } from "@opentelemetry/auto-instrumentations-node";
+import { OTLPTraceExporter } from "@opentelemetry/exporter-trace-otlp-http";
 
 const sdk = new NodeSDK({
   traceExporter: new OTLPTraceExporter(),

package/.docs/raw/observability/overview.mdx

@@ -1,10 +1,8 @@
 ---
-title: "Overview | Observability | Mastra Docs"
+title: "Observability Overview | Observability | Mastra Docs"
 description: Monitor and debug applications with Mastra's Observability features.
 ---
 
-import { Callout } from "nextra/components";
-
 # Observability Overview
 
 Mastra provides comprehensive observability features designed specifically for AI applications. Monitor LLM operations, trace agent decisions, and debug complex workflows with specialized tools that understand AI-specific patterns.
@@ -12,19 +10,25 @@ Mastra provides comprehensive observability features designed specifically for A
 ## Key Features
 
 ### Structured Logging
+
 Debug applications with contextual logging:
+
 - **Context propagation**: Automatic correlation with traces
 - **Configurable levels**: Filter by severity in development and production
 
 ### AI Tracing
+
 Specialized tracing for AI operations that captures:
+
 - **LLM interactions**: Token usage, latency, prompts, and completions
 - **Agent execution**: Decision paths, tool calls, and memory operations
 - **Workflow steps**: Branching logic, parallel execution, and step outputs
 - **Automatic instrumentation**: Zero-configuration tracing with decorators
 
 ### OTEL Tracing
+
 Traditional distributed tracing with OpenTelemetry:
+
 - **Standard OTLP protocol**: Compatible with existing observability infrastructure
 - **HTTP and database instrumentation**: Automatic spans for common operations
 - **Provider integrations**: Datadog, New Relic, Jaeger, and other OTLP collectors
@@ -34,7 +38,7 @@ Traditional distributed tracing with OpenTelemetry:
 
 Configure Observability in your Mastra instance:
 
-```typescript filename="src/mastra/index.ts"
+```typescript title="src/mastra/index.ts"
 import { Mastra } from "@mastra/core";
 import { PinoLogger } from "@mastra/core";
 import { LibSqlStorage } from "@mastra/libsql";
@@ -50,17 +54,17 @@ export const mastra = new Mastra({
   }),
   telemetry: {
     enabled: true, // Enables OTEL Tracing
-  }
+  },
 });
 ```
 
 With this basic setup, you will see Traces and Logs in both the Playground and in Mastra Cloud.
 
-We also support various external tracing providers like Langfuse, Braintrust, and any OpenTelemetry-compatible platform (Datadog, New Relic, SigNoz, etc.). See more about this in the [AI Tracing](/docs/observability/ai-tracing.mdx) documentation.
+We also support various external tracing providers like Langfuse, Braintrust, and any OpenTelemetry-compatible platform (Datadog, New Relic, SigNoz, etc.). See more about this in the [AI Tracing](/docs/observability/ai-tracing/overview) documentation.
 
 ## What's Next?
 
-- **[Set up AI Tracing](/docs/observability/ai-tracing.mdx)**: Configure tracing for your application
-- **[Configure Logging](/docs/observability/logging.mdx)**: Add structured logging
-- **[View Examples](/examples/observability/basic-ai-tracing.mdx)**: See observability in action
-- **[API Reference](/reference/observability/ai-tracing/ai-tracing.mdx)**: Detailed configuration options
+- **[Set up AI Tracing](/docs/observability/ai-tracing/overview)**: Configure tracing for your application
+- **[Configure Logging](/docs/observability/logging)**: Add structured logging
+- **[View Examples](/examples/observability/basic-ai-tracing)**: See observability in action
+- **[API Reference](/reference/observability/ai-tracing/)**: Detailed configuration options

package/.docs/raw/rag/chunking-and-embedding.mdx

@@ -3,7 +3,7 @@ title: Chunking and Embedding Documents | RAG | Mastra Docs
 description: Guide on chunking and embedding documents in Mastra for efficient processing and retrieval.
 ---
 
-## Chunking and Embedding Documents
+# Chunking and Embedding Documents
 
 Before processing, create a MDocument instance from your content. You can initialize it from various formats:
 
@@ -69,7 +69,7 @@ const chunks = await doc.chunk({
 
 **Note:** Metadata extraction may use LLM calls, so ensure your API key is set.
 
-We go deeper into chunking strategies in our [chunk documentation](/reference/rag/chunk.mdx).
+We go deeper into chunking strategies in our [chunk documentation](/reference/rag/chunk).
 
 ## Step 2: Embedding Generation
 
@@ -83,7 +83,9 @@ The simplest way is to use Mastra's model router with `provider/model` strings:
 import { ModelRouterEmbeddingModel } from "@mastra/core";
 import { embedMany } from "ai";
 
-const embeddingModel = new ModelRouterEmbeddingModel("openai/text-embedding-3-small");
+const embeddingModel = new ModelRouterEmbeddingModel(
+  "openai/text-embedding-3-small",
+);
 
 const { embeddings } = await embedMany({
   model: embeddingModel,
@@ -92,6 +94,7 @@ const { embeddings } = await embedMany({
 ```
 
 Supported embedding models:
+
 - **OpenAI**: `text-embedding-3-small`, `text-embedding-3-large`, `text-embedding-ada-002`
 - **Google**: `gemini-embedding-001`, `text-embedding-004`
 
@@ -198,11 +201,10 @@ await vectorStore.upsert({
 
 For more examples of different chunking strategies and embedding configurations, see:
 
-- [Adjust Chunk Size](/reference/rag/chunk.mdx#adjust-chunk-size)
-- [Adjust Chunk Delimiters](/reference/rag/chunk.mdx#adjust-chunk-delimiters)
-- [Embed Text with Cohere](/reference/rag/embeddings.mdx#using-cohere)
+- [Chunk Reference](/reference/rag/chunk)
+- [Embeddings Reference](/reference/rag/embeddings)
 
 For more details on vector databases and embeddings, see:
 
-- [Vector Databases](./vector-databases.mdx)
-- [Embedding API Reference](/reference/rag/embeddings.mdx)
+- [Vector Databases](./vector-databases)
+- [Embedding API Reference](/reference/rag/embeddings)

package/.docs/raw/rag/overview.mdx

@@ -1,5 +1,5 @@
 ---
-title: RAG (Retrieval-Augmented Generation) in Mastra | Mastra Docs
+title: "RAG (Retrieval-Augmented Generation) in Mastra | RAG | Mastra Docs"
 description: Overview of Retrieval-Augmented Generation (RAG) in Mastra, detailing its capabilities for enhancing LLM outputs with relevant context.
 ---
 
@@ -64,11 +64,11 @@ This example shows the essentials: initialize a document, create chunks, generat
 
 ## Document Processing
 
-The basic building block of RAG is document processing. Documents can be chunked using various strategies (recursive, sliding window, etc.) and enriched with metadata. See the [chunking and embedding doc](./chunking-and-embedding.mdx).
+The basic building block of RAG is document processing. Documents can be chunked using various strategies (recursive, sliding window, etc.) and enriched with metadata. See the [chunking and embedding doc](./chunking-and-embedding).
 
 ## Vector Storage
 
-Mastra supports multiple vector stores for embedding persistence and similarity search, including pgvector, Pinecone, Qdrant, and MongoDB. See the [vector database doc](./vector-databases.mdx).
+Mastra supports multiple vector stores for embedding persistence and similarity search, including pgvector, Pinecone, Qdrant, and MongoDB. See the [vector database doc](./vector-databases).
 
 ## Observability and Debugging
 
@@ -79,9 +79,9 @@ Mastra's RAG system includes observability features to help you optimize your re
 - Analyze query patterns and cache hit rates
 - Export metrics to your observability platform
 
-See the [OTel Configuration](../../reference/observability/otel-config.mdx) page for more details.
+See the [OTEL Tracing](/docs/observability/otel-tracing) documentation for more details.
 
 ## More resources
 
-- [Chain of Thought RAG Example](../../examples/rag/usage/cot-rag.mdx)
+- [Chain of Thought RAG Example](/examples/rag/usage/cot-rag)
 - [All RAG Examples](../../examples/) (including different chunking strategies, embedding models, and vector stores)