@mastra/mcp-docs-server 1.2.17-alpha.13 → 1.2.17-alpha.16

package/.docs/docs/{long-running-agents → harness}/durable-agents.md

@@ -198,7 +198,7 @@ await durableAgent.stream('Research topic', {
 })
 ```
 
-Visit [Background tasks](https://mastra.ai/docs/long-running-agents/background-tasks) for the full background task guide, including configuration, subagents, and suspend/resume.
+Visit [Background tasks](https://mastra.ai/docs/harness/background-tasks) for the full background task guide, including configuration, subagents, and suspend/resume.
 
 ## Cleanup
 
@@ -267,7 +267,7 @@ 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)
+- [Background tasks](https://mastra.ai/docs/harness/background-tasks)
 - [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 → harness}/goals.md

@@ -10,7 +10,7 @@ A goal is a durable, thread-scoped objective: a standing instruction the agent k
 
 The objective is persisted in thread state, so it survives reloads and is evaluated in-loop, even when a new message arrives in the middle of an already-running turn.
 
-Goals build on the same machinery as [`isTaskComplete`](https://mastra.ai/docs/capabilities/subagents): an LLM-as-judge scores the agent's output each iteration and gates the loop. The difference is that a goal is **durable** (stored in thread state, not passed per call) and is set and updated through `Agent` methods rather than per-`stream()` options.
+Goals build on the same machinery as [`isTaskComplete`](https://mastra.ai/docs/subagents): an LLM-as-judge scores the agent's output each iteration and gates the loop. The difference is that a goal is **durable** (stored in thread state, not passed per call) and is set and updated through `Agent` methods rather than per-`stream()` options.
 
 ## When to use goals
 
@@ -20,11 +20,11 @@ Use a goal when you want an agent to keep working toward a single objective acro
 - Work that should continue across mid-run messages (a message delivered into a live run is still judged against the goal).
 - An objective that must persist across thread reloads or process restarts.
 
-For a one-off completion check within a single `stream()` call, use [`isTaskComplete`](https://mastra.ai/docs/capabilities/subagents) instead.
+For a one-off completion check within a single `stream()` call, use [`isTaskComplete`](https://mastra.ai/docs/subagents) instead.
 
 ## Quickstart
 
-Goals require a configured [storage](https://mastra.ai/docs/storage/overview) backend and a memory-backed thread. Add a `goal` config to the agent, a judge model is required for the goal to do anything, then set an objective for a thread:
+Goals require a configured [storage](https://mastra.ai/docs/storage) backend and a memory-backed thread. Add a `goal` config to the agent, a judge model is required for the goal to do anything, then set an objective for a thread:
 
 ```typescript
 import { Agent } from '@mastra/core/agent'
@@ -113,7 +113,7 @@ Per-objective values written by `setObjective` / `updateObjectiveOptions` take p
 
 ## Related
 
