@mastra/mcp-docs-server 1.2.15-alpha.20 → 1.2.15-alpha.22

package/.docs/{guides → reference}/rag/retrieval.md

@@ -534,4 +534,4 @@ The re-ranked results combine vector similarity with semantic understanding to i
 
 For more details about re-ranking, see the [rerank()](https://mastra.ai/reference/rag/rerankWithScorer) method.
 
-For graph-based retrieval that follows connections between chunks, see the [GraphRAG](https://mastra.ai/guides/rag/graph-rag) documentation.
+For graph-based retrieval that follows connections between chunks, see the [GraphRAG](https://mastra.ai/reference/rag/graph-rag-guide) documentation.

package/.docs/{guides → reference}/rag/vector-databases.md

@@ -407,7 +407,7 @@ await store.createIndex({
 
 The dimension size must match the output dimension of your chosen embedding model. Common dimension sizes are:
 
-- `OpenAI text-embedding-3-small`: 1536 dimensions (or custom, e.g., 256)
+- OpenAI `text-embedding-3-small`: 1536 dimensions (or custom, e.g., 256)
 - `Cohere embed-multilingual-v3`: 1024 dimensions
 - `VoyageAI voyage-3.5`: 1024 dimensions (or custom: 256, 512, 1024, 2048)
 - `Google gemini-embedding-001`: 768 dimensions (or custom)

package/.docs/reference/storage/composite.md

@@ -338,7 +338,7 @@ const storage = new MastraCompositeStore({
 
 Observability data can quickly overwhelm general-purpose databases in production. A single agent interaction can generate hundreds of spans, and high-traffic applications can produce thousands of traces per day.
 
-**[ClickHouse](https://mastra.ai/reference/storage/clickhouse)** is recommended for production observability because it's optimized for high-volume, write-heavy analytics workloads. Use composite storage to route observability to ClickHouse while keeping other data in your primary database:
+**[ClickHouse](https://mastra.ai/integrations/databases/clickhouse)** is recommended for production observability because it's optimized for high-volume, write-heavy analytics workloads. Use composite storage to route observability to ClickHouse while keeping other data in your primary database:
 
 ```typescript
 import { MastraCompositeStore } from '@mastra/core/storage'
@@ -360,7 +360,7 @@ const storage = new MastraCompositeStore({
 })
 ```
 
-> **Note:** `ObservabilityStorageClickhouseVNext` is the current observability domain implementation. The legacy `ObservabilityStorageClickhouse` class is also exported and remains supported for projects that haven't migrated. See the [ClickHouse storage reference](https://mastra.ai/reference/storage/clickhouse) for details.
+> **Note:** `ObservabilityStorageClickhouseVNext` is the current observability domain implementation. The legacy `ObservabilityStorageClickhouse` class is also exported and remains supported for projects that haven't migrated. See the [ClickHouse storage reference](https://mastra.ai/integrations/databases/clickhouse) for details.
 
 ### Replicated ClickHouse for multi-replica clusters
 
@@ -392,6 +392,6 @@ const storage = new MastraCompositeStore({
 })
 ```
 
-Don't set `replication` on ClickHouse Cloud. Cloud rewrites `MergeTree` to `SharedMergeTree` server-side. See the [ClickHouse storage reference](https://mastra.ai/reference/storage/clickhouse) for the full config shape and operator notes.
+Don't set `replication` on ClickHouse Cloud. Cloud rewrites `MergeTree` to `SharedMergeTree` server-side. See the [ClickHouse storage reference](https://mastra.ai/integrations/databases/clickhouse) for the full config shape and operator notes.
 
 > **Note:** This approach is also required when using storage providers that don't support observability (like Convex, DynamoDB, or Cloudflare). See the [MastraStorageExporter documentation](https://mastra.ai/docs/observability/integrations/exporters/mastra-storage) for the full list of supported providers.

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

@@ -8,7 +8,7 @@ Storage grows without bound by default. Retention is an opt-in, age-based cleanu
 
 Retention covers **growth tables** only: tables that accumulate rows unbounded as a side effect of normal operation (conversation history, telemetry, job and run records, schedule fire history, event feeds). User-authored artifacts and config (agents, skills, workspaces, prompt blocks, datasets, schedule definitions, channel installations, and so on) grow with user intent and are edited or deleted explicitly, so they're not valid retention keys.
 
-The reference implementations are [libSQL](https://mastra.ai/reference/storage/libsql), [PostgreSQL](https://mastra.ai/reference/storage/postgresql), and [MongoDB](https://mastra.ai/reference/storage/mongodb). Other adapters keep rows forever until they implement retention.
+The reference implementations are [libSQL](https://mastra.ai/integrations/databases/libsql), [PostgreSQL](https://mastra.ai/integrations/databases/postgresql), and [MongoDB](https://mastra.ai/integrations/databases/mongodb). Other adapters keep rows forever until they implement retention.
 
 ## Usage example
 
@@ -238,11 +238,11 @@ Handing that free space back to the OS is a separate concern that Mastra doesn't
 
 For MongoDB, deleted documents are reused by future insertions. To reclaim disk space, run [`db.runCommand({ compact: "collection_name" })`](https://www.mongodb.com/docs/manual/reference/command/compact/) during a maintenance window.
 
-> **LibSQL and Turso:** [Turso Cloud](https://mastra.ai/reference/storage/libsql) manages storage compaction for you, so there's nothing to reclaim manually. This applies only to self-hosted libSQL files.
+> **LibSQL and Turso:** [Turso Cloud](https://mastra.ai/integrations/databases/libsql) manages storage compaction for you, so there's nothing to reclaim manually. This applies only to self-hosted libSQL files.
 
 ## Related
 
-- [libSQL storage](https://mastra.ai/reference/storage/libsql)
-- [PostgreSQL storage](https://mastra.ai/reference/storage/postgresql)
+- [libSQL storage](https://mastra.ai/integrations/databases/libsql)
+- [PostgreSQL storage](https://mastra.ai/integrations/databases/postgresql)
 - [Composite storage](https://mastra.ai/reference/storage/composite)
 - [Storage overview](https://mastra.ai/reference/storage/overview)

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

@@ -310,7 +310,7 @@ Signals the completion of a processing step.
 
 **payload.messageId** (`string`): Optional message identifier
 
-**payload.stepResult** (`object`): Step execution result with reason, warnings, and continuation info
+**payload.stepResult** (`object`): Step execution result with reason, warnings, and continuation info. rawReason holds the provider's own finish reason when it reports one.
 
 **payload.output** (`object`): Output information including usage statistics
 
@@ -334,13 +334,13 @@ Contains raw data from the provider.
 
 ### finish
 
-Stream has completed successfully.
+Stream has completed.
 
 **type** (`"finish"`): Chunk type identifier
 
 **payload** (`FinishPayload`): Completion information
 
-**payload.stepResult** (`object`): Step execution result
+**payload.stepResult** (`object`): Step execution result. reason holds the normalized finish reason, and rawReason holds the provider's own finish reason when it reports one. A reason of "error" means the run failed.
 
 **payload.output** (`object`): Output information including usage
 

package/.docs/reference/streaming/agents/streamLegacy.md

@@ -2,7 +2,7 @@
 
 # Agent.streamLegacy() (Legacy)
 
-> **Warning:** **Deprecated**: This method is deprecated and only works with V1 models. For V2 models, use the new [`.stream()`](https://mastra.ai/reference/streaming/agents/stream) method instead. See the [migration guide](https://mastra.ai/guides/migrations/vnext-to-standard-apis) for details on upgrading.
+> **Warning:** **Deprecated**: This method is deprecated and only works with V1 models. For V2 models, use the new [`.stream()`](https://mastra.ai/reference/streaming/agents/stream) method instead. See the [migration guide](https://mastra.ai/reference/migrations/vnext-to-standard-apis) for details on upgrading.
 
 The `.streamLegacy()` method is the legacy version of the agent streaming API, used for real-time streaming of responses from V1 model agents. This method accepts messages and optional streaming options.
 
@@ -152,7 +152,7 @@ await agent.streamLegacy('message for agent', {
 
 ## Migration to new API
 
-> **Note:** The new `.stream()` method offers enhanced capabilities including AI SDK v5+ compatibility, better structured output handling, and improved callback system. See the [migration guide](https://mastra.ai/guides/migrations/vnext-to-standard-apis) for detailed migration instructions.
+> **Note:** The new `.stream()` method offers enhanced capabilities including AI SDK v5+ compatibility, better structured-output handling, and improved callback system. See the [migration guide](https://mastra.ai/reference/migrations/vnext-to-standard-apis) for detailed migration instructions.
 
 ### Quick Migration Example
 
@@ -180,7 +180,7 @@ const result = await agent.stream('message', {
 
 ## Related
 
-- [Migration Guide](https://mastra.ai/guides/migrations/vnext-to-standard-apis)
+- [Migration Guide](https://mastra.ai/reference/migrations/vnext-to-standard-apis)
 - [New .stream() method](https://mastra.ai/reference/streaming/agents/stream)
 - [Generating responses](https://mastra.ai/docs/agents/overview)
 - [Streaming responses](https://mastra.ai/docs/agents/overview)

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

@@ -929,7 +929,7 @@ Notification methods (`resources.notifyListChanged()`, `prompts.notifyListChange
 
 ## Examples
 
-For practical examples of setting up and deploying an MCPServer, see the [Publishing an MCP Server guide](https://mastra.ai/guides/guide/publishing-mcp-server).
+For a practical example of packaging a stdio server, see [Publish a stdio server package](https://mastra.ai/docs/mcp/overview).
 
 The example at the beginning of this page also demonstrates how to instantiate `MCPServer` with both tools and agents.
 

package/.docs/reference/vectors/convex.md

@@ -36,7 +36,7 @@ bun add @mastra/convex@latest
 
 ## Convex setup
 
-Before using `ConvexVector`, you need to set up the Convex schema and storage handler. See [Convex Storage Setup](https://mastra.ai/reference/storage/convex) for setup instructions.
+Before using `ConvexVector`, you need to set up the Convex schema and storage handler. See [Convex Storage Setup](https://mastra.ai/integrations/databases/convex) for setup instructions.
 
 ## Constructor options
 
@@ -419,6 +419,6 @@ Use an external vector database when you need runtime-defined index creation at
 
 ## Related
 
-- [Convex Storage](https://mastra.ai/reference/storage/convex)
+- [Convex Storage](https://mastra.ai/integrations/databases/convex)
 - [Metadata Filters](https://mastra.ai/reference/rag/metadata-filters)
 - [Convex Documentation](https://docs.convex.dev/)

package/.docs/reference/vectors/oracledb.md

@@ -342,6 +342,6 @@ export const oracleAgent = new Agent({
 
 ## Related
 
-- [OracleDB storage](https://mastra.ai/reference/storage/oracledb)
+- [OracleDB storage](https://mastra.ai/integrations/databases/oracledb)
 - [Metadata Filters](https://mastra.ai/reference/rag/metadata-filters)
-- [Vector databases](https://mastra.ai/guides/rag/vector-databases)
+- [Vector databases](https://mastra.ai/reference/rag/vector-databases)

package/.docs/reference/workers/overview.md

@@ -77,13 +77,13 @@ Executes background tool calls dispatched by agents.
 
 A deployment running all worker types requires a storage backend that implements the `workflows`, `backgroundTasks`, and `schedules` domains. The `schedules` domain is specifically required by the SchedulerWorker. If you don't use scheduled workflows, backends without it can still support orchestration and background tasks. The following backends support all three:
 
-| Backend    | Package                                                          |
-| ---------- | ---------------------------------------------------------------- |
-| PostgreSQL | [`@mastra/pg`](https://mastra.ai/reference/storage/postgresql)   |
-| LibSQL     | [`@mastra/libsql`](https://mastra.ai/reference/storage/libsql)   |
-| MySQL      | `@mastra/mysql`                                                  |
-| MongoDB    | [`@mastra/mongodb`](https://mastra.ai/reference/storage/mongodb) |
-| Spanner    | [`@mastra/spanner`](https://mastra.ai/reference/storage/spanner) |
-| Convex     | [`@mastra/convex`](https://mastra.ai/reference/storage/convex)   |
+| Backend    | Package                                                               |
+| ---------- | --------------------------------------------------------------------- |
+| PostgreSQL | [`@mastra/pg`](https://mastra.ai/integrations/databases/postgresql)   |
+| LibSQL     | [`@mastra/libsql`](https://mastra.ai/integrations/databases/libsql)   |
+| MySQL      | `@mastra/mysql`                                                       |
+| MongoDB    | [`@mastra/mongodb`](https://mastra.ai/integrations/databases/mongodb) |
+| Spanner    | [`@mastra/spanner`](https://mastra.ai/integrations/databases/spanner) |
+| Convex     | [`@mastra/convex`](https://mastra.ai/integrations/databases/convex)   |
 
 Other storage backends (Upstash, DynamoDB, Cloudflare D1, ClickHouse, Redis) support workflows and some worker features, but are missing the `schedules` domain. They can still be used for orchestration and background task workers if you don't deploy the scheduler.

package/.docs/reference/workspace/platform-filesystem.md

@@ -4,7 +4,7 @@
 
 Stores files in a Mastra Platform workspace bucket. Each Mastra Platform environment can have one bucket, and `PlatformFilesystem` gives agents `read`, `write`, `list`, `delete`, and `move` operations against it.
 
-Related providers: [`S3Filesystem`](https://mastra.ai/reference/workspace/s3-filesystem) for direct S3 access, [`LocalFilesystem`](https://mastra.ai/reference/workspace/local-filesystem) for local directories.
+Related providers: [`S3Filesystem`](https://mastra.ai/integrations/file-storage/amazon-s3) for direct S3 access, [`LocalFilesystem`](https://mastra.ai/reference/workspace/local-filesystem) for local directories.
 
 > **Note:** For interface details, see [WorkspaceFilesystem interface](https://mastra.ai/reference/workspace/filesystem).
 
@@ -181,5 +181,5 @@ try {
 ## Related
 
 - [PlatformSandbox reference](https://mastra.ai/reference/workspace/platform-sandbox)
-- [S3Filesystem reference](https://mastra.ai/reference/workspace/s3-filesystem)
+- [S3Filesystem reference](https://mastra.ai/integrations/file-storage/amazon-s3)
 - [WorkspaceFilesystem interface](https://mastra.ai/reference/workspace/filesystem)

package/.docs/reference/workspace/platform-sandbox.md

@@ -6,7 +6,7 @@ Client for provisioning sandboxes in a Mastra Platform environment. Each `Platfo
 
 Sandboxes boot from a pre-built recipe checkpoint with Python 3, Node 22, TypeScript, tsx, and common build tooling already installed. Pass a stable `id` to opt into [checkpoint recovery](#checkpoint-recovery) so a new sandbox boots from the previous one's filesystem.
 
-Related providers: [`RailwaySandbox`](https://mastra.ai/reference/workspace/railway-sandbox) for self-hosted Railway sandboxes, [`LocalSandbox`](https://mastra.ai/reference/workspace/local-sandbox) for local sandboxes.
+Related providers: [`RailwaySandbox`](https://mastra.ai/integrations/sandboxes/railway) for self-hosted Railway sandboxes, [`LocalSandbox`](https://mastra.ai/reference/workspace/local-sandbox) for local sandboxes.
 
 > **Note:** For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
 
@@ -279,6 +279,6 @@ try {
 ## Related
 
 - [PlatformFilesystem reference](https://mastra.ai/reference/workspace/platform-filesystem)
-- [RailwaySandbox reference](https://mastra.ai/reference/workspace/railway-sandbox)
+- [RailwaySandbox reference](https://mastra.ai/integrations/sandboxes/railway)
 - [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox)
 - [SandboxProcessManager reference](https://mastra.ai/reference/workspace/process-manager)

package/.docs/reference/workspace/process-manager.md

@@ -6,7 +6,7 @@
 
 Abstract base class for managing background processes in sandboxes. Provides methods to spawn processes, list them, get handles by PID, and kill them.
 
-[`BlaxelSandbox`](https://mastra.ai/reference/workspace/blaxel-sandbox), [`DaytonaSandbox`](https://mastra.ai/reference/workspace/daytona-sandbox), [`E2BSandbox`](https://mastra.ai/reference/workspace/e2b-sandbox), [`ModalSandbox`](https://mastra.ai/reference/workspace/modal-sandbox), and [`LocalSandbox`](https://mastra.ai/reference/workspace/local-sandbox) all include built-in process managers. You don't need to instantiate this class directly unless you're building a custom sandbox provider.
+[`BlaxelSandbox`](https://mastra.ai/integrations/sandboxes/blaxel), [`DaytonaSandbox`](https://mastra.ai/integrations/sandboxes/daytona), [`E2BSandbox`](https://mastra.ai/integrations/sandboxes/e2b), [`ModalSandbox`](https://mastra.ai/integrations/sandboxes/modal), and [`LocalSandbox`](https://mastra.ai/reference/workspace/local-sandbox) all include built-in process managers. You don't need to instantiate this class directly unless you're building a custom sandbox provider.
 
 ## Usage example
 
@@ -294,5 +294,5 @@ When a process manager is provided, `MastraSandbox` automatically creates a defa
 - [Sandbox](https://mastra.ai/docs/workspace/sandbox)
 - [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox)
 - [LocalSandbox reference](https://mastra.ai/reference/workspace/local-sandbox)
-- [E2BSandbox reference](https://mastra.ai/reference/workspace/e2b-sandbox)
-- [DaytonaSandbox reference](https://mastra.ai/reference/workspace/daytona-sandbox)
+- [E2BSandbox reference](https://mastra.ai/integrations/sandboxes/e2b)
+- [DaytonaSandbox reference](https://mastra.ai/integrations/sandboxes/daytona)

package/CHANGELOG.md

@@ -1,5 +1,21 @@
 # @mastra/mcp-docs-server
 
+## 1.2.15-alpha.22
+
+### Patch Changes
+
+- Updated dependencies [[`dc4a25d`](https://github.com/mastra-ai/mastra/commit/dc4a25d41af4e2fe97a816070eaec6aa963ab53b), [`dc4a25d`](https://github.com/mastra-ai/mastra/commit/dc4a25d41af4e2fe97a816070eaec6aa963ab53b)]:
+  - @mastra/core@1.58.0-alpha.15
+
+## 1.2.15-alpha.21
+
+### Patch Changes
+
+- Fixed migration docs lookup after docs moved to reference. ([#21236](https://github.com/mastra-ai/mastra/pull/21236))
+
+- Updated dependencies [[`210cb7a`](https://github.com/mastra-ai/mastra/commit/210cb7a167998c7bbf72cb3b93e6eb0563330239), [`5f798b3`](https://github.com/mastra-ai/mastra/commit/5f798b3362e9bdf4d690f85245606e146eef60b9), [`01a2943`](https://github.com/mastra-ai/mastra/commit/01a2943a7d886edefdff072bfa51f055bab54437), [`01a2943`](https://github.com/mastra-ai/mastra/commit/01a2943a7d886edefdff072bfa51f055bab54437), [`25ca73d`](https://github.com/mastra-ai/mastra/commit/25ca73d25dee7ce9f0ca72939e3a505c4db7257e), [`e1cead1`](https://github.com/mastra-ai/mastra/commit/e1cead17b5f3653cf00d2f90cc19b113119c02ba), [`01a2943`](https://github.com/mastra-ai/mastra/commit/01a2943a7d886edefdff072bfa51f055bab54437)]:
+  - @mastra/core@1.58.0-alpha.14
+
 ## 1.2.15-alpha.20
 
 ### Patch Changes

package/dist/index.js

@@ -1,2 +1,2 @@
-import { n as server, t as runServer } from "./src-BZcgzbk9.js";
+import { n as server, t as runServer } from "./src-D-W-bx5t.js";
 export { runServer, server };

package/dist/{src-BZcgzbk9.js → src-D-W-bx5t.js}

@@ -1508,7 +1508,7 @@ Try:
 };
 //#endregion
 //#region src/tools/migration.ts
-const migrationsBaseDir = fromPackageRoot(".docs/guides/migrations");
+const migrationsBaseDir = fromPackageRoot(".docs/reference/migrations");
 function parseSections(content) {
 	const lines = content.split("\n");
 	const sections = [];
@@ -1771,4 +1771,4 @@ async function runServer() {
 //#endregion
 export { writeErrorLog as i, server as n, setLogLevel as r, runServer as t };
 
-//# sourceMappingURL=src-BZcgzbk9.js.map
+//# sourceMappingURL=src-D-W-bx5t.js.map