@mastra/mcp-docs-server 1.2.17-alpha.9 → 1.2.18-alpha.1

package/.docs/docs/memory/overview.md

@@ -13,7 +13,7 @@ Mastra agents can be configured to store [message history](https://mastra.ai/doc
 
 If the combined memory exceeds the model's context limit, [memory processors](https://mastra.ai/docs/memory/memory-processors) can filter, trim, or prioritize content so the most relevant information is preserved.
 
-Memory results will be stored in one or more of your configured [storage providers](https://mastra.ai/docs/storage/overview).
+Memory results will be stored in one or more of your configured [storage providers](https://mastra.ai/docs/storage).
 
 > **📹 Watch:** Watch [Mastra memory concepts](https://www.youtube.com/watch?v=18iIHQtIPmc) for a conceptual overview of the memory layers agents can use.
 
@@ -77,7 +77,7 @@ Use memory when your agent needs to maintain multi-turn conversations that refer
    bun add @mastra/libsql@latest
    ```
 
-   For more details on available providers and how storage works in Mastra, visit the [storage](https://mastra.ai/docs/storage/overview) documentation.
+   For more details on available providers and how storage works in Mastra, visit the [storage](https://mastra.ai/docs/storage) documentation.
 
 3. Add the storage provider to your main Mastra instance to enable memory across all configured agents.
 
@@ -188,7 +188,7 @@ Conversation messages are ordered by timestamp and deduplicated by message ID, s
 
 ## Memory in multi-agent systems
 
-When a [supervisor agent](https://mastra.ai/docs/capabilities/subagents) delegates to a subagent, Mastra isolates subagent memory automatically. No flag enables this as it happens on every delegation. Understanding how this scoping works lets you decide what stays private and what to share intentionally.
+When a [supervisor agent](https://mastra.ai/docs/subagents) delegates to a subagent, Mastra isolates subagent memory automatically. No flag enables this as it happens on every delegation. Understanding how this scoping works lets you decide what stays private and what to share intentionally.
 
 ### How delegation scopes memory
 
@@ -200,7 +200,7 @@ Each delegation creates a fresh `threadId` and a deterministic `resourceId` for
 
 > **Note:** Title generation (`generateTitle`) is a top-level thread concern and **isn't** applied to inherited subagent threads. Because each delegation creates an ephemeral thread that no one sees, running title generation for it would waste an LLM call per delegation. To generate titles for a subagent's own threads, give that subagent its own memory configuration.
 
-The supervisor forwards its conversation context to the subagent so it has enough background to complete the task. Only the delegation prompt and the subagent's response are saved, the full parent conversation isn't stored. You can control which messages reach the subagent with the [`messageFilter`](https://mastra.ai/docs/capabilities/subagents) callback.
+The supervisor forwards its conversation context to the subagent so it has enough background to complete the task. Only the delegation prompt and the subagent's response are saved, the full parent conversation isn't stored. You can control which messages reach the subagent with the [`messageFilter`](https://mastra.ai/docs/subagents) callback.
 
 > **Note:** Subagent resource IDs are always suffixed with the agent name (`{parentResourceId}-{agentName}`). Different subagents under the same supervisor never share a resource ID through delegation.
 

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

@@ -400,7 +400,7 @@ const response = await agent.generate('What do you know about me?', {
 
 ## Opt in to state signals (experimental)
 
-By default, working memory reaches the model as part of the system message. You can opt into delivering it as a [state signal](https://mastra.ai/docs/long-running-agents/signals) instead by setting `useStateSignals: true`:
+By default, working memory reaches the model as part of the system message. You can opt into delivering it as a [state signal](https://mastra.ai/docs/harness/signals) instead by setting `useStateSignals: true`:
 
 ```typescript
 const memory = new Memory({

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

@@ -244,4 +244,4 @@ new MastraStorageExporter({
 - [Tracing Overview](https://mastra.ai/docs/observability/tracing/overview)
 - [MastraPlatformExporter](https://mastra.ai/docs/mastra-platform/observability)
 - [Composite Storage](https://mastra.ai/reference/storage/composite): Combine multiple storage providers
-- [Storage Configuration](https://mastra.ai/docs/storage/overview)
+- [Storage Configuration](https://mastra.ai/docs/storage)

package/.docs/docs/{workspace → sandbox}/filesystem.md

@@ -165,7 +165,7 @@ const workspace = new Workspace({
 
 ### Per-user or per-thread mounts
 
-Workspace-level `mounts` require a sandbox provider object and can't be combined with a sandbox resolver. For one sandbox and storage prefix per user or thread, create and mount the filesystem inside the sandbox resolver. See [Multi-tenant sandboxes](https://mastra.ai/docs/workspace/sandbox) for a complete example.
+Workspace-level `mounts` require a sandbox provider object and can't be combined with a sandbox resolver. For one sandbox and storage prefix per user or thread, create and mount the filesystem inside the sandbox resolver. See [Multi-tenant sandboxes](https://mastra.ai/docs/sandbox/overview) for a complete example.
 
 ## Workspace-only filesystem
 
@@ -262,6 +262,6 @@ Each tenant's prefix seeds its own workspace view. Workspace tools resolve the f
 
 ## Related
 
-- [Sandbox](https://mastra.ai/docs/workspace/sandbox)
+- [Sandbox](https://mastra.ai/docs/sandbox/overview)
 - [`WorkspaceFilesystem` reference](https://mastra.ai/reference/workspace/filesystem)
 - [`Workspace` reference](https://mastra.ai/reference/workspace/workspace-class)

package/.docs/docs/{workspace → sandbox}/lsp.md

@@ -210,7 +210,7 @@ const workspace = new Workspace({
 
 ## Related
 
-- [Filesystem](https://mastra.ai/docs/workspace/filesystem)
-- [Sandbox](https://mastra.ai/docs/workspace/sandbox)
-- [Search and indexing](https://mastra.ai/docs/workspace/search)
+- [Filesystem](https://mastra.ai/docs/sandbox/filesystem)
+- [Sandbox](https://mastra.ai/docs/sandbox/overview)
+- [Search and indexing](https://mastra.ai/docs/sandbox/search)
 - [Workspace class reference](https://mastra.ai/reference/workspace/workspace-class)

package/.docs/docs/{workspace/sandbox.md → sandbox/overview.md}

@@ -111,6 +111,7 @@ Use a remote or container backend when commands need a stronger boundary from th
 - [AgentCore](https://mastra.ai/integrations/sandboxes/agentcore)
 - [Apple Container](https://mastra.ai/integrations/sandboxes/apple-container)
 - [Blaxel](https://mastra.ai/integrations/sandboxes/blaxel)
+- [Cloudflare Sandbox](https://mastra.ai/integrations/sandboxes/cloudflare-sandbox)
 - [Daytona](https://mastra.ai/integrations/sandboxes/daytona)
 - [Docker](https://mastra.ai/integrations/sandboxes/docker)
 - [E2B](https://mastra.ai/integrations/sandboxes/e2b)
@@ -145,7 +146,7 @@ const workspace = new Workspace({
 
 The agent receives filesystem tools for the mounted storage, and commands in the sandbox can access the same files under `/data`. This lets you seed an ephemeral sandbox with existing files and persist its output after the sandbox stops.
 
-Mount support varies by sandbox backend. See [Filesystem](https://mastra.ai/docs/workspace/filesystem) for supported storage backends, detailed mount configuration, and how to mount multiple filesystems.
+Mount support varies by sandbox backend. See [Filesystem](https://mastra.ai/docs/sandbox/filesystem) for supported storage backends, detailed mount configuration, and how to mount multiple filesystems.
 
 ## Multi-tenant sandboxes
 
@@ -200,7 +201,7 @@ Workspace-level `mounts` can't be combined with a sandbox resolver. This is a kn
 
 The workspace doesn't own sandboxes returned by a resolver. Return a sandbox that's ready to use, and destroy it through your application's lifecycle code when it's no longer needed. `workspace.destroy()` doesn't destroy resolver-returned sandboxes.
 
-Resolvers are incompatible with `mounts` and [`lsp: true`](https://mastra.ai/docs/workspace/lsp), because both require a static sandbox when the workspace is constructed. Using a resolver with `mounts` throws an `INVALID_CONFIG` error. With `lsp: true`, Mastra disables LSP and logs a warning.
+Resolvers are incompatible with `mounts` and [`lsp: true`](https://mastra.ai/docs/sandbox/lsp), because both require a static sandbox when the workspace is constructed. Using a resolver with `mounts` throws an `INVALID_CONFIG` error. With `lsp: true`, Mastra disables LSP and logs a warning.
 
 ### Tool availability
 
@@ -335,4 +336,4 @@ await sandbox.executeCommand('node', ['scripts/download-reports.js'], {
 
 - [`SandboxProcessManager` reference](https://mastra.ai/reference/workspace/process-manager)
 - [`WorkspaceSandbox` reference](https://mastra.ai/reference/workspace/sandbox)
-- [Filesystem](https://mastra.ai/docs/workspace/filesystem)
+- [Filesystem](https://mastra.ai/docs/sandbox/filesystem)

package/.docs/docs/{workspace → sandbox}/search.md

@@ -4,7 +4,7 @@
 
 Search lets agents find relevant content in indexed workspace files. When an agent needs to answer a question or find information, it can search the indexed content instead of reading every file.
 
-Search works with both [`mounts`](https://mastra.ai/docs/workspace/filesystem) and a [workspace-only filesystem](https://mastra.ai/docs/workspace/filesystem). With `mounts`, paths from every mounted filesystem are available through one composite filesystem. With `filesystem`, search uses that provider directly. In both cases, queries search the workspace index rather than reading live files on demand.
+Search works with both [`mounts`](https://mastra.ai/docs/sandbox/filesystem) and a [workspace-only filesystem](https://mastra.ai/docs/sandbox/filesystem). With `mounts`, paths from every mounted filesystem are available through one composite filesystem. With `filesystem`, search uses that provider directly. In both cases, queries search the workspace index rather than reading live files on demand.
 
 ## When to use search
 
@@ -327,6 +327,6 @@ See [workspace class reference](https://mastra.ai/reference/workspace/workspace-
 
 ## Related
 
-- [Sandbox](https://mastra.ai/docs/workspace/sandbox)
+- [Sandbox](https://mastra.ai/docs/sandbox/overview)
 - [RAG overview](https://mastra.ai/reference/rag/overview)
 - [Workspace class reference](https://mastra.ai/reference/workspace/workspace-class)

package/.docs/docs/{workspace → sandbox}/skills.md

@@ -4,7 +4,7 @@
 
 Skills are reusable instructions that teach agents how to perform specific tasks. They follow the [Agent Skills specification](https://agentskills.io) - an open standard for packaging agent capabilities.
 
-> **Note:** Workspace skills are discovered through a workspace and shared with every agent that uses it. To attach skills directly to one agent without requiring a workspace, use [agent skills](https://mastra.ai/docs/agents/skills).
+> **Note:** Workspace skills are discovered through a workspace and shared with every agent that uses it. To attach skills directly to one agent without requiring a workspace, use [agent skills](https://mastra.ai/docs/skills).
 
 ## When to use skills
 
@@ -205,7 +205,7 @@ When `skillSource` is provided, it's used instead of the workspace filesystem fo
 
 You can also attach skills directly to an agent without a workspace using `createSkill()` and the agent's `skills` config. When both agent-level and workspace-level skills exist, they merge, agent-level skills take precedence on name conflicts.
 
-See [Agent skills](https://mastra.ai/docs/agents/skills) for details.
+See [Agent skills](https://mastra.ai/docs/skills) for details.
 
 ## Dynamic skills
 
@@ -226,8 +226,8 @@ const workspace = new Workspace({
 
 ## Related
 
-- [Agent skills](https://mastra.ai/docs/agents/skills)
+- [Agent skills](https://mastra.ai/docs/skills)
 - [Agent skills specification](https://agentskills.io)
-- [Sandbox](https://mastra.ai/docs/workspace/sandbox)
-- [Search and indexing](https://mastra.ai/docs/workspace/search)
+- [Sandbox](https://mastra.ai/docs/sandbox/overview)
+- [Search and indexing](https://mastra.ai/docs/sandbox/search)
 - [`createSkill()` reference](https://mastra.ai/reference/agents/createSkill)

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

@@ -295,7 +295,7 @@ registerApiRoute('/user-profile', {
 })
 ```
 
-For more information about authentication providers, see the [Auth documentation](https://mastra.ai/docs/server/auth).
+For more information about authentication providers, see the [Auth documentation](https://mastra.ai/docs/auth/overview).
 
 ## Continue generation after client disconnect
 
@@ -372,4 +372,4 @@ export const mastra = new Mastra({
 
 - [registerApiRoute() Reference](https://mastra.ai/reference/server/register-api-route): Full API reference
 - [Server Middleware](https://mastra.ai/docs/server/middleware): Global middleware configuration
-- [Mastra Server](https://mastra.ai/docs/server/mastra-server): Server configuration options
+- [Mastra Server](https://mastra.ai/docs/server/overview): Server configuration options

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

@@ -2,7 +2,7 @@
 
 # Mastra client
 
-The Mastra Client SDK provides a concise and type-safe interface for interacting with your [Mastra Server](https://mastra.ai/docs/server/mastra-server) from your client environment.
+The Mastra Client SDK provides a concise and type-safe interface for interacting with your [Mastra Server](https://mastra.ai/docs/server/overview) from your client environment.
 
 ## Prerequisites
 
@@ -59,7 +59,7 @@ export const mastraClient = new MastraClient({
 The Mastra Client SDK exposes all resources served by the Mastra Server.
 
 - **[Agents](https://mastra.ai/reference/client-js/agents)**: Generate responses and stream conversations.
-- **[A2A](https://mastra.ai/docs/agents/a2a)**: Discover agents through agent cards and work with task-based A2A streams.
+- **[A2A](https://mastra.ai/docs/connections/a2a)**: Discover agents through agent cards and work with task-based A2A streams.
 - **[Memory](https://mastra.ai/reference/client-js/memory)**: Manage conversation threads and message history.
 - **[Tools](https://mastra.ai/reference/client-js/tools)**: Executed and managed tools.
 - **[Workflows](https://mastra.ai/reference/client-js/workflows)**: Trigger workflows and track their execution.

package/.docs/docs/server/{mastra-server.md → overview.md}

@@ -14,8 +14,8 @@ Mastra runs as an HTTP server that exposes your agents, workflows, and other fun
 - **[Server Adapters](https://mastra.ai/docs/server/server-adapters)**: Run Mastra with Express, Hono, or your own HTTP server instead of the generated server.
 - **[Custom Adapters](https://mastra.ai/docs/server/custom-adapters)**: Build adapters for frameworks not officially supported.
 - **[Mastra Client SDK](https://mastra.ai/docs/server/mastra-client)**: Type-safe client for calling agents, workflows, and tools from browser or server environments.
-- **[A2A](https://mastra.ai/docs/agents/a2a)**: Expose agents through A2A agent cards and task streams, plus push notifications.
-- **[Authentication](https://mastra.ai/docs/server/auth)**: Secure endpoints with JWT, Clerk, Supabase, Firebase, Auth0, or WorkOS.
+- **[A2A](https://mastra.ai/docs/connections/a2a)**: Expose agents through A2A agent cards and task streams, plus push notifications.
+- **[Authentication](https://mastra.ai/docs/auth/overview)**: Secure endpoints with JWT, Clerk, Supabase, Firebase, Auth0, or WorkOS.
 
 ## Configuration
 
@@ -101,5 +101,5 @@ Mastra requires `module` and `moduleResolution` settings compatible with modern
 
 - Add [middleware](https://mastra.ai/docs/server/middleware)
 - Create [custom API routes](https://mastra.ai/docs/server/custom-api-routes)
-- Add [authentication](https://mastra.ai/docs/server/auth)
+- Add [authentication](https://mastra.ai/docs/auth/overview)
 - [Deploy](https://mastra.ai/docs/deployment/overview) your server to production

package/.docs/docs/server/pubsub.md

@@ -12,7 +12,7 @@ Several built-in systems publish and subscribe to events through the same pub/su
 
 - **Workflow execution**: The scheduler publishes a `workflow.start` event, and a long-lived worker consumes it to run the workflow. Step and lifecycle events flow over pub/sub during execution.
 - **Scheduled workflows**: The scheduler dispatches due runs by publishing to the workflow topic. See [Scheduled workflows](https://mastra.ai/docs/workflows/scheduled-workflows).
-- **Background tasks**: A task manager dispatches work to a worker group and fans task lifecycle updates out to subscribers, which is how background task streams stay live. See [Background task streaming](https://mastra.ai/docs/long-running-agents/background-tasks).
+- **Background tasks**: A task manager dispatches work to a worker group and fans task lifecycle updates out to subscribers, which is how background task streams stay live. See [Background task streaming](https://mastra.ai/docs/harness/background-tasks).
 - **Agent signals**: Sending a signal to an active agent run publishes an event on a thread topic, so a run executing in another process receives the signal.
 - **Resumable streams**: Stream chunks are published per run, so a client that reconnects can replay what it missed.
 
@@ -125,5 +125,5 @@ Visit the [PubSub reference](https://mastra.ai/reference/pubsub/base) for the fu
 - [PubSub reference](https://mastra.ai/reference/pubsub/base)
 - [Mastra class](https://mastra.ai/reference/core/mastra-class)
 - [Workers](https://mastra.ai/docs/deployment/workers): Run workflow orchestration and background tasks in dedicated processes using PubSub
-- [Background task streaming](https://mastra.ai/docs/long-running-agents/background-tasks)
+- [Background task streaming](https://mastra.ai/docs/harness/background-tasks)
 - [Scheduled workflows](https://mastra.ai/docs/workflows/scheduled-workflows)

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

@@ -12,7 +12,7 @@ Server adapters let you run Mastra with your own HTTP server instead of the Hono
 - You need direct access to the server instance for custom configuration
 - Your team prefers using another server framework instead of the Hono server created by `mastra build`.
 
-> **Tip:** For deployments without custom server requirements, use `mastra build` instead. It configures server setup and registers middleware, plus applies deployment settings based on your project configuration. See [Server Configuration](https://mastra.ai/docs/server/mastra-server).
+> **Tip:** For deployments without custom server requirements, use `mastra build` instead. It configures server setup and registers middleware, plus applies deployment settings based on your project configuration. See [Server Configuration](https://mastra.ai/docs/server/overview).
 >
 > If you want to use [Studio](https://mastra.ai/docs/studio/overview) with your server adapter, use [`mastra studio`](https://mastra.ai/reference/cli/mastra) to only launch the Studio UI.
 
@@ -635,7 +635,7 @@ const server = new MastraServer({
 
 When `serverless: true`, MCP HTTP requests run without session management, making them compatible with stateless execution environments.
 
-See [MCP](https://mastra.ai/docs/mcp/overview) for configuration details and how to set up MCP servers.
+See [MCP](https://mastra.ai/docs/connections/mcp) for configuration details and how to set up MCP servers.
 
 ## Related
 
@@ -643,7 +643,7 @@ See [MCP](https://mastra.ai/docs/mcp/overview) for configuration details and how
 - [Express Adapter](https://mastra.ai/reference/server/express-adapter) - Express-specific setup
 - [NestJS Adapter](https://mastra.ai/reference/server/nestjs-adapter) - NestJS-specific setup
 - [Custom Adapters](https://mastra.ai/docs/server/custom-adapters) - Building adapters for other frameworks
-- [Server Configuration](https://mastra.ai/docs/server/mastra-server) - Using `mastra build` instead
-- [Authentication](https://mastra.ai/docs/server/auth) - Configuring auth for your server
+- [Server Configuration](https://mastra.ai/docs/server/overview) - Using `mastra build` instead
+- [Authentication](https://mastra.ai/docs/auth/overview) - Configuring auth for your server
 - [MastraServer Reference](https://mastra.ai/reference/server/mastra-server) - Full API reference
 - [createRoute() Reference](https://mastra.ai/reference/server/create-route) - Creating type-safe custom routes

package/.docs/docs/{agents/skills.md → skills.md}

@@ -4,7 +4,7 @@
 
 Skills are reusable instructions that teach agents how to perform specific tasks. They follow the [Agent Skills specification](https://agentskills.io).
 
-You can attach skills directly to an agent through its `skills` config, or configure them on a [workspace](https://mastra.ai/docs/workspace/skills). Attach them to the agent when the skills belong to that specific agent and you want to define them in code with no workspace required. Use a workspace when you want skills discovered from the filesystem and shared across every agent that uses it. This page covers the agent-level approach, defining skills in code and loading them from files, plus resolving them per request.
+You can attach skills directly to an agent through its `skills` config, or configure them on a [workspace](https://mastra.ai/docs/sandbox/skills). Attach them to the agent when the skills belong to that specific agent and you want to define them in code with no workspace required. Use a workspace when you want skills discovered from the filesystem and shared across every agent that uses it. This page covers the agent-level approach, defining skills in code and loading them from files, plus resolving them per request.
 
 ## When to use agent-level skills
 
@@ -15,7 +15,7 @@ Use agent-level skills when:
 - You're building packages or libraries that contain agent capabilities
 - You need per-request skill resolution based on context
 
-For filesystem-based skill discovery across a project, use [workspace skills](https://mastra.ai/docs/workspace/skills) instead.
+For filesystem-based skill discovery across a project, use [workspace skills](https://mastra.ai/docs/sandbox/skills) instead.
 
 ## Quickstart
 
@@ -90,7 +90,7 @@ export const agent = new Agent({
 })
 ```
 
-Filesystem paths use `LocalSkillSource` under the hood, which reads `SKILL.md` files following the same format as [workspace skills](https://mastra.ai/docs/workspace/skills).
+Filesystem paths use `LocalSkillSource` under the hood, which reads `SKILL.md` files following the same format as [workspace skills](https://mastra.ai/docs/sandbox/skills).
 
 ## Dynamic skills
 
@@ -193,7 +193,7 @@ Visit [`.getSkill()` reference](https://mastra.ai/reference/agents/getSkill) and
 
 ## Related
 
-- [Workspace skills](https://mastra.ai/docs/workspace/skills)
+- [Workspace skills](https://mastra.ai/docs/sandbox/skills)
 - [`createSkill()` reference](https://mastra.ai/reference/agents/createSkill)
 - [`.getSkill()` reference](https://mastra.ai/reference/agents/getSkill)
 - [`.listSkills()` reference](https://mastra.ai/reference/agents/listSkills)

package/.docs/docs/{storage/overview.md → storage.md}

@@ -10,7 +10,7 @@ Storage powers:
 - [Workflows](https://mastra.ai/docs/workflows/overview): Durable snapshots for suspended and resumed workflow runs.
 - [Observability](https://mastra.ai/docs/observability/overview): Traces, spans, metrics, logs, and feedback.
 - [Evals](https://mastra.ai/docs/evals/overview): Scores, datasets, experiments, and evaluation results.
-- [Long-running agents](https://mastra.ai/docs/long-running-agents/durable-agents): Background tasks, schedules, goals, and thread state.
+- [Long-running agents](https://mastra.ai/docs/harness/durable-agents): Background tasks, schedules, goals, and thread state.
 
 ## When to configure storage
 
@@ -200,6 +200,7 @@ Each provider page includes installation instructions, configuration parameters,
 - [Google Cloud Spanner](https://mastra.ai/integrations/databases/spanner)
 - [LanceDB](https://mastra.ai/integrations/databases/lancedb)
 - [libSQL](https://mastra.ai/integrations/databases/libsql)
+- [Mastra](https://mastra.ai/docs/mastra-platform/database)
 - [MongoDB](https://mastra.ai/integrations/databases/mongodb)
 - [MSSQL](https://mastra.ai/integrations/databases/mssql)
 - [Neon Postgres](https://mastra.ai/integrations/databases/neon)

package/.docs/docs/studio/auth.md

@@ -2,7 +2,7 @@
 
 # Studio auth
 
-When you configure [authentication](https://mastra.ai/docs/server/auth) on your Mastra server, Studio automatically displays a login screen and enforces access control. One configuration secures both the Studio UI and your API routes.
+When you configure [authentication](https://mastra.ai/docs/auth/overview) on your Mastra server, Studio automatically displays a login screen and enforces access control. One configuration secures both the Studio UI and your API routes.
 
 Without authentication, Studio and all API routes are publicly accessible.
 
@@ -14,7 +14,7 @@ Without authentication, Studio and all API routes are publicly accessible.
 
 ## Quickstart
 
-Add an auth provider to your Mastra server configuration. This example uses [Simple Auth](https://mastra.ai/docs/server/auth/simple-auth) for a minimal setup:
+Add an auth provider to your Mastra server configuration. This example uses [Simple Auth](https://mastra.ai/docs/auth/simple-auth) for a minimal setup:
 
 ```typescript
 import { Mastra } from '@mastra/core'
@@ -35,7 +35,7 @@ export const mastra = new Mastra({
 })
 ```
 
-Once configured, Studio shows a login screen and requires authentication for all API requests. Visit the [Auth docs](https://mastra.ai/docs/server/auth) for a full list of supported providers.
+Once configured, Studio shows a login screen and requires authentication for all API requests. Visit the [Auth docs](https://mastra.ai/docs/auth/overview) for a full list of supported providers.
 
 ## How it works
 
@@ -157,6 +157,6 @@ Studio Auth features (SSO login, RBAC, permission-based UI) are part of the Mast
 
 ## Related
 
-- [Auth overview](https://mastra.ai/docs/server/auth): Full list of supported auth providers.
+- [Auth overview](https://mastra.ai/docs/auth/overview): Full list of supported auth providers.
 - [Studio deployment](https://mastra.ai/docs/studio/deployment): Deploy Studio to production.
 - [Custom API routes](https://mastra.ai/docs/server/custom-api-routes): Control authentication on individual endpoints.

package/.docs/docs/studio/overview.md

@@ -57,7 +57,7 @@ You can also attach [scorers](#scorers) to measure and compare response quality
 
 You can send a follow-up message in the same thread during an agent response stream. Studio shows the message as pending until the stream confirms it, then continues the response below that follow-up. Other Studio tabs that have the same thread open can observe the active stream.
 
-Use [Editor](https://mastra.ai/docs/editor/overview) to let non-technical team members iterate on agents and version every change, plus run experiments without redeploying.
+Use [Editor](https://mastra.ai/docs/studio/editor) to let non-technical team members iterate on agents and version every change, plus run experiments without redeploying.
 
 Use [Agent Builder](https://agent-builder.mastra.ai) to create and manage fully stored agents through a separate browser-based interface.
 
@@ -85,7 +85,7 @@ Run tools on their own to observe behavior and test them before assigning them t
 
 Browse the files in your agent's workspace filesystem using a built-in file browser. Switch between workspace mounts, create directories, and view file contents with syntax highlighting. Writable workspaces allow directory creation and file deletion; read-only workspaces are labeled accordingly. The Skills tab lists all discovered skills with their instructions, references, and metadata. Install community skills from [skills.sh](https://skills.sh) or remove existing ones.
 
-See [workspaces](https://mastra.ai/docs/workspace/sandbox) for configuration details.
+See [workspaces](https://mastra.ai/docs/sandbox/overview) for configuration details.
 
 ### Request context
 

package/.docs/docs/{capabilities/subagents.md → subagents.md}

@@ -166,6 +166,36 @@ The `context` object includes:
 | `error`       | Error if the delegation failed           |
 | `bail()`      | Function to stop the parent agent's loop |
 
+### Hook errors
+
+If a delegation hook throws, the delegation continues by default: `onDelegationStart` proceeds with the original prompt, `messageFilter` falls back to the unfiltered context, and `onDelegationComplete` keeps the subagent's original result. Set `hookErrorStrategy: 'throw'` to fail the delegation instead.
+
+```typescript
+const stream = await parentAgent.stream('Research AI trends', {
+  maxSteps: 10,
+  delegation: {
+    hookErrorStrategy: 'throw',
+    onDelegationComplete: async ({ result }) => {
+      // If this throws, the parent sees a failed delegation instead of a
+      // successful one whose result was silently dropped.
+      await reportToAnalytics(result)
+    },
+  },
+})
+```
+
+Either way, every hook failure is recorded on the run's request context under `__mastra_delegationHookErrors` as a list of `{ hook, primitiveId, toolCallId, runId, name, message }` entries, so you can detect a hook failure programmatically:
+
+```typescript
+const requestContext = new RequestContext()
+
+await parentAgent.generate('Research AI trends', { maxSteps: 10, requestContext })
+
+const hookErrors = requestContext.get('__mastra_delegationHookErrors') ?? []
+```
+
+When `hookErrorStrategy` is `'throw'`, a throwing `onDelegationStart` blocks the subagent from running at all, and a throwing `messageFilter` or `onDelegationComplete` surfaces to the parent as a failed tool call. If `onDelegationComplete` throws while handling a failed delegation, the original delegation error is still what surfaces, and the hook is never re-invoked for its own failure.
+
 ## Message filtering
 
 By default, subagents receive the full conversation context from the parent agent. Use `messageFilter` to control what messages are shared, for example, to remove sensitive data or limit context size.
@@ -399,7 +429,7 @@ Success criteria:
 
 ## Running subagents in the background
 
-Subagent invocations are dispatched as tool calls, so they can run as [background tasks](https://mastra.ai/docs/long-running-agents/background-tasks). This is useful when one or more delegations are long-running and you don't want them to block the parent agent's response.
+Subagent invocations are dispatched as tool calls, so they can run as [background tasks](https://mastra.ai/docs/harness/background-tasks). This is useful when one or more delegations are long-running and you don't want them to block the parent agent's response.
 
 Enable the [backgroundTasks manager](https://mastra.ai/reference/configuration) on the Mastra instance, then opt subagents in on the parent agent:
 
@@ -424,11 +454,11 @@ const stream = await parentAgent.streamUntilIdle('Research AI in education and w
 
 Use [`streamUntilIdle()`](https://mastra.ai/reference/streaming/agents/streamUntilIdle) instead of `stream()` so the stream stays open until the subagents complete and the parent agent has had a chance to respond to their results.
 
-If a subagent isn't listed under the parent agent's `backgroundTasks.tools` but has its own background-eligible tools, the parent agent still dispatches the subagent as a background task and inherits its config. See [Inheriting from the subagent](https://mastra.ai/docs/long-running-agents/background-tasks) for details.
+If a subagent isn't listed under the parent agent's `backgroundTasks.tools` but has its own background-eligible tools, the parent agent still dispatches the subagent as a background task and inherits its config. See [Inheriting from the subagent](https://mastra.ai/docs/harness/background-tasks) for details.
 
 ## Subagent versioning
 
-When using the [editor](https://mastra.ai/docs/editor/overview), you can control which stored version of each subagent the parent agent uses at runtime. Set version overrides on the Mastra instance or per invocation:
+When using the [editor](https://mastra.ai/docs/studio/editor), you can control which stored version of each subagent the parent agent uses at runtime. Set version overrides on the Mastra instance or per invocation:
 
 ```typescript
 const result = await parentAgent.generate('Research and write about AI safety', {
@@ -445,13 +475,13 @@ Version overrides propagate automatically through delegation. See [Subagent vers
 
 ## Related
 
-- [Background tasks](https://mastra.ai/docs/long-running-agents/background-tasks)
+- [Background tasks](https://mastra.ai/docs/harness/background-tasks)
 - [Subagent versioning](https://mastra.ai/reference/editor/versioning)
 - [Guide: Research coordinator](https://mastra.ai/blog/build-a-research-coordinator-with-supervisor-agents)
 - [Agent.stream() reference](https://mastra.ai/reference/streaming/agents/stream)
 - [Agent.streamUntilIdle() reference](https://mastra.ai/reference/streaming/agents/streamUntilIdle)
 - [Agent.generate() reference](https://mastra.ai/reference/agents/generate)
-- [Agent approval](https://mastra.ai/docs/agents/agent-approval)
+- [Agent approval](https://mastra.ai/docs/agents/human-in-the-loop)
 - [Memory in multi-agent systems](https://mastra.ai/docs/memory/overview)
 - [Concept: Multi-agent systems](https://mastra.ai/docs/guides/multi-agent-systems)
 - 📹 [Mastra supervisor agents workshop](https://www.youtube.com/watch?v=FNb2fL9WhQg\&t=1872s)

package/.docs/docs/workflows/agents-and-tools.md

@@ -189,4 +189,4 @@ Like `.agent()`, `.tool()` records a declarative entry, so the workflow can be p
 ## Related
 
 - [Using Agents](https://mastra.ai/docs/agents/overview)
-- [MCP Overview](https://mastra.ai/docs/mcp/overview)
+- [MCP Overview](https://mastra.ai/docs/connections/mcp)

package/.docs/docs/workflows/control-flow.md

@@ -17,8 +17,6 @@ Each step connects to the next in the workflow through defined schemas that keep
 
 Use `.then()` to run steps in order, allowing each step to access the result of the step before it.
 
-![Chaining steps with .then()](/assets/images/workflows-control-flow-then-bde5e0fbefe5c64c19a8c3471c0e8439.jpg)
-
 ```typescript
 const step1 = createStep({
   inputSchema: z.object({
@@ -55,8 +53,6 @@ export const testWorkflow = createWorkflow({
 
 Use `.parallel()` to run steps simultaneously. All parallel steps must complete before the workflow continues to the next step. Each step's `id` is used when defining a following step's `inputSchema` and becomes the key on the `inputData` object used to access the previous step's values. The outputs of parallel steps can then be referenced or combined by a following step.
 
-![Concurrent steps with .parallel()](/assets/images/workflows-control-flow-parallel-8e7fe60f1c4daa510431b37c973f6f8d.jpg)
-
 ```typescript
 const step1 = createStep({
   id: 'step-1',

package/.docs/docs/workflows/human-in-the-loop.md

@@ -8,8 +8,6 @@ Some workflows need to pause for human input before continuing. When a workflow
 
 Human-in-the-loop (HITL) input works much like [pausing a workflow](https://mastra.ai/docs/workflows/suspend-and-resume) using `suspend()`. The key difference is that when human input is required, you can return `suspend()` with a payload that provides context or guidance to the user on how to continue.
 
-![Pausing a workflow with suspend()](/assets/images/workflows-suspend-4540783670f918109ac35beaf4db914b.jpg)
-
 ```typescript
 import { createWorkflow, createStep } from '@mastra/core/workflows'
 import { z } from 'zod'
@@ -93,8 +91,6 @@ The data returned by the step can include a reason and help the user understand
 
 As with [restarting a workflow](https://mastra.ai/docs/workflows/suspend-and-resume), use `resume()` with `resumeData` to continue a workflow after receiving input from a human. The workflow resumes from the step where it was paused.
 
-![Restarting a workflow with resume()](/assets/images/workflows-resume-1e54b4d0c753ff79571f6d6b05109a60.jpg)
-
 ```typescript
 const workflow = mastra.getWorkflow('testWorkflow')
 const run = await workflow.createRun()

package/.docs/docs/workflows/overview.md

@@ -105,7 +105,7 @@ Visit [`Step`](https://mastra.ai/reference/workflows/step) for a full list of co
 
 ### Using agents and tools
 
-Workflow steps can also call registered agents or import and execute tools directly, visit the [Using Tools](https://mastra.ai/docs/agents/using-tools) page for more information.
+Workflow steps can also call registered agents or import and execute tools directly, visit the [Using Tools](https://mastra.ai/docs/agents/tools) page for more information.
 
 ## Creating a workflow
 

package/.docs/docs/workflows/scheduled-workflows.md

@@ -137,7 +137,7 @@ A few rules worth knowing:
 - Resume recomputes `nextFireAt` from now. A schedule paused for a week doesn't fire seven backlogged runs the moment you resume it. It fires on the next regular cron tick.
 - Unpause with `resumeSchedule` or the **Resume** button in Studio. Editing the workflow's `schedule` config doesn't unpause a paused row.
 - Pause and resume are idempotent. Calling pause on an already-paused schedule is a no-op.
-- This operational override controls existing schedules. Author declarative schedules in code. Declarative schedules are created, deleted, and edited in code via the `schedule` field on `createWorkflow`. To create schedules imperatively at runtime instead, use the unified [`mastra.schedules`](https://mastra.ai/docs/long-running-agents/schedules) service with a `workflowId`.
+- This operational override controls existing schedules. Author declarative schedules in code. Declarative schedules are created, deleted, and edited in code via the `schedule` field on `createWorkflow`. To create schedules imperatively at runtime instead, use the unified [`mastra.schedules`](https://mastra.ai/docs/harness/schedules) service with a `workflowId`.
 
 The underlying HTTP routes are `POST /api/schedules/:scheduleId/pause` and `POST /api/schedules/:scheduleId/resume`. Both require the `schedules:write` permission.
 
@@ -182,4 +182,4 @@ Manage Inngest schedules from the [Inngest dashboard](https://www.inngest.com/do
 - [Workflow overview](https://mastra.ai/docs/workflows/overview)
 - [Suspend and resume](https://mastra.ai/docs/workflows/suspend-and-resume)
 - [Workers](https://mastra.ai/docs/deployment/workers): The [scheduler worker](https://mastra.ai/docs/deployment/workers) runs cron schedules in a dedicated process
-- [Agent schedules](https://mastra.ai/docs/long-running-agents/schedules): Run an agent rather than a workflow on a cron schedule, and manage both schedule types at runtime through `mastra.schedules`.
+- [Agent schedules](https://mastra.ai/docs/harness/schedules): Run an agent rather than a workflow on a cron schedule, and manage both schedule types at runtime through `mastra.schedules`.

package/.docs/docs/workflows/snapshots.md

@@ -147,7 +147,7 @@ export const mastra = new Mastra({
 - [Upstash Storage](https://mastra.ai/integrations/databases/upstash)
 - [Cloudflare D1](https://mastra.ai/integrations/databases/cloudflare-d1)
 - [DynamoDB](https://mastra.ai/integrations/databases/dynamodb)
-- [More storage providers](https://mastra.ai/docs/storage/overview)
+- [More storage providers](https://mastra.ai/docs/storage)
 
 ## Best practices
 

package/.docs/docs/workflows/suspend-and-resume.md

@@ -11,8 +11,6 @@ Use `suspend()` to pause workflow execution at a specific step. You can define a
 - If the condition isn’t met, the workflow pauses and returns `suspend()`.
 - If the condition is met, the workflow continues with the remaining logic in the step.
 
-![Pausing a workflow with suspend()](/assets/images/workflows-suspend-4540783670f918109ac35beaf4db914b.jpg)
-
 ```typescript
 const step1 = createStep({
   id: 'step-1',
@@ -56,8 +54,6 @@ export const testWorkflow = createWorkflow({
 
 Use `resume()` to restart a suspended workflow from the step where it paused. Pass `resumeData` matching the step's `resumeSchema` to satisfy the suspend condition and continue execution.
 
-![Restarting a workflow with resume()](/assets/images/workflows-resume-1e54b4d0c753ff79571f6d6b05109a60.jpg)
-
 ```typescript
 import { step1 } from './workflows/test-workflow'
 

package/.docs/integrations/agentic-ui/ai-sdk-ui.md

@@ -909,7 +909,7 @@ export function TaskChat() {
 
 ### Tool streaming
 
-Tools can also stream data using `context.writer.write()` for lower-level control, or pipe an agent's stream directly to the tool's writer. For more details, see [Tool Streaming](https://mastra.ai/docs/agents/using-tools).
+Tools can also stream data using `context.writer.write()` for lower-level control, or pipe an agent's stream directly to the tool's writer. For more details, see [Tool Streaming](https://mastra.ai/docs/agents/tools).
 
 ### Examples
 

package/.docs/integrations/agentic-ui/copilotkit.md

@@ -545,7 +545,7 @@ export default function Page() {
 
 Inside `StepsFeedback`, let the user toggle steps and then call `respond({ accepted: true, steps })` to resume the agent, or `respond({ accepted: false })` to reject. The agent reads the returned value and continues accordingly. See the full component in the [UI Dojo](https://ui-dojo.mastra.ai/).
 
-The example above uses a client tool: the agent calls `generate_task_steps` and the frontend fulfills it through `respond`. Mastra can also pause on the server, suspending a tool call before it executes so a human approves or supplies input. For that path, see Mastra's [Agent approval](https://mastra.ai/docs/agents/agent-approval) guide for the backend side and CopilotKit's [`useHumanInTheLoop`](https://docs.copilotkit.ai/reference/hooks/useHumanInTheLoop) reference for the frontend.
+The example above uses a client tool: the agent calls `generate_task_steps` and the frontend fulfills it through `respond`. Mastra can also pause on the server, suspending a tool call before it executes so a human approves or supplies input. For that path, see Mastra's [Agent approval](https://mastra.ai/docs/agents/human-in-the-loop) guide for the backend side and CopilotKit's [`useHumanInTheLoop`](https://docs.copilotkit.ai/reference/hooks/useHumanInTheLoop) reference for the frontend.
 
 ## Channels
 

package/.docs/integrations/auth/google.md

@@ -278,6 +278,6 @@ curl -X POST http://localhost:4111/api/agents/weatherAgent/generate \
 
 ## Related
 
-- [Auth overview](https://mastra.ai/docs/server/auth)
-- [Composite Auth](https://mastra.ai/docs/server/auth/composite-auth)
+- [Auth overview](https://mastra.ai/docs/auth/overview)
+- [Composite Auth](https://mastra.ai/docs/auth/composite-auth)
 - [MastraAuthGoogle reference](https://mastra.ai/reference/auth/google)

package/.docs/integrations/auth/workos.md

@@ -89,7 +89,7 @@ By default, `MastraAuthWorkos` grants access to any authenticated WorkOS user. T
 
 ### FGA membership loading
 
-Set `fetchMemberships: true` when you use [`MastraFGAWorkos`](https://mastra.ai/docs/server/auth/fga). This tells the auth provider to load the user's WorkOS organization memberships during authentication so FGA checks can resolve the correct organization membership ID.
+Set `fetchMemberships: true` when you use [`MastraFGAWorkos`](https://mastra.ai/docs/auth/fga). This tells the auth provider to load the user's WorkOS organization memberships during authentication so FGA checks can resolve the correct organization membership ID.
 
 ```typescript
 import { MastraAuthWorkos, MastraFGAWorkos } from '@mastra/auth-workos'