-- [Supervisor agents](https://mastra.ai/docs/capabilities/subagents): `isTaskComplete` and the rubric scorer
-- [Signal providers](https://mastra.ai/docs/long-running-agents/signal-providers): How the objective is projected into context
-- [Memory storage](https://mastra.ai/docs/storage/overview): The storage backend goals require
+- [Supervisor agents](https://mastra.ai/docs/subagents): `isTaskComplete` and the rubric scorer
+- [Signal providers](https://mastra.ai/docs/harness/signal-providers): How the objective is projected into context
+- [Memory storage](https://mastra.ai/docs/storage): The storage backend goals require
 - [Mastra Factory](https://factory.mastra.ai) and [Mastra Code](https://code.mastra.ai): Examples of goal-driven coding agents

package/.docs/docs/harness/overview.md

@@ -12,13 +12,14 @@ In Mastra, harness refers to a set of capabilities for managing an agent beyond
 
 Choose a starting point based on what the agent needs. You may use one capability or several.
 
-| If you want to                                                                        | Start here                                                                      | Why                                                                               |
-| ------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- |
-| Keep a run available through client disconnects or server restarts                    | [Durable Agents](https://mastra.ai/docs/long-running-agents/durable-agents)     | Persist run state and let clients reconnect to its stream.                        |
-| Run slow tools, workflows, or subagents without blocking                              | [Background Tasks](https://mastra.ai/docs/long-running-agents/background-tasks) | Finish work asynchronously and return its result to the agent.                    |
-| Keep an agent working until it reaches an objective                                   | [Goals](https://mastra.ai/docs/long-running-agents/goals)                       | Evaluate a thread-scoped objective until it's complete or reaches its run budget. |
-| Start work automatically at recurring times                                           | [Schedules](https://mastra.ai/docs/long-running-agents/schedules)               | Start isolated runs or send prompts into an existing thread on a cron schedule.   |
-| Add context, redirect active work, or wake an idle thread                             | [Signals](https://mastra.ai/docs/long-running-agents/signals)                   | Deliver input now or hold it for the next turn.                                   |
-| React to changes in GitHub, Slack, continuous integration, or another external system | [Signal Providers](https://mastra.ai/docs/long-running-agents/signal-providers) | Track subscriptions and forward matching events to agent threads.                 |
-| Build an interactive product with sessions, modes, state, approvals, and events       | [AgentController](https://mastra.ai/docs/harness/agent-controller)              | Host isolated sessions around a shared agent runtime.                             |
-| Let users steer, queue follow-up work, or stop an interactive run                     | [AgentController](https://mastra.ai/docs/harness/agent-controller)              | Expose run controls through each session.                                         |
+| If you want to                                                                        | Start here                                                                            | Why                                                                                     |
+| ------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
+| Keep a run available through client disconnects or server restarts                    | [Durable Agents](https://mastra.ai/docs/harness/durable-agents)                       | Persist run state and let clients reconnect to its stream.                              |
+| Run slow tools, workflows, or subagents without blocking                              | [Background Tasks](https://mastra.ai/docs/harness/background-tasks)                   | Finish work asynchronously and return its result to the agent.                          |
+| Keep an agent working until it reaches an objective                                   | [Goals](https://mastra.ai/docs/harness/goals)                                         | Evaluate a thread-scoped objective until it's complete or reaches its run budget.       |
+| Start work automatically at recurring times                                           | [Schedules](https://mastra.ai/docs/harness/schedules)                                 | Start isolated runs or send prompts into an existing thread on a cron schedule.         |
+| Add context, redirect active work, or wake an idle thread                             | [Signals](https://mastra.ai/docs/harness/signals)                                     | Deliver input now or hold it for the next turn.                                         |
+| React to changes in GitHub, Slack, continuous integration, or another external system | [Signal Providers](https://mastra.ai/docs/harness/signal-providers)                   | Track subscriptions and forward matching events to agent threads.                       |
+| Build an interactive product with sessions, modes, state, approvals, and events       | [AgentController](https://mastra.ai/docs/harness/agent-controller)                    | Host isolated sessions around a shared agent runtime.                                   |
+| Let users steer, queue follow-up work, or stop an interactive run                     | [AgentController](https://mastra.ai/docs/harness/agent-controller)                    | Expose run controls through each session.                                               |
+| Give an agent files, a shell, and the defaults a coding agent needs                   | [`createCodingAgent()`](https://mastra.ai/reference/coding-agent/create-coding-agent) | Build a standard agent with a workspace, task tracking, and retries already configured. |

package/.docs/docs/{long-running-agents → harness}/schedules.md

@@ -6,11 +6,11 @@
 
 > **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.
+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/harness/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.
 
 Schedules are persisted, so they survive restarts and redeploys. Manage them at runtime through [`mastra.schedules`](https://mastra.ai/reference/schedules/overview), the canonical create, read, update, and delete (CRUD) surface. The same surface also manages [workflow schedules](https://mastra.ai/docs/workflows/scheduled-workflows) (pass `workflowId` instead of `agentId` to schedule a workflow).
 
-> **Note:** Schedules require a [storage](https://mastra.ai/docs/storage/overview) adapter that implements the schedules domain. See the [`mastra.schedules` reference](https://mastra.ai/reference/schedules/overview) for supported adapters and API behavior.
+> **Note:** Schedules require a [storage](https://mastra.ai/docs/storage) adapter that implements the schedules domain. See the [`mastra.schedules` reference](https://mastra.ai/reference/schedules/overview) for supported adapters and API behavior.
 
 ## Quickstart
 
@@ -71,7 +71,7 @@ Without a `threadId`, each fire is an isolated `agent.generate()` run. Nothing i
 
 ### Threaded
 
-With a `threadId`, the schedule sends a [signal](https://mastra.ai/docs/long-running-agents/signals) into that thread, so the prompt joins the agent's conversation. Threaded schedules require a `resourceId` alongside the `threadId`.
+With a `threadId`, the schedule sends a [signal](https://mastra.ai/docs/harness/signals) into that thread, so the prompt joins the agent's conversation. Threaded schedules require a `resourceId` alongside the `threadId`.
 
 ```typescript
 await mastra.schedules.create({
@@ -83,7 +83,7 @@ await mastra.schedules.create({
 })
 ```
 
-Threaded schedules accept extra fields that control how the signal behaves, including the signal type, XML tag, tag attributes, and active-or-idle delivery behavior. They mirror the options [`agent.sendSignal()`](https://mastra.ai/docs/long-running-agents/signals) accepts and stay JSON-serializable so they persist with the schedule.
+Threaded schedules accept extra fields that control how the signal behaves, including the signal type, XML tag, tag attributes, and active-or-idle delivery behavior. They mirror the options [`agent.sendSignal()`](https://mastra.ai/docs/harness/signals) accepts and stay JSON-serializable so they persist with the schedule.
 
 These fields require a `threadId`. For the full threaded input shape, see the [agent schedule input reference](https://mastra.ai/reference/schedules/overview).
 
@@ -197,5 +197,5 @@ Hook exceptions are caught and logged. They never re-route the worker or trigger
 ## Related
 
 - [`mastra.schedules`](https://mastra.ai/reference/schedules/overview): API reference for creating and managing schedules.
-- [Signals](https://mastra.ai/docs/long-running-agents/signals): the delivery mechanism behind threaded schedules.
+- [Signals](https://mastra.ai/docs/harness/signals): the delivery mechanism behind threaded schedules.
 - [Scheduled workflows](https://mastra.ai/docs/workflows/scheduled-workflows): declare a cron schedule on a workflow definition.

package/.docs/docs/{long-running-agents → harness}/signal-providers.md

@@ -6,7 +6,7 @@
 
 > **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.
+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/harness/signals) into subscribed agent threads.
 
 ## When to use a signal provider
 
@@ -20,7 +20,7 @@ If you only need to push a one-off event into a thread, call [`agent.sendNotific
 
 ## How signal providers work
 
-A signal provider is the producing side of the [signals](https://mastra.ai/docs/long-running-agents/signals) system. It brings external events into a thread, while the signal APIs control how the thread consumes them.
+A signal provider is the producing side of the [signals](https://mastra.ai/docs/harness/signals) system. It brings external events into a thread, while the signal APIs control how the thread consumes them.
 
 A signal provider combines three capabilities:
 
@@ -205,7 +205,7 @@ For a production provider that watches GitHub pull requests, see the [GitHub Cha
 ## Related
 
 - [Guide: Building a signal provider](https://mastra.ai/blog/building-a-signal-provider)
-- [Signals](https://mastra.ai/docs/long-running-agents/signals)
-- [Notification signals](https://mastra.ai/docs/long-running-agents/signals)
+- [Signals](https://mastra.ai/docs/harness/signals)
+- [Notification signals](https://mastra.ai/docs/harness/signals)
 - [`SignalProvider` reference](https://mastra.ai/reference/signals/signal-provider)
 - [`WebhookSignalProvider` reference](https://mastra.ai/reference/signals/webhook-signal-provider)

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

@@ -63,7 +63,7 @@ A local `.env` file is optional. Environment variables stored on the platform ar
 
 4. Verify your deployment at the URL printed by the CLI. Append `/api/agents` to confirm it returns a JSON list of your agents.
 
-   > **Warning:** Set up [authentication](https://mastra.ai/docs/server/auth) before exposing your endpoints publicly.
+   > **Warning:** Set up [authentication](https://mastra.ai/docs/auth/overview) before exposing your endpoints publicly.
 
 The first deploy writes a `.mastra-project.json` file linking your directory to the platform project. Commit it so later deploys, CI runs, and [`mastra env`](https://mastra.ai/docs/mastra-platform/environments) commands target the same project without extra flags.
 

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

@@ -29,7 +29,7 @@ Choose the path that matches what you want to do:
 Your Mastra application is built from three building blocks:
 
 - [Agents](https://mastra.ai/docs/agents/overview): AI agents that can use tools and follow instructions while maintaining context
-- [Tools](https://mastra.ai/docs/agents/using-tools): Callable functions and integrations available to your agents
+- [Tools](https://mastra.ai/docs/agents/tools): Callable functions and integrations available to your agents
 - [Workflows](https://mastra.ai/docs/workflows/overview): Multi-step orchestration pipelines that coordinate agents and tools
 
 ## Going to production

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

@@ -56,7 +56,7 @@ You get a stable API endpoint with environment variable management and custom do
 
 4. Verify your deployment at the URL printed by the CLI. Append `/api/agents` to confirm it returns a JSON list of your agents.
 
-   > **Warning:** Set up [authentication](https://mastra.ai/docs/server/auth) before exposing your endpoints publicly.
+   > **Warning:** Set up [authentication](https://mastra.ai/docs/auth/overview) before exposing your endpoints publicly.
 
 ## Deploy lifecycle
 

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

@@ -25,7 +25,7 @@ Studio automatically generates a thread and resource ID for you. When calling `s
 
 ## Getting started
 
-Install the Mastra memory module along with a [storage adapter](https://mastra.ai/docs/storage/overview) for your database. The examples below use `@mastra/libsql`, which stores data locally in a `mastra.db` file.
+Install the Mastra memory module along with a [storage adapter](https://mastra.ai/docs/storage) for your database. The examples below use `@mastra/libsql`, which stores data locally in a `mastra.db` file.
 
 **npm**:
 

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}

@@ -145,7 +145,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 +200,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 +335,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
 

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