@mastra/mcp-docs-server 1.2.6 → 1.2.7-alpha.10

package/.docs/docs/agent-builder/integrations.md

@@ -40,7 +40,7 @@ export const mastra = new Mastra({
 })
 ```
 
-Each provider's toolkits become available in the Builder once it is registered. Use `allowedToolkits` to restrict which toolkits the provider exposes — by slug, such as `gmail` or `googlecalendar`. Omit it to expose every toolkit the provider offers. To add another provider, import it and add another entry to `toolProviders`. For the full list of providers and their options, see [Tools — Integration providers](https://mastra.ai/docs/editor/tools).
+Each provider's toolkits become available in the Builder once it's registered. Use `allowedToolkits` to restrict which toolkits the provider exposes — by slug, such as `gmail` or `googlecalendar`. Omit it to expose every toolkit the provider offers. To add another provider, import it and add another entry to `toolProviders`. For the full list of providers and their options, see [Tools — Integration providers](https://mastra.ai/docs/editor/tools).
 
 ## Set up a Composio auth config
 

package/.docs/docs/agent-builder/overview.md

@@ -4,10 +4,10 @@
 
 > **Note:** The Agent Builder is part of the Mastra Enterprise Edition. Production deployments require a valid EE license. [Contact sales](https://mastra.ai/contact) for more information.
 
-[YouTube video player](https://www.youtube-nocookie.com/embed/AbdgIu4Z07I)
-
 The Agent Builder lets you build, configure, and operate Mastra agents all within the UI. It runs inside your Mastra server, persists everything to `Mastra.storage`, and supports multi-tenant agent workflows with RBAC and channel integrations.
 
+> **📹 Watch:** Watch [Mastra Agent Builder overview](https://www.youtube.com/watch?v=AbdgIu4Z07I) to see how teams create and configure agents from the UI.
+
 - [**Configuration**](https://mastra.ai/docs/agent-builder/configuration): Toggle UI sections and pin admin-controlled defaults for every new agent.
 - [**Model policy**](https://mastra.ai/docs/agent-builder/model-policy): Restrict which providers and models the Builder exposes, and pin a default.
 - [**Memory**](https://mastra.ai/docs/agent-builder/memory): Configure the default memory shape for every Builder-created agent.
@@ -108,4 +108,5 @@ Omitting the `builder` field has the same effect.
 
 - [Configuration](https://mastra.ai/docs/agent-builder/configuration): Toggle Builder surfaces and pin defaults for new agents.
 - [Access control](https://mastra.ai/docs/agent-builder/access-control): Gate the Builder with authentication and role-based access control.
-- [Deploying](https://mastra.ai/docs/agent-builder/deploying): Replace local development primitives with production-ready storage, filesystems, and sandboxes.
+- [Deploying](https://mastra.ai/docs/agent-builder/deploying): Replace local development primitives with production-ready storage, filesystems, and sandboxes.
+- 📹 [Mastra Agent Builder workshop](https://www.youtube.com/watch?v=p2p_wb-rUPg\&t=666s)

package/.docs/docs/agent-builder/skill-registries.md

@@ -23,9 +23,7 @@ new MastraEditor({
 })
 ```
 
