@mastra/mcp-docs-server 0.13.37 → 0.13.38

package/.docs/raw/reference/tools/vector-query-tool.mdx

@@ -1,10 +1,10 @@
 ---
-title: "Reference: createVectorQueryTool() | RAG | Mastra Tools Docs"
+title: "Reference: createVectorQueryTool() | Tools & MCP | Mastra Docs"
 description: Documentation for the Vector Query Tool in Mastra, which facilitates semantic search over vector stores with filtering and reranking capabilities.
 ---
 
-import { Callout } from "nextra/components";
-import { Tabs } from "nextra/components";
+import Tabs from "@theme/Tabs";
+import TabItem from "@theme/TabItem";
 
 # createVectorQueryTool()
 
@@ -25,13 +25,15 @@ const queryTool = createVectorQueryTool({
 
 ## Parameters
 
-<Callout>
-  **Parameter Requirements:** Most fields can be set at creation as defaults.
-  Some fields can be overridden at runtime via the runtime context or input. If
-  a required field is missing from both creation and runtime, an error will be
-  thrown. Note that `model`, `id`, and `description` can only be set at creation
-  time.
-</Callout>
+:::note
+
+**Parameter Requirements:** Most fields can be set at creation as defaults.
+Some fields can be overridden at runtime via the runtime context or input. If
+a required field is missing from both creation and runtime, an error will be
+thrown. Note that `model`, `id`, and `description` can only be set at creation
+time.
+
+:::
 
 <PropertiesTable
   content={[
@@ -152,7 +154,8 @@ The `DatabaseConfig` type allows you to specify database-specific configurations
     {
       name: "pgvector",
       type: "PgVectorConfig",
-      description: "Configuration specific to PostgreSQL with pgvector extension",
+      description:
+        "Configuration specific to PostgreSQL with pgvector extension",
       isOptional: true,
       properties: [
         {
@@ -166,13 +169,15 @@ The `DatabaseConfig` type allows you to specify database-specific configurations
             },
             {
               name: "ef",
-              description: "HNSW search parameter - controls accuracy vs speed tradeoff",
+              description:
+                "HNSW search parameter - controls accuracy vs speed tradeoff",
               isOptional: true,
               type: "number",
             },
             {
               name: "probes",
-              description: "IVFFlat probe parameter - number of cells to visit during search",
+              description:
+                "IVFFlat probe parameter - number of cells to visit during search",
               isOptional: true,
               type: "number",
             },
@@ -321,7 +326,7 @@ This agent-driven approach:
 
 For detailed filter syntax and store-specific capabilities, see the [Metadata Filters](../rag/metadata-filters) documentation.
 
-For an example of how agent-driven filtering works, see the [Agent-Driven Metadata Filtering](../../../examples/rag/usage/filter-rag.mdx) example.
+For an example of how agent-driven filtering works, see the [Agent-Driven Metadata Filtering](/examples/rag/usage/filter-rag) example.
 
 ## Example with Reranking
 
@@ -371,8 +376,8 @@ This example shows how to customize the tool description for a specific use case
 
 The `databaseConfig` parameter allows you to leverage unique features and optimizations specific to each vector database. These configurations are automatically applied during query execution.
 
-<Tabs items={['Pinecone', 'pgVector', 'Chroma', 'Multiple Configs']}>
-  <Tabs.Tab>
+<Tabs>
+  <TabItem value="pinecone" label="Pinecone">
     ### Pinecone Configuration
 
     ```typescript
@@ -396,9 +401,10 @@ The `databaseConfig` parameter allows you to leverage unique features and optimi
     - **Namespace**: Isolate different data sets within the same index
     - **Sparse Vector**: Combine dense and sparse embeddings for improved search quality
     - **Use Cases**: Multi-tenant applications, hybrid semantic search
-  </Tabs.Tab>
 
-  <Tabs.Tab>
+  </TabItem>
+
+  <TabItem value="pgvector" label="pgVector">
     ### pgVector Configuration
 
     ```typescript
@@ -421,9 +427,10 @@ The `databaseConfig` parameter allows you to leverage unique features and optimi
     - **ef (HNSW)**: Control accuracy vs speed for HNSW indexes
     - **probes (IVFFlat)**: Control recall vs speed for IVFFlat indexes
     - **Use Cases**: Performance tuning, quality filtering
-  </Tabs.Tab>
 
-  <Tabs.Tab>
+  </TabItem>
+
+  <TabItem value="chroma" label="Chroma">
     ### Chroma Configuration
 
     ```typescript
@@ -449,9 +456,10 @@ The `databaseConfig` parameter allows you to leverage unique features and optimi
     - **where**: Filter by metadata fields
     - **whereDocument**: Filter by document content
     - **Use Cases**: Advanced filtering, content-based search
-  </Tabs.Tab>
 
-  <Tabs.Tab>
+  </TabItem>
+
+  <TabItem value="multiple-configs" label="Multiple Configs">
     ### Multiple Database Configurations
 
     ```typescript
@@ -479,7 +487,8 @@ The `databaseConfig` parameter allows you to leverage unique features and optimi
     - Support multiple vector stores with one tool
     - Database-specific optimizations are automatically applied
     - Flexible deployment scenarios
-  </Tabs.Tab>
+
+  </TabItem>
 </Tabs>
 
 ### Runtime Configuration Override
@@ -487,7 +496,7 @@ The `databaseConfig` parameter allows you to leverage unique features and optimi
 You can override database configurations at runtime to adapt to different scenarios:
 
 ```typescript
-import { RuntimeContext } from '@mastra/core/runtime-context';
+import { RuntimeContext } from "@mastra/core/runtime-context";
 
 const queryTool = createVectorQueryTool({
   vectorStoreName: "pinecone",
@@ -495,26 +504,26 @@ const queryTool = createVectorQueryTool({
   model: openai.embedding("text-embedding-3-small"),
   databaseConfig: {
     pinecone: {
-      namespace: "development"
-    }
-  }
+      namespace: "development",
+    },
+  },
 });
 
 // Override at runtime
 const runtimeContext = new RuntimeContext();
-runtimeContext.set('databaseConfig', {
+runtimeContext.set("databaseConfig", {
   pinecone: {
-    namespace: 'production'  // Switch to production namespace
-  }
+    namespace: "production", // Switch to production namespace
+  },
 });
 
-const response = await agent.generate(
-  "Find information about deployment",
-  { runtimeContext }
-);
+const response = await agent.generate("Find information about deployment", {
+  runtimeContext,
+});
 ```
 
 This approach allows you to:
+
 - Switch between environments (dev/staging/prod)
 - Adjust performance parameters based on load
 - Apply different filtering strategies per request
@@ -544,7 +553,7 @@ runtimeContext.set("indexName", "my-index");
 runtimeContext.set("topK", 5);
 runtimeContext.set("filter", { category: "docs" });
 runtimeContext.set("databaseConfig", {
-  pinecone: { namespace: "runtime-namespace" }
+  pinecone: { namespace: "runtime-namespace" },
 });
 runtimeContext.set("model", openai.embedding("text-embedding-3-small"));
 
@@ -558,13 +567,14 @@ const response = await agent.generate(
 
 For more information on runtime context, please see:
 
-- [Agent Runtime Context](../../docs/server-db/runtime-context.mdx)
-- [Tool Runtime Context](../../docs/tools-mcp/overview.mdx#using-runtimecontext)
+- [Agent Runtime Context](/docs/server-db/runtime-context)
+- [Tool Runtime Context](/docs/tools-mcp/overview#using-runtimecontext)
 
 ## Usage Without a Mastra Server
 
 The tool can be used by itself to retrieve documents matching a query:
-```typescript copy showLineNumbers filename="src/index.ts"
+
+```typescript copy showLineNumbers title="src/index.ts"
 import { openai } from "@ai-sdk/openai";
 import { RuntimeContext } from "@mastra/core/runtime-context";
 import { createVectorQueryTool } from "@mastra/rag";

package/.docs/raw/reference/vectors/astra.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Reference: Astra Vector Store | Vector Databases | Mastra Docs"
+title: "Reference: Astra Vector Store | Vectors | Mastra Docs"
 description: Documentation for the AstraVector class in Mastra, which provides vector search using DataStax Astra DB.
 ---
 

package/.docs/raw/reference/vectors/chroma.mdx

@@ -1,23 +1,22 @@
 ---
-title: "Reference: Chroma Vector Store | Vector Databases | Mastra Docs"
+title: "Reference: Chroma Vector Store | Vectors | Mastra Docs"
 description: Documentation for the ChromaVector class in Mastra, which provides vector search using ChromaDB.
 ---
 
-import { Callout } from "nextra/components";
-
 # Chroma Vector Store
 
 The ChromaVector class provides vector search using [Chroma](https://docs.trychroma.com/docs/overview/getting-started), an open-source embedding database.
 It offers efficient vector search with metadata filtering and hybrid search capabilities.
 
-<Callout type="info">
-  <b>Chroma Cloud</b>
-  <p>
+:::info
+
+<b>Chroma Cloud</b>
+
     Chroma Cloud powers serverless vector and full-text search. It's extremely fast, cost-effective, scalable and painless. Create a DB and try it out in under 30 seconds with $5 of free credits.
 
     [Get started with Chroma Cloud](https://trychroma.com/signup)
-  </p>
-</Callout>
+
+:::
 
 ## Constructor Options
 
@@ -27,7 +26,8 @@ It offers efficient vector search with metadata filtering and hybrid search capa
       name: "host",
       type: "string",
       isOptional: true,
-      description: "The host address of the Chroma server. Defaults to 'localhost'",
+      description:
+        "The host address of the Chroma server. Defaults to 'localhost'",
     },
     {
       name: "port",
@@ -39,7 +39,8 @@ It offers efficient vector search with metadata filtering and hybrid search capa
       name: "ssl",
       type: "boolean",
       isOptional: true,
-      description: "Whether to use SSL/HTTPS for connections. Defaults to false",
+      description:
+        "Whether to use SSL/HTTPS for connections. Defaults to false",
     },
     {
       name: "apiKey",
@@ -51,13 +52,15 @@ It offers efficient vector search with metadata filtering and hybrid search capa
       name: "tenant",
       type: "string",
       isOptional: true,
-      description: "The tenant name in the Chroma server to connect to. Defaults to 'default_tenant' for single-node Chroma. Auto-resolved for Chroma Cloud users based on the provided API key",
+      description:
+        "The tenant name in the Chroma server to connect to. Defaults to 'default_tenant' for single-node Chroma. Auto-resolved for Chroma Cloud users based on the provided API key",
     },
     {
       name: "database",
       type: "string",
       isOptional: true,
-      description: "The database name to connect to. Defaults to 'default_database' for single-node Chroma. Auto-resolved for Chroma Cloud users based on the provided API key",
+      description:
+        "The database name to connect to. Defaults to 'default_database' for single-node Chroma. Auto-resolved for Chroma Cloud users based on the provided API key",
     },
     {
       name: "headers",
@@ -70,7 +73,7 @@ It offers efficient vector search with metadata filtering and hybrid search capa
       type: "RequestInit",
       isOptional: true,
       description: "Additional fetch options for HTTP requests",
-    }
+    },
   ]}
 />
 
@@ -81,9 +84,10 @@ If you are a Chroma Cloud user, simply provide the `ChromaVector` constructor yo
 When you install the `@mastra/chroma` package, you get access to the [Chroma CLI](https://docs.trychroma.com/docs/cli/db), which can set these as environment variables for you: `chroma db connect [DB-NAME] --env-file`.
 
 Otherwise, you have several options for setting up your single-node Chroma server:
-* Run one locally using the Chroma CLI: `chroma run`. You can find more configuration options on the [Chroma docs](https://docs.trychroma.com/docs/cli/run).
-* Run on [Docker](https://docs.trychroma.com/guides/deploy/docker) using the official Chroma image.
-* Deploy your own Chroma server on your provider of choice. Chroma offers example templates for [AWS](https://docs.trychroma.com/guides/deploy/aws), [Azure](https://docs.trychroma.com/guides/deploy/azure), and [GCP](https://docs.trychroma.com/guides/deploy/gcp).
+
+- Run one locally using the Chroma CLI: `chroma run`. You can find more configuration options on the [Chroma docs](https://docs.trychroma.com/docs/cli/run).
+- Run on [Docker](https://docs.trychroma.com/guides/deploy/docker) using the official Chroma image.
+- Deploy your own Chroma server on your provider of choice. Chroma offers example templates for [AWS](https://docs.trychroma.com/guides/deploy/aws), [Azure](https://docs.trychroma.com/guides/deploy/azure), and [GCP](https://docs.trychroma.com/guides/deploy/gcp).
 
 ## Methods
 
@@ -128,7 +132,7 @@ Note: Forking is only supported on Chroma Cloud, or if you deploy your own OSS *
       name: "newIndexName",
       type: "string",
       description: "The name of the forked index",
-    }
+    },
   ]}
 />
 
@@ -251,7 +255,8 @@ You can also provide the shape of your metadata to a `get` call for type inferen
       name: "ids",
       type: "string[]",
       isOptional: true,
-      description: "A list of record IDs to return. If not provided, all records are returned.",
+      description:
+        "A list of record IDs to return. If not provided, all records are returned.",
     },
     {
       name: "filter",
@@ -284,7 +289,8 @@ You can also provide the shape of your metadata to a `get` call for type inferen
       type: "number",
       isOptional: true,
       defaultValue: 0,
-      description: "Offset for returning records. Use with `limit` to paginate results.",
+      description:
+        "Offset for returning records. Use with `limit` to paginate results.",
     },
   ]}
 />

package/.docs/raw/reference/vectors/couchbase.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Reference: Couchbase Vector Store | Vector Databases | Mastra Docs"
+title: "Reference: Couchbase Vector Store | Vectors | Mastra Docs"
 description: Documentation for the CouchbaseVector class in Mastra, which provides vector search using Couchbase Vector Search.
 ---
 
@@ -21,7 +21,7 @@ npm install @mastra/couchbase
 ## Usage Example
 
 ```typescript copy showLineNumbers
-import { CouchbaseVector } from '@mastra/couchbase';
+import { CouchbaseVector } from "@mastra/couchbase";
 
 const store = new CouchbaseVector({
   connectionString: process.env.COUCHBASE_CONNECTION_STRING,
@@ -317,7 +317,7 @@ try {
   // Handle specific error cases
   if (error.message.includes("Invalid index name")) {
     console.error(
-      "Index name must start with a letter or underscore and contain only valid characters."
+      "Index name must start with a letter or underscore and contain only valid characters.",
     );
   } else if (error.message.includes("Index not found")) {
     console.error("The specified index does not exist");
@@ -342,4 +342,4 @@ try {
 
 ## Related
 
-- [Metadata Filters](../rag/metadata-filters) 
+- [Metadata Filters](../rag/metadata-filters)

package/.docs/raw/reference/vectors/lance.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Reference: Lance Vector Store | Vector Databases | Mastra Docs"
+title: "Reference: Lance Vector Store | Vectors | Mastra Docs"
 description: "Documentation for the LanceVectorStore class in Mastra, which provides vector search using LanceDB, an embedded vector database based on the Lance columnar format."
 ---
 
@@ -21,8 +21,7 @@ The LanceVectorStore uses a factory pattern for creation. You should use the sta
     {
       name: "options",
       type: "ConnectionOptions",
-      description:
-        "Additional connection options for LanceDB",
+      description: "Additional connection options for LanceDB",
       isOptional: true,
     },
   ]}
@@ -42,8 +41,8 @@ const vectorStore = await LanceVectorStore.create("/path/to/db");
 const cloudStore = await LanceVectorStore.create("db://host:port");
 
 // Connect to a cloud database with options
-const s3Store = await LanceVectorStore.create("s3://bucket/db", { 
-  storageOptions: { timeout: '60s' }
+const s3Store = await LanceVectorStore.create("s3://bucket/db", {
+  storageOptions: { timeout: "60s" },
 });
 ```
 
@@ -448,4 +447,4 @@ try {
 
 ## Related
 
-- [Metadata Filters](../rag/metadata-filters)
+- [Metadata Filters](../rag/metadata-filters)

package/.docs/raw/reference/vectors/libsql.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Default Vector Store | Vector Databases | Mastra Docs"
+title: "Reference: LibSQLVector Store | Vectors | Mastra Docs"
 description: Documentation for the LibSQLVector class in Mastra, which provides vector search using LibSQL with vector extensions.
 ---
 

package/.docs/raw/reference/vectors/mongodb.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Reference: MongoDB Vector Store | Vector Databases | Mastra Docs"
+title: "Reference: MongoDB Vector Store | Vectors | Mastra Docs"
 description: Documentation for the MongoDBVector class in Mastra, which provides vector search using MongoDB Atlas and Atlas Vector Search.
 ---
 

package/.docs/raw/reference/vectors/opensearch.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Reference: OpenSearch Vector Store | Vector Databases | Mastra Docs"
+title: "Reference: OpenSearch Vector Store | Vectors | Mastra Docs"
 description: Documentation for the OpenSearchVector class in Mastra, which provides vector search using OpenSearch.
 ---
 

package/.docs/raw/reference/vectors/pg.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Reference: PG Vector Store | Vector Databases | Mastra Docs"
+title: "Reference: PG Vector Store | Vectors | Mastra Docs"
 description: Documentation for the PgVector class in Mastra, which provides vector search using PostgreSQL with pgvector extension.
 ---
 
@@ -584,16 +584,18 @@ try {
 ### Performance Optimization
 
 #### IVFFlat Tuning
+
 - **lists parameter**: Set to `sqrt(n) * 2` where n is the number of vectors
 - More lists = better accuracy but slower build time
 - Fewer lists = faster build but potentially lower accuracy
 
 #### HNSW Tuning
-- **m parameter**: 
+
+- **m parameter**:
   - 8-16: Moderate accuracy, lower memory
   - 16-32: High accuracy, moderate memory
   - 32-64: Very high accuracy, high memory
-- **efConstruction**: 
+- **efConstruction**:
   - 32-64: Fast build, good quality
   - 64-128: Slower build, better quality
   - 128-256: Slowest build, best quality
@@ -601,6 +603,7 @@ try {
 ### Index Recreation Behavior
 
 The system automatically detects configuration changes and only rebuilds indexes when necessary:
+
 - Same configuration: Index is kept (no recreation)
 - Changed configuration: Index is dropped and rebuilt
 - This prevents the performance issues from unnecessary index recreations
@@ -617,10 +620,11 @@ The system automatically detects configuration changes and only rebuilds indexes
 The `PgVector` class exposes its underlying PostgreSQL connection pool as a public field:
 
 ```typescript
-pgVector.pool // instance of pg.Pool
+pgVector.pool; // instance of pg.Pool
 ```
 
 This enables advanced usage such as running direct SQL queries, managing transactions, or monitoring pool state. When using the pool directly:
+
 - You are responsible for releasing clients (`client.release()`) after use.
 - The pool remains accessible after calling `disconnect()`, but new queries will fail.
 - Direct access bypasses any validation or transaction logic provided by PgVector methods.

package/.docs/raw/reference/vectors/pinecone.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Reference: Pinecone Vector Store | Vector DBs | Mastra Docs"
+title: "Reference: Pinecone Vector Store | Vectors | Mastra Docs"
 description: Documentation for the PineconeVector class in Mastra, which provides an interface to Pinecone's vector database.
 ---
 

package/.docs/raw/reference/vectors/qdrant.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Reference: Qdrant Vector Store | Vector Databases | Mastra Docs"
+title: "Reference: Qdrant Vector Store | Vectors | Mastra Docs"
 description: Documentation for integrating Qdrant with Mastra, a vector similarity search engine for managing vectors and payloads.
 ---
 

package/.docs/raw/reference/vectors/s3vectors.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Reference: Amazon S3 Vectors Store | Vector Databases | Mastra Docs"
+title: "Reference: Amazon S3 Vectors Store | Vectors | Mastra Docs"
 description: Documentation for the S3Vectors class in Mastra, which provides vector search using Amazon S3 Vectors (Preview).
 ---
 
@@ -47,7 +47,12 @@ const ids = await store.upsert({
     [0.3, 0.4 /* … */],
   ],
   metadata: [
-    { text: "doc1", genre: "documentary", year: 2023, createdAt: new Date("2024-01-01") },
+    {
+      text: "doc1",
+      genre: "documentary",
+      year: 2023,
+      createdAt: new Date("2024-01-01"),
+    },
     { text: "doc2", genre: "comedy", year: 2021 },
   ],
 });
@@ -84,7 +89,8 @@ await store.disconnect();
       name: "nonFilterableMetadataKeys",
       type: "string[]",
       isOptional: true,
-      description: "Metadata keys that should NOT be filterable (applied to the index at creation time). Use this for large text fields like `content`.",
+      description:
+        "Metadata keys that should NOT be filterable (applied to the index at creation time). Use this for large text fields like `content`.",
     },
   ]}
 />
@@ -100,7 +106,8 @@ Creates a new vector index in the configured vector bucket. If the index already
     {
       name: "indexName",
       type: "string",
-      description: "Logical index name. Normalized internally: underscores are replaced with hyphens and the name is lowercased.",
+      description:
+        "Logical index name. Normalized internally: underscores are replaced with hyphens and the name is lowercased.",
     },
     {
       name: "dimension",
@@ -112,7 +119,8 @@ Creates a new vector index in the configured vector bucket. If the index already
       type: "'cosine' | 'euclidean'",
       isOptional: true,
       defaultValue: "cosine",
-      description: "Distance metric for similarity search. `dotproduct` is not supported by S3 Vectors.",
+      description:
+        "Distance metric for similarity search. `dotproduct` is not supported by S3 Vectors.",
     },
   ]}
 />
@@ -175,7 +183,8 @@ Searches for nearest neighbors with optional metadata filtering.
       name: "filter",
       type: "S3VectorsFilter",
       isOptional: true,
-      description: "JSON-based metadata filter supporting `$and`, `$or`, `$eq`, `$ne`, `$gt`, `$gte`, `$lt`, `$lte`, `$in`, `$nin`, `$exists`.",
+      description:
+        "JSON-based metadata filter supporting `$and`, `$or`, `$eq`, `$ne`, `$gt`, `$gte`, `$lt`, `$lte`, `$in`, `$nin`, `$exists`.",
     },
     {
       name: "includeVector",
@@ -187,7 +196,6 @@ Searches for nearest neighbors with optional metadata filtering.
   ]}
 />
 
-
 > **Scoring:** Results include `score = 1/(1 + distance)` so that higher is better while preserving the underlying distance ranking.
 
 ### describeIndex()
@@ -310,20 +318,20 @@ interface QueryResult {
 
 S3 Vectors supports a strict subset of operators and value types. The Mastra filter translator:
 
-* **Canonicalizes implicit AND**: `{a:1,b:2}` → `{ $and: [{a:1},{b:2}] }`.
-* **Normalizes Date values** to epoch ms for numeric comparisons and array elements.
-* **Disallows Date** in equality positions (`field: value` or `$eq/$ne`); equality values must be **string | number | boolean**.
-* **Rejects** null/undefined for equality; **array equality** is not supported (use `$in`/`$nin`).
-* Only **`$and` / `$or`** are allowed as top-level logical operators.
-* Logical operators must contain **field conditions** (not direct operators).
+- **Canonicalizes implicit AND**: `{a:1,b:2}` → `{ $and: [{a:1},{b:2}] }`.
+- **Normalizes Date values** to epoch ms for numeric comparisons and array elements.
+- **Disallows Date** in equality positions (`field: value` or `$eq/$ne`); equality values must be **string | number | boolean**.
+- **Rejects** null/undefined for equality; **array equality** is not supported (use `$in`/`$nin`).
+- Only **`$and` / `$or`** are allowed as top-level logical operators.
+- Logical operators must contain **field conditions** (not direct operators).
 
 **Supported operators:**
 
-* **Logical:** `$and`, `$or` (non-empty arrays)
-* **Basic:** `$eq`, `$ne` (string | number | boolean)
-* **Numeric:** `$gt`, `$gte`, `$lt`, `$lte` (number or `Date` → epoch ms)
-* **Array:** `$in`, `$nin` (non-empty arrays of string | number | boolean; `Date` → epoch ms)
-* **Element:** `$exists` (boolean)
+- **Logical:** `$and`, `$or` (non-empty arrays)
+- **Basic:** `$eq`, `$ne` (string | number | boolean)
+- **Numeric:** `$gt`, `$gte`, `$lt`, `$lte` (number or `Date` → epoch ms)
+- **Array:** `$in`, `$nin` (non-empty arrays of string | number | boolean; `Date` → epoch ms)
+- **Element:** `$exists` (boolean)
 
 **Unsupported / disallowed (rejected):** `$not`, `$nor`, `$regex`, `$all`, `$elemMatch`, `$size`, `$text`, etc.
 
@@ -369,18 +377,18 @@ try {
 
 Typical environment variables when wiring your app:
 
-* `S3_VECTORS_BUCKET_NAME`: Your S3 **vector bucket** name (used to populate `vectorBucketName`).
-* `AWS_REGION`: AWS region for the S3 Vectors bucket.
-* **AWS credentials**: via the standard AWS SDK provider chain (`AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, `AWS_PROFILE`, etc.).
+- `S3_VECTORS_BUCKET_NAME`: Your S3 **vector bucket** name (used to populate `vectorBucketName`).
+- `AWS_REGION`: AWS region for the S3 Vectors bucket.
+- **AWS credentials**: via the standard AWS SDK provider chain (`AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, `AWS_PROFILE`, etc.).
 
 ## Best Practices
 
-* Choose the metric (`cosine` or `euclidean`) to match your embedding model; `dotproduct` is not supported.
-* Keep **filterable** metadata small and structured (string/number/boolean). Store large text (e.g., `content`) as **non-filterable**.
-* Use **dotted paths** for nested metadata and explicit `$and`/`$or` for complex logic.
-* Avoid calling `describeIndex()` on hot paths—`count` is computed with paginated `ListVectors` (**O(n)**).
-* Use `includeVector: true` only when you need raw vectors.
+- Choose the metric (`cosine` or `euclidean`) to match your embedding model; `dotproduct` is not supported.
+- Keep **filterable** metadata small and structured (string/number/boolean). Store large text (e.g., `content`) as **non-filterable**.
+- Use **dotted paths** for nested metadata and explicit `$and`/`$or` for complex logic.
+- Avoid calling `describeIndex()` on hot paths—`count` is computed with paginated `ListVectors` (**O(n)**).
+- Use `includeVector: true` only when you need raw vectors.
 
 ## Related
 
-* [Metadata Filters](../rag/metadata-filters)
+- [Metadata Filters](../rag/metadata-filters)

package/.docs/raw/reference/vectors/turbopuffer.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Reference: Turbopuffer Vector Store | Vector Databases | Mastra Docs"
+title: "Reference: Turbopuffer Vector Store | Vectors | Mastra Docs"
 description: Documentation for integrating Turbopuffer with Mastra, a high-performance vector database for efficient similarity search.
 ---