@mastra/mcp-docs-server 1.3.8-alpha.0 → 1.3.8-alpha.11

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

@@ -29,7 +29,7 @@ A supplied `ProviderHistoryCompat` is used instead of the default. The default i
 
 The placement decides which half of the processor works:
 
-- **Reactive rules need `errorProcessors`.** On the standard loop, `processAPIError` runs from any of the three lists, so an input-processor registration does repair the message list, but the retry it asks for is only honored when the agent has a retry budget. With the default error processors in place the resolved list is non-empty, so a safety cap of `3` applies. The budget is left `undefined` only when the caller runs with no error processors at all (`errorProcessorDefaults: false` with none configured) and doesn't set `maxProcessorRetries` explicitly. Registered only as an input processor in that no-budget state, a reactive rule repairs the history and the request still fails. On the durable path the API-error pass additionally requires a non-empty `errorProcessors` list. If that list is empty, an input-processor registration can't trigger reactive recovery there at all, even with `maxProcessorRetries` set.
+- **Reactive rules need `errorProcessors`.** An agent wraps its input processors in a single processor workflow, and the API-error pass only runs `processAPIError` on error processors, so an instance registered only in `inputProcessors` never runs its reactive rules.
 - **Preemptive rules run from either list.** `processLLMRequest` runs over the input processors and over the resolved error processors, so a `ProviderHistoryCompat` in `errorProcessors` gets its prompt rewrites as well as its reactive recovery. An instance registered in `inputProcessors` runs once, in its input position.
 
 Registering in `errorProcessors` alone, as the example above does, covers both halves. Double registration can't cause a double retry: the runner stops at the first processor that asks for one, and each reactive rule bails once `retryCount` is above zero, so a repaired turn is attempted exactly once more.

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

