@mastra/mcp-docs-server 1.0.0-beta.13 → 1.0.0-beta.14

package/.docs/raw/agents/agent-memory.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Agent Memory | Agents"
-description: Learn how to add memory to agents to store conversation history and maintain context across interactions.
+description: Learn how to add memory to agents to store message history and maintain context across interactions.
 ---
 
 import Steps from "@site/src/components/Steps";
@@ -8,9 +8,9 @@ import StepItem from "@site/src/components/StepItem";
 
 # Agent memory
 
-Agents use memory to maintain context across interactions. LLMs are stateless and don't retain information between calls, so agents need memory to track conversation history and recall relevant information.
+Agents use memory to maintain context across interactions. LLMs are stateless and don't retain information between calls, so agents need memory to track message history and recall relevant information.
 
-Mastra agents can be configured to store conversation history, with optional [working memory](../memory/working-memory) to maintain recent context or [semantic recall](../memory/semantic-recall) to retrieve past messages based on meaning.
+Mastra agents can be configured to store message history, with optional [working memory](../memory/working-memory) to maintain recent context or [semantic recall](../memory/semantic-recall) to retrieve past messages based on meaning.
 
 ## When to use memory
 
@@ -20,13 +20,13 @@ Use memory when your agent needs to maintain multi-turn conversations that refer
 
 To enable memory in Mastra, install the `@mastra/memory` package along with a storage provider.
 
-```bash npm2yarn copy
+```bash npm2yarn
 npm install @mastra/memory@beta @mastra/libsql@beta
 ```
 
 ## Storage providers
 
-Memory requires a storage provider to persist conversation history, including user messages and agent responses. For more details on available providers and how storage works in Mastra, see the [Storage](/docs/v1/memory/storage/overview) documentation.
+Memory requires a storage provider to persist message history, including user messages and agent responses. For more details on available providers and how storage works in Mastra, see the [Storage](/docs/v1/memory/storage) documentation.
 
 ## Configuring memory
 
@@ -35,14 +35,13 @@ Memory requires a storage provider to persist conversation history, including us
 
 Enable memory by creating a `Memory` instance and passing it to the agent’s `memory` option.
 
-```typescript {6-9} title="src/mastra/agents/memory-agent.ts" copy
+```typescript {7-11} title="src/mastra/agents/memory-agent.ts"
 import { Agent } from "@mastra/core/agent";
 import { Memory } from "@mastra/memory";
 
 export const memoryAgent = new Agent({
   id: 'memory-agent',
   name: 'Memory Agent',
-  // ...
   memory: new Memory({
     options: {
       lastMessages: 20,
@@ -51,9 +50,9 @@ export const memoryAgent = new Agent({
 });
 ```
 
-:::note
+:::info
 
-See the [Memory Class](/reference/v1/memory/memory-class) docs for a full list of configuration options.
+Visit [Memory Class](/reference/v1/memory/memory-class) for a full list of configuration options.
 
 :::
 
@@ -63,12 +62,11 @@ See the [Memory Class](/reference/v1/memory/memory-class) docs for a full list o
 
 Add a storage provider to your main Mastra instance to enable memory across all configured agents.
 
