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

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'

package/.docs/integrations/browsers/agent-browser.md

@@ -99,11 +99,11 @@ const browser = new AgentBrowser({
 })
 ```
 
-This adds `browser_record` and `browser_record_caption` to the agent's toolset. See [Browser recording (Beta)](https://mastra.ai/docs/browser/overview) for details. See [AgentBrowser reference](https://mastra.ai/reference/browser/agent-browser) for all configuration options and tool details.
+This adds `browser_record` and `browser_record_caption` to the agent's toolset. See [Browser recording (Beta)](https://mastra.ai/docs/browser) for details. See [AgentBrowser reference](https://mastra.ai/reference/browser/agent-browser) for all configuration options and tool details.
 
 ## Related
 
-- [Browser overview](https://mastra.ai/docs/browser/overview)
+- [Browser overview](https://mastra.ai/docs/browser)
 - [Stagehand](https://mastra.ai/integrations/browsers/stagehand)
 - [Firecrawl](https://mastra.ai/integrations/browsers/firecrawl)
 - [AgentBrowser reference](https://mastra.ai/reference/browser/agent-browser)

package/.docs/integrations/browsers/browser-viewer.md

@@ -2,7 +2,7 @@
 
 # BrowserViewer
 
-The `@mastra/browser-viewer` package provides browser automation for CLI-based tools like [agent-browser](https://www.npmjs.com/package/agent-browser), [browser-use](https://pypi.org/project/browser-use/), and [browse](https://www.npmjs.com/package/browse). BrowserViewer launches Chrome via Playwright, exposes a Chrome DevTools Protocol (CDP) URL, and automatically injects it into CLI commands run through [sandbox tools](https://mastra.ai/docs/workspace/sandbox).
+The `@mastra/browser-viewer` package provides browser automation for CLI-based tools like [agent-browser](https://www.npmjs.com/package/agent-browser), [browser-use](https://pypi.org/project/browser-use/), and [browse](https://www.npmjs.com/package/browse). BrowserViewer launches Chrome via Playwright, exposes a Chrome DevTools Protocol (CDP) URL, and automatically injects it into CLI commands run through [sandbox tools](https://mastra.ai/docs/sandbox/overview).
 
 ## When to use BrowserViewer
 
@@ -49,7 +49,7 @@ Install the CLI tool in your workspace environment. This example uses `browser-u
 pip install browser-use
 ```
 
-Install the corresponding [skill](https://mastra.ai/docs/workspace/skills) so the agent knows how to use the CLI:
+Install the corresponding [skill](https://mastra.ai/docs/sandbox/skills) so the agent knows how to use the CLI:
 
 ```bash
 npx skills add browser-use/browser-use --skill browser-use
@@ -104,7 +104,7 @@ When the agent runs a CLI command like `browser-use open https://example.com`, M
 
 ## Supported CLIs
 