-The Builder library tab now exposes a **Browse** view backed by skills.sh. End users can preview a skill, then install it into an agent.
-
-> **Note:** See the [AgentBuilderOptions reference](https://mastra.ai/reference/editor/agent-builder/agent-builder-options) for the full `registries` schema.
+The Builder library tab now exposes a **Browse** view backed by skills.sh. End users can preview a skill, then install it into an agent. See the [AgentBuilderOptions reference](https://mastra.ai/reference/editor/agent-builder/agent-builder-options) for the full `registries` schema.
 
 ## Related
 

package/.docs/docs/agent-controller/modes.md

@@ -98,7 +98,7 @@ const reviewMode = {
 
 - **`undefined`** (default): no mode-level restriction — every tool is visible.
 - **`[]`**: no tools are available for this mode.
-- A denied tool stays hidden even if it appears in the list. Per-tool and per-category `deny` rules in your permission config always take precedence.
+- A denied tool stays hidden even when the list includes it. Per-tool and per-category `deny` rules in your permission config always take precedence.
 
 Workspace tools use the same list as every other tool — reference them by their exposed names (`view`, `write_file`, `find_files`, etc.). Visibility is enforced at LLM-call time, so the model never sees — and can't attempt to call — a tool outside the allowlist.
 

package/.docs/docs/agent-controller/overview.md

@@ -32,7 +32,7 @@ Use the AgentController when your application needs:
 - Subagent orchestration to delegate focused subtasks with constrained tools
 - Session continuity with persistent threads, state, and observational memory across restarts
 
-You could assemble all of this yourself on top of the [Agent class](https://mastra.ai/docs/agents/overview), which exposes the full agent loop, tools, and memory. The AgentController is an opinionated set of defaults that wires those pieces into one application style: an ongoing session where the agent acts as a collaborator rather than a one-shot endpoint. Reach for the Agent class directly when you want full control or a simple request-response call; reach for the AgentController when you want the collaborative-session model without building the runtime around it.
+You could assemble all of this yourself on top of the [Agent class](https://mastra.ai/docs/agents/overview), which exposes the full agent loop, tools, and memory. The AgentController is an opinionated set of defaults that wires those pieces into one application style: an ongoing session where the agent acts as a collaborator rather than a one-shot endpoint. Reach for the Agent class directly when you want full control or a request-response call; reach for the AgentController when you want the collaborative-session model without building the runtime around it.
 
 ## Key capabilities
 
@@ -88,7 +88,7 @@ await agentController.selectOrCreateThread()
 await agentController.sendMessage({ content: 'Hello!' })
 ```
 
-> **Note:** Visit the [AgentController reference](https://mastra.ai/reference/agent-controller/agent-controller-class) for the full constructor parameters and method signatures.
+Visit the [AgentController reference](https://mastra.ai/reference/agent-controller/agent-controller-class) for the full constructor parameters and method signatures.
 
 ## Architecture
 
@@ -128,4 +128,5 @@ Your app sends commands — send a message, switch mode, approve a tool call —
 - [Threads and state](https://mastra.ai/docs/agent-controller/threads-and-state): Manage persistent conversations
 - [Subagents](https://mastra.ai/docs/agent-controller/subagents): Delegate focused subtasks
 - [Tool approvals and permissions](https://mastra.ai/docs/agent-controller/tool-approvals): Human-in-the-loop gating
-- [API reference](https://mastra.ai/reference/agent-controller/agent-controller-class): Full constructor and method docs
+- [API reference](https://mastra.ai/reference/agent-controller/agent-controller-class): Full constructor and method docs
+- 📹 [Mastra AgentController harness workshop](https://www.youtube.com/watch?v=tV1pSleP-LM)

package/.docs/docs/agent-controller/session.md

@@ -6,9 +6,9 @@ A [`Session`](https://mastra.ai/reference/agent-controller/session) holds the li
 
 ## What the Session tracks
 
-The Session is the live state of a single user's interaction with the AgentController. It answers "what is true right now": who the session belongs to, which thread is currently bound, which mode and model are selected, what the user has approved, what's queued or running, the application state, and the snapshot to render. A session has one active thread at a time but can list, switch between, and clone many threads over its lifetime. Anything that describes the current state lives here; the AgentController owns the shared infrastructure every session runs on.
+The Session is the live state of a single user's interaction with the AgentController. It answers "what's true right now": who the session belongs to, which thread is currently bound, which mode and model are selected, what the user has approved, what's queued or running, the application state, and the snapshot to render. A session has one active thread at a time but can list, switch between, and clone many threads over its lifetime. Anything that describes the current state lives here; the AgentController owns the shared infrastructure every session runs on.
 
-Because each session has its own identity and state, one AgentController can serve many users at once — each backed by its own Session — without one session's mode, grants, or active thread leaking into another.
+Because each session has its own identity and state, one AgentController can serve many users at once — each with a different `resourceId` backed by its own Session — without one session's mode, grants, or active thread leaking into another. Calling `createSession` with the same `resourceId` returns the existing session (get-or-create), so a resource always resumes its own session.
 
 The rest of this page walks through the Session's state. Each part is a focused sub-object on `agentController.session`:
 
@@ -133,9 +133,7 @@ agentController.subscribe(event => {
 })
 ```
 
-This is the recommended pattern for most UIs. Subscribe to individual typed events only when you need to react to a specific transition rather than re-render the whole view.
-
-> **Note:** Visit the [Session reference](https://mastra.ai/reference/agent-controller/session) for the full list of sub-objects and method signatures.
+This is the recommended pattern for most UIs. Subscribe to individual typed events only when you need to react to a specific transition rather than re-render the whole view. Visit the [Session reference](https://mastra.ai/reference/agent-controller/session) for the full list of sub-objects and method signatures.
 
 ## Related
 

package/.docs/docs/agents/a2a.md

@@ -261,4 +261,5 @@ Use this hook to enforce expected providers, expected endpoints, certificate-bou
 - [Agent reference](https://mastra.ai/reference/agents/agent)
 - [JavaScript client agents reference](https://mastra.ai/reference/client-js/agents)
 - [A2A core concepts](https://a2a-protocol.org/latest/topics/key-concepts/)
-- [A2A discovery guide](https://a2a-protocol.org/latest/topics/agent-discovery/)
+- [A2A discovery guide](https://a2a-protocol.org/latest/topics/agent-discovery/)
+- 📹 [Agent-to-agent with Mastra workshop](https://www.youtube.com/watch?v=LQDzyNGm-aw)

package/.docs/docs/agents/agent-approval.md

@@ -48,7 +48,7 @@ for await (const chunk of stream.fullStream) {
 }
 ```
 
-> **Note:** Agent approval uses snapshots to capture request state. Configure a [storage provider](https://mastra.ai/docs/memory/storage) on your Mastra instance or you'll see a "snapshot not found" error.
+> **Note:** Agent approval uses snapshots to capture request state. Configure a [storage provider](https://mastra.ai/docs/storage/overview) on your Mastra instance or you'll see a "snapshot not found" error.
 >
 > Snapshots for agent runs are minimal resume artifacts: they hold only what's needed to resume the suspended run and are deleted once the run finishes. Use [tracing](https://mastra.ai/docs/observability/overview) for the execution record and [memory](https://mastra.ai/docs/memory/overview) for the conversation history.
 
@@ -420,7 +420,7 @@ Each returned run includes the suspended tool calls (`toolCallId`, `toolName`, `
 
 The same discovery is available over HTTP as `GET /agents/:agentId/suspended-runs` and in the client SDK as [`agent.listSuspendedRuns()`](https://mastra.ai/reference/client-js/agents), so browser-based approval UIs can rediscover pending runs directly.
 
-> **Note:** Suspended runs only survive restarts when your Mastra instance is configured with a persistent [storage provider](https://mastra.ai/docs/memory/storage). The default in-memory store loses snapshots when the process exits.
+> **Note:** Suspended runs only survive restarts when your Mastra instance is configured with a persistent [storage provider](https://mastra.ai/docs/storage/overview). The default in-memory store loses snapshots when the process exits.
 
 ## Tool approval: Supervisor agents
 

package/.docs/docs/agents/code-mode.md

@@ -94,7 +94,7 @@ For `createCodeMode()` to work well, keep these tips in mind:
 - Keep tools focused, so each does one thing well and the model composes them in code.
 - Code mode helps most when calls can be parallelized with `Promise.all`.
 
-> **Note:** Visit the [`createCodeMode()` reference](https://mastra.ai/reference/tools/create-code-mode) for configuration options, return values, result shape, and instructions inspection.
+Visit the [`createCodeMode()` reference](https://mastra.ai/reference/tools/create-code-mode) for configuration options, return values, result shape, and instructions inspection.
 
 ## Scoping tools across multiple code tools
 

package/.docs/docs/agents/guardrails.md

@@ -29,7 +29,7 @@ export const normalizedAgent = new Agent({
 })
 ```
 
-> **Note:** Visit [`UnicodeNormalizer()`](https://mastra.ai/reference/processors/unicode-normalizer) reference for a full list of configuration options.
+Visit [`UnicodeNormalizer()`](https://mastra.ai/reference/processors/unicode-normalizer) reference for a full list of configuration options.
 
 ### Prevent prompt injection
 
@@ -52,7 +52,7 @@ export const secureAgent = new Agent({
 })
 ```
 
-> **Note:** Visit [`PromptInjectionDetector()`](https://mastra.ai/reference/processors/prompt-injection-detector) reference for a full list of configuration options.
+Visit [`PromptInjectionDetector()`](https://mastra.ai/reference/processors/prompt-injection-detector) reference for a full list of configuration options.
 
 ### Detect and translate language
 
@@ -75,7 +75,7 @@ export const multilingualAgent = new Agent({
 })
 ```
 
-> **Note:** Visit [`LanguageDetector()`](https://mastra.ai/reference/processors/language-detector) reference for a full list of configuration options.
+Visit [`LanguageDetector()`](https://mastra.ai/reference/processors/language-detector) reference for a full list of configuration options.
 
 ## Output processors
 
@@ -101,7 +101,7 @@ export const batchedAgent = new Agent({
 })
 ```
 
-> **Note:** Visit [`BatchPartsProcessor()`](https://mastra.ai/reference/processors/batch-parts-processor) reference for a full list of configuration options.
+Visit [`BatchPartsProcessor()`](https://mastra.ai/reference/processors/batch-parts-processor) reference for a full list of configuration options.
 
 ### Scrub system prompts
 
@@ -128,7 +128,7 @@ const scrubbedAgent = new Agent({
 })
 ```
 
-> **Note:** Visit [`SystemPromptScrubber()`](https://mastra.ai/reference/processors/system-prompt-scrubber) reference for a full list of configuration options.
+Visit [`SystemPromptScrubber()`](https://mastra.ai/reference/processors/system-prompt-scrubber) reference for a full list of configuration options.
 
 > **Note:** When streaming responses over HTTP, Mastra redacts sensitive request data (system prompts, tool definitions, API keys) from stream chunks at the server level by default. See [Stream data redaction](https://mastra.ai/docs/server/mastra-server) for details.
 
@@ -158,7 +158,7 @@ export const moderatedAgent = new Agent({
 })
 ```
 
-> **Note:** Visit [`ModerationProcessor()`](https://mastra.ai/reference/processors/moderation-processor) reference for a full list of configuration options.
+Visit [`ModerationProcessor()`](https://mastra.ai/reference/processors/moderation-processor) reference for a full list of configuration options.
 
 ### Detect and redact PII
 
@@ -184,7 +184,7 @@ export const privateAgent = new Agent({
 })
 ```
 
-> **Note:** Visit [`PIIDetector()`](https://mastra.ai/reference/processors/pii-detector) reference for a full list of configuration options.
+Visit [`PIIDetector()`](https://mastra.ai/reference/processors/pii-detector) reference for a full list of configuration options.
 
 ### Enforce cost limits
 
@@ -206,7 +206,7 @@ export const budgetedAgent = new Agent({
 })
 ```
 
-> **Note:** Visit [`CostGuardProcessor()`](https://mastra.ai/reference/processors/cost-guard-processor) reference for scoping modes, time windows, metric persistence delays, and the `onViolation` callback. Requires observability storage with `getMetricAggregate` support.
+Visit [`CostGuardProcessor()`](https://mastra.ai/reference/processors/cost-guard-processor) reference for scoping modes, time windows, metric persistence delays, and the `onViolation` callback. Requires observability storage with `getMetricAggregate` support.
 
 ## Processor strategies
 
@@ -386,4 +386,5 @@ outputProcessors: [
 
 - [Processors](https://mastra.ai/docs/agents/processors): How processors work, execution order, custom processors, and retry mechanism
 - [`Processor` Interface](https://mastra.ai/reference/processors/processor-interface): API reference for the `Processor` interface
-- [Memory Processors](https://mastra.ai/docs/memory/memory-processors): Processors for message history, semantic recall, and working memory
+- [Memory Processors](https://mastra.ai/docs/memory/memory-processors): Processors for message history, semantic recall, and working memory
+- 📹 [Mastra processors and guardrails workshop](https://www.youtube.com/watch?v=4Vpp7xQYvl0)

package/.docs/docs/agents/networks.md

@@ -95,7 +95,7 @@ console.log(final?.summary)
 
 When a primitive requires approval, the stream emits an `agent-execution-approval` or `tool-execution-approval` chunk. Use `approveNetworkToolCall()` or `declineNetworkToolCall()` to respond.
 
-Network approval uses snapshots to capture execution state. Ensure a [storage provider](https://mastra.ai/docs/memory/storage) is enabled in your Mastra instance.
+Network approval uses snapshots to capture execution state. Ensure a [storage provider](https://mastra.ai/docs/storage/overview) is enabled in your Mastra instance.
 
 ```typescript
 const stream = await routingAgent.network('Perform some sensitive action', {

package/.docs/docs/agents/overview.md

@@ -54,7 +54,7 @@ export const weatherTool = createTool({
 })
 ```
 
-If you need to create an agent, create a new file and use `import { Agent } from "@mastra/core/agent"`. The constructor takes `{ id, name, instructions, model }`. The `model` property is a string in Mastra's model router format: `provider/model`, for example `openai/gpt-5.5`. For OpenAI models, use `openai/<model>`, not `openai:<model>`, and don't pass a provider object. No provider import is needed for this format. Do not install any AI SDK package unless Mastra's documentation says otherwise.
+If you need to create an agent, create a new file and use `import { Agent } from "@mastra/core/agent"`. The constructor takes `{ id, name, instructions, model }`. The `model` property is a string in Mastra's model router format: `provider/model`, for example `openai/gpt-5.5`. For OpenAI models, use `openai/<model>`, not `openai:<model>`, and don't pass a provider object. No provider import is needed for this format. Don't install any AI SDK package unless Mastra's documentation says otherwise.
 
 Add a tool an agent by importing the tool and passing it to the agent constructor as a tools object.
 
@@ -119,7 +119,7 @@ console.log(response.text)
 
 Use agents when the task is open-ended and the steps aren't known in advance. An agent decides which tools to call, how many times to loop, and when to stop. You provide the goal and constraints instead of defining each step. For predetermined, multi-step processes with explicit control flow, use [workflows](https://mastra.ai/docs/workflows/overview) instead.
 
-> **Tip:** Watch an introduction to agents, and how they compare to workflows on [YouTube (7 minutes)](https://youtu.be/0jg2g3sNvgw).
+> **📹 Watch:** Watch [Mastra agent quickstart](https://www.youtube.com/watch?v=G8tXjcseNjg) for a short walkthrough of creating and testing a Mastra agent.
 
 ## Quickstart
 
@@ -151,9 +151,9 @@ export const mastra = new Mastra({
 
 Once registered, it can be called from workflows, tools, or other agents, and has access to shared resources such as memory, logging, and observability features.
 
-> **Tip:** Use [Studio](https://mastra.ai/docs/studio/overview) to test your agent with different messages, inspect tool calls and responses, and debug agent behavior.
+Visit the [agent reference](https://mastra.ai/reference/agents/agent) for more information on available properties and configurations.
 
-> **Note:** Visit the [agent reference](https://mastra.ai/reference/agents/agent) for more information on available properties and configurations.
+> **Tip:** Use [Studio](https://mastra.ai/docs/studio/overview) to test your agent with different messages, inspect tool calls and responses, and debug agent behavior.
 
 ## Use your agent
 
@@ -205,7 +205,7 @@ Once your agent is running, use this table to find the right page for what you w
 | Build agents that correct their work                           | [Rubric scorer](https://mastra.ai/docs/agents/supervisor-agents)       |
 | Swap instructions or models based on request context           | [Dynamic configuration](https://mastra.ai/docs/server/request-context) |
 | Add speech-to-text or text-to-speech                           | [Voice](https://mastra.ai/docs/voice/overview)                         |
-| Connect to Slack, Discord, or Telegram                         | [Channels](https://mastra.ai/docs/agents/channels)                     |
+| Connect to Slack, Discord, or Telegram                         | [Channels](https://mastra.ai/docs/capabilities/channels/overview)      |
 
 ## Multi-agent systems
 

package/.docs/docs/agents/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 without setting up a workspace, filesystem, or sandbox. This is useful when you want portable, code-defined capabilities that travel with your agent definition.
+You can attach skills directly to an agent through its `skills` config, or configure them on a [workspace](https://mastra.ai/docs/workspace/overview). 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, loading them from files, and resolving them per request.
 
 ## When to use agent-level skills
 
@@ -69,9 +69,7 @@ export const releaseChecklist = createSkill({
 })
 ```
 
-The `references` field bundles supporting documents that the agent can read with the `skill_read` tool, just like `references/` files in a filesystem skill.
-
-> **Note:** Visit [`createSkill()` reference](https://mastra.ai/reference/agents/createSkill) for the full API.
+The `references` field bundles supporting documents that the agent can read with the `skill_read` tool, like `references/` files in a filesystem skill. Visit [`createSkill()` reference](https://mastra.ai/reference/agents/createSkill) for the full API.
 
 ## Filesystem path skills
 
@@ -179,7 +177,7 @@ for (const meta of allSkills) {
 }
 ```
 
-> **Note:** Visit [`.getSkill()` reference](https://mastra.ai/reference/agents/getSkill) and [`.listSkills()` reference](https://mastra.ai/reference/agents/listSkills) for the full API.
+Visit [`.getSkill()` reference](https://mastra.ai/reference/agents/getSkill) and [`.listSkills()` reference](https://mastra.ai/reference/agents/listSkills) for the full API.
 
 ## Related
 

package/.docs/docs/agents/structured-output.md

@@ -103,7 +103,7 @@ const response = await testAgent.generate('Help me plan my day.', {
 console.log(response.object)
 ```
 
-> **Note:** Visit [`.generate()`](https://mastra.ai/reference/agents/generate) for a full list of configuration options.
+Visit [`.generate()`](https://mastra.ai/reference/agents/generate) for a full list of configuration options.
 
 **Example output:** The `response.object` will contain the structured data as defined by the schema.
 

package/.docs/docs/agents/supervisor-agents.md

@@ -226,9 +226,7 @@ How it works:
 2. **Scoped memory saves**: Only the delegation prompt and the subagent's response are saved to the subagent's memory
 3. **Fresh thread per invocation**: Each delegation uses a unique thread ID, ensuring clean separation
 
-This ensures subagents have the context they need without cluttering their memory with the entire supervisor conversation.
-
-> **Note:** Visit [memory in multi-agent systems](https://mastra.ai/docs/memory/overview) for more details.
+This ensures subagents have the context they need without cluttering their memory with the entire supervisor conversation. Visit [memory in multi-agent systems](https://mastra.ai/docs/memory/overview) for more details.
 
 ## Tool approval propagation
 
@@ -428,4 +426,5 @@ Version overrides propagate automatically through delegation. See [Subagent vers
 - [Agent.generate() reference](https://mastra.ai/reference/agents/generate)
 - [Agent approval](https://mastra.ai/docs/agents/agent-approval)
 - [Memory in multi-agent systems](https://mastra.ai/docs/memory/overview)
-- [Concept: Multi-agent systems](https://mastra.ai/guides/concepts/multi-agent-systems)
+- [Concept: Multi-agent systems](https://mastra.ai/guides/concepts/multi-agent-systems)
+- 📹 [Mastra supervisor agents workshop](https://www.youtube.com/watch?v=FNb2fL9WhQg\&t=1872s)

package/.docs/docs/agents/using-tools.md

@@ -38,9 +38,7 @@ export const weatherTool = createTool({
 })
 ```
 
-When creating tools, keep descriptions concise and focused on what the tool does, emphasizing its primary use case. Descriptive schema names can also help guide the agent on how to use the tool.
-
-> **Note:** Visit the [`createTool`](https://mastra.ai/reference/tools/create-tool) reference for more information on available properties, configurations, and examples.
+When creating tools, keep descriptions concise and focused on what the tool does, emphasizing its primary use case. Descriptive schema names can also help guide the agent on how to use the tool. Visit the [`createTool`](https://mastra.ai/reference/tools/create-tool) reference for more information on available properties, configurations, and examples.
 
 To make a tool available to an agent, add it to the `tools` property on the `Agent` class. Mentioning available tools and their general purpose in the agent's system prompt helps the agent decide when to call a tool and when not to.
 
@@ -359,7 +357,7 @@ await agent.generate('Check the forecast', {
 })
 ```
 
-> **Note:** See the [`Agent.generate()` reference](https://mastra.ai/reference/agents/generate) for all runtime options including `toolsets`, `clientTools`, and `prepareStep`.
+See the [`Agent.generate()` reference](https://mastra.ai/reference/agents/generate) for all runtime options including `toolsets`, `clientTools`, and `prepareStep`.
 
 ## Control `toolName` in stream responses
 

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

@@ -99,9 +99,7 @@ const browser = new AgentBrowser({
 })
 ```
 
-This adds `browser_record` and `browser_record_caption` to the agent's toolset. See [Browser recording (alpha)](https://mastra.ai/docs/browser/recording) for details.
-
-> **Note:** 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 (alpha)](https://mastra.ai/docs/browser/recording) for details. See [AgentBrowser reference](https://mastra.ai/reference/browser/agent-browser) for all configuration options and tool details.
 
 ## Related
 

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

@@ -140,9 +140,7 @@ npm install -g browse
 browse skills install
 ```
 
-CDP flag: `--ws`
-
-> **Note:** See [BrowserViewer reference](https://mastra.ai/reference/browser/browser-viewer) for all configuration options, advanced connection modes, and method details.
+CDP flag: `--ws` See [BrowserViewer reference](https://mastra.ai/reference/browser/browser-viewer) for all configuration options, advanced connection modes, and method details.
 
 ## Related
 

package/.docs/docs/browser/overview.md

@@ -169,4 +169,5 @@ const browser = new AgentBrowser({
 - [Stagehand](https://mastra.ai/docs/browser/stagehand)
 - [Browser recording (alpha)](https://mastra.ai/docs/browser/recording)
 - [BrowserViewer](https://mastra.ai/docs/browser/browser-viewer)
-- [MastraBrowser reference](https://mastra.ai/reference/browser/mastra-browser)
+- [MastraBrowser reference](https://mastra.ai/reference/browser/mastra-browser)
+- 📹 [Mastra browser capabilities workshop](https://www.youtube.com/watch?v=E9KFsZEnQO8\&t=5s)

package/.docs/docs/browser/recording.md

@@ -101,7 +101,7 @@ When the user asks for a recording:
 
 ## Output format and limits
 
-Recordings are saved as Motion-JPEG AVI files. This format is encoded in JavaScript and does not require `ffmpeg` or native dependencies.
+Recordings are saved as Motion-JPEG AVI files. This format is encoded in JavaScript and doesn't require `ffmpeg` or native dependencies.
 
 Default limits:
 

package/.docs/docs/browser/stagehand.md

@@ -146,7 +146,7 @@ const browser = new StagehandBrowser({
 })
 ```
 
-> **Note:** See [StagehandBrowser reference](https://mastra.ai/reference/browser/stagehand-browser) for all configuration options.
+See [StagehandBrowser reference](https://mastra.ai/reference/browser/stagehand-browser) for all configuration options.
 
 ## Recording
 

package/.docs/docs/capabilities/channels/discord.md

@@ -0,0 +1,98 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
+# Discord
+
+Discord channels let a Mastra agent receive Discord interactions and bot messages. Mastra handles the agent wiring and webhook route; the Chat SDK Discord adapter docs cover Discord application setup, bot permissions, and Gateway behavior.
+
+## Install the adapter
+
+Install the Discord adapter from the Chat SDK:
+
+**npm**:
+
+```bash
+npm install @chat-adapter/discord
+```
+
+**pnpm**:
+
+```bash
+pnpm add @chat-adapter/discord
+```
+
+**Yarn**:
+
+```bash
+yarn add @chat-adapter/discord
+```
+
+**Bun**:
+
+```bash
+bun add @chat-adapter/discord
+```
+
+## Agent configuration
+
+Add `createDiscordAdapter()` to the agent's `channels.adapters` object:
+
+```typescript
+import { Agent } from '@mastra/core/agent'
+import { createDiscordAdapter } from '@chat-adapter/discord'
+
+export const discordAgent = new Agent({
+  id: 'discord-agent',
+  name: 'Discord Agent',
+  instructions: 'Answer questions and help with tasks in Discord.',
+  model: 'openai/gpt-5.5',
+  channels: {
+    adapters: {
+      discord: createDiscordAdapter(),
+    },
+  },
+})
+```
+
+Register the agent on the Mastra instance:
+
+```typescript
+import { Mastra } from '@mastra/core'
+import { discordAgent } from './agents/discord-agent'
+
+export const mastra = new Mastra({
+  agents: { discordAgent },
+})
+```
+
+## Adapter setup
+
+Follow the [Chat SDK Discord adapter docs](https://chat-sdk.dev/adapters/official/discord) for Discord-specific setup, including application creation, bot tokens, interaction endpoints, permissions, and Gateway behavior.
+
+The adapter reads Discord credentials from environment variables such as:
+
+```bash
+DISCORD_BOT_TOKEN=your-discord-bot-token
+DISCORD_PUBLIC_KEY=your-discord-application-public-key
+DISCORD_APPLICATION_ID=your-discord-application-id
+```
+
+## Webhook URL
+
+Mastra generates the Discord webhook route from the agent ID and adapter key:
+
+```text
+/api/agents/discord-agent/channels/discord/webhook
+```
+
+Use your public Mastra server URL as the base URL:
+
+```text
+https://your-app.example.com/api/agents/discord-agent/channels/discord/webhook
+```
+
+Use this URL anywhere the Discord adapter docs ask for the interactions endpoint or webhook URL. Discord regular message events may require Gateway setup outside the generated webhook route; follow the Chat SDK adapter docs for that path.
+
+## Related
+
+- [Channels overview](https://mastra.ai/docs/capabilities/channels/overview)
+- [More](https://mastra.ai/docs/capabilities/channels/other-adapters)

package/.docs/docs/capabilities/channels/other-adapters.md

@@ -0,0 +1,68 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
+# More
+
+Mastra channels use Chat SDK adapters, so the pages in this section are not the full list of supported platforms. Use any Chat SDK platform adapter that exports an adapter factory compatible with `channels.adapters`.
+
+## Adapter catalog
+
+The [Chat SDK adapter catalog](https://chat-sdk.dev/adapters) is the canonical source for available adapters. The list below is only a snapshot and may not always be up to date.
+
+At the time of writing, Chat SDK lists adapters for:
+
+- AgentPhone
+- Baileys WhatsApp
+- Discord
+- Google Chat
+- GitHub
+- iMessage
+- Kapso
+- Lark / Feishu
+- Linear
+- Liveblocks
+- Matrix
+- Messenger
+- Mattermost
+- Novu
+- Resend
+- Sendblue
+- Telegram
+- Twilio
+- Velt
+- Web
+- Webex
+- WeChat
+- WhatsApp Business Cloud
+- X
+- Zalo
+- Zernio
+
+Check the adapter's docs for its package name, credential variables, webhook requirements, and platform-specific behavior.
+
+## Use the same Mastra wiring
+
+The Mastra side of each Chat SDK adapter is similar: install the adapter package, add its adapter factory to `channels.adapters`, configure platform credentials, and point the platform webhook to the generated Mastra route.
+
+Use one of the platform pages in this section as a reference for the Mastra wiring:
+
+- [Slack](https://mastra.ai/docs/capabilities/channels/slack)
+- [Microsoft Teams](https://mastra.ai/docs/capabilities/channels/teams)
+- [Discord](https://mastra.ai/docs/capabilities/channels/discord)
+- [Telegram](https://mastra.ai/docs/capabilities/channels/telegram)
+- [WhatsApp](https://mastra.ai/docs/capabilities/channels/whatsapp)
+
+## What to check in adapter docs
+
+Before wiring a new adapter into Mastra, check the adapter docs for:
+
+- Credential environment variables.
+- Required platform permissions or scopes.
+- Webhook verification behavior.
+- Whether the platform needs separate routes for setup, events, or interactions.
+- Whether regular messages require long-running listeners or polling.
+- Attachment, card, and rich message support.
+
+## Related
+
+- [Channels overview](https://mastra.ai/docs/capabilities/channels/overview)
+- [Channels reference](https://mastra.ai/reference/agents/channels)