-```typescript {6-8} title="src/mastra/index.ts" copy
+```typescript {5-8} title="src/mastra/index.ts"
 import { Mastra } from "@mastra/core";
 import { LibSQLStore } from "@mastra/libsql";
 
 export const mastra = new Mastra({
-  // ..
   storage: new LibSQLStore({
     id: 'mastra-storage',
     url: ":memory:",
@@ -76,9 +74,9 @@ export const mastra = new Mastra({
 });
 ```
 
-:::note
+:::info
 
-See the [LibSQL Storage](/reference/v1/storage/libsql) docs for a full list of configuration options.
+Visit [libSQL Storage](/reference/v1/storage/libsql) for a full list of configuration options.
 
 :::
 
@@ -87,7 +85,7 @@ See the [LibSQL Storage](/reference/v1/storage/libsql) docs for a full list of c
 
 Alternatively, add storage directly to an agent’s memory to keep data separate or use different providers per agent.
 
-```typescript {7-10} title="src/mastra/agents/memory-agent.ts" copy
+```typescript {9-12} title="src/mastra/agents/memory-agent.ts"
 import { Agent } from "@mastra/core/agent";
 import { Memory } from "@mastra/memory";
 import { LibSQLStore } from "@mastra/libsql";
@@ -95,7 +93,6 @@ import { LibSQLStore } from "@mastra/libsql";
 export const memoryAgent = new Agent({
   id: 'memory-agent',
   name: 'Memory Agent',
-  // ...
   memory: new Memory({
     storage: new LibSQLStore({
       id: 'mastra-storage',
@@ -105,16 +102,16 @@ export const memoryAgent = new Agent({
 });
 ```
 
-## Conversation history
+## Message history
 
-Include a `memory` object with both `resource` and `thread` to track conversation history during agent calls.
+Include a `memory` object with both `resource` and `thread` to track message history during agent calls.
 
 - `resource`: A stable identifier for the user or entity.
 - `thread`: An ID that isolates a specific conversation or session.
 
 These fields tell the agent where to store and retrieve context, enabling persistent, thread-aware memory across a conversation.
 
-```typescript {5-6}
+```typescript {4-7}
 const response = await memoryAgent.generate(
   "Remember my favorite color is blue.",
   {
@@ -128,7 +125,7 @@ const response = await memoryAgent.generate(
 
 To recall information stored in memory, call the agent with the same `resource` and `thread` values used in the original conversation.
 
-```typescript {3-4}
+```typescript {2-5}
 const response = await memoryAgent.generate("What's my favorite color?", {
   memory: {
     resource: "user-123",
@@ -143,23 +140,18 @@ To learn more about memory see the [Memory](../memory/overview) documentation.
 
 Use [RequestContext](/docs/v1/server/request-context) to access request-specific values. This lets you conditionally select different memory or storage configurations based on the context of the request.
 
-```typescript title="src/mastra/agents/memory-agent.ts" showLineNumbers
+```typescript title="src/mastra/agents/memory-agent.ts"
 export type UserTier = {
   "user-tier": "enterprise" | "pro";
 };
 
-const premiumMemory = new Memory({
-  // ...
-});
+const premiumMemory = new Memory();
 
-const standardMemory = new Memory({
-  // ...
-});
+const standardMemory = new Memory();
 
 export const memoryAgent = new Agent({
   id: 'memory-agent',
   name: 'Memory Agent',
-  // ...
   memory: ({ requestContext }) => {
     const userTier = requestContext.get("user-tier") as UserTier["user-tier"];
 
@@ -168,9 +160,9 @@ export const memoryAgent = new Agent({
 });
 ```
 
-:::note
+:::info
 
-See [Request Context](/docs/v1/server/request-context) docs for more information.
+Visit [Request Context](/docs/v1/server/request-context) for more information.
 
 :::
 
@@ -178,5 +170,5 @@ See [Request Context](/docs/v1/server/request-context) docs for more information
 
 - [Working Memory](../memory/working-memory)
 - [Semantic Recall](../memory/semantic-recall)
-- [Threads and Resources](../memory/threads-and-resources)
+- [Storage](../memory/storage)
 - [Request Context](/docs/v1/server/request-context)

package/.docs/raw/agents/guardrails.mdx

@@ -22,7 +22,7 @@ Use processors for content moderation, prompt injection prevention, response san
 
 Import and instantiate the relevant processor class, and pass it to your agent’s configuration using either the `inputProcessors` or `outputProcessors` option:
 
-```typescript {2,8-16} title="src/mastra/agents/moderated-agent.ts" showLineNumbers copy
+```typescript {2,9-17} title="src/mastra/agents/moderated-agent.ts"
 import { Agent } from "@mastra/core/agent";
 import { ModerationProcessor } from "@mastra/core/processors";
 
@@ -51,13 +51,12 @@ Input processors are applied before user messages reach the language model. They
 
 The `UnicodeNormalizer` is an input processor that cleans and normalizes user input by unifying Unicode characters, standardizing whitespace, and removing problematic symbols, allowing the LLM to better understand user messages.
 
-```typescript {8-11} title="src/mastra/agents/normalized-agent.ts" showLineNumbers copy
+```typescript {7-10} title="src/mastra/agents/normalized-agent.ts"
 import { UnicodeNormalizer } from "@mastra/core/processors";
 
 export const normalizedAgent = new Agent({
   id: "normalized-agent",
   name: "Normalized Agent",
-  // ...
   inputProcessors: [
     new UnicodeNormalizer({
       stripControlChars: true,
@@ -67,19 +66,22 @@ export const normalizedAgent = new Agent({
 });
 ```
 
-> See [UnicodeNormalizer](/reference/v1/processors/unicode-normalizer) for a full list of configuration options.
+:::info
+
+Visit [UnicodeNormalizer](/reference/v1/processors/unicode-normalizer) for a full list of configuration options.
+
+:::
 
 ### Preventing prompt injection
 
 The `PromptInjectionDetector` is an input processor that scans user messages for prompt injection, jailbreak attempts, and system override patterns. It uses an LLM to classify risky input and can block or rewrite it before it reaches the model.
 
-```typescript {8-13} title="src/mastra/agents/secure-agent.ts" showLineNumbers copy
+```typescript {7-12} title="src/mastra/agents/secure-agent.ts"
 import { PromptInjectionDetector } from "@mastra/core/processors";
 
 export const secureAgent = new Agent({
   id: "secure-agent",
   name: "Secure Agent",
-  // ...
   inputProcessors: [
     new PromptInjectionDetector({
       model: "openrouter/openai/gpt-oss-safeguard-20b",
@@ -91,19 +93,22 @@ export const secureAgent = new Agent({
 });
 ```
 
-> See [PromptInjectionDetector](/reference/v1/processors/prompt-injection-detector) for a full list of configuration options.
+:::info
+
+Visit [PromptInjectionDetector](/reference/v1/processors/prompt-injection-detector) for a full list of configuration options.
+
+:::
 
 ### Detecting and translating language
 
 The `LanguageDetector` is an input processor that detects and translates user messages into a target language, enabling multilingual support while maintaining consistent interaction. It uses an LLM to identify the language and perform the translation.
 
-```typescript {8-13} title="src/mastra/agents/multilingual-agent.ts" showLineNumbers copy
+```typescript {7-12} title="src/mastra/agents/multilingual-agent.ts"
 import { LanguageDetector } from "@mastra/core/processors";
 
 export const multilingualAgent = new Agent({
   id: "multilingual-agent",
   name: "Multilingual Agent",
-  // ...
   inputProcessors: [
     new LanguageDetector({
       model: "openrouter/openai/gpt-oss-safeguard-20b",
@@ -115,7 +120,11 @@ export const multilingualAgent = new Agent({
 });
 ```
 
-> See [LanguageDetector](/reference/v1/processors/language-detector) for a full list of configuration options.
+:::info
+
+Visit [LanguageDetector](/reference/v1/processors/language-detector) for a full list of configuration options.
+
+:::
 
 ## Output processors
 
@@ -125,13 +134,12 @@ Output processors are applied after the language model generates a response, but
 
 The `BatchPartsProcessor` is an output processor that combines multiple stream parts before emitting them to the client. This reduces network overhead and improves the user experience by consolidating small chunks into larger batches.
 
-```typescript {8-12} title="src/mastra/agents/batched-agent.ts" showLineNumbers copy
+```typescript {7-11} title="src/mastra/agents/batched-agent.ts"
 import { BatchPartsProcessor } from "@mastra/core/processors";
 
 export const batchedAgent = new Agent({
   id: "batched-agent",
   name: "Batched Agent",
-  // ...
   outputProcessors: [
     new BatchPartsProcessor({
       batchSize: 5,
@@ -142,19 +150,22 @@ export const batchedAgent = new Agent({
 });
 ```
 
-> See [BatchPartsProcessor](/reference/v1/processors/batch-parts-processor) for a full list of configuration options.
+:::info
+
+Visit [BatchPartsProcessor](/reference/v1/processors/batch-parts-processor) for a full list of configuration options.
+
+:::
 
 ### Limiting token usage
 
 The `TokenLimiterProcessor` is an output processor that limits the number of tokens in model responses. It helps manage cost and performance by truncating or blocking messages when the limit is exceeded.
 
-```typescript {8-12} title="src/mastra/agents/limited-agent.ts" showLineNumbers copy
+```typescript {7-11} title="src/mastra/agents/limited-agent.ts"
 import { TokenLimiterProcessor } from "@mastra/core/processors";
 
 export const limitedAgent = new Agent({
   id: "limited-agent",
   name: "Limited Agent",
-  // ...
   outputProcessors: [
     new TokenLimiterProcessor({
       limit: 1000,
@@ -165,13 +176,17 @@ export const limitedAgent = new Agent({
 });
 ```
 
-> See [TokenLimiterProcessor](/reference/v1/processors/token-limiter-processor) for a full list of configuration options.
+:::info
+
+Visit [TokenLimiterProcessor](/reference/v1/processors/token-limiter-processor) for a full list of configuration options.
+
+:::
 
 ### Scrubbing system prompts
 
 The `SystemPromptScrubber` is an output processor that detects and redacts system prompts or other internal instructions from model responses. It helps prevent unintended disclosure of prompt content or configuration details that could introduce security risks. It uses an LLM to identify and redact sensitive content based on configured detection types.
 
-```typescript {7-16} title="src/mastra/agents/scrubbed-agent.ts" copy showLineNumbers
+```typescript {7-16} title="src/mastra/agents/scrubbed-agent.ts"
 import { SystemPromptScrubber } from "@mastra/core/processors";
 
 const scrubbedAgent = new Agent({
@@ -192,7 +207,11 @@ const scrubbedAgent = new Agent({
 });
 ```
 
-> See [SystemPromptScrubber](/reference/v1/processors/system-prompt-scrubber) for a full list of configuration options.
+:::info
+
+Visit [SystemPromptScrubber](/reference/v1/processors/system-prompt-scrubber) for a full list of configuration options.
+
+:::
 
 :::note
 When streaming responses over HTTP, Mastra redacts sensitive request data (system prompts, tool definitions, API keys) from stream chunks at the server level by default. See [Stream data redaction](/docs/v1/server/mastra-server#stream-data-redaction) for details.
@@ -206,13 +225,12 @@ Hybrid processors can be applied either before messages are sent to the language
 
 The `ModerationProcessor` is a hybrid processor that detects inappropriate or harmful content across categories like hate, harassment, and violence. It can be used to moderate either user input or model output, depending on where it's applied. It uses an LLM to classify the message and can block or rewrite it based on your configuration.
 
-```typescript {8-13,16-18} title="src/mastra/agents/moderated-agent.ts" showLineNumbers copy
+```typescript {7-12,15} title="src/mastra/agents/moderated-agent.ts"
 import { ModerationProcessor } from "@mastra/core/processors";
 
 export const moderatedAgent = new Agent({
   id: "moderated-agent",
   name: "Moderated Agent",
-  // ...
   inputProcessors: [
     new ModerationProcessor({
       model: "openrouter/openai/gpt-oss-safeguard-20b",
@@ -222,26 +240,27 @@ export const moderatedAgent = new Agent({
     }),
   ],
   outputProcessors: [
-    new ModerationProcessor({
-      // ...
-    }),
+    new ModerationProcessor(),
   ],
 });
 ```
 
-> See [ModerationProcessor](/reference/v1/processors/moderation-processor) for a full list of configuration options.
+:::info
+
+Visit [ModerationProcessor](/reference/v1/processors/moderation-processor) for a full list of configuration options.
+
+:::
 
 ### Detecting and redacting PII
 
 The `PIIDetector` is a hybrid processor that detects and removes personally identifiable information such as emails, phone numbers, and credit cards. It can redact either user input or model output, depending on where it's applied. It uses an LLM to identify sensitive content based on configured detection types.
 
-```typescript {8-15,18-20} title="src/mastra/agents/private-agent.ts" showLineNumbers copy
+```typescript {7-14,17} title="src/mastra/agents/private-agent.ts"
 import { PIIDetector } from "@mastra/core/processors";
 
 export const privateAgent = new Agent({
   id: "private-agent",
   name: "Private Agent",
-  // ...
   inputProcessors: [
     new PIIDetector({
       model: "openrouter/openai/gpt-oss-safeguard-20b",
@@ -253,14 +272,16 @@ export const privateAgent = new Agent({
     }),
   ],
   outputProcessors: [
-    new PIIDetector({
-      // ...
-    }),
+    new PIIDetector(),
   ],
 });
 ```
 
-> See [PIIDetector](/reference/v1/processors/pii-detector) for a full list of configuration options.
+:::info
+
+Visit [PIIDetector](/reference/v1/processors/pii-detector) for a full list of configuration options.
+
+:::
 
 ## Applying multiple processors
 
@@ -274,7 +295,7 @@ A typical order might be:
 
 The order affects behavior, so arrange processors to suit your goals.
 
-```typescript title="src/mastra/agents/test-agent.ts" showLineNumbers copy
+```typescript title="src/mastra/agents/test-agent.ts"
 import {
   UnicodeNormalizer,
   ModerationProcessor,
@@ -285,20 +306,11 @@ import {
 export const testAgent = new Agent({
   id: "test-agent",
   name: "Test Agent",
-  // ...
   inputProcessors: [
-    new UnicodeNormalizer({
-      //...
-    }),
-    new PromptInjectionDetector({
-      // ...
-    }),
-    new PIIDetector({
-      // ...
-    }),
-    new ModerationProcessor({
-      // ...
-    }),
+    new UnicodeNormalizer(),
+    new PromptInjectionDetector(),
+    new PIIDetector(),
+    new ModerationProcessor(),
   ],
 });
 ```
@@ -309,16 +321,14 @@ Many of the built-in processors support a `strategy` parameter that controls how
 
 Most strategies allow the request to continue without interruption. When `block` is used, the processor calls its internal `abort()` function, which immediately stops the request and prevents any subsequent processors from running.
 
-```typescript {10} title="src/mastra/agents/private-agent.ts" showLineNumbers copy
+```typescript {8} title="src/mastra/agents/private-agent.ts"
 import { PIIDetector } from "@mastra/core/processors";
 
 export const privateAgent = new Agent({
   id: "private-agent",
   name: "Private Agent",
-  // ...
   inputProcessors: [
     new PIIDetector({
-      // ...
       strategy: "block",
     }),
   ],
@@ -333,7 +343,7 @@ For example, if an agent uses the `PIIDetector` with `strategy: "block"` and the
 
 #### `.generate()` example
 
-```typescript showLineNumbers
+```typescript
 const result = await agent.generate(
   "Is this credit card number valid?: 4543 1374 5089 4332",
 );
@@ -350,7 +360,7 @@ if (result.tripwire) {
 
 #### `.stream()` example
 
-```typescript showLineNumbers
+```typescript
 const stream = await agent.stream(
   "Is this credit card number valid?: 4543 1374 5089 4332",
 );
@@ -373,7 +383,7 @@ PII detected. Types: credit-card
 
 Processors can request that the LLM retry its response with feedback. This is useful for implementing quality checks:
 
-```typescript showLineNumbers
+```typescript
 export class QualityChecker implements Processor {
   id = "quality-checker";
 

package/.docs/raw/agents/networks.mdx

@@ -23,7 +23,7 @@ Mastra agent networks operate using these principles:
 
 An agent network is built around a top-level routing agent that delegates tasks to agents, workflows, and tools defined in its configuration. Memory is configured on the routing agent using the `memory` option, and `instructions` define the agent's routing behavior.
 
-```typescript {22-23,26,29} title="src/mastra/agents/routing-agent.ts" showLineNumbers copy
+```typescript {22-23,26,29} title="src/mastra/agents/routing-agent.ts"
 import { Agent } from "@mastra/core/agent";
 import { Memory } from "@mastra/memory";
 import { LibSQLStore } from "@mastra/libsql";
@@ -71,25 +71,23 @@ When configuring a Mastra agent network, each primitive (agent, workflow, or too
 
 Each agent in a network should include a clear `description` that explains what the agent does.
 
-```typescript title="src/mastra/agents/research-agent.ts" showLineNumbers
+```typescript title="src/mastra/agents/research-agent.ts"
 export const researchAgent = new Agent({
   id: "research-agent",
   name: "Research Agent",
   description: `This agent gathers concise research insights in bullet-point form.
     It's designed to extract key facts without generating full
     responses or narrative content.`,
-  // ...
 });
 ```
 
-```typescript title="src/mastra/agents/writing-agent.ts" showLineNumbers
+```typescript title="src/mastra/agents/writing-agent.ts"
 export const writingAgent = new Agent({
   id: "writing-agent",
   name: "Writing Agent",
   description: `This agent turns researched material into well-structured
     written content. It produces full-paragraph reports with no bullet points,
     suitable for use in articles, summaries, or blog posts.`,
-  // ...
 });
 ```
 
@@ -97,7 +95,7 @@ export const writingAgent = new Agent({
 
 Workflows in a network should include a `description` to explain their purpose, along with `inputSchema` and `outputSchema` to describe the expected data.
 
-```typescript title="src/mastra/workflows/city-workflow.ts" showLineNumbers
+```typescript title="src/mastra/workflows/city-workflow.ts"
 export const cityWorkflow = createWorkflow({
   id: "city-workflow",
   description: `This workflow handles city-specific research tasks.
@@ -110,7 +108,6 @@ export const cityWorkflow = createWorkflow({
   outputSchema: z.object({
     text: z.string(),
   }),
-  //...
 });
 ```
 
@@ -118,7 +115,7 @@ export const cityWorkflow = createWorkflow({
 
 Tools in a network should include a `description` to explain their purpose, along with `inputSchema` and `outputSchema` to describe the expected data.
 
-```typescript title="src/mastra/tools/weather-tool.ts" showLineNumbers
+```typescript title="src/mastra/tools/weather-tool.ts"
 export const weatherTool = createTool({
   id: "weather-tool",
   description: ` Retrieves current weather information using the wttr.in API.
@@ -131,7 +128,6 @@ export const weatherTool = createTool({
   outputSchema: z.object({
     weather: z.string(),
   }),
-  // ...
 });
 ```
 
@@ -143,7 +139,7 @@ Call a Mastra agent network using `.network()` with a user message. The method r
 
 In this example, the network interprets the message and would route the request to both the `researchAgent` and `writingAgent` to generate a complete response.
 
-```typescript showLineNumbers copy
+```typescript
 const result = await routingAgent.network(
   "Tell me three cool ways to use Mastra",
 );
@@ -179,7 +175,7 @@ network-execution-event-step-finish
 
 In this example, the routing agent recognizes the city name in the message and runs the `cityWorkflow`. The workflow defines steps that call the `researchAgent` to gather facts, then the `writingAgent` to generate the final text.
 
-```typescript showLineNumbers copy
+```typescript
 const result = await routingAgent.network(
   "Tell me some historical facts about London",
 );
@@ -212,7 +208,7 @@ network-execution-event-step-finish
 
 In this example, the routing agent skips the `researchAgent`, `writingAgent`, and `cityWorkflow`, and calls the `weatherTool` directly to complete the task.
 
-```typescript showLineNumbers copy
+```typescript
 const result = await routingAgent.network("What's the weather in London?");
 
 for await (const chunk of result) {