@mastra/mcp-docs-server 1.1.8 → 1.1.9-alpha.1

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

@@ -1,8 +1,8 @@
-# Metadata Filters
+# 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.
 
-## Basic Example
+## Basic example
 
 ```typescript
 import { PgVector } from '@mastra/pg'
@@ -24,7 +24,7 @@ const results = await store.query({
 })
 ```
 
-## Supported Operators
+## Supported operators
 
 ### Basic Comparison
 
@@ -46,9 +46,9 @@ const results = await store.query({
 
 `$contains`Text contains substring{ description: { $contains: "sale" } }Supported by: Upstash, libSQL, PgVector`$regex`Regular expression match{ name: { $regex: "^test" } }Supported by: Qdrant, PgVector, Upstash, MongoDB`$size`Array length check{ tags: { $size: { $gt: 2 } } }Supported by: Astra, libSQL, PgVector, MongoDB`$geo`Geospatial query{ location: { $geo: { type: "radius", ... } } }Supported by: Qdrant`$datetime`Datetime range query{ created: { $datetime: { range: { gt: "2024-01-01" } } } }Supported by: Qdrant`$hasId`Vector ID existence check{ $hasId: \["id1", "id2"] }Supported by: Qdrant`$hasVector`Vector existence check{ $hasVector: true }Supported by: Qdrant
 
-## Common Rules and Restrictions
+## Common rules and restrictions
 
-1. Field names cannot:
+1. Field names can't:
 
    - Contain dots (.) unless referring to nested fields
    - Start with $ or contain null characters
@@ -63,11 +63,11 @@ const results = await store.query({
 3. Logical operators:
 
    - Must contain valid conditions
-   - Cannot be empty
+   - Can't be empty
    - Must be properly nested
    - Can only be used at top level or nested within other logical operators
-   - Cannot be used at field level or nested inside a field
-   - Cannot be used inside an operator
+   - Can't be used at field level or nested inside a field
+   - Can't be used inside an operator
    - Valid: `{ "$and": [{ "field": { "$gt": 100 } }] }`
    - Valid: `{ "$or": [{ "$and": [{ "field": { "$gt": 100 } }] }] }`
    - Invalid: `{ "field": { "$and": [{ "$gt": 100 }] } }`
@@ -76,7 +76,7 @@ const results = await store.query({
 4. $not operator:
 
    - Must be an object
-   - Cannot be empty
+   - Can't be empty
    - Can be used at field level or top level
    - Valid: `{ "$not": { "field": "value" } }`
    - Valid: `{ "field": { "$not": { "$eq": "value" } } }`
@@ -87,7 +87,7 @@ const results = await store.query({
    - Valid: `{ "$and": [{ "field": { "$gt": 100 } }] }`
    - Invalid: `{ "$and": [{ "$gt": 100 }] }`
 
-## Store-Specific Notes
+## Store-specific notes
 
 ### Astra
 
@@ -98,7 +98,7 @@ const results = await store.query({
 ### ChromaDB
 
 - Where filters only return results where the filtered field exists in metadata
-- Empty metadata fields are not included in filter results
+- Empty metadata fields aren't included in filter results
 - Metadata fields must be present for negative matches (e.g., $ne won't match documents missing the field)
 
 ### Cloudflare Vectorize
@@ -109,7 +109,7 @@ const results = await store.query({
 - String values are indexed up to first 64 bytes (truncated on UTF-8 boundaries)
 - Number values use float64 precision
 - Filter JSON must be under 2048 bytes
-- Field names cannot contain dots (.) or start with $
+- Field names can't contain dots (.) or start with $
 - Field names limited to 512 characters
 - Vectors must be re-upserted after creating new metadata indexes to be included in filtered results
 - Range queries may have reduced accuracy with very large datasets (\~10M+ vectors)
@@ -186,12 +186,12 @@ const results = await store.query({
 
 ### Couchbase
 
-- Currently does not have support for metadata filters. Filtering must be done client-side after retrieving results or by using the Couchbase SDK's Search capabilities directly for more complex queries.
+- Currently doesn't have support for metadata filters. Filtering must be done client-side after retrieving results or by using the Couchbase SDK's Search capabilities directly for more complex queries.
 
 ### Amazon S3 Vectors
 
-- Equality values must be primitives (string/number/boolean). `null`/`undefined`, arrays, objects, and Date are not allowed for equality. Range operators accept numbers or Date (Dates are normalized to epoch ms).
-- `$in`/`$nin` require **non-empty arrays of primitives**; Date elements are allowed and normalized to epoch ms. **Array equality** is not supported.
+- Equality values must be primitives (string/number/boolean). `null`/`undefined`, arrays, objects, and Date aren't allowed for equality. Range operators accept numbers or Date (Dates are normalized to epoch ms).
+- `$in`/`$nin` require **non-empty arrays of primitives**; Date elements are allowed and normalized to epoch ms. **Array equality** isn't supported.
 - Implicit AND is canonicalized (`{a:1,b:2}` → `{$and:[{a:1},{b:2}]}`). Logical operators must contain field conditions, use non-empty arrays, and appear only at the root or within other logical operators (not inside field values).
 - Keys listed in `nonFilterableMetadataKeys` at index creation are stored but not filterable; this setting is immutable.
 - $exists requires a boolean value.

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

@@ -11,7 +11,7 @@ function rerank(
 ): Promise<RerankResult[]>
 ```
 
-## Usage Example
+## Usage example
 
 ```typescript
 import { rerank } from '@mastra/rag'
@@ -64,7 +64,7 @@ The function returns an array of `RerankResult` objects:
 
 **details** (`ScoringDetails`): Detailed scoring information
 
-### ScoringDetails
+### `ScoringDetails`
 
 **semantic** (`number`): Semantic relevance score (0-1)
 

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

@@ -11,7 +11,7 @@ function rerankWithScorer({
 }): Promise<RerankResult[]>;
 ```
 
-## Usage Example
+## Usage example
 
 ```typescript
 import { rerankWithScorer as rerank, CohereRelevanceScorer } from '@mastra/rag'
@@ -69,7 +69,7 @@ The function returns an array of `RerankResult` objects:
 
 **details** (`ScoringDetails`): Detailed scoring information
 
-### ScoringDetails
+### `ScoringDetails`
 
 **semantic** (`number`): Semantic relevance score (0-1)
 

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

@@ -46,6 +46,8 @@ function createRoute<TPath, TQuery, TBody, TResponse, TResponseType>(
 
 **deprecated** (`boolean`): Mark route as deprecated
 
+**onValidationError** (`(error: ZodError, context: 'query' | 'body' | 'path') => { status: number; body: unknown } | undefined`): Custom validation error handler for this route. Overrides the server-level \`onValidationError\` hook. Return \`{ status, body }\` to customize the response, or \`undefined\` to use the default.
+
 ## Handler parameters
 
 The handler receives validated parameters plus runtime context:

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

@@ -1,4 +1,4 @@
-# Express Adapter
+# 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,4 +1,4 @@
-# Fastify Adapter
+# 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,4 +1,4 @@
-# Hono Adapter
+# 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,4 +1,4 @@
-# Koa Adapter
+# Koa adapter
 
 The `@mastra/koa` package provides a server adapter for running Mastra with [Koa](https://koajs.com).
 
@@ -97,7 +97,7 @@ const server = new MastraServer({ app, mastra })
 await server.init()
 ```
 
-The [`server.onError`](https://mastra.ai/reference/configuration) hook is also supported. When configured, it is called before the error propagates to middleware, and its response is used directly:
+The [`server.onError`](https://mastra.ai/reference/configuration) hook is also supported. When configured, it's called before the error propagates to middleware, and its response is used directly:
 
 ```typescript
 const mastra = new Mastra({

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

@@ -52,7 +52,7 @@ constructor(options: MastraServerOptions<TApp>)
 
 These methods must be implemented by adapters:
 
-### registerContextMiddleware()
+### `registerContextMiddleware()`
 
 Attach Mastra context to every request.
 
@@ -67,7 +67,7 @@ abstract registerContextMiddleware(): void
 - `tools` - Available tools
 - `abortSignal` - Request cancellation signal
 
-### registerAuthMiddleware()
+### `registerAuthMiddleware()`
 
 Register authentication and authorization middleware.
 
@@ -75,7 +75,7 @@ Register authentication and authorization middleware.
 abstract registerAuthMiddleware(): void
 ```
 
-### registerRoute()
+### `registerRoute()`
 
 Register a single route with the framework.
 
@@ -87,7 +87,7 @@ abstract registerRoute(
 ): Promise<void>
 ```
 
-### getParams()
+### `getParams()`
 
 Extract parameters from the request.
 
@@ -102,7 +102,7 @@ abstract getParams(
 }>
 ```
 
-### sendResponse()
+### `sendResponse()`
 
 Send response based on route type.
 
@@ -114,7 +114,7 @@ abstract sendResponse(
 ): Promise<unknown>
 ```
 
-### stream()
+### `stream()`
 
 Handle streaming responses.
 
@@ -128,7 +128,7 @@ abstract stream(
 
 ## Instance methods
 
-### init()
+### `init()`
 
 Initialize the server by registering all middleware and routes.
 
@@ -142,7 +142,7 @@ Calls in order:
 2. `registerAuthMiddleware()`
 3. `registerRoutes()`
 
-### registerRoutes()
+### `registerRoutes()`
 
 Register all Mastra routes.
 
@@ -150,7 +150,7 @@ Register all Mastra routes.
 async registerRoutes(): Promise<void>
 ```
 
-### getApp()
+### `getApp()`
 
 Get the framework app instance.
 
@@ -158,7 +158,7 @@ Get the framework app instance.
 getApp<T = TApp>(): T
 ```
 
-### parsePathParams()
+### `parsePathParams()`
 
 Validate path parameters with the route's Zod schema.
 
@@ -169,7 +169,7 @@ async parsePathParams(
 ): Promise<Record<string, unknown>>
 ```
 
-### parseQueryParams()
+### `parseQueryParams()`
 
 Validate query parameters with the route's Zod schema.
 
@@ -180,7 +180,7 @@ async parseQueryParams(
 ): Promise<Record<string, unknown>>
 ```
 
-### parseBody()
+### `parseBody()`
 
 Validate request body with the route's Zod schema.
 
@@ -191,7 +191,7 @@ async parseBody(
 ): Promise<unknown>
 ```
 
-### registerOpenAPIRoute()
+### `registerOpenAPIRoute()`
 
 Register an endpoint that serves the OpenAPI specification.
 
@@ -205,7 +205,7 @@ async registerOpenAPIRoute(
 
 ## Protected methods
 
-### mergeRequestContext()
+### `mergeRequestContext()`
 
 Merge request context from multiple sources (query params and body).
 
@@ -218,7 +218,7 @@ protected mergeRequestContext(options: {
 
 ## Types
 
-### BodyLimitOptions
+### `BodyLimitOptions`
 
 ```typescript
 interface BodyLimitOptions {
@@ -227,7 +227,7 @@ interface BodyLimitOptions {
 }
 ```
 
-### StreamOptions
+### `StreamOptions`
 
 ```typescript
 interface StreamOptions {

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

@@ -18,7 +18,7 @@ The URL path for the route. Supports path parameters using `:param` syntax.
 registerApiRoute("/items/:itemId", { ... })
 ```
 
-**Note:** Paths cannot start with `/api/` as this prefix is reserved for Mastra server routes.
+**Note:** Paths can't start with `/api/` as this prefix is reserved for Mastra server routes.
 
 ### options
 
@@ -32,9 +32,9 @@ registerApiRoute("/items/:itemId", { ... })
 
 **openapi** (`DescribeRouteOptions`): OpenAPI metadata for Swagger UI documentation
 
-## OpenAPI Options
+## OpenAPI options
 
-The `openapi` property accepts standard OpenAPI 3.1 operation fields from [hono-openapi](https://github.com/honojs/middleware/tree/main/packages/openapi). Routes without an `openapi` property are not included in Swagger UI.
+The `openapi` property accepts standard OpenAPI 3.1 operation fields from [hono-openapi](https://github.com/honojs/middleware/tree/main/packages/openapi). Routes without an `openapi` property aren't included in Swagger UI.
 
 **summary** (`string`): Short summary of the operation
 
@@ -52,11 +52,11 @@ The `openapi` property accepts standard OpenAPI 3.1 operation fields from [hono-
 
 **security** (`SecurityRequirementObject[]`): Security requirements for the operation
 
-## Return Value
+## Return value
 
 Returns an `ApiRoute` object to be passed to `server.apiRoutes` in the Mastra configuration.
 
-## Handler Context
+## Handler context
 
 The handler receives a Hono `Context` object with access to:
 
@@ -201,7 +201,7 @@ registerApiRoute('/items/:itemId', {
 })
 ```
 
-### Using createHandler
+### Using `createHandler()`
 
 For routes that need async initialization:
 
@@ -219,7 +219,7 @@ registerApiRoute('/dynamic', {
 })
 ```
 
-## Error Handling
+## Error handling
 
 Throw errors with status codes using Hono's `HTTPException`:
 

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

@@ -1,4 +1,4 @@
-# Server Routes
+# 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/storage/cloudflare-d1.md

@@ -1,8 +1,8 @@
-# Cloudflare D1 Storage
+# Cloudflare D1 storage
 
 The Cloudflare D1 storage implementation provides a serverless SQL database solution using Cloudflare D1, supporting relational operations and transactional consistency.
 
-> **Observability Not Supported:** Cloudflare D1 storage **does not support the observability domain**. Traces from the `DefaultExporter` cannot be persisted to D1, and Mastra Studio's observability features won't work with D1 as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
+> **Observability Not Supported:** Cloudflare D1 storage **doesn't support the observability domain**. Traces from the `DefaultExporter` can't be persisted to D1, and Mastra Studio's observability features won't work with D1 as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
 
 > **Row Size Limit:** Cloudflare D1 enforces a **1 MiB maximum row size**. This limit can be exceeded when storing messages with base64-encoded attachments such as images. See [Handling large attachments](https://mastra.ai/docs/memory/storage) for workarounds including uploading attachments to external storage.
 
@@ -85,7 +85,7 @@ export default {
 > - The **property name** (`D1Database`) must match the `binding` name in your `wrangler.toml`
 > - The **type** (`: D1Database`) is from `@cloudflare/workers-types` for TypeScript type checking
 >
-> At runtime, Cloudflare Workers provides the actual D1 database instance via `env.D1Database`. You cannot use `D1Database` directly outside of the worker's context.
+> At runtime, Cloudflare Workers provides the actual D1 database instance via `env.D1Database`. You can't use `D1Database` directly outside of the worker's context.
 
 ### Using with REST API
 
@@ -139,7 +139,7 @@ Or in `wrangler.jsonc`:
 
 **tablePrefix** (`string`): Optional prefix for all table names (useful for environment isolation)
 
-## Additional Notes
+## Additional notes
 
 ### Schema Management
 
@@ -207,7 +207,7 @@ export default {
 }
 ```
 
-> **Warning:** If `init()` is not called, tables won't be created and storage operations will fail silently or throw errors.
+> **Warning:** If `init()` isn't called, tables won't be created and storage operations will fail silently or throw errors.
 
 ### Transactions & Consistency
 

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

@@ -1,8 +1,8 @@
-# Cloudflare Storage
+# Cloudflare storage
 
 The Cloudflare KV storage implementation provides a globally distributed, serverless key-value store solution using Cloudflare Workers KV.
 
-> **Observability Not Supported:** Cloudflare KV storage **does not support the observability domain**. Traces from the `DefaultExporter` cannot be persisted to KV, and Mastra Studio's observability features won't work with Cloudflare KV as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
+> **Observability Not Supported:** Cloudflare KV storage **doesn't support the observability domain**. Traces from the `DefaultExporter` can't be persisted to KV, and Mastra Studio's observability features won't work with Cloudflare KV as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
 
 ## Installation
 
@@ -69,7 +69,7 @@ const storageRest = new CloudflareStore({
 
 **keyPrefix** (`string`): Optional prefix for all keys (useful for environment isolation)
 
-### Additional Notes
+### Additional notes
 
 ### Schema Management
 

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

@@ -1,4 +1,4 @@
-# Composite Storage
+# 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,8 +1,8 @@
-# Convex Storage
+# 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.
 
-> **Observability Not Supported:** Convex storage **does not support the observability domain**. Traces from the `DefaultExporter` cannot be persisted to Convex, and Mastra Studio's observability features won't work with Convex as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
+> **Observability Not Supported:** Convex storage **doesn't support the observability domain**. Traces from the `DefaultExporter` can't be persisted to Convex, and Mastra Studio's observability features won't work with Convex as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
 
 > **Record Size Limit:** Convex enforces a **1 MiB maximum record size**. This limit can be exceeded when storing messages with base64-encoded attachments such as images. See [Handling large attachments](https://mastra.ai/docs/memory/storage) for workarounds including uploading attachments to external storage like S3, Cloudflare R2, or [Convex file storage](https://docs.convex.dev/file-storage).
 
@@ -32,7 +32,7 @@ yarn add @mastra/convex@latest
 bun add @mastra/convex@latest
 ```
 
-## Convex Setup
+## Convex setup
 
 Before using `ConvexStore`, you need to set up the Convex schema and storage handler in your Convex project.
 
@@ -103,7 +103,7 @@ const storage = new ConvexStore({
 
 **storageFunction** (`string`): Path to the storage mutation function (default: 'mastra/storage:handle') (Default: `mastra/storage:handle`)
 
-## Constructor Examples
+## Constructor examples
 
 ```ts
 import { ConvexStore } from '@mastra/convex'
@@ -124,7 +124,7 @@ const storeCustom = new ConvexStore({
 })
 ```
 
-## Additional Notes
+## Additional notes
 
 ### Schema Management
 
@@ -148,7 +148,7 @@ All typed tables include:
 
 This design ensures compatibility with Mastra's storage contract while leveraging Convex's automatic indexing and real-time capabilities.
 
-### Environment Variables
+### Environment variables
 
 Set these environment variables for your deployment:
 

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

@@ -1,8 +1,8 @@
-# DynamoDB Storage
+# 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/).
 
-> **Observability Not Supported:** DynamoDB storage **does not support the observability domain**. Traces from the `DefaultExporter` cannot be persisted to DynamoDB, and Mastra Studio's observability features won't work with DynamoDB as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
+> **Observability Not Supported:** DynamoDB storage **doesn't support the observability domain**. Traces from the `DefaultExporter` can't be persisted to DynamoDB, and Mastra Studio's observability features won't work with DynamoDB as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
 
 > **Item Size Limit:** DynamoDB enforces a **400 KB maximum item size**. This limit can be exceeded when storing messages with base64-encoded attachments such as images. See [Handling large attachments](https://mastra.ai/docs/memory/storage) for workarounds including uploading attachments to external storage.
 
@@ -120,7 +120,7 @@ For local development, you can use [DynamoDB Local](https://docs.aws.amazon.com/
 
 **config.ttl** (`object`): TTL (Time To Live) configuration for automatic data expiration. Configure per entity type: thread, message, trace, eval, workflow\_snapshot, resource, score. Each entity config includes: enabled (boolean), attributeName (string, default: 'ttl'), defaultTtlSeconds (number).
 
-## TTL (Time To Live) Configuration
+## TTL (time to live) configuration
 
 DynamoDB TTL allows you to automatically delete items after a specified time period. This is useful for:
 
@@ -211,12 +211,12 @@ aws dynamodb update-time-to-live \
 1. Go to the DynamoDB console
 2. Select your table
 3. Go to "Additional settings" tab
-4. Under "Time to Live (TTL)", click "Manage TTL"
+4. Under "Time to Live (TTL)", select "Manage TTL"
 5. Enable TTL and specify the attribute name (default: `ttl`)
 
 > **Note:** DynamoDB deletes expired items within 48 hours after expiration. Items remain queryable until actually deleted.
 
-## AWS IAM Permissions
+## AWS IAM permissions
 
 The IAM role or user executing the code needs appropriate permissions to interact with the specified DynamoDB table and its indexes. Below is a sample policy. Replace `${YOUR_TABLE_NAME}` with your actual table name and `${YOUR_AWS_REGION}` and `${YOUR_AWS_ACCOUNT_ID}` with appropriate values.
 
@@ -246,7 +246,7 @@ The IAM role or user executing the code needs appropriate permissions to interac
 }
 ```
 
-## Key Considerations
+## Key considerations
 
 Before diving into the architectural details, keep these key points in mind when working with the DynamoDB storage adapter:
 
@@ -255,7 +255,7 @@ Before diving into the architectural details, keep these key points in mind when
 - **Understanding GSIs:** Familiarity with how the GSIs are structured (as per `TABLE_SETUP.md`) is important for understanding data retrieval and potential query patterns.
 - **ElectroDB:** The adapter uses ElectroDB to manage interactions with DynamoDB, providing a layer of abstraction and type safety over raw DynamoDB operations.
 
-## Architectural Approach
+## Architectural approach
 
 This storage adapter utilizes a **single-table design pattern** leveraging [ElectroDB](https://electrodb.dev/), a common and recommended approach for DynamoDB. This differs architecturally from relational database adapters (like `@mastra/pg` or `@mastra/libsql`) that typically use multiple tables, each dedicated to a specific entity (threads, messages, etc.).
 

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

@@ -1,8 +1,8 @@
-# LanceDB Storage
+# 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.
 
-> **Observability Not Supported:** LanceDB storage **does not support the observability domain**. Traces from the `DefaultExporter` cannot be persisted to LanceDB, and Mastra Studio's observability features won't work with LanceDB as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
+> **Observability Not Supported:** LanceDB storage **doesn't support the observability domain**. Traces from the `DefaultExporter` can't be persisted to LanceDB, and Mastra Studio's observability features won't work with LanceDB as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
 
 ## Installation
 
@@ -51,7 +51,7 @@ const storage = await LanceStorage.create('my-storage', 's3://bucket/db', {
 
 ## Parameters
 
-### LanceStorage.create()
+### `LanceStorage.create()`
 
 **name** (`string`): Name identifier for the storage instance
 
@@ -59,7 +59,7 @@ const storage = await LanceStorage.create('my-storage', 's3://bucket/db', {
 
 **options** (`ConnectionOptions`): Connection options for LanceDB, such as timeout settings, authentication, etc.
 
-## Additional Notes
+## Additional notes
 
 ### Schema Management
 
@@ -101,7 +101,7 @@ const memoryStore = await storage.getStore('memory')
 const thread = await memoryStore?.getThreadById({ threadId: '...' })
 ```
 
-> **Warning:** If `init()` is not called, tables won't be created and storage operations will fail silently or throw errors.
+> **Warning:** If `init()` isn't called, tables won't be created and storage operations will fail silently or throw errors.
 
 ### Deployment Options
 

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

@@ -1,4 +1,4 @@
-# libSQL Storage
+# 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,4 +1,4 @@
-# MongoDB Storage
+# MongoDB storage
 
 The MongoDB storage implementation provides a scalable storage solution using MongoDB databases with support for both document storage and vector operations.
 
@@ -56,7 +56,7 @@ const storage = new MongoDBStore({
 
 > **Deprecation Notice:** The `url` parameter is deprecated but still supported for backward compatibility. Please use `uri` instead in all new code.
 
-## Constructor Examples
+## Constructor examples
 
 You can instantiate `MongoDBStore` in the following ways:
 
@@ -84,7 +84,7 @@ const store2 = new MongoDBStore({
 })
 ```
 
-## Additional Notes
+## Additional notes
 
 ### Collection Management
 
@@ -136,9 +136,9 @@ const memoryStore = await storage.getStore('memory')
 const thread = await memoryStore?.getThreadById({ threadId: '...' })
 ```
 
-> **Warning:** If `init()` is not called, collections won't be created and storage operations will fail silently or throw errors.
+> **Warning:** If `init()` isn't called, collections won't be created and storage operations will fail silently or throw errors.
 
-## Vector Search Capabilities
+## Vector search capabilities
 
 MongoDB storage includes built-in vector search capabilities for AI applications:
 
@@ -190,7 +190,7 @@ const results = await vectorStore.query({
 });
 ```
 
-## Usage Example
+## Usage example
 
 ### Adding memory to an agent