@mastra/mcp-docs-server 1.0.0-beta.9 → 1.0.1

package/.docs/raw/rag/retrieval.mdx

@@ -1,6 +1,20 @@
 ---
 title: "Retrieval, Semantic Search, Reranking | RAG"
 description: Guide on retrieval processes in Mastra's RAG systems, including semantic search, filtering, and re-ranking.
+packages:
+  - "@mastra/astra"
+  - "@mastra/chroma"
+  - "@mastra/core"
+  - "@mastra/libsql"
+  - "@mastra/mongodb"
+  - "@mastra/opensearch"
+  - "@mastra/pg"
+  - "@mastra/pinecone"
+  - "@mastra/qdrant"
+  - "@mastra/rag"
+  - "@mastra/s3vectors"
+  - "@mastra/upstash"
+  - "@mastra/vectorize"
 ---
 
 import Tabs from "@theme/Tabs";
@@ -26,7 +40,7 @@ Mastra provides flexible retrieval options with support for semantic search, fil
 
 The simplest approach is direct semantic search. This method uses vector similarity to find chunks that are semantically similar to the query:
 
-```ts showLineNumbers copy
+```ts
 import { embed } from "ai";
 import { PgVector } from "@mastra/pg";
 import { ModelRouterEmbeddingModel } from "@mastra/core/llm";
@@ -56,7 +70,7 @@ The `topK` parameter specifies the maximum number of most similar results to ret
 
 Results include both the text content and a similarity score:
 
-```ts showLineNumbers copy
+```ts
 [
   {
     text: "Climate change poses significant challenges...",
@@ -68,7 +82,6 @@ Results include both the text content and a similarity score:
     score: 0.82,
     metadata: { source: "article1.txt" },
   },
-  // ... more results
 ];
 ```
 
@@ -76,13 +89,15 @@ Results include both the text content and a similarity score:
 
 ### Metadata Filtering
 
-Filter results based on metadata fields to narrow down the search space. This is useful when you have documents from different sources, time periods, or with specific attributes. Mastra provides a unified MongoDB-style query syntax that works across all supported vector stores.
+Filter results based on metadata fields to narrow down the search space. This approach - combining vector similarity search with metadata filters - is sometimes called hybrid vector search, as it merges semantic search with structured filtering criteria.
+
+This is useful when you have documents from different sources, time periods, or with specific attributes. Mastra provides a unified MongoDB-style query syntax that works across all supported vector stores.
 
 For detailed information about available operators and syntax, see the [Metadata Filters Reference](/reference/v1/rag/metadata-filters).
 
 Basic filtering examples:
 
-```ts showLineNumbers copy
+```ts
 // Simple equality filter
 const results = await pgVector.query({
   indexName: "embeddings",
@@ -146,13 +161,14 @@ Common use cases for metadata filtering:
 - Combine multiple conditions for precise querying
 - Filter by document attributes (e.g., language, author)
 
-For an example of how to use metadata filtering, see the [Hybrid Vector Search](/examples/v1/rag/query/hybrid-vector-search) example.
-
 ### Vector Query Tool
 
 Sometimes you want to give your agent the ability to query a vector database directly. The Vector Query Tool allows your agent to be in charge of retrieval decisions, combining semantic search with optional filtering and reranking based on the agent's understanding of the user's needs.
 
-```ts showLineNumbers copy
+```ts
+import { createVectorQueryTool } from "@mastra/rag";
+import { ModelRouterEmbeddingModel } from "@mastra/core/llm";
+
 const vectorQueryTool = createVectorQueryTool({
   vectorStoreName: "pgVector",
   indexName: "embeddings",
@@ -176,10 +192,13 @@ The Vector Query Tool supports database-specific configurations that enable you
 These configurations are for **query-time options** like namespaces, performance tuning, and filtering—not for database connection setup. 
 
 
-Connection credentials (URLs, auth tokens) are configured when you instantiate the vector store class (e.g., `new LibSQLVector({ connectionUrl: '...' })`).
+Connection credentials (URLs, auth tokens) are configured when you instantiate the vector store class (e.g., `new LibSQLVector({ url: '...' })`).
 :::
 
-```ts showLineNumbers copy
+```ts
+import { createVectorQueryTool } from "@mastra/rag";
+import { ModelRouterEmbeddingModel } from "@mastra/core/llm";
+
 // Pinecone with namespace
 const pineconeQueryTool = createVectorQueryTool({
   vectorStoreName: "pinecone",
@@ -251,7 +270,7 @@ const lanceQueryTool = createVectorQueryTool({
 
 You can also override these configurations at runtime using the request context:
 
-```ts showLineNumbers copy
+```ts
 import { RequestContext } from "@mastra/core/request-context";
 
 const requestContext = new RequestContext();
@@ -261,11 +280,10 @@ requestContext.set("databaseConfig", {
   },
 });
 
-await pineconeQueryTool.execute({
-  context: { queryText: "search query" },
-  mastra,
-  requestContext,
-});
+await pineconeQueryTool.execute(
+  { queryText: "search query" },
+  { mastra, requestContext }
+);
 ```
 
 For detailed configuration options and advanced usage, see the [Vector Query Tool Reference](/reference/v1/tools/vector-query-tool).