-BrowserViewer supports three CLI providers. Each CLI must be installed separately in your workspace environment. Each CLI also publishes a [skill](https://mastra.ai/docs/workspace/skills) that teaches the agent its commands and workflows.
+BrowserViewer supports three CLI providers. Each CLI must be installed separately in your workspace environment. Each CLI also publishes a [skill](https://mastra.ai/docs/sandbox/skills) that teaches the agent its commands and workflows.
 
 Set the `cli` option to match the CLI your agent uses:
 
@@ -144,8 +144,8 @@ CDP flag: `--ws` See [BrowserViewer reference](https://mastra.ai/reference/brows
 
 ## Related
 
-- [Browser overview](https://mastra.ai/docs/browser/overview)
+- [Browser overview](https://mastra.ai/docs/browser)
 - [AgentBrowser](https://mastra.ai/integrations/browsers/agent-browser)
 - [Stagehand](https://mastra.ai/integrations/browsers/stagehand)
-- [Sandbox](https://mastra.ai/docs/workspace/sandbox)
-- [Workspace skills](https://mastra.ai/docs/workspace/skills)
+- [Sandbox](https://mastra.ai/docs/sandbox/overview)
+- [Workspace skills](https://mastra.ai/docs/sandbox/skills)

package/.docs/integrations/browsers/firecrawl.md

@@ -123,6 +123,6 @@ const browser = new FirecrawlBrowser({
 
 ## Related
 
-- [Browser overview](https://mastra.ai/docs/browser/overview)
+- [Browser overview](https://mastra.ai/docs/browser)
 - [AgentBrowser](https://mastra.ai/integrations/browsers/agent-browser)
 - [FirecrawlBrowser reference](https://mastra.ai/reference/browser/firecrawl-browser)

package/.docs/integrations/browsers/stagehand.md

@@ -162,10 +162,10 @@ const browser = new StagehandBrowser({
 })
 ```
 
-This adds `browser_record` and `browser_record_caption` to the agent's toolset. See [Browser recording (Beta)](https://mastra.ai/docs/browser/overview) for details.
+This adds `browser_record` and `browser_record_caption` to the agent's toolset. See [Browser recording (Beta)](https://mastra.ai/docs/browser) for details.
 
 ## Related
 
-- [Browser overview](https://mastra.ai/docs/browser/overview)
+- [Browser overview](https://mastra.ai/docs/browser)
 - [AgentBrowser](https://mastra.ai/integrations/browsers/agent-browser)
 - [StagehandBrowser reference](https://mastra.ai/reference/browser/stagehand-browser)

package/.docs/integrations/channels/discord.md

@@ -94,5 +94,5 @@ Use this URL anywhere the Discord adapter docs ask for the interactions endpoint
 
 ## Related
 
-- [Channels overview](https://mastra.ai/docs/capabilities/channels)
-- [More](https://mastra.ai/docs/capabilities/channels)
+- [Channels overview](https://mastra.ai/docs/channels)
+- [More](https://mastra.ai/docs/channels)

package/.docs/integrations/channels/github.md

@@ -2,7 +2,7 @@
 
 # GitHub
 
-The `@mastra/github-signals` provider lets an agent follow pull requests (PRs). It polls subscribed PRs and sends [notification signals](https://mastra.ai/docs/long-running-agents/signals) to the agent thread when relevant activity occurs.
+The `@mastra/github-signals` provider lets an agent follow pull requests (PRs). It polls subscribed PRs and sends [notification signals](https://mastra.ai/docs/harness/signals) to the agent thread when relevant activity occurs.
 
 ## Installation
 

package/.docs/integrations/channels/imessage.md

@@ -110,7 +110,7 @@ https://your-app.example.com/api/agents/imessage-agent/channels/imessage/webhook
 
 Register this URL in the [Photon dashboard](https://app.photon.codes), then set the signing secret it returns as `IMESSAGE_WEBHOOK_SECRET`. The secret is shown once at registration. The adapter verifies the signature on every delivery and rejects requests that don't match. Webhooks are available in hosted mode only.
 
-> **Note:** Photon delivers to public HTTPS endpoints only. It won't deliver to `http://`, to private addresses like `localhost`, or through a redirect. For local development, use a tunnel as described in the [Channels overview](https://mastra.ai/docs/capabilities/channels).
+> **Note:** Photon delivers to public HTTPS endpoints only. It won't deliver to `http://`, to private addresses like `localhost`, or through a redirect. For local development, use a tunnel as described in the [Channels overview](https://mastra.ai/docs/channels).
 
 ## Duplicate deliveries
 
@@ -181,9 +181,9 @@ imessage: {
 },
 ```
 
-On serverless platforms, prefer webhooks. A gateway listener needs a process that stays alive. See [Serverless deployment](https://mastra.ai/docs/capabilities/channels).
+On serverless platforms, prefer webhooks. A gateway listener needs a process that stays alive. See [Serverless deployment](https://mastra.ai/docs/channels).
 
 ## Related
 
-- [Channels overview](https://mastra.ai/docs/capabilities/channels)
-- [More](https://mastra.ai/docs/capabilities/channels)
+- [Channels overview](https://mastra.ai/docs/channels)
+- [More](https://mastra.ai/docs/channels)

package/.docs/integrations/channels/slack.md

@@ -273,7 +273,7 @@ For finer control, gate on the sender's identity. Every request carries the send
 
 ### Server authentication
 
-The Slack webhook route is exempt from Mastra's [server authentication](https://mastra.ai/docs/server/auth). Slack can't send a bearer token, so Mastra registers the channel webhook as a public route and verifies each request with the Slack signing secret instead. This holds even when you enable a provider like [`MastraAuthSimple`](https://mastra.ai/docs/server/auth/simple-auth): the rest of your API stays protected, but the webhook route relies on the signing secret rather than your server auth. Keep `SLACK_SIGNING_SECRET` set so the adapter can reject requests that Slack didn't sign.
+The Slack webhook route is exempt from Mastra's [server authentication](https://mastra.ai/docs/auth/overview). Slack can't send a bearer token, so Mastra registers the channel webhook as a public route and verifies each request with the Slack signing secret instead. This holds even when you enable a provider like [`MastraAuthSimple`](https://mastra.ai/docs/auth/simple-auth): the rest of your API stays protected, but the webhook route relies on the signing secret rather than your server auth. Keep `SLACK_SIGNING_SECRET` set so the adapter can reject requests that Slack didn't sign.
 
 ### External channels
 
@@ -315,13 +315,13 @@ The channel context includes:
 - `platform`: The platform identifier, `slack` for this adapter.
 - `userId` and `userName`: The sender's Slack user ID and display name.
 
-Mastra also turns this context into a short system message. The agent learns the platform and its own identity, plus whether the conversation is a direct message or a public channel. See [thread context](https://mastra.ai/docs/capabilities/channels) in the channels overview for how to change that behavior.
+Mastra also turns this context into a short system message. The agent learns the platform and its own identity, plus whether the conversation is a direct message or a public channel. See [thread context](https://mastra.ai/docs/channels) in the channels overview for how to change that behavior.
 
 ## Production deployment
 
 When you deploy the Mastra server, update both request URLs in the Slack app settings to the production webhook URL. The tunnel URL used for local development is temporary and changes when the tunnel restarts.
 
-Channels on serverless platforms may need `waitUntil` and shared pub/sub configuration so background responses and thread leases work across short-lived instances. See [serverless deployment](https://mastra.ai/docs/capabilities/channels) in the channels overview.
+Channels on serverless platforms may need `waitUntil` and shared pub/sub configuration so background responses and thread leases work across short-lived instances. See [serverless deployment](https://mastra.ai/docs/channels) in the channels overview.
 
 ### Idle servers
 
@@ -329,7 +329,7 @@ Platform servers scale down to idle when they aren't receiving traffic, and that
 
 ## Related
 
-- [Channels overview](https://mastra.ai/docs/capabilities/channels)
-- [More](https://mastra.ai/docs/capabilities/channels)
+- [Channels overview](https://mastra.ai/docs/channels)
+- [More](https://mastra.ai/docs/channels)
 - [Channels reference](https://mastra.ai/reference/agents/channels)
 - [Deployment overview](https://mastra.ai/docs/deployment/overview)

package/.docs/integrations/channels/teams.md

@@ -96,5 +96,5 @@ Use this URL anywhere the Teams adapter docs ask for the bot endpoint or webhook
 
 ## Related
 
-- [Channels overview](https://mastra.ai/docs/capabilities/channels)
-- [More](https://mastra.ai/docs/capabilities/channels)
+- [Channels overview](https://mastra.ai/docs/channels)
+- [More](https://mastra.ai/docs/channels)

package/.docs/integrations/channels/telegram.md

@@ -94,5 +94,5 @@ Use this URL anywhere the Telegram adapter docs ask for the webhook URL. Telegra
 
 ## Related
 
-- [Channels overview](https://mastra.ai/docs/capabilities/channels)
-- [More](https://mastra.ai/docs/capabilities/channels)
+- [Channels overview](https://mastra.ai/docs/channels)
+- [More](https://mastra.ai/docs/channels)

package/.docs/integrations/channels/whatsapp.md

@@ -95,5 +95,5 @@ Use this URL for incoming WhatsApp event delivery. The generated Mastra route ha
 
 ## Related
 
-- [Channels overview](https://mastra.ai/docs/capabilities/channels)
-- [More](https://mastra.ai/docs/capabilities/channels)
+- [Channels overview](https://mastra.ai/docs/channels)
+- [More](https://mastra.ai/docs/channels)

package/.docs/integrations/databases/postgresql.md

@@ -408,6 +408,7 @@ PostgreSQL storage creates composite indexes during initialization for common qu
 - `mastra_ai_spans_scope_startedat_idx`: (scope, startedAt DESC)
 - `mastra_scores_trace_id_span_id_created_at_idx`: (traceId, spanId, createdAt DESC)
 - `mastra_workflow_snapshot_name_createdat_idx`: (workflow\_name, createdAt DESC)
+- `mastra_workflow_snapshot_name_status_createdat_idx`: (workflow\_name, snapshot->>'status', createdAt DESC), created only when the `snapshot` column is `jsonb`
 
 These indexes improve performance for filtered queries with sorting, including `dateRange` filters on message queries and Studio's workflow runs-list.
 

package/.docs/integrations/deploy/amazon-ec2.md

@@ -4,7 +4,7 @@
 
 Deploy your Mastra server to Amazon EC2. The server runs on infrastructure you manage and can support long-running agents and workflows.
 
-> **Note:** This guide covers deploying the [Mastra server](https://mastra.ai/docs/server/mastra-server). If you're using a [server adapter](https://mastra.ai/docs/server/server-adapters) or [web framework](https://mastra.ai/docs/deployment/web-framework), deploy the way you normally would for that framework.
+> **Note:** This guide covers deploying the [Mastra server](https://mastra.ai/docs/server/overview). If you're using a [server adapter](https://mastra.ai/docs/server/server-adapters) or [web framework](https://mastra.ai/docs/deployment/web-framework), deploy the way you normally would for that framework.
 
 ## Before you begin
 
@@ -114,7 +114,7 @@ For production, you'll also need:
 
    This is a basic example. In production, use a process manager like [PM2](https://pm2.keymetrics.io/) or [systemd](https://systemd.io/) to keep your application running and handle restarts.
 
-   > **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.
 
 6. Your Mastra server is now running on port 4111, but it's only accessible locally.
 

package/.docs/integrations/deploy/aws-lambda.md

@@ -4,7 +4,7 @@
 
 Deploy your Mastra application to AWS Lambda using Docker containers and the [AWS Lambda Web Adapter](https://github.com/awslabs/aws-lambda-web-adapter). This approach runs your Mastra server as a containerized Lambda function with automatic scaling.
 
-> **Note:** This guide covers deploying the [Mastra server](https://mastra.ai/docs/server/mastra-server). If you're using a [server adapter](https://mastra.ai/docs/server/server-adapters) or [web framework](https://mastra.ai/docs/deployment/web-framework), deploy the way you normally would for that framework.
+> **Note:** This guide covers deploying the [Mastra server](https://mastra.ai/docs/server/overview). If you're using a [server adapter](https://mastra.ai/docs/server/server-adapters) or [web framework](https://mastra.ai/docs/deployment/web-framework), deploy the way you normally would for that framework.
 
 ## Before you begin
 
@@ -146,7 +146,7 @@ CMD ["node", ".mastra/output/index.mjs"]
 
 2. You can now call your Mastra endpoints over HTTP.
 
-   > **Warning:** For production deployments, set up [authentication](https://mastra.ai/docs/server/auth) before exposing your endpoints publicly, restrict CORS origins to your trusted domains, use AWS IAM roles for secure access to other AWS services, and store sensitive environment variables in AWS Secrets Manager or Parameter Store.
+   > **Warning:** For production deployments, set up [authentication](https://mastra.ai/docs/auth/overview) before exposing your endpoints publicly, restrict CORS origins to your trusted domains, use AWS IAM roles for secure access to other AWS services, and store sensitive environment variables in AWS Secrets Manager or Parameter Store.
 
 ## Next steps
 
@@ -155,7 +155,7 @@ This guide provides a quickstart for deploying Mastra to AWS Lambda. For product
 ## Related
 
 - [Deployment overview](https://mastra.ai/docs/deployment/overview)
-- [Mastra server](https://mastra.ai/docs/server/mastra-server)
+- [Mastra server](https://mastra.ai/docs/server/overview)
 - [Server adapters](https://mastra.ai/docs/server/server-adapters)
 - [AWS Lambda documentation](https://docs.aws.amazon.com/lambda/)
 - [AWS Lambda Web Adapter](https://github.com/awslabs/aws-lambda-web-adapter)

package/.docs/integrations/deploy/azure-app-services.md

@@ -4,7 +4,7 @@
 
 Deploy your Mastra applications to Azure App Services.
 
-> **Note:** This guide covers deploying the [Mastra server](https://mastra.ai/docs/server/mastra-server). If you're using a [server adapter](https://mastra.ai/docs/server/server-adapters) or [web framework](https://mastra.ai/docs/deployment/web-framework), deploy the way you normally would for that framework.
+> **Note:** This guide covers deploying the [Mastra server](https://mastra.ai/docs/server/overview). If you're using a [server adapter](https://mastra.ai/docs/server/server-adapters) or [web framework](https://mastra.ai/docs/deployment/web-framework), deploy the way you normally would for that framework.
 
 ## Before you begin
 
@@ -83,7 +83,7 @@ Copy the URL from the Azure portal and visit `https://<your-app-name>.azurewebsi
 
 You can now call your Mastra endpoints over HTTP.
 
-> **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.
 
 ## Next steps
 

package/.docs/integrations/deploy/cloudflare.md

@@ -94,8 +94,8 @@ After setting up your project, push it to your remote Git provider of choice (e.
 
 3. Try out your newly deployed function by going to `https://<your-project-name>.<slug>.workers.dev/api/agents`. You should get a JSON response listing all available agents.
 
-   Since the [Mastra server](https://mastra.ai/docs/server/mastra-server) prefixes every API endpoint with `/api`, you have to add it to your URLs when making requests.
+   Since the [Mastra server](https://mastra.ai/docs/server/overview) prefixes every API endpoint with `/api`, you have to add it to your URLs when making requests.
 
 4. You can now call your Mastra endpoints over HTTP.
 
-   > **Note:** Set up [authentication](https://mastra.ai/docs/server/auth) before exposing your endpoints publicly.
+   > **Note:** Set up [authentication](https://mastra.ai/docs/auth/overview) before exposing your endpoints publicly.

package/.docs/integrations/deploy/digital-ocean.md

@@ -4,7 +4,7 @@
 
 This guide covers Digital Ocean's App Platform and Droplets. Each of these offerings has its own set of strengths and is suited for different types of projects and developer expertise. Read [Digital Ocean's comparison](https://www.digitalocean.com/community/conceptual-articles/digitalocean-app-platform-vs-doks-vs-droplets) to understand the differences and choose the best option for your project.
 
-> **Note:** This guide covers deploying the [Mastra server](https://mastra.ai/docs/server/mastra-server). If you're using a [server adapter](https://mastra.ai/docs/server/server-adapters) or [web framework](https://mastra.ai/docs/deployment/web-framework), deploy the way you normally would for that framework.
+> **Note:** This guide covers deploying the [Mastra server](https://mastra.ai/docs/server/overview). If you're using a [server adapter](https://mastra.ai/docs/server/server-adapters) or [web framework](https://mastra.ai/docs/deployment/web-framework), deploy the way you normally would for that framework.
 
 ## Before you begin
 
@@ -50,7 +50,7 @@ After setting up your project, push it to your remote Git provider of choice (e.
 
 5. You can now call your Mastra endpoints over HTTP.
 
-   > **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.
 
 ## Droplets
 
@@ -162,7 +162,7 @@ After setting up your project, push it to your remote Git provider of choice (e.
 
 6. You can now call your Mastra endpoints over HTTP.
 
-   > **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.
 
 ## Related