@mastra/mcp-docs-server 1.2.4-alpha.1 → 1.2.4-alpha.6

package/.docs/reference/processors/prefill-error-handler.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # PrefillErrorHandler
 
 The `PrefillErrorHandler` is an **error processor** that handles assistant-response prefill errors. This error occurs when a conversation ends with an assistant message and the model rejects the request because it interprets it as prefilling the assistant response.
@@ -24,6 +26,7 @@ import { Agent } from '@mastra/core/agent'
 import { PrefillErrorHandler } from '@mastra/core/processors'
 
 export const agent = new Agent({
+  id: 'my-agent',
   name: 'my-agent',
   instructions: 'You are a helpful assistant.',
   model: 'anthropic/claude-opus-4-7',
@@ -45,6 +48,7 @@ const customErrorHandler: Processor = {
 }
 
 export const agent = new Agent({
+  id: 'my-agent',
   name: 'my-agent',
   instructions: 'You are a helpful assistant.',
   model: 'anthropic/claude-opus-4-7',

package/.docs/reference/processors/processor-interface.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # Processor interface
 
 The `Processor` interface defines the contract for all processors in Mastra. Processors can implement one or more methods to handle different stages of the agent execution pipeline.
@@ -726,7 +728,7 @@ Configure processors that implement `processAPIError` in `errorProcessors`:
 
 ```typescript
 const agent = new Agent({
-  // ...
+  id: 'agent',
   errorProcessors: [new PrefillErrorHandler()],
 })
 ```
@@ -987,6 +989,7 @@ import { Agent } from '@mastra/core/agent'
 import { PrefillErrorHandler } from '@mastra/core/processors'
 
 const agent = new Agent({
+  id: 'support-agent',
   name: 'support-agent',
   model: 'openai/gpt-5',
   instructions: '...',
@@ -1005,7 +1008,7 @@ Each array also accepts a function so processors can be built per-request from `
 
 ```typescript
 new Agent({
-  // ...
+  id: 'processor-interface-agent',
   inputProcessors: ({ requestContext }) => {
     const blockedWords = requestContext.get('blockedWords') ?? []
     return [new ContentFilter(blockedWords)]

package/.docs/reference/processors/prompt-injection-detector.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # PromptInjectionDetector
 
 The `PromptInjectionDetector` is an **input processor** that detects and prevents prompt injection attacks, jailbreaks, and system manipulation attempts before messages are sent to the language model. This processor helps maintain security by identifying various types of injection attempts and providing flexible strategies for handling them, including content rewriting to neutralize attacks while preserving legitimate user intent.
@@ -51,6 +53,7 @@ import { Agent } from '@mastra/core/agent'
 import { PromptInjectionDetector } from '@mastra/core/processors'
 
 export const agent = new Agent({
+  id: 'secure-agent',
   name: 'secure-agent',
   instructions: 'You are a helpful assistant',
   model: 'openai/gpt-5.5',

package/.docs/reference/processors/provider-history-compat.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # ProviderHistoryCompat
 
 The `ProviderHistoryCompat` processor handles provider-specific history incompatibilities. It can rewrite the outbound language model prompt before a provider call, or react to API errors and retry with repaired message history.
@@ -13,6 +15,7 @@ import { Agent } from '@mastra/core/agent'
 import { ProviderHistoryCompat } from '@mastra/core/processors'
 
 export const agent = new Agent({
+  id: 'my-agent',
   name: 'my-agent',
   instructions: 'You are a helpful assistant.',
   model: 'anthropic/claude-sonnet-4-5',
@@ -112,6 +115,7 @@ const stripUnsupportedAssistantMetadata: CompatRule = {
 }
 
 export const agent = new Agent({
+  id: 'custom-provider-agent',
   name: 'custom-provider-agent',
   instructions: 'You are a helpful assistant.',
   model: 'example-provider/model',

package/.docs/reference/processors/regex-filter-processor.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # RegexFilterProcessor
 
 The `RegexFilterProcessor` applies zero-cost regex pattern matching to filter, redact, or block content in agent messages. No LLM calls are made — all detection is regex-based.
@@ -48,6 +50,7 @@ import { Agent } from '@mastra/core/agent'
 import { RegexFilterProcessor } from '@mastra/core/processors'
 
 const agent = new Agent({
+  id: 'my-agent',
   name: 'my-agent',
   model: 'openai/gpt-5-nano',
   processors: {

package/.docs/reference/processors/response-cache.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # ResponseCache
 
 `ResponseCache` is an input processor that caches LLM responses on the request/response boundary inside the agentic loop. It hooks into `processLLMRequest` (cache lookup; short-circuits on hit) and `processLLMResponse` (cache write on completion).
@@ -16,6 +18,7 @@ import { ResponseCache } from '@mastra/core/processors'
 const cache = new InMemoryServerCache()
 
 const agent = new Agent({
+  id: 'search-agent',
   name: 'Search Agent',
   instructions: 'You answer questions concisely.',
   model: 'openai/gpt-5',

package/.docs/reference/processors/semantic-recall-processor.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # SemanticRecall
 
 The `SemanticRecall` is a **hybrid processor** that enables semantic search over conversation history using vector embeddings. On input, it performs semantic search to find relevant historical messages. On output, it creates embeddings for new messages to enable future semantic retrieval.
@@ -80,6 +82,7 @@ const semanticRecall = new SemanticRecall({
 })
 
 export const agent = new Agent({
+  id: 'semantic-memory-agent',
   name: 'semantic-memory-agent',
   instructions: 'You are a helpful assistant with semantic memory recall',
   model: 'openai/gpt-5.5',

package/.docs/reference/processors/skill-search-processor.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # SkillSearchProcessor
 
 The `SkillSearchProcessor` is an **input processor** that enables on-demand skill discovery and loading. Instead of injecting all skill metadata into the system prompt upfront (like `SkillsProcessor`), it gives the agent two meta-tools (`search_skills` and `load_skill`) that let it find and load skills on demand. This reduces context token usage when workspaces have many skills.
@@ -71,6 +73,7 @@ const skillSearch = new SkillSearchProcessor({
 })
 
 const agent = new Agent({
+  id: 'skill-agent',
   name: 'skill-agent',
   instructions:
     'You are a helpful assistant. Use search_skills to find relevant skills, then load_skill to load their instructions.',

package/.docs/reference/processors/stream-error-retry-processor.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # StreamErrorRetryProcessor
 
 `StreamErrorRetryProcessor` is an **error processor** that retries transient errors emitted after an LLM stream starts. It includes built-in matching for OpenAI Responses stream errors and supports additional matchers for other provider-specific stream error shapes.
@@ -13,6 +15,7 @@ import { Agent } from '@mastra/core/agent'
 import { StreamErrorRetryProcessor } from '@mastra/core/processors'
 
 export const agent = new Agent({
+  id: 'openai-agent',
   name: 'openai-agent',
   instructions: 'You are a helpful assistant.',
   model: 'openai/gpt-5',
@@ -49,6 +52,7 @@ const isECONNRESET = (error: unknown) => {
 }
 
 export const agent = new Agent({
+  id: 'resilient-agent',
   name: 'resilient-agent',
   instructions: 'You are a helpful assistant.',
   model: 'openai/gpt-5',

package/.docs/reference/processors/system-prompt-scrubber.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # SystemPromptScrubber
 
 The `SystemPromptScrubber` is an **output processor** that detects and handles system prompts, instructions, and other revealing information that could introduce security vulnerabilities. This processor helps maintain security by identifying various types of system prompts and providing flexible strategies for handling them, including multiple redaction methods to ensure sensitive information is properly sanitized.
@@ -55,6 +57,7 @@ import { Agent } from '@mastra/core/agent'
 import { BatchPartsProcessor, SystemPromptScrubber } from '@mastra/core/processors'
 
 export const agent = new Agent({
+  id: 'scrubbed-agent',
   name: 'scrubbed-agent',
   instructions: 'You are a helpful assistant',
   model: 'openai/gpt-5.5',

package/.docs/reference/processors/token-limiter-processor.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # TokenLimiterProcessor
 
 The `TokenLimiterProcessor` limits the number of tokens in messages. It can be used as an input, per-step input, and output processor:
@@ -79,6 +81,7 @@ import { Memory } from '@mastra/memory'
 import { TokenLimiterProcessor } from '@mastra/core/processors'
 
 export const agent = new Agent({
+  id: 'context-limited-agent',
   name: 'context-limited-agent',
   instructions: 'You are a helpful assistant',
   model: 'openai/gpt-5.5',
@@ -100,6 +103,7 @@ import { Agent } from '@mastra/core/agent'
 import { TokenLimiterProcessor } from '@mastra/core/processors'
 
 export const agent = new Agent({
+  id: 'multi-step-agent',
   name: 'multi-step-agent',
   instructions: 'You are a helpful research assistant with access to tools',
   model: 'openai/gpt-5.5',
@@ -123,6 +127,7 @@ import { Agent } from '@mastra/core/agent'
 import { TokenLimiterProcessor } from '@mastra/core/processors'
 
 export const agent = new Agent({
+  id: 'response-limited-agent',
   name: 'response-limited-agent',
   instructions: 'You are a helpful assistant',
   model: 'openai/gpt-5.5',

package/.docs/reference/processors/tool-call-filter.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # ToolCallFilter
 
 The `ToolCallFilter` is an **input processor** that filters out tool calls and their results from the message history before sending to the model. This is useful when you want to exclude specific tool interactions from context or remove all tool calls entirely.
@@ -88,6 +90,7 @@ import { Agent } from '@mastra/core/agent'
 import { ToolCallFilter } from '@mastra/core/processors'
 
 export const agent = new Agent({
+  id: 'filtered-agent',
   name: 'filtered-agent',
   instructions: 'You are a helpful assistant',
   model: 'openai/gpt-5.5',
@@ -113,6 +116,7 @@ import { Agent } from '@mastra/core/agent'
 import { ToolCallFilter } from '@mastra/core/processors'
 
 export const agent = new Agent({
+  id: 'no-tools-context-agent',
   name: 'no-tools-context-agent',
   instructions: 'You are a helpful assistant',
   model: 'openai/gpt-5.5',

package/.docs/reference/processors/tool-search-processor.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # ToolSearchProcessor
 
 The `ToolSearchProcessor` is an **input processor** that enables dynamic tool discovery and loading. Instead of providing all tools to the agent upfront, it gives the agent two meta-tools (`search_tools` and `load_tool`) that let it find and load tools on demand. This reduces context token usage when working with large tool libraries.
@@ -144,6 +146,7 @@ const toolSearch = new ToolSearchProcessor({
 })
 
 const agent = new Agent({
+  id: 'dynamic-tools-agent',
   name: 'dynamic-tools-agent',
   instructions:
     'You are a helpful assistant with access to many tools. Use search_tools to find relevant tools, then load_tool to make them available.',
@@ -225,6 +228,7 @@ import { Agent } from '@mastra/core/agent'
 import { ToolSearchProcessor, TokenLimiter } from '@mastra/core/processors'
 
 const agent = new Agent({
+  id: 'my-agent',
   name: 'my-agent',
   model: 'openai/gpt-5.5',
   inputProcessors: [

package/.docs/reference/processors/unicode-normalizer.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # UnicodeNormalizer
 
 The `UnicodeNormalizer` is an **input processor** that normalizes Unicode text to ensure consistent formatting and remove potentially problematic characters before messages are sent to the language model. This processor helps maintain text quality by handling various Unicode representations, removing control characters, and standardizing whitespace formatting.

package/.docs/reference/processors/working-memory-processor.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # WorkingMemory
 
 The `WorkingMemory` is an **input processor** that injects working memory data as a system message. It retrieves persistent information from storage and formats it as instructions for the LLM, enabling the agent to maintain context about users across conversations.
@@ -65,6 +67,7 @@ const storage = new PostgresStorage({
 })
 
 export const agent = new Agent({
+  id: 'personalized-agent',
   name: 'personalized-agent',
   instructions: 'You are a helpful assistant that remembers user preferences',
   model: 'openai/gpt-5.5',

package/.docs/reference/pubsub/base.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # PubSub
 
 `PubSub` is the abstract base class for Mastra's event system. It defines the contract that every pub/sub backend implements, so the rest of Mastra can publish and subscribe to events without knowing which transport is in use.

package/.docs/reference/pubsub/caching-pubsub.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # CachingPubSub
 
 `CachingPubSub` wraps any [`PubSub`](https://mastra.ai/reference/pubsub/base) implementation and adds event caching and replay. It records every published event per topic in a cache, so a subscriber that connects late or reconnects after a disconnect can replay the events it missed before continuing with live events.

package/.docs/reference/pubsub/event-emitter.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # EventEmitterPubSub
 
 `EventEmitterPubSub` is the default [`PubSub`](https://mastra.ai/reference/pubsub/base) implementation. It delivers events in-process using a Node.js [`EventEmitter`](https://nodejs.org/api/events.html#class-eventemitter), so it works without any external service.

package/.docs/reference/pubsub/google-cloud-pubsub.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # GoogleCloudPubSub
 
 `GoogleCloudPubSub` is a [`PubSub`](https://mastra.ai/reference/pubsub/base) implementation backed by [Google Cloud Pub/Sub](https://cloud.google.com/pubsub/docs). It delivers events across processes and hosts using Google Cloud topics and subscriptions, with ordered delivery and message acknowledgment.

package/.docs/reference/pubsub/lease-provider.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # LeaseProvider
 
 `LeaseProvider` is the distributed leasing contract, separate from event delivery ([`PubSub`](https://mastra.ai/reference/pubsub/base)). Mastra's [signals layer](https://mastra.ai/docs/agents/signals) uses it to elect a single owner across multiple processes (for example, serverless invocations) for a given resource, most commonly a thread key. The owner is the process that wakes and runs the agent stream, so other processes route follow-up work to it instead of starting a competing run.

package/.docs/reference/pubsub/redis-streams.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # RedisStreamsPubSub
 
 `RedisStreamsPubSub` is a [`PubSub`](https://mastra.ai/reference/pubsub/base) implementation backed by [Redis Streams](https://redis.io/docs/latest/develop/data-types/streams/). It delivers events across processes and hosts, with persistence, consumer groups, and redelivery on failure. It also implements [`LeaseProvider`](https://mastra.ai/reference/pubsub/lease-provider), so the signals layer can elect a single owner per resource across instances, which is what lets signals coordinate runs in distributed and serverless deployments.

package/.docs/reference/pubsub/unix-socket-pubsub.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # UnixSocketPubSub
 
 `UnixSocketPubSub` is a [`PubSub`](https://mastra.ai/reference/pubsub/base) implementation that delivers events across processes on a single host using a Unix domain socket. It elects one process as a broker, and other processes connect to it as clients. If the broker exits, the remaining clients elect a new broker automatically.

package/.docs/reference/rag/chunk.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # .chunk()
 
 The `.chunk()` function splits documents into smaller segments using various strategies and options.

package/.docs/reference/rag/database-config.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # DatabaseConfig
 
 The `DatabaseConfig` type allows you to specify database-specific configurations when using vector query tools. These configurations enable you to leverage unique features and optimizations offered by different vector stores.

package/.docs/reference/rag/document.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # MDocument
 
 The MDocument class processes documents for RAG applications. The main methods are `.chunk()` and `.extractMetadata()`.

package/.docs/reference/rag/embeddings.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # Embed
 
 Mastra uses the AI SDK's `embed` and `embedMany` functions to generate vector embeddings for text inputs, enabling similarity search and RAG workflows.

package/.docs/reference/rag/extract-params.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # ExtractParams
 
 ExtractParams configures metadata extraction from document chunks using LLM analysis.

package/.docs/reference/rag/graph-rag.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # GraphRAG
 
 The `GraphRAG` class implements a graph-based approach to retrieval augmented generation. It creates a knowledge graph from document chunks where nodes represent documents and edges represent semantic relationships, enabling both direct similarity matching and discovery of related content through graph traversal.

package/.docs/reference/rag/metadata-filters.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # Metadata filters
 
 Mastra provides a unified metadata filtering syntax across all vector stores, based on MongoDB/Sift query syntax. Each vector store translates these filters into their native format.

package/.docs/reference/rag/rerank.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # rerank()
 
 The `rerank()` function provides advanced reranking capabilities for vector search results by combining semantic relevance, vector similarity, and position-based scoring.

package/.docs/reference/rag/rerankWithScorer.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # rerankWithScorer()
 
 The `rerankWithScorer()` function provides advanced reranking capabilities for vector search results by combining semantic relevance, vector similarity, and position-based scoring.

package/.docs/reference/server/create-route.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # createRoute()
 
 The `createRoute()` function creates type-safe routes with Zod validation. When an `openapiPath` is configured on the server adapter, it generates OpenAPI schema entries from the supplied Zod schemas.

package/.docs/reference/server/express-adapter.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # Express adapter
 
 The `@mastra/express` package provides a server adapter for running Mastra with [Express](https://expressjs.com).

package/.docs/reference/server/fastify-adapter.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # Fastify adapter
 
 The `@mastra/fastify` package provides a server adapter for running Mastra with [Fastify](https://fastify.dev).

package/.docs/reference/server/hono-adapter.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # Hono adapter
 
 The `@mastra/hono` package provides a server adapter for running Mastra with [Hono](https://hono.dev).

package/.docs/reference/server/koa-adapter.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # Koa adapter
 
 The `@mastra/koa` package provides a server adapter for running Mastra with [Koa](https://koajs.com).

package/.docs/reference/server/mastra-server.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # MastraServer
 
 The `MastraServer` abstract class is the base for all server adapters. Extend this class to create adapters for frameworks other than Hono or Express.

package/.docs/reference/server/nestjs-adapter.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # NestJS Adapter
 
 The `@mastra/nestjs` package provides a NestJS module for running Mastra with the Express-based NestJS platform.

package/.docs/reference/server/register-api-route.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # registerApiRoute()
 
 The `registerApiRoute()` function creates custom HTTP routes that integrate with the Mastra server. Routes can include OpenAPI metadata to appear in the Swagger UI documentation.

package/.docs/reference/server/routes.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # Server routes
 
 Server adapters register these routes when you call `server.init()`. All routes are prefixed with the `prefix` option if configured.

package/.docs/reference/signals/create-notification-inbox-tool.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # createNotificationInboxTool()
 
 **Added in:** `@mastra/core@1.39.0`

package/.docs/reference/signals/signal-provider.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # SignalProvider
 
 **Added in:** `@mastra/core@1.39.0`
@@ -44,6 +46,7 @@ Register with an agent:
 import { Agent } from '@mastra/core/agent'
 
 const agent = new Agent({
+  id: 'agent',
   signals: [new SlackSignals()],
 })
 ```

package/.docs/reference/signals/task-signal-provider.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # TaskSignalProvider
 
 Bundles the built-in task tools (`task_write`, `task_update`, `task_complete`, `task_check`) and the `TaskStateProcessor` behind a single agent registration. Use it to add a structured, durable task list to an agent without wiring the tools and processor separately.
@@ -13,6 +15,7 @@ import { Agent } from '@mastra/core/agent'
 import { TaskSignalProvider } from '@mastra/core/signals'
 
 const agent = new Agent({
+  id: 'coder',
   name: 'coder',
   instructions: '...',
   model,

package/.docs/reference/signals/webhook-signal-provider.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # WebhookSignalProvider
 
 **Added in:** `@mastra/core@1.39.0`
@@ -30,6 +32,7 @@ Register with an agent and subscribe a thread:
 import { Agent } from '@mastra/core/agent'
 
 const agent = new Agent({
+  id: 'agent',
   signals: [webhookProvider],
 })
 

package/.docs/reference/storage/clickhouse.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # ClickHouse storage
 
 [ClickHouse](https://clickhouse.com/) is a columnar database designed for analytical workloads. The `@mastra/clickhouse` package provides storage adapters for several Mastra storage domains and is the recommended backend for production observability.

package/.docs/reference/storage/cloudflare-d1.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # Cloudflare D1 storage
 
 The Cloudflare D1 storage implementation provides a serverless SQL database solution using Cloudflare D1, supporting relational operations and transactional consistency.

package/.docs/reference/storage/cloudflare.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # Cloudflare storage
 
 Mastra provides two Cloudflare storage implementations:

package/.docs/reference/storage/composite.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # Composite storage
 
 `MastraCompositeStore` can compose storage domains from different providers. Use it when you need different databases for different purposes. For example, use LibSQL for memory and PostgreSQL for workflows.

package/.docs/reference/storage/convex.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # Convex storage
 
 The Convex storage implementation provides a serverless storage solution using [Convex](https://convex.dev), a full-stack TypeScript development platform with real-time sync and automatic caching.

package/.docs/reference/storage/dsql.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # Aurora DSQL Storage
 
 The Aurora DSQL storage implementation provides storage using Amazon Aurora DSQL with IAM authentication.

package/.docs/reference/storage/duckdb.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # DuckDB storage
 
 [DuckDB](https://duckdb.org/) is an embedded, in-process analytical database. The `@mastra/duckdb` package provides an OLAP-backed observability store for local development, suitable for traces, logs, metrics, scores, and feedback without running an external service.

package/.docs/reference/storage/dynamodb.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # DynamoDB storage
 
 The DynamoDB storage implementation provides a scalable and performant NoSQL database solution for Mastra, leveraging a single-table design pattern with [ElectroDB](https://electrodb.dev/).

package/.docs/reference/storage/lance.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # LanceDB storage
 
 The LanceDB storage implementation provides a high-performance storage solution using the LanceDB database system, which excels at handling both traditional data storage and vector operations.

package/.docs/reference/storage/libsql.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # libSQL storage
 
 [libSQL](https://docs.turso.tech/libsql) is an open-source, SQLite-compatible database that supports both local and remote deployments. It can be used to store message history, workflow snapshots, traces, and eval scores.

package/.docs/reference/storage/mongodb.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # MongoDB storage
 
 The MongoDB storage implementation provides a scalable storage solution using MongoDB databases with support for both document storage and vector operations.

package/.docs/reference/storage/mssql.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # MSSQL storage
 
 The MSSQL storage implementation provides a production-ready storage solution using Microsoft SQL Server databases.

package/.docs/reference/storage/overview.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # Storage overview
 
 Mastra storage is organized into domains. Each domain owns a set of tables or collections. Depending on your adapter and configuration, you may use all domains or only a subset.

package/.docs/reference/storage/postgresql.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # PostgreSQL storage
 
 The PostgreSQL storage implementation provides a production-ready storage solution using PostgreSQL databases.

package/.docs/reference/storage/redis.md

@@ -1,3 +1,5 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
 # Redis Storage
 
 The Redis storage implementation provides a high-performance storage solution using direct Redis connections via [`node-redis`](https://github.com/redis/node-redis) (the official Redis client for Node.js). It supports standalone Redis, and through custom client configuration, Redis Sentinel and Cluster deployments.