@@ -28,7 +28,7 @@ export const agent = new Agent({
 
 Set `maxProcessorRetries` alongside a `maxRetries` above `3`, because the agent stops error-processor retries at `3` when it's unset. See [Retry limits](#retry-limits).
 
-To run only the processors you configure, with none of the defaults merged in, set `errorProcessorDefaults: false`. Without an `errorProcessors` list, the agent then runs no error processors. An empty `errorProcessors` list still gets the defaults. Supplying your own processor for all three default ids replaces every default with your own implementation.
+To run only the processors you configure, with none of the defaults merged in, set `errorProcessorDefaults: false`. Without an `errorProcessors` list, the agent then runs only the error processors its memory contributes, if any. When memory contributes one, the retry cap of `3` applies. See [Error processors are enabled by default](https://mastra.ai/docs/agents/processors). An empty agent-level `errorProcessors` list still gets the defaults. A call-time `errorProcessors: []` replaces the resolved list instead, though the agent still runs the error processors its memory contributes. Supplying your own processor for all three default ids replaces every default with your own implementation.
 
 ## How it works
 

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

@@ -41,7 +41,7 @@ const toolSearch = new ToolSearchProcessor({
 
 **options.search.autoLoad** (`boolean`): When true, tools returned by search\_tools are activated immediately as part of the search. The load\_tool meta-tool is not exposed, collapsing the two-step search then load flow into a single search step. Discovered tools become available on the next turn. Keep topK conservative since every match is activated.
 
-**options.storage** (`'in-memory' | 'context'`): Where loaded-tool state lives. 'in-memory' (default) tracks loaded tools in an in-memory map per thread with TTL cleanup (see ttl); state is lost on restart and anonymous requests share a 'default' entry. 'context' derives loaded state from the conversation messages — a tool is loaded while a search\_tools/load\_tool result naming it remains in the messages; it is restart-safe, requires no memory, and de-loads automatically once that result is no longer present in the messages. The 'context' store is opt-in.
+**options.storage** (`'in-memory' | 'context'`): Where loaded-tool state lives. 'in-memory' (default) tracks loaded tools in an in-memory map per thread with TTL cleanup (see ttl); state is lost on restart and anonymous requests share a 'default' entry. 'context' derives loaded state from the conversation messages — a tool is loaded while a search\_tools/load\_tool result naming it remains in the messages; it works without memory (same-process only, and only for requests with a real thread ID), survives a restart whenever the messages are available again (memory with message history, or the caller resending the conversation), and de-loads automatically once that result is no longer present in the messages. The 'context' store is opt-in.
 
 **options.ttl** (`number`): Time-to-live for in-memory thread state, in milliseconds. Only applies to the default storage: 'in-memory' store; after this duration of inactivity thread state is cleaned up. Set to 0 to disable cleanup. Ignored by the 'context' store.
 
@@ -238,8 +238,8 @@ Use `clearState`, `clearAllState`, `getStateStats`, and `cleanupNow` to inspect
 
 Loaded state is derived from the conversation messages: a tool is loaded while a `search_tools` or `load_tool` result naming it remains in the messages. This mode:
 
-- Requires no memory configuration.
-- Is restart-safe: the durable record is the persisted message history.
+- Works without memory configuration. Without memory, loaded tools are kept for the current process only, and only for requests with a real thread ID; anonymous requests retain nothing between calls unless the caller resends the relevant messages.
+- Survives a restart whenever the messages are available again: from memory with message history, or because the caller resends the conversation. Without memory, a restart restores only what's in the messages the caller sends.
 - De-loads a tool automatically once that result is no longer present in the messages.
 
 ```typescript

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

@@ -16,6 +16,7 @@ Server adapters register these routes when you call `server.init()`. All routes
 | `POST` | `/api/agents/:agentId/stream`                 | Stream agent response                                                   |
 | `POST` | `/api/agents/:agentId/send-message`           | Send a user message to an active or idle thread                         |
 | `POST` | `/api/agents/:agentId/queue-message`          | Queue a user message for the next thread turn                           |
+| `POST` | `/api/agents/:agentId/queue-signal`           | Queue a typed signal for the next thread turn                           |
 | `POST` | `/api/agents/:agentId/signals`                | Send a lower-level signal to an active or idle thread                   |
 | `POST` | `/api/agents/:agentId/threads/subscribe`      | Subscribe to a thread stream                                            |
 | `POST` | `/api/agents/:agentId/threads/abort`          | Abort a thread, optionally clearing pending signals                     |
@@ -83,6 +84,8 @@ GET /api/agents/my-agent?versionId=abc123
 
 Use `POST /api/agents/:agentId/send-message` to send a user message to the active agent loop or wake an idle thread. Use `POST /api/agents/:agentId/queue-message` when the active run should finish before Mastra starts a follow-up run.
 
+To queue a typed signal with the same ordering, use `POST /api/agents/:agentId/queue-signal` with a `signal` field in place of `message`. The `signal` field takes the same shape as `POST /api/agents/:agentId/signals`.
+
 Both routes accept the same request body:
 
 ```typescript
@@ -542,12 +545,20 @@ Returns the persisted experiment result row.
 
 ## MCP
 
-| Method | Path                               | Description        |
-| ------ | ---------------------------------- | ------------------ |
-| `GET`  | `/api/mcp/servers`                 | List MCP servers   |
-| `GET`  | `/api/mcp/servers/:serverId/tools` | List server tools  |
-| `POST` | `/api/mcp/:serverId`               | MCP HTTP transport |
-| `GET`  | `/api/mcp/:serverId/sse`           | MCP SSE transport  |
+| Method | Path                                       | Description              |
+| ------ | ------------------------------------------ | ------------------------ |
+| `GET`  | `/api/mcp/v0/servers`                      | List MCP servers         |
+| `GET`  | `/api/mcp/v0/servers/:id`                  | Get server details       |
+| `GET`  | `/api/mcp/:serverId/tools`                 | List server tools        |
+| `GET`  | `/api/mcp/:serverId/tools/:toolId`         | Get tool details         |
+| `POST` | `/api/mcp/:serverId/tools/:toolId/execute` | Execute a tool           |
+| `GET`  | `/api/mcp/:serverId/resources`             | List server resources    |
+| `POST` | `/api/mcp/:serverId/resources/read`        | Read a resource          |
+| `ALL`  | `/api/mcp/:serverId/mcp`                   | MCP HTTP transport       |
+| `ALL`  | `/api/mcp/:serverId/sse`                   | Legacy MCP SSE transport |
+| `POST` | `/api/mcp/:serverId/messages`              | Legacy MCP SSE messages  |
+
+All MCP routes declare `requiresAuth: true`. Authentication is enforced only when `server.auth` is configured. Paths use the default `/api` prefix. The legacy SSE routes return `404` for MCP v2 servers.
 
 ## Responses API
 

package/.docs/reference/storage/retention.md

@@ -12,18 +12,21 @@ Retention covers **growth tables** only: tables that accumulate rows unbounded a
 
 Storage adapters use the shared core retention contract for `prune()`, or a database-native mechanism when that better matches the backend.
 
-| Adapter              | Mechanism               | Retention support                                                                                                                                                                      |
-| -------------------- | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| libSQL               | `prune()`               | All supported growth domains                                                                                                                                                           |
-| PostgreSQL           | `prune()`               | All supported growth domains. vNext observability drops expired partitions or chunks                                                                                                   |
-| MongoDB              | `prune()` or native TTL | All supported growth domains. Native TTL indexes are also available                                                                                                                    |
-| DuckDB               | `prune()`               | Observability spans, metrics, logs, scores, and feedback                                                                                                                               |
-| MySQL                | `prune()`               | Observability spans                                                                                                                                                                    |
-| Microsoft SQL Server | `prune()`               | Observability spans                                                                                                                                                                    |
-| Oracle Database      | `prune()`               | Observability spans and logs                                                                                                                                                           |
-| Amazon Aurora DSQL   | `prune()`               | Observability spans                                                                                                                                                                    |
-| Google Cloud Spanner | `prune()`               | Observability spans, plus metrics when metrics storage is enabled                                                                                                                      |
-| ClickHouse           | Native TTL              | Observability spans, metrics, logs, scores, and feedback. When all five signals have finite retention, deletion-request records expire after the longest signal retention plus 30 days |
+| Adapter                           | Mechanism               | Retention support                                                                                                                                                                      |
+| --------------------------------- | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| libSQL                            | `prune()`               | All supported growth domains                                                                                                                                                           |
+| PostgreSQL                        | `prune()`               | All supported growth domains. vNext observability drops expired partitions or chunks                                                                                                   |
+| MongoDB                           | `prune()` or native TTL | All supported growth domains. Native TTL indexes are also available                                                                                                                    |
+| DuckDB                            | `prune()`               | Observability spans, metrics, logs, scores, and feedback                                                                                                                               |
+| MySQL                             | `prune()`               | Observability spans, durable agent run fencing (`runOwnership`, `runFences`)                                                                                                           |
+| Microsoft SQL Server              | `prune()`               | Observability spans, durable agent run fencing (`runOwnership`, `runFences`)                                                                                                           |
+| Oracle Database                   | `prune()`               | Observability spans and logs, durable agent run fencing (`runOwnership`, `runFences`)                                                                                                  |
+| Amazon Aurora DSQL                | `prune()`               | Observability spans, durable agent run fencing (`runOwnership`, `runFences`)                                                                                                           |
+| Google Cloud Spanner              | `prune()`               | Observability spans, plus metrics when metrics storage is enabled. Durable agent run fencing (`runOwnership`, `runFences`)                                                             |
+| DynamoDB                          | `prune()`               | Durable agent run fencing (`runOwnership`, `runFences`)                                                                                                                                |
+| Convex                            | `prune()`               | Durable agent run fencing (`runOwnership`, `runFences`). Redeploy your Convex functions after upgrading                                                                                |
+| Cloudflare D1 and Durable Objects | `prune()`               | Durable agent run fencing (`runOwnership`, `runFences`)                                                                                                                                |
+| ClickHouse                        | Native TTL              | Observability spans, metrics, logs, scores, and feedback. When all five signals have finite retention, deletion-request records expire after the longest signal retention plus 30 days |
 
 ## Storage-specific maintenance
 

package/.docs/reference/streaming/ChunkType.md

@@ -330,6 +330,10 @@ Signals the start of a processing step.
 
 **payload.messageId** (`string`): Optional message identifier
 
+**payload.modelId** (`string`): ID of the model this step calls. After a fallback, the fallback model.
+
+**payload.provider** (`string`): Provider of the model this step calls
+
 **payload.request** (`object`): Request information including body and other data
 
 **payload.warnings** (`LanguageModelV2CallWarning[]`): Any warnings from the language model call

package/.docs/reference/tools/create-tool.md

@@ -61,6 +61,8 @@ The first `execute` parameter is the validated value from `inputSchema`. Destruc
 
 **requireApproval** (`boolean`): When true, the tool requires explicit approval before execution. The agent will emit a tool-call-approval chunk and pause until approved or declined.
 
+**beforeApproval** (`(input, context) => void | { proceed: false; output: unknown } | Promise<...>`): Runs before the approval gate for calls that require approval, receiving the input validated against inputSchema (defaults applied) and a context with toolCallId, toolName, requestContext, and workspace. Return { proceed: false, output } to reject the call: the agent does not pause for approval, execute is not called, and output is returned to the model as the tool result. Return nothing to continue to the approval gate. Not run when the input fails inputSchema validation (execute reports the validation error after approval) or when resuming after an approval decision. If the hook throws, the error is logged and the call proceeds to the approval gate, so keep validating inside execute as well.
+
 **mcp** (`MCPToolProperties`): MCP-specific properties for tools exposed via Model Context Protocol. Includes annotations (tool behavior hints like title, readOnlyHint, destructiveHint, idempotentHint, openWorldHint) and \_meta (arbitrary metadata passed through to MCP clients).
 
 **requestContextSchema** (`StandardJSONSchemaV1`): A Standard JSON Schema for validating request context values. When provided, the context is validated before execute() runs, returning an error object if validation fails.

package/.docs/reference/tools/mcp-server.md

@@ -456,7 +456,7 @@ getToolInfo(toolId: string): ToolInfo | undefined
 
 ### `executeTool()`
 
-Runs a tool without a protocol client, which is how the Mastra REST route `POST /api/mcp/:serverId/tools/:toolId/execute` and Studio invoke tools.
+Runs a tool without a protocol client, which is how the Mastra REST route `POST /api/mcp/:serverId/tools/:toolId/execute` and Studio invoke tools. See [authentication for registered MCP routes](https://mastra.ai/docs/guides/mcp-authentication-authorization) and the [MCP routes reference](https://mastra.ai/reference/server/routes).
 
 ```typescript
 async executeTool(

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mastra/mcp-docs-server",
-  "version": "1.3.8-alpha.0",
+  "version": "1.3.8-alpha.11",
   "description": "MCP server for accessing Mastra.ai documentation, changelogs, and news.",
   "type": "module",
   "main": "dist/index.js",
@@ -26,8 +26,8 @@
     "@mastra/mcp-legacy": "npm:@mastra/mcp@^1.18.0",
     "local-pkg": "^1.1.2",
     "zod": "^4.6.4",
-    "@mastra/core": "1.78.0-alpha.0",
-    "@mastra/mcp": "^2.4.0"
+    "@mastra/core": "1.78.0-alpha.8",
+    "@mastra/mcp": "^2.4.1-alpha.1"
   },
   "devDependencies": {
     "@hono/node-server": "^2.0.0",
@@ -43,9 +43,9 @@
     "tsx": "^4.23.1",
     "typescript": "^7.0.2",
     "vitest": "4.1.11",
-    "@internal/types-builder": "0.0.118",
     "@internal/lint": "0.0.143",
-    "@mastra/core": "1.78.0-alpha.0"
+    "@mastra/core": "1.78.0-alpha.8",
+    "@internal/types-builder": "0.0.118"
   },
   "homepage": "https://mastra.ai",
   "repository": {