@mastra/mcp-docs-server 1.2.15-alpha.7 → 1.2.15

package/.docs/docs/index.md

@@ -153,14 +153,14 @@ You can open [Studio](https://mastra.ai/docs/studio/overview) immediately, which
 
 Add Mastra to an existing project, or create a new app with your preferred framework:
 
-- [Next.js](https://mastra.ai/guides/getting-started/next-js)
-- [React](https://mastra.ai/guides/getting-started/vite-react)
-- [Astro](https://mastra.ai/guides/getting-started/astro)
-- [Express](https://mastra.ai/guides/getting-started/express)
-- [SvelteKit](https://mastra.ai/guides/getting-started/sveltekit)
-- [Hono](https://mastra.ai/guides/getting-started/hono)
-
-For other frameworks, see the [framework integration guides](https://mastra.ai/guides/getting-started/next-js).
+- [Next.js](https://mastra.ai/integrations/frameworks/next-js)
+- [React](https://mastra.ai/integrations/frameworks/vite-react)
+- [Astro](https://mastra.ai/integrations/frameworks/astro)
+- [Express](https://mastra.ai/integrations/frameworks/express)
+- [SvelteKit](https://mastra.ai/integrations/frameworks/sveltekit)
+- [Hono](https://mastra.ai/integrations/frameworks/hono)
+
+For other frameworks, see the [framework integration guides](https://mastra.ai/integrations/frameworks/next-js).
 
 ## Templates
 

package/.docs/docs/long-running-agents/durable-agents.md

@@ -4,7 +4,7 @@
 
 **Added in:** `@mastra/core@1.45.0`
 
-> **Warning:** Durable agents are currently in **beta**. APIs may change in future releases.
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
 
 A durable agent wraps a regular [`Agent`](https://mastra.ai/docs/agents/overview) so the agentic loop runs inside a workflow. Events flow through [PubSub](https://mastra.ai/docs/server/pubsub), which means a client can disconnect and reconnect without missing chunks. The run state is persisted, so it survives process restarts.
 
@@ -15,7 +15,7 @@ Use a durable agent when any of the following apply:
 - The client may drop and reconnect mid-stream (mobile, spotty networks, long-running calls).
 - The agentic loop may outlive a single HTTP request (background research, multi-step tool use).
 - You need an observe/reconnect API where a second client picks up a stream that a first client started.
-- You want [Inngest-powered execution](https://mastra.ai/guides/deployment/inngest) with step memoization, retries, and monitoring.
+- You want [Inngest-powered execution](https://mastra.ai/integrations/deploy/inngest) with step memoization, retries, and monitoring.
 
 For short-lived, request-scoped calls where the client stays connected, a regular `Agent` with `stream()` or `generate()` is simpler.
 
@@ -268,6 +268,6 @@ Mastra doesn't provide a distributed lease or lock yet. In multi-replica deploym
 - [DurableAgent reference](https://mastra.ai/reference/agents/durable-agent)
 - [`createInngestAgent()` reference](https://mastra.ai/reference/agents/inngest-agent)
 - [Background tasks](https://mastra.ai/docs/long-running-agents/background-tasks)
-- [Inngest deployment guide](https://mastra.ai/guides/deployment/inngest)
+- [Inngest deployment guide](https://mastra.ai/integrations/deploy/inngest)
 - [Agent overview](https://mastra.ai/docs/agents/overview)
 - [Worker overview](https://mastra.ai/docs/deployment/workers)

package/.docs/docs/long-running-agents/goals.md

@@ -4,7 +4,7 @@
 
 **Added in:** `@mastra/core@1.42.0`
 
-> **Beta:** The Goals feature is in beta stage and subject to breaking changes in minor versions until it graduates from its beta status.
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
 
 A goal is a durable, thread-scoped objective: a standing instruction the agent keeps working toward across loop iterations until a judge model decides it's satisfied or a run budget is exhausted.
 

package/.docs/docs/long-running-agents/schedules.md

@@ -4,7 +4,7 @@
 
 **Added in:** `@mastra/core@1.50.0`
 
-> **Beta:** This feature is in beta. Breaking changes may occur without a major version bump until the API is stable.
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
 
 A schedule runs an agent on a cron cadence. On each fire, Mastra sends a prompt to the agent, either as a [signal](https://mastra.ai/docs/long-running-agents/signals) into a thread or as a threadless [`agent.generate()`](https://mastra.ai/reference/agents/generate) run. Use schedules for recurring agent work such as daily summaries, periodic checks, or scheduled nudges into a conversation.
 

package/.docs/docs/long-running-agents/signal-providers.md

@@ -4,7 +4,7 @@
 
 **Added in:** `@mastra/core@1.39.0`
 
-> **Beta:** This feature is in beta. Breaking changes may occur without a major version bump until the API is stable.
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
 
 A signal provider monitors an external source, such as GitHub, Slack, continuous integration (CI), or your own API, and pushes [notification signals](https://mastra.ai/docs/long-running-agents/signals) into subscribed agent threads.
 
@@ -45,7 +45,7 @@ export const supportAgent = new Agent({
 })
 ```
 
-> **Note:** Notification delivery requires a storage adapter with notification support, such as [libSQL](https://mastra.ai/reference/storage/libsql), [PostgreSQL](https://mastra.ai/reference/storage/postgresql), or [MongoDB](https://mastra.ai/reference/storage/mongodb). Configure storage on the Mastra instance so `notify()` can store notification records.
+> **Note:** Notification delivery requires a storage adapter with notification support, such as [libSQL](https://mastra.ai/integrations/databases/libsql), [PostgreSQL](https://mastra.ai/integrations/databases/postgresql), or [MongoDB](https://mastra.ai/integrations/databases/mongodb). Configure storage on the Mastra instance so `notify()` can store notification records.
 
 ## Quickstart
 
@@ -200,20 +200,7 @@ A provider can support more than event ingestion. Add only the capabilities your
 - **Lifecycle hooks:** Override [`start()`](https://mastra.ai/reference/signals/signal-provider) for async setup and [`stop()`](https://mastra.ai/reference/signals/signal-provider) for cleanup. Call `super.stop()` when overriding `stop()` so the base provider can stop polling and clear its registry.
 - **Processors and tools:** Return processors from [`getInputProcessors()`](https://mastra.ai/reference/signals/signal-provider) or [`getOutputProcessors()`](https://mastra.ai/reference/signals/signal-provider), and return agent-callable tools from [`getTools()`](https://mastra.ai/reference/signals/signal-provider).
 
-The `@mastra/github-signals` package is a production signal provider that watches GitHub pull requests and notifies threads about comments, review state, continuous integration status, and merges. Use it as a reference for polling, durable subscriptions, tools, processors, and lifecycle hooks.
-
-```typescript
-import { Agent } from '@mastra/core/agent'
-import { GithubSignals } from '@mastra/github-signals'
-
-export const devAgent = new Agent({
-  id: 'dev-agent',
-  name: 'Dev Agent',
-  instructions: 'Help triage pull request activity.',
-  model: 'openai/gpt-5.6-sol',
-  signals: [new GithubSignals()],
-})
-```
+For a production provider that watches GitHub pull requests, see the [GitHub Channels integration](https://mastra.ai/integrations/channels/github).
 
 ## Related
 

package/.docs/docs/long-running-agents/signals.md

@@ -4,7 +4,7 @@
 
 **Added in:** `@mastra/core@1.39.0`
 
-> **Beta:** This feature is in beta. Breaking changes may occur without a major version bump until the API is stable.
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
 
 Signals are a way to interact with an agent through a thread. Instead of starting every interaction with `agent.stream()`, subscribe to a thread and send messages or signals. Mastra either wakes the agent when the thread is idle or drops input into the running agent loop, or alternatively queues input for the next turn.
 
@@ -147,7 +147,7 @@ Use XML-safe `tagName` and attribute names. They can contain letters, numbers, s
 
 #### Storage support
 
-Notification inbox storage is available in the storage adapters that support richer memory and signal workflows: [libSQL](https://mastra.ai/reference/storage/libsql), [PostgreSQL](https://mastra.ai/reference/storage/postgresql), and [MongoDB](https://mastra.ai/reference/storage/mongodb). These adapters expose notification records through `getStore('notifications')`.
+Notification inbox storage is available in the storage adapters that support richer memory and signal workflows: [libSQL](https://mastra.ai/integrations/databases/libsql), [PostgreSQL](https://mastra.ai/integrations/databases/postgresql), and [MongoDB](https://mastra.ai/integrations/databases/mongodb). These adapters expose notification records through `getStore('notifications')`.
 
 ### Send processor context
 

package/.docs/docs/mastra-platform/database.md

@@ -99,7 +99,7 @@ When a database is `ready`, the provider has finished provisioning and the platf
 
 ### Turso (LibSQL)
 
-Turso exposes two environment variables: `TURSO_DATABASE_URL` and `TURSO_AUTH_TOKEN`. The following example connects a [LibSQLStore](https://mastra.ai/reference/storage/libsql) using those variables.
+Turso exposes two environment variables: `TURSO_DATABASE_URL` and `TURSO_AUTH_TOKEN`. The following example connects a [LibSQLStore](https://mastra.ai/integrations/databases/libsql) using those variables.
 
 ```ts
 import { LibSQLStore } from '@mastra/libsql'
@@ -139,7 +139,7 @@ bun add @mastra/libsql@latest
 
 ### PostgreSQL
 
-PostgreSQL exposes a single `DATABASE_URL` connection string. The following example connects a [PostgresStore](https://mastra.ai/reference/storage/postgresql) using that variable.
+PostgreSQL exposes a single `DATABASE_URL` connection string. The following example connects a [PostgresStore](https://mastra.ai/integrations/databases/postgresql) using that variable.
 
 ```ts
 import { PostgresStore } from '@mastra/pg'

package/.docs/docs/mastra-platform/deploy.md

@@ -132,6 +132,33 @@ mastra deploy --env staging --env-file .env.staging
 
 To change variables on a running service without a redeploy, update them in the dashboard and run [`mastra env restart`](https://mastra.ai/reference/cli/mastra).
 
+## Private npm packages
+
+Projects that depend on packages from a private registry install them during the deploy using the standard `NPM_TOKEN` contract.
+
+1. Store a read-only registry token as `NPM_TOKEN` on the project or environment through the dashboard.
+
+2. Commit a token-free `.npmrc` that points your scope at the registry and reads the token from the environment:
+
+   ```ini
+   @your-org:registry=https://npm.pkg.github.com
+   //npm.pkg.github.com/:_authToken=${NPM_TOKEN}
+   ```
+
+   Keep the `${NPM_TOKEN}` reference literal. The package manager resolves it at install time, so the token itself never lands in your repository.
+
+3. Deploy as usual:
+
+   ```bash
+   mastra deploy
+   ```
+
+In a monorepo, a `.npmrc` in your project directory takes precedence over one at the repository root.
+
+`NPM_TOKEN` is available during dependency installation. Mastra redacts its value from the Mastra source-build logs that it streams. The generated Dockerfile receives it as a build argument, so the runtime image stays free of the token. `NPM_TOKEN` is also injected into the running service as a regular environment variable, so treat it as a secret your application can read.
+
+Projects without a private-registry `.npmrc` need no changes. When your `.npmrc` references `${NPM_TOKEN}`, set the variable or the dependency install fails.
+
 ## Project resolution
 
 Every deploy resolves its target project in this order:

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

@@ -8,7 +8,7 @@ You get a stable API endpoint, environment variable management, custom domain su
 
 > **Note:** `mastra server deploy` is the earlier split deploy path. New projects should use the unified [`mastra deploy`](https://mastra.ai/docs/mastra-platform/deploy) command, which adds preflight validation, environments, and CLI-managed databases.
 
-> **Note:** Server deploy provisions hosted storage automatically. If you override storage with [LibSQLStore](https://mastra.ai/reference/storage/libsql) and a file URL, switch to a remotely hosted database because Mastra platform uses an ephemeral filesystem.
+> **Note:** Server deploy provisions hosted storage automatically. If you override storage with [LibSQLStore](https://mastra.ai/integrations/databases/libsql) and a file URL, switch to a remotely hosted database because Mastra platform uses an ephemeral filesystem.
 
 ## Quickstart
 

package/.docs/docs/mastra-platform/trace-intelligence.md

@@ -56,12 +56,9 @@ The flow chart connects themes in adjacent trace signal columns:
 
 The flow shows association, not causation or execution order. For example, a ribbon between a Goal and an Outcome means that both themes occurred in the same traces. It doesn't show that the goal caused the outcome.
 
-### Distributions, Other, and Noise
+### Other and Noise
 
-The cards below the flow show each trace signal's theme distribution:
-
-- **Trace count**: The number of distinct traces assigned to a theme in the selected snapshot.
-- **Stage share**: The percentage of analyzed traces for that trace signal assigned to the theme.
+Each node shows its trace count: the number of distinct traces assigned to that theme in the selected snapshot. A theme's details also state its share, for example "28 of 70 traces in this snapshot (40%)".
 
 Studio shows the most common themes for each trace signal type. It may combine smaller themes into **Other** to preserve totals without overcrowding the chart.
 
@@ -69,26 +66,25 @@ Studio shows the most common themes for each trace signal type. It may combine s
 
 ### Snapshots
 
-A snapshot is a moving analysis window over a set of traces. Snapshots can overlap, so don't add their trace counts together. Compare trace count and stage share together because traffic volume can change between windows.
+A snapshot is a moving analysis window over a set of traces. Snapshots can overlap, so don't add their trace counts together. Compare a theme's trace count and its share of the snapshot together because traffic volume can change between windows.
 
 A theme can persist, disappear, split, merge, or return across snapshots. Treat theme names and descriptions as generated summaries, not fixed taxonomies.
 
 ## Use the Trace Intelligence page
 
 1. Use the **Agent** selector to switch between agents with available analysis. An agent doesn't appear until its first themes are ready.
-2. Select a theme in the flow to filter every column to traces containing that theme.
-3. Select **View theme details** to inspect its description, trace count, stage share, generated examples, and history.
+2. Select a theme in the flow to open its details and filter every column to traces containing that theme.
+3. The details panel shows the theme's description, its share of the snapshot, paged example summaries, and a trend of its trace count over time.
 4. Select **Clear filter** to restore the complete flow.
 
 You can also:
 
-- Select a theme in a distribution card to open its details and generated example summaries.
-- Select **Noise** in a distribution card to inspect its distribution and generated example summaries.
-- Drag the distribution cards to reorder the trace signal columns and see a different relationship perspective.
+- Select **Noise** in the flow to inspect its share and generated example summaries.
+- Drag the column headers above the chart to reorder the trace signal columns and see a different relationship perspective.
 - Use the timeline to select a snapshot, or select **Play** to watch themes change over time.
-- Open a theme's history to see whether it persisted and how its coverage changed.
+- Switch to **Compare** to see which themes grew, shrank, entered the range, or left the range between two points in time, or **Lifelines** to follow each theme's share across the whole selected range.
 
-Filtering the flow by a theme is unavailable for snapshots with more than 2,000 traces. Choose another snapshot or clear the active filter to return to the full flow. Theme and Noise details remain available from the distribution cards.
+Filtering the flow by a theme is unavailable for snapshots with more than 2,000 traces. Selecting a theme still opens its details there without filtering the flow.
 
 ## Troubleshooting
 

package/.docs/docs/mcp/overview.md

@@ -202,6 +202,48 @@ export const mastra = new Mastra({
 
 Visit the [`MCPServer` reference](https://mastra.ai/reference/tools/mcp-server) for prompts, resources, transports, and other server options.
 
+### Publish a stdio server package
+
+Package a server that uses the standard input/output (stdio) transport when you want clients to run it locally through a command such as `npx`. Create a separate executable entry point that starts the server:
+
+```typescript
+#!/usr/bin/env node
+import { mcpServer } from './server'
+
+mcpServer.startStdio().catch(error => {
+  console.error('Failed to start MCP server:', error)
+  process.exit(1)
+})
+```
+
+Build the entry point as an executable Node.js file, then point the package's `bin` field to that output. Include the built file in the published package and keep the shebang as its first line:
+
+```json
+{
+  "bin": {
+    "my-mcp-server": "dist/stdio.js"
+  },
+  "files": ["dist"]
+}
+```
+
+After publishing the package, configure clients to run it by package name:
+
+```typescript
+import { MCPClient } from '@mastra/mcp'
+
+const mcpClient = new MCPClient({
+  servers: {
+    myServer: {
+      command: 'npx',
+      args: ['-y', '@your-org/my-mcp-server@1.0.0'],
+    },
+  },
+})
+```
+
+Visit the [npm package publishing documentation](https://docs.npmjs.com/creating-and-publishing-scoped-public-packages) for package naming, authentication, and publication commands.
+
 ## Build MCP Apps
 
 The [MCP Apps extension](https://github.com/modelcontextprotocol/ext-apps) lets MCP tools serve interactive HTML interfaces through `ui://` resources. Mastra Studio renders these apps in sandboxed iframes on tool pages and in agent chat.

package/.docs/docs/memory/memory-processors.md

@@ -313,11 +313,11 @@ Both scenarios are safe - guardrails prevent inappropriate content from being pe
 
 Some storage providers enforce record size limits that base64-encoded file attachments can exceed:
 
-| Provider                                                           | Record size limit |
-| ------------------------------------------------------------------ | ----------------- |
-| [DynamoDB](https://mastra.ai/reference/storage/dynamodb)           | 400 KB            |
-| [Convex](https://mastra.ai/reference/storage/convex)               | 1 MiB             |
-| [Cloudflare D1](https://mastra.ai/reference/storage/cloudflare-d1) | 1 MiB             |
+| Provider                                                                | Record size limit |
+| ----------------------------------------------------------------------- | ----------------- |
+| [DynamoDB](https://mastra.ai/integrations/databases/dynamodb)           | 400 KB            |
+| [Convex](https://mastra.ai/integrations/databases/convex)               | 1 MiB             |
+| [Cloudflare D1](https://mastra.ai/integrations/databases/cloudflare-d1) | 1 MiB             |
 
 PostgreSQL, MongoDB, and libSQL have higher limits and are usually unaffected.
 

package/.docs/docs/memory/message-history.md

@@ -6,13 +6,13 @@ Message history is the most basic and important form of memory. It gives the LLM
 
 You can also retrieve message history to display past conversations in your UI.
 
-> **Info:** Each message belongs to a thread (the conversation) and a resource (the user or entity it's associated with). See [Threads and resources](#threads-and-resources) for more detail.
+> **Note:** Each message belongs to a thread (the conversation) and a resource (the user or entity it's associated with). See [Threads and resources](#threads-and-resources) for more detail.
 
 > **Warning:** When you use memory with a client application, send **only the new message** from the client instead of the full conversation history.
 >
 > Sending the full history is redundant because Mastra loads messages from storage, and it can cause message ordering bugs when client-side timestamps conflict with stored timestamps.
 >
-> For an AI SDK example, see [Using Mastra Memory](https://mastra.ai/guides/build-your-ui/ai-sdk-ui).
+> For an AI SDK example, see [Using Mastra Memory](https://mastra.ai/integrations/agentic-ui/ai-sdk-ui).
 
 ## Threads and resources
 
@@ -113,7 +113,7 @@ await agent.stream('Hello', {
 })
 ```
 
-> **Info:** Threads and messages are created automatically when you call `agent.generate()` or `agent.stream()`, but you can also create them manually with [`createThread()`](https://mastra.ai/reference/memory/createThread) and [`saveMessages()`](https://mastra.ai/reference/memory/memory-class).
+> **Note:** Threads and messages are created automatically when you call `agent.generate()` or `agent.stream()`, but you can also create them manually with [`createThread()`](https://mastra.ai/reference/memory/createThread) and [`saveMessages()`](https://mastra.ai/reference/memory/memory-class).
 
 You can use this history in two ways:
 

package/.docs/docs/memory/multi-user-threads.md

@@ -156,7 +156,7 @@ const memory = new Memory({
 })
 ```
 
-OM requires a storage adapter that supports it: `@mastra/libsql`, `@mastra/pg`, or `@mastra/mongodb`.
+OM requires a storage adapter that supports it: `@mastra/libsql`, `@mastra/pg`, `@mastra/mongodb`, or `@mastra/oracledb`.
 
 > **Note:** If you switch the Observer to a weaker model and see facts collapse to a generic `User`, use [`observation.instruction`](https://mastra.ai/reference/memory/observational-memory) to teach the Observer how to read the `<turn>` tag.
 

package/.docs/docs/memory/observational-memory.md

@@ -92,9 +92,9 @@ See [configuration options](https://mastra.ai/reference/memory/observational-mem
 >
 > Observational memory still relies on stored conversation history. Sending the full history is redundant and can cause message ordering bugs when client-side timestamps conflict with stored timestamps.
 >
-> For an AI SDK example, see [Using Mastra Memory](https://mastra.ai/guides/build-your-ui/ai-sdk-ui).
+> For an AI SDK example, see [Using Mastra Memory](https://mastra.ai/integrations/agentic-ui/ai-sdk-ui).
 
-> **Note:** OM currently only supports `@mastra/pg`, `@mastra/libsql`, `@mastra/mysql`, `@mastra/mongodb`, and `@mastra/convex` storage adapters. It uses background agents for managing memory. When no model is set, the default model is `google/gemini-2.5-flash`.
+> **Note:** OM currently only supports `@mastra/pg`, `@mastra/libsql`, `@mastra/mysql`, `@mastra/mongodb`, `@mastra/convex`, and `@mastra/oracledb` storage adapters. It uses background agents for managing memory. When no model is set, the default model is `google/gemini-2.5-flash`.
 
 ## Temporal gap markers
 

package/.docs/docs/memory/semantic-recall.md

@@ -148,6 +148,7 @@ Each vector store page below includes installation instructions, configuration p
 - [libSQL](https://mastra.ai/reference/vectors/libsql)
 - [MongoDB](https://mastra.ai/reference/vectors/mongodb)
 - [OpenSearch](https://mastra.ai/reference/vectors/opensearch)
+- [OracleDB](https://mastra.ai/reference/vectors/oracledb)
 - [Pinecone](https://mastra.ai/reference/vectors/pinecone)
 - [PostgreSQL](https://mastra.ai/reference/vectors/pg)
 - [Qdrant](https://mastra.ai/reference/vectors/qdrant)
@@ -180,7 +181,7 @@ const agent = new Agent({
 })
 ```
 
-> **Note:** `scope: 'resource'` is supported by the LibSQL, PostgreSQL, MongoDB, and Upstash storage adapters.
+> **Note:** `scope: 'resource'` is supported by the LibSQL, OracleDB, PostgreSQL, MongoDB, and Upstash storage adapters.
 
 ### Metadata filtering
 

package/.docs/docs/memory/working-memory.md

@@ -129,6 +129,7 @@ Resource-scoped working memory requires specific storage adapters that support t
 
 - **libSQL** (`@mastra/libsql`)
 - **PostgreSQL** (`@mastra/pg`)
+- **OracleDB** (`@mastra/oracledb`)
 - **Upstash** (`@mastra/upstash`)
 - **MongoDB** (`@mastra/mongodb`)
 

package/.docs/docs/observability/integrations/exporters/mastra-platform.md

@@ -186,7 +186,7 @@ When you deploy with Mastra Studio, set **Deployment → Service Name** to a sta
 
 ## Performance
 
-> **Info:** MastraPlatformExporter uses batching to optimize network usage. Events are buffered and sent in batches, reducing overhead while maintaining near real-time visibility.
+> **Note:** MastraPlatformExporter uses batching to optimize network usage. Events are buffered and sent in batches, reducing overhead while maintaining near real-time visibility.
 
 ### Batching behavior
 

package/.docs/docs/observability/integrations/exporters/mastra-storage.md

@@ -6,7 +6,7 @@ The `MastraStorageExporter` persists traces to your configured storage backend,
 
 > **Note:** `MastraStorageExporter` was previously called `DefaultExporter`. The original `DefaultExporter` class is still exported from `@mastra/observability` for backward compatibility, but it's deprecated. New code should use `MastraStorageExporter`.
 
-> **Production Observability:** Observability data can quickly overwhelm general-purpose databases in production. For high-traffic applications, route the observability storage domain to [ClickHouse](https://mastra.ai/reference/storage/clickhouse) through [composite storage](https://mastra.ai/reference/storage/composite). See [Production Recommendations](#production-recommendations) for details.
+> **Production Observability:** Observability data can quickly overwhelm general-purpose databases in production. For high-traffic applications, route the observability storage domain to [ClickHouse](https://mastra.ai/integrations/databases/clickhouse) through [composite storage](https://mastra.ai/reference/storage/composite). See [Production Recommendations](#production-recommendations) for details.
 
 ## Configuration
 
@@ -116,24 +116,25 @@ If you set the strategy to `'auto'`, the `MastraStorageExporter` automatically s
 
 ### Providers with Observability Support
 
-| Storage Provider                                                 | Preferred Strategy | Supported Strategies            | Recommended Use                       |
-| ---------------------------------------------------------------- | ------------------ | ------------------------------- | ------------------------------------- |
-| **[ClickHouse](https://mastra.ai/reference/storage/clickhouse)** | insert-only        | insert-only                     | Production (high-volume)              |
-| **[PostgreSQL](https://mastra.ai/reference/storage/postgresql)** | batch-with-updates | batch-with-updates, insert-only | Production (low volume)               |
-| **[MSSQL](https://mastra.ai/reference/storage/mssql)**           | batch-with-updates | batch-with-updates, insert-only | Production (low volume)               |
-| **[MongoDB](https://mastra.ai/reference/storage/mongodb)**       | batch-with-updates | batch-with-updates, insert-only | Production (low volume)               |
-| **[libSQL](https://mastra.ai/reference/storage/libsql)**         | batch-with-updates | batch-with-updates, insert-only | Default storage, good for development |
+| Storage Provider                                                      | Preferred Strategy | Supported Strategies            | Recommended Use                       |
+| --------------------------------------------------------------------- | ------------------ | ------------------------------- | ------------------------------------- |
+| **[ClickHouse](https://mastra.ai/integrations/databases/clickhouse)** | insert-only        | insert-only                     | Production (high-volume)              |
+| **[PostgreSQL](https://mastra.ai/integrations/databases/postgresql)** | batch-with-updates | batch-with-updates, insert-only | Production (low volume)               |
+| **[MSSQL](https://mastra.ai/integrations/databases/mssql)**           | batch-with-updates | batch-with-updates, insert-only | Production (low volume)               |
+| **[MongoDB](https://mastra.ai/integrations/databases/mongodb)**       | batch-with-updates | batch-with-updates, insert-only | Production (low volume)               |
+| **[OracleDB](https://mastra.ai/integrations/databases/oracledb)**     | batch-with-updates | batch-with-updates, insert-only | Production (low volume)               |
+| **[libSQL](https://mastra.ai/integrations/databases/libsql)**         | batch-with-updates | batch-with-updates, insert-only | Default storage, good for development |
 
 ### Providers without Observability Support
 
 The following storage providers **don't support** the observability domain. If you're using one of these providers and need observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider:
 
-- [Convex](https://mastra.ai/reference/storage/convex)
-- [DynamoDB](https://mastra.ai/reference/storage/dynamodb)
-- [Cloudflare D1](https://mastra.ai/reference/storage/cloudflare-d1)
-- [Cloudflare Durable Objects](https://mastra.ai/reference/storage/cloudflare)
-- [Upstash](https://mastra.ai/reference/storage/upstash)
-- [LanceDB](https://mastra.ai/reference/storage/lance)
+- [Convex](https://mastra.ai/integrations/databases/convex)
+- [DynamoDB](https://mastra.ai/integrations/databases/dynamodb)
+- [Cloudflare D1](https://mastra.ai/integrations/databases/cloudflare-d1)
+- [Cloudflare Durable Objects](https://mastra.ai/integrations/databases/cloudflare-kv)
+- [Upstash](https://mastra.ai/integrations/databases/upstash)
+- [LanceDB](https://mastra.ai/integrations/databases/lancedb)
 
 ### Strategy Benefits
 
@@ -147,7 +148,7 @@ Observability data grows quickly in production environments. A single agent inte
 
 ### Recommended: ClickHouse for High-Volume Production
 
-[ClickHouse](https://mastra.ai/reference/storage/clickhouse) is a columnar database designed for high-volume analytics workloads. It's the recommended choice for production observability because:
+[ClickHouse](https://mastra.ai/integrations/databases/clickhouse) is a columnar database designed for high-volume analytics workloads. It's the recommended choice for production observability because:
 
 - **Optimized for writes**: Handles millions of inserts per second
 - **Efficient compression**: Reduces storage costs for trace data

package/.docs/docs/observability/integrations/overview.md

@@ -30,8 +30,8 @@ Exporters send observability data to a destination:
 
 Bridges connect Mastra to an existing distributed tracing context:
 
-- [OpenTelemetry bridge](https://mastra.ai/docs/observability/integrations/bridges/otel): Integrate Mastra with an existing OpenTelemetry trace.
-- [Datadog bridge](https://mastra.ai/docs/observability/integrations/bridges/datadog): Send Mastra traces to Datadog and its LLM Observability product.
+- [OpenTelemetry bridge](https://mastra.ai/integrations/observability/opentelemetry): Integrate Mastra with an existing OpenTelemetry trace.
+- [Datadog bridge](https://mastra.ai/integrations/observability/datadog): Send Mastra traces to Datadog and its LLM Observability product.
 
 ## Processors
 
@@ -44,4 +44,4 @@ Processors transform or redact spans before export:
 - [Configuration](https://mastra.ai/docs/observability/overview)
 - [Tracing](https://mastra.ai/docs/observability/tracing/overview)
 - [Mastra Storage](https://mastra.ai/docs/observability/integrations/exporters/mastra-storage)
-- [OpenTelemetry bridge](https://mastra.ai/docs/observability/integrations/bridges/otel)
+- [OpenTelemetry bridge](https://mastra.ai/integrations/observability/opentelemetry)

package/.docs/docs/server/auth/fga.md

@@ -300,4 +300,4 @@ The actor signal is trusted input, so construct it server-side:
 
 - [`IFGAProvider` reference](https://mastra.ai/reference/auth/fga)
 - [Authentication overview](https://mastra.ai/docs/server/auth)
-- [WorkOS authentication](https://mastra.ai/docs/server/auth/workos)
+- [WorkOS authentication](https://mastra.ai/integrations/auth/workos)

package/.docs/docs/server/auth/simple-auth.md

@@ -171,4 +171,4 @@ SimpleAuth is designed for simplicity, not production security:
 - No cryptographic verification
 - All tokens must be known at startup
 
-For production applications, consider using [JWT](https://mastra.ai/docs/server/auth/jwt), [Clerk](https://mastra.ai/docs/server/auth/clerk), [Auth0](https://mastra.ai/docs/server/auth/auth0), or another identity provider.
+For production applications, consider using [JWT](https://mastra.ai/docs/server/auth/jwt), [Clerk](https://mastra.ai/integrations/auth/clerk), [Auth0](https://mastra.ai/integrations/auth/auth0), or another identity provider.

package/.docs/docs/server/auth/workers.md

@@ -2,6 +2,8 @@
 
 # Workers
 
+> **Beta:** Breaking changes may occur without a major version bump until the API is stable.
+
 When workers run in separate processes from the API, they communicate over HTTP. The orchestration worker calls the API's step execution endpoint to run workflow steps on the API server. Push-mode PubSub brokers (like Google Cloud Pub/Sub in push mode) can also deliver events directly to the API's event endpoint. This is a distinct integration path from pull-mode workers, which pull events from the broker themselves. Both HTTP endpoints require authentication when an auth provider is configured.
 
 ## How it works

package/.docs/docs/server/auth.md

@@ -17,6 +17,8 @@ Authentication is optional. If no auth is configured, all routes and Studio are
 
 See [Custom API Routes](https://mastra.ai/docs/server/custom-api-routes) for controlling authentication on custom endpoints. Visit the [Studio Auth docs](https://mastra.ai/docs/studio/auth) for more on securing your Studio deployment.
 
+> **Warning:** The default auth configuration protects `/api/*` and treats `/api`, `/api/auth/*` as public. When you set a custom `server.apiPrefix`, those defaults no longer match and built-in routes fall outside the protected pattern. Update `server.auth.protected` and `server.auth.public` to reference your new prefix.
+
 > **Note:** Authentication for Studio is currently supported by the following providers: Simple Auth, JWT, WorkOS, Better Auth, and Google.
 
 ## Available providers
@@ -28,14 +30,14 @@ See [Custom API Routes](https://mastra.ai/docs/server/custom-api-routes) for con
 
 ### Third-party integrations
 
-- [Auth0](https://mastra.ai/docs/server/auth/auth0)
-- [Better Auth](https://mastra.ai/docs/server/auth/better-auth)
-- [Clerk](https://mastra.ai/docs/server/auth/clerk)
-- [Firebase](https://mastra.ai/docs/server/auth/firebase)
-- [Google](https://mastra.ai/docs/server/auth/google)
-- [Okta](https://mastra.ai/docs/server/auth/okta)
-- [Supabase](https://mastra.ai/docs/server/auth/supabase)
-- [WorkOS](https://mastra.ai/docs/server/auth/workos)
+- [Auth0](https://mastra.ai/integrations/auth/auth0)
+- [Better Auth](https://mastra.ai/integrations/auth/better-auth)
+- [Clerk](https://mastra.ai/integrations/auth/clerk)
+- [Firebase](https://mastra.ai/integrations/auth/firebase)
+- [Google](https://mastra.ai/integrations/auth/google)
+- [Okta](https://mastra.ai/integrations/auth/okta)
+- [Supabase](https://mastra.ai/integrations/auth/supabase)
+- [WorkOS](https://mastra.ai/integrations/auth/workos)
 
 ### Advanced
 

package/.docs/docs/server/custom-adapters.md

@@ -6,7 +6,7 @@ Create a custom adapter when the prebuilt server adapters (Hono, Express, Fastif
 
 A custom adapter translates between Mastra's route definitions and your framework's routing system. You'll implement methods that register middleware, handle requests, and send responses using your framework's APIs.
 
-> **Info:** Use any of these prebuilt server adapters:
+> **Note:** Use any of these prebuilt server adapters:
 >
 > - [@mastra/hono](https://mastra.ai/reference/server/hono-adapter)
 > - [@mastra/express](https://mastra.ai/reference/server/express-adapter)

package/.docs/docs/server/custom-api-routes.md

@@ -35,6 +35,41 @@ curl http://localhost:4111/my-custom-route
 
 Each route's handler receives the Hono `Context`. Within the handler you can access the `Mastra` instance to fetch or call agents and workflows.
 
+## Schema validation
+
+Use [`createRoute()`](https://mastra.ai/reference/server/create-route) in `apiRoutes` to parse and validate path parameters, query parameters, and request bodies with Zod. The schemas also infer the handler parameters and generate OpenAPI metadata.
+
+```typescript
+import { Mastra } from '@mastra/core'
+import { createRoute } from '@mastra/server/server-adapter'
+import { z } from 'zod'
+
+const createItemRoute = createRoute({
+  method: 'POST',
+  path: '/items',
+  responseType: 'json',
+  bodySchema: z.object({
+    name: z.string().min(1),
+  }),
+  responseSchema: z.object({
+    id: z.string(),
+    name: z.string(),
+  }),
+  handler: async ({ name }) => ({
+    id: crypto.randomUUID(),
+    name,
+  }),
+})
+
+export const mastra = new Mastra({
+  server: {
+    apiRoutes: [createItemRoute],
+  },
+})
+```
+
+By default, Mastra returns a `400` response when validation fails. The `onValidationError` callback can override the status and response body. Validated values and the `Mastra` server context are passed directly to the handler.
+
 ## Middleware
 
 To add route-specific middleware pass a `middleware` array when calling `registerApiRoute()`.