@@ -278,7 +296,7 @@ When implementing filtering, these prompts are required in the agent's instructi
 <Tabs>
   <TabItem value="pgvector" label="pgVector">
 
-```ts showLineNumbers copy
+```ts
 import { PGVECTOR_PROMPT } from "@mastra/pg";
 
 export const ragAgent = new Agent({
@@ -297,7 +315,7 @@ export const ragAgent = new Agent({
 
   <TabItem value="pinecone" label="Pinecone">
 
-```ts title="vector-store.ts" showLineNumbers copy
+```ts title="vector-store.ts"
 import { PINECONE_PROMPT } from "@mastra/pinecone";
 
 export const ragAgent = new Agent({
@@ -316,7 +334,7 @@ export const ragAgent = new Agent({
 
   <TabItem value="qdrant" label="Qdrant">
 
-```ts title="vector-store.ts" showLineNumbers copy
+```ts title="vector-store.ts"
 import { QDRANT_PROMPT } from "@mastra/qdrant";
 
 export const ragAgent = new Agent({
@@ -335,7 +353,7 @@ export const ragAgent = new Agent({
 
   <TabItem value="chroma" label="Chroma">
 
-```ts title="vector-store.ts" showLineNumbers copy
+```ts title="vector-store.ts"
 import { CHROMA_PROMPT } from "@mastra/chroma";
 
 export const ragAgent = new Agent({
@@ -354,7 +372,7 @@ export const ragAgent = new Agent({
 
   <TabItem value="astra" label="Astra">
 
-```ts title="vector-store.ts" showLineNumbers copy
+```ts title="vector-store.ts"
 import { ASTRA_PROMPT } from "@mastra/astra";
 
 export const ragAgent = new Agent({
@@ -371,9 +389,9 @@ export const ragAgent = new Agent({
 
   </TabItem>
 
-  <TabItem value="libsql" label="LibSQL">
+  <TabItem value="libsql" label="libSQL">
 
-```ts title="vector-store.ts" showLineNumbers copy
+```ts title="vector-store.ts"
 import { LIBSQL_PROMPT } from "@mastra/libsql";
 
 export const ragAgent = new Agent({
@@ -392,7 +410,7 @@ export const ragAgent = new Agent({
 
   <TabItem value="upstash" label="Upstash">
 
-```ts title="vector-store.ts" showLineNumbers copy
+```ts title="vector-store.ts"
 import { UPSTASH_PROMPT } from "@mastra/upstash";
 
 export const ragAgent = new Agent({
@@ -411,7 +429,7 @@ export const ragAgent = new Agent({
 
   <TabItem value="vectorize" label="Vectorize">
 
-```ts title="vector-store.ts" showLineNumbers copy
+```ts title="vector-store.ts"
 import { VECTORIZE_PROMPT } from "@mastra/vectorize";
 
 export const ragAgent = new Agent({
@@ -430,7 +448,7 @@ export const ragAgent = new Agent({
 
   <TabItem value="mongodb" label="MongoDB">
 
-```ts title="vector-store.ts" showLineNumbers copy
+```ts title="vector-store.ts"
 import { MONGODB_PROMPT } from "@mastra/mongodb";
 
 export const ragAgent = new Agent({
@@ -449,7 +467,7 @@ export const ragAgent = new Agent({
 
   <TabItem value="opensearch" label="OpenSearch">
 
-```ts title="vector-store.ts" showLineNumbers copy
+```ts title="vector-store.ts"
 import { OPENSEARCH_PROMPT } from "@mastra/opensearch";
 
 export const ragAgent = new Agent({
@@ -468,7 +486,7 @@ export const ragAgent = new Agent({
 
   <TabItem value="s3vectors" label="S3Vectors">
 
-```ts title="vector-store.ts" showLineNumbers copy
+```ts title="vector-store.ts"
 import { S3VECTORS_PROMPT } from "@mastra/s3vectors";
 
 export const ragAgent = new Agent({
@@ -497,7 +515,7 @@ Initial vector similarity search can sometimes miss nuanced relevance. Re-rankin
 
 Here's how to use re-ranking:
 
-```ts showLineNumbers copy
+```ts
 import {
   rerankWithScorer as rerank,
   MastraAgentRelevanceScorer
@@ -535,16 +553,17 @@ The weights control how different factors influence the final ranking:
 - `vector`: Higher values favor the original vector similarity scores
 - `position`: Higher values help maintain the original ordering of results
 
-
-> **Note:** For semantic scoring to work properly during re-ranking, each result must include the text content in its `metadata.text` field.
+:::note
+For semantic scoring to work properly during re-ranking, each result must include the text content in its `metadata.text` field.
+:::
 
 You can also use other relevance score providers like Cohere or ZeroEntropy:
 
-```ts showLineNumbers copy
+```ts
 const relevanceProvider = new CohereRelevanceScorer("rerank-v3.5");
 ```
 
-```ts showLineNumbers copy
+```ts
 const relevanceProvider = new ZeroEntropyRelevanceScorer("zerank-1");
 ```
 
@@ -552,27 +571,4 @@ The re-ranked results combine vector similarity with semantic understanding to i
 
 For more details about re-ranking, see the [rerank()](/reference/v1/rag/rerankWithScorer) method.
 
-### Graph-based Retrieval
-
-For documents with complex relationships, graph-based retrieval can follow connections between chunks. This helps when:
-
-- Information is spread across multiple documents
-- Documents reference each other
-- You need to traverse relationships to find complete answers
-
-Example setup:
-
-```ts showLineNumbers copy
-const graphQueryTool = createGraphQueryTool({
-  vectorStoreName: "pgVector",
-  indexName: "embeddings",
-  model: new ModelRouterEmbeddingModel("openai/text-embedding-3-small"),
-  graphOptions: {
-    threshold: 0.7,
-  },
-});
-```
-
-For more details about graph-based retrieval, see the [GraphRAG](/reference/v1/rag/graph-rag) class and the [createGraphQueryTool()](/reference/v1/tools/graph-rag-tool) function.
-
-For an example of how to use the graph-based retrieval method, see the [Graph-based Retrieval](/examples/v1/rag/usage/graph-rag) example.
+For graph-based retrieval that follows connections between chunks, see the [GraphRAG](/docs/v1/rag/graph-rag) documentation.

package/.docs/raw/rag/vector-databases.mdx

@@ -1,6 +1,21 @@
 ---
 title: "Storing Embeddings in A Vector Database | RAG"
 description: Guide on vector storage options in Mastra, including embedded and dedicated vector databases for similarity search.
+packages:
+  - "@mastra/astra"
+  - "@mastra/chroma"
+  - "@mastra/core"
+  - "@mastra/couchbase"
+  - "@mastra/elasticsearch"
+  - "@mastra/lance"
+  - "@mastra/mongodb"
+  - "@mastra/opensearch"
+  - "@mastra/pg"
+  - "@mastra/pinecone"
+  - "@mastra/qdrant"
+  - "@mastra/s3vectors"
+  - "@mastra/upstash"
+  - "@mastra/vectorize"
 ---
 
 import Tabs from "@theme/Tabs";
@@ -15,10 +30,11 @@ After generating embeddings, you need to store them in a database that supports
 <Tabs>
   <TabItem value="mongodb" label="MongoDB">
 
-```ts title="vector-store.ts" showLineNumbers copy
+```ts title="vector-store.ts"
 import { MongoDBVector } from "@mastra/mongodb";
 
 const store = new MongoDBVector({
+  id: 'mongodb-vector',
   uri: process.env.MONGODB_URI,
   dbName: process.env.MONGODB_DATABASE,
 });
@@ -33,7 +49,7 @@ await store.upsert({
 });
 ```
 
-### Using MongoDB Atlas Vector search
+<h3>Using MongoDB Atlas Vector search</h3>
 
 For detailed setup instructions and best practices, see the [official MongoDB Atlas Vector Search documentation](https://www.mongodb.com/docs/atlas/atlas-vector-search/vector-search-overview/?utm_campaign=devrel&utm_source=third-party-content&utm_medium=cta&utm_content=mastra-docs).
 
@@ -41,7 +57,7 @@ For detailed setup instructions and best practices, see the [official MongoDB At
 
   <TabItem value="pg-vector" label="PgVector">
 
-```ts title="vector-store.ts" showLineNumbers copy
+```ts title="vector-store.ts"
 import { PgVector } from "@mastra/pg";
 
 const store = new PgVector({
@@ -61,7 +77,7 @@ await store.upsert({
 });
 ```
 
-### Using PostgreSQL with pgvector
+<h3>Using PostgreSQL with pgvector</h3>
 
 PostgreSQL with the pgvector extension is a good solution for teams already using PostgreSQL who want to minimize infrastructure complexity.
 For detailed setup instructions and best practices, see the [official pgvector repository](https://github.com/pgvector/pgvector).
@@ -70,7 +86,7 @@ For detailed setup instructions and best practices, see the [official pgvector r
 
   <TabItem value="pinecone" label="Pinecone">
 
-```ts title="vector-store.ts" showLineNumbers copy
+```ts title="vector-store.ts"
 import { PineconeVector } from "@mastra/pinecone";
 
 const store = new PineconeVector({
@@ -92,7 +108,7 @@ await store.upsert({
 
   <TabItem value="qdrant" label="Qdrant">
 
-```ts title="vector-store.ts" showLineNumbers copy
+```ts title="vector-store.ts"
 import { QdrantVector } from "@mastra/qdrant";
 
 const store = new QdrantVector({
@@ -117,7 +133,7 @@ await store.upsert({
 
   <TabItem value="chroma" label="Chroma">
 
-```ts title="vector-store.ts" showLineNumbers copy
+```ts title="vector-store.ts"
 import { ChromaVector } from "@mastra/chroma";
 
 // Running Chroma locally
@@ -147,10 +163,11 @@ await store.upsert({
 
   <TabItem value="astra" label="Astra">
 
-```ts title="vector-store.ts" showLineNumbers copy
+```ts title="vector-store.ts"
 import { AstraVector } from "@mastra/astra";
 
 const store = new AstraVector({
+  id: 'astra-vector',
   token: process.env.ASTRA_DB_TOKEN,
   endpoint: process.env.ASTRA_DB_ENDPOINT,
   keyspace: process.env.ASTRA_DB_KEYSPACE,
@@ -170,14 +187,14 @@ await store.upsert({
 
   </TabItem>
 
-  <TabItem value="libsql" label="LibSQL">
+  <TabItem value="libsql" label="libSQL">
 
-```ts title="vector-store.ts" showLineNumbers copy
+```ts title="vector-store.ts"
 import { LibSQLVector } from "@mastra/core/vector/libsql";
 
 const store = new LibSQLVector({
   id: 'libsql-vector',
-  connectionUrl: process.env.DATABASE_URL,
+  url: process.env.DATABASE_URL,
   authToken: process.env.DATABASE_AUTH_TOKEN, // Optional: for Turso cloud databases
 });
 
@@ -197,7 +214,7 @@ await store.upsert({
 
   <TabItem value="upstash" label="Upstash">
 
-```ts title="vector-store.ts" showLineNumbers copy
+```ts title="vector-store.ts"
 import { UpstashVector } from "@mastra/upstash";
 
 // In upstash they refer to the store as an index
@@ -220,10 +237,11 @@ await store.upsert({
 
   <TabItem value="cloudflare" label="Cloudflare">
 
-```ts title="vector-store.ts" showLineNumbers copy
+```ts title="vector-store.ts"
 import { CloudflareVector } from "@mastra/vectorize";
 
 const store = new CloudflareVector({
+  id: 'cloudflare-vector',
   accountId: process.env.CF_ACCOUNT_ID,
   apiToken: process.env.CF_API_TOKEN,
 });
@@ -242,10 +260,10 @@ await store.upsert({
 
   <TabItem value="opensearch" label="OpenSearch">
 
-```ts title="vector-store.ts" showLineNumbers copy
+```ts title="vector-store.ts"
 import { OpenSearchVector } from "@mastra/opensearch";
 
-const store = new OpenSearchVector({ url: process.env.OPENSEARCH_URL });
+const store = new OpenSearchVector({ id: "opensearch", node: process.env.OPENSEARCH_URL });
 
 await store.createIndex({
   indexName: "my-collection",
@@ -263,10 +281,10 @@ await store.upsert({
 
   <TabItem value="elasticsearch" label="ElasticSearch">
 
-```ts title="vector-store.ts" showLineNumbers copy
+```ts title="vector-store.ts"
 import { ElasticSearchVector } from "@mastra/elasticsearch";
 
-const store = new ElasticSearchVector({ url: process.env.ELASTICSEARCH_URL });
+const store = new ElasticSearchVector({ id: 'elasticsearch-vector', url: process.env.ELASTICSEARCH_URL });
 
 await store.createIndex({
   indexName: "my-collection",
@@ -283,10 +301,11 @@ await store.upsert({
   </TabItem>
   <TabItem value="couchbase" label="Couchbase">
 
-```ts title="vector-store.ts" showLineNumbers copy
+```ts title="vector-store.ts"
 import { CouchbaseVector } from "@mastra/couchbase";
 
 const store = new CouchbaseVector({
+  id: 'couchbase-vector',
   connectionString: process.env.COUCHBASE_CONNECTION_STRING,
   username: process.env.COUCHBASE_USERNAME,
   password: process.env.COUCHBASE_PASSWORD,
@@ -308,7 +327,7 @@ await store.upsert({
   </TabItem>
   <TabItem value="lancedb" label="Lance">
 
-```ts title="vector-store.ts" showLineNumbers copy
+```ts title="vector-store.ts"
 import { LanceVectorStore } from "@mastra/lance";
 
 const store = await LanceVectorStore.create("/path/to/db");
@@ -326,7 +345,7 @@ await store.upsert({
 });
 ```
 
-### Using LanceDB
+<h3>Using LanceDB</h3>
 
 LanceDB is an embedded vector database built on the Lance columnar format, suitable for local development or cloud deployment.
 For detailed setup instructions and best practices, see the [official LanceDB documentation](https://lancedb.github.io/lancedb/).
@@ -334,10 +353,11 @@ For detailed setup instructions and best practices, see the [official LanceDB do
   </TabItem>
   <TabItem value="s3vectors" label="S3 Vectors">
 
-```ts title="vector-store.ts" showLineNumbers copy
+```ts title="vector-store.ts"
 import { S3Vectors } from "@mastra/s3vectors";
 
 const store = new S3Vectors({
+  id: 's3-vectors',
   vectorBucketName: "my-vector-bucket",
   clientConfig: {
     region: "us-east-1",
@@ -368,7 +388,7 @@ Once initialized, all vector stores share the same interface for creating indexe
 
 Before storing embeddings, you need to create an index with the appropriate dimension size for your embedding model:
 
-```ts title="store-embeddings.ts" showLineNumbers copy
+```ts title="store-embeddings.ts"
 // Create an index with dimension 1536 (for text-embedding-3-small)
 await store.createIndex({
   indexName: "myCollection",
@@ -380,9 +400,11 @@ The dimension size must match the output dimension of your chosen embedding mode
 
 - OpenAI text-embedding-3-small: 1536 dimensions (or custom, e.g., 256)
 - Cohere embed-multilingual-v3: 1024 dimensions
-- Google `text-embedding-004`: 768 dimensions (or custom)
+- Google text-embedding-004: 768 dimensions (or custom)
 
-> **Important**: Index dimensions cannot be changed after creation. To use a different model, delete and recreate the index with the new dimension size.
+:::warning
+Index dimensions cannot be changed after creation. To use a different model, delete and recreate the index with the new dimension size.
+:::
 
 ### Naming Rules for Databases
 
@@ -443,7 +465,7 @@ Each vector database enforces specific naming conventions for indexes and collec
     - Example: `my_collection_123` is valid
     - Example: `my-collection` is not valid (contains hyphen)
   </TabItem>
-  <TabItem value="libsql" label="LibSQL">
+  <TabItem value="libsql" label="libSQL">
     Index names must:
     - Start with a letter or underscore
     - Contain only letters, numbers, and underscores
@@ -512,7 +534,7 @@ Each vector database enforces specific naming conventions for indexes and collec
 
 After creating an index, you can store embeddings along with their basic metadata:
 
-```ts title="store-embeddings.ts" showLineNumbers copy
+```ts title="store-embeddings.ts"
 // Store embeddings with their corresponding metadata
 await store.upsert({
   indexName: "myCollection", // index name
@@ -535,9 +557,11 @@ The upsert operation:
 
 Vector stores support rich metadata (any JSON-serializable fields) for filtering and organization. Since metadata is stored with no fixed schema, use consistent field naming to avoid unexpected query results.
 
-**Important**: Metadata is crucial for vector storage - without it, you'd only have numerical embeddings with no way to return the original text or filter results. Always store at least the source text as metadata.
+:::warning
+Metadata is crucial for vector storage - without it, you'd only have numerical embeddings with no way to return the original text or filter results. Always store at least the source text as metadata.
+:::
 
-```ts showLineNumbers copy
+```ts
 // Store embeddings with rich metadata for better organization and filtering
 await store.upsert({
   indexName: "myCollection",
@@ -577,7 +601,7 @@ When building RAG applications, you often need to clean up stale vectors when do
 
 The most common use case is deleting all vectors for a specific document when a user deletes it:
 
-```ts title="delete-vectors.ts" showLineNumbers copy
+```ts title="delete-vectors.ts"
 // Delete all vectors for a specific document
 await store.deleteVectors({
   indexName: "myCollection",
@@ -594,7 +618,7 @@ This is particularly useful when:
 
 You can also use complex filters to delete vectors matching multiple conditions:
 
-```ts title="delete-vectors-advanced.ts" showLineNumbers copy
+```ts title="delete-vectors-advanced.ts"
 // Delete all vectors for multiple documents
 await store.deleteVectors({
   indexName: "myCollection",
@@ -619,7 +643,7 @@ await store.deleteVectors({
 
 If you have specific vector IDs to delete, you can pass them directly:
 
-```ts title="delete-by-ids.ts" showLineNumbers copy
+```ts title="delete-by-ids.ts"
 // Delete specific vectors by their IDs
 await store.deleteVectors({
   indexName: "myCollection",

package/.docs/raw/reference/agents/agent.mdx

@@ -1,6 +1,8 @@
 ---
 title: "Reference: Agent Class | Agents"
 description: "Documentation for the `Agent` class in Mastra, which provides the foundation for creating AI agents with various capabilities."
+packages:
+  - "@mastra/core"
 ---
 
 # Agent Class
@@ -11,7 +13,7 @@ The `Agent` class is the foundation for creating AI agents in Mastra. It provide
 
 ### Basic string instructions
 
-```typescript title="src/mastra/agents/string-agent.ts" showLineNumbers copy
+```typescript title="src/mastra/agents/string-agent.ts"
 import { Agent } from "@mastra/core/agent";
 
 // String instructions
@@ -49,7 +51,7 @@ export const agent3 = new Agent({
 
 Use CoreSystemMessage format to access additional properties like `providerOptions` for provider-specific configurations:
 
-```typescript title="src/mastra/agents/core-message-agent.ts" showLineNumbers copy
+```typescript title="src/mastra/agents/core-message-agent.ts"
 import { Agent } from "@mastra/core/agent";
 
 export const agent = new Agent({
@@ -71,7 +73,7 @@ export const agent = new Agent({
 
 ### Multiple CoreSystemMessages
 
-```typescript title="src/mastra/agents/multi-message-agent.ts" showLineNumbers copy
+```typescript title="src/mastra/agents/multi-message-agent.ts"
 import { Agent } from "@mastra/core/agent";
 
 // This could be customizable based on the user
@@ -191,12 +193,6 @@ export const agent = new Agent({
       description:
         "Scoring configuration for runtime evaluation and telemetry. Can be static or dynamically provided.",
     },
-    {
-      name: "evals",
-      type: "Record<string, Metric>",
-      isOptional: true,
-      description: "Evaluation metrics for scoring agent responses.",
-    },
     {
       name: "memory",
       type: "MastraMemory | ({ requestContext: RequestContext }) => MastraMemory | Promise<MastraMemory>",
@@ -212,17 +208,24 @@ export const agent = new Agent({
     },
     {
       name: "inputProcessors",
-      type: "Processor[] | ({ requestContext: RequestContext }) => Processor[] | Promise<Processor[]>",
+      type: "(Processor | ProcessorWorkflow)[] | ({ requestContext: RequestContext }) => (Processor | ProcessorWorkflow)[] | Promise<(Processor | ProcessorWorkflow)[]>",
       isOptional: true,
       description:
-        "Input processors that can modify or validate messages before they are processed by the agent. Must implement the `processInput` function.",
+        "Input processors that can modify or validate messages before they are processed by the agent. Can be individual Processor objects or workflows created with `createWorkflow()` using ProcessorStepSchema.",
     },
     {
       name: "outputProcessors",
-      type: "Processor[] | ({ requestContext: RequestContext }) => Processor[] | Promise<Processor[]>",
+      type: "(Processor | ProcessorWorkflow)[] | ({ requestContext: RequestContext }) => (Processor | ProcessorWorkflow)[] | Promise<(Processor | ProcessorWorkflow)[]>",
+      isOptional: true,
+      description:
+        "Output processors that can modify or validate messages from the agent before they are sent to the client. Can be individual Processor objects or workflows.",
+    },
+    {
+      name: "maxProcessorRetries",
+      type: "number",
       isOptional: true,
       description:
-        "Output processors that can modify or validate messages from the agent, before it is sent to the client. Must implement either (or both) of the `processOutputResult` and `processOutputStream` functions.",
+        "Maximum number of times a processor can request retrying the LLM step.",
     },
   ]}
 />
@@ -233,7 +236,7 @@ export const agent = new Agent({
   content={[
     {
       name: "agent",
-      type: "Agent<TAgentId, TTools, TMetrics>",
+      type: "Agent<TAgentId, TTools>",
       description: "A new Agent instance with the specified configuration.",
     },
   ]}