@mastra/mcp-docs-server 1.2.15-alpha.19 → 1.2.15-alpha.21

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

@@ -134,7 +134,7 @@ The generated code for `sales_code` can't call an inventory tool, and the revers
 
 ## Remote sandboxes
 
-By default, code mode uses a transport that writes the program to the host filesystem and runs `node` against it. That works for `LocalSandbox`, which shares the host, but not for remote sandboxes that run in their own micro-VM (such as [E2B](https://mastra.ai/reference/workspace/e2b-sandbox)), where the host paths don't exist.
+By default, code mode uses a transport that writes the program to the host filesystem and runs `node` against it. That works for `LocalSandbox`, which shares the host, but not for remote sandboxes that run in their own micro-VM (such as [E2B](https://mastra.ai/integrations/sandboxes/e2b)), where the host paths don't exist.
 
 Remote sandboxes need a transport that writes the program into the sandbox filesystem. For E2B, pass the included `E2BCodeModeTransport` as the second argument to `createCodeMode`:
 

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

@@ -4,7 +4,7 @@
 
 > **Deprecated:** Agent networks are deprecated and will be removed in a future major release. [Supervisor agents](https://mastra.ai/docs/capabilities/subagents) using `agent.stream()` or `agent.generate()` are now the recommended approach. It provides the same multi-agent coordination with better control, a simpler API, and easier debugging.
 >
-> See the [migration guide](https://mastra.ai/guides/migrations/network-to-supervisor) to upgrade.
+> See the [migration guide](https://mastra.ai/reference/migrations/network-to-supervisor) to upgrade.
 
 A **routing agent** uses an LLM to interpret a request and decide which primitives (subagents, workflows, or tools) to call, in what order, and with what data.
 
@@ -181,4 +181,4 @@ Requirements for automatic resumption:
 ## Related
 
 - [Supervisor agents](https://mastra.ai/docs/capabilities/subagents)
-- [Migration: `.network()` to supervisor agents](https://mastra.ai/guides/migrations/network-to-supervisor)
+- [Migration: `.network()` to supervisor agents](https://mastra.ai/reference/migrations/network-to-supervisor)

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

@@ -211,10 +211,10 @@ 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/capabilities/subagents)         |
 | 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/guides/voice/overview)                       |
-| Connect to Slack, Discord, or Telegram                         | [Channels](https://mastra.ai/docs/capabilities/channels/overview)      |
+| Connect to Slack, Discord, or Telegram                         | [Channels](https://mastra.ai/docs/capabilities/channels)               |
 
 ## Multi-agent systems
 
 A multi-agent system uses multiple agents to solve a task that's too broad or too specialized for a single agent. Instead of building one agent with dozens of tools and a long instruction set, you split responsibilities across focused agents and let a coordinator bring results together.
 
-Read the [conceptual overview of multi-agent systems](https://mastra.ai/guides/concepts/multi-agent-systems) to learn how you can apply different patterns with Mastra.
+Read the [conceptual overview of multi-agent systems](https://mastra.ai/docs/guides/multi-agent-systems) to learn how you can apply different patterns with Mastra.

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

@@ -353,7 +353,7 @@ Agent-level and per-execution hooks merge per key: passing only `beforeToolCall`
 
 Tools support lifecycle hooks that allow you to monitor different stages of tool execution during streaming. These hooks are particularly useful for logging or analytics.
 
-For generic `writer` API usage, see [Streaming](https://mastra.ai/guides/concepts/streaming).
+For generic `writer` API usage, see [Streaming](https://mastra.ai/docs/guides/streaming).
 
 ### Available Hooks
 

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

@@ -6,10 +6,10 @@ Browser support enables agents to move through websites, interact with page elem
 
 Mastra supports three SDK providers and one CLI provider:
 
-- [**AgentBrowser**](https://mastra.ai/docs/browser/agent-browser): A Playwright-based provider with accessibility-first element targeting. Best for general web automation and scraping.
-- [**Stagehand**](https://mastra.ai/docs/browser/stagehand): A Browserbase provider with AI-powered element detection. Best for complex interactions that benefit from natural language selectors.
-- [**FirecrawlBrowser**](https://mastra.ai/docs/browser/firecrawl): A Firecrawl Browser Sandbox provider that runs AgentBrowser tools against hosted browser sessions. Best for running automation on hosted browser sessions without managing local browser infrastructure.
-- [**BrowserViewer**](https://mastra.ai/docs/browser/browser-viewer): A CLI provider that launches Chrome and injects CDP URLs into CLI tools like agent-browser, browser-use, and browse. Best for workspace agents that drive browsers through shell commands.
+- [**AgentBrowser**](https://mastra.ai/integrations/browsers/agent-browser): A Playwright-based provider with accessibility-first element targeting. Best for general web automation and scraping.
+- [**Stagehand**](https://mastra.ai/integrations/browsers/stagehand): A Browserbase provider with AI-powered element detection. Best for complex interactions that benefit from natural language selectors.
+- [**FirecrawlBrowser**](https://mastra.ai/integrations/browsers/firecrawl): A Firecrawl Browser Sandbox provider that runs AgentBrowser tools against hosted browser sessions. Best for running automation on hosted browser sessions without managing local browser infrastructure.
+- [**BrowserViewer**](https://mastra.ai/integrations/browsers/browser-viewer): A CLI provider that launches Chrome and injects CDP URLs into CLI tools like agent-browser, browser-use, and browse. Best for workspace agents that drive browsers through shell commands.
 - [**Browser recording (alpha)**](https://mastra.ai/docs/browser/recording): An opt-in tool layer that saves browser sessions as Motion-JPEG AVI videos with optional captions.
 
 ## When to use browser
@@ -178,10 +178,10 @@ const browser = new AgentBrowser({
 
 ## Next steps
 
-- [AgentBrowser](https://mastra.ai/docs/browser/agent-browser)
-- [Stagehand](https://mastra.ai/docs/browser/stagehand)
-- [Firecrawl](https://mastra.ai/docs/browser/firecrawl)
+- [AgentBrowser](https://mastra.ai/integrations/browsers/agent-browser)
+- [Stagehand](https://mastra.ai/integrations/browsers/stagehand)
+- [Firecrawl](https://mastra.ai/integrations/browsers/firecrawl)
 - [Browser recording (alpha)](https://mastra.ai/docs/browser/recording)
-- [BrowserViewer](https://mastra.ai/docs/browser/browser-viewer)
+- [BrowserViewer](https://mastra.ai/integrations/browsers/browser-viewer)
 - [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

@@ -115,6 +115,6 @@ Use shorter recordings when possible. Long browser sessions produce larger files
 
 ## Next steps
 
-- [AgentBrowser](https://mastra.ai/docs/browser/agent-browser)
-- [Stagehand](https://mastra.ai/docs/browser/stagehand)
+- [AgentBrowser](https://mastra.ai/integrations/browsers/agent-browser)
+- [Stagehand](https://mastra.ai/integrations/browsers/stagehand)
 - [Browser overview](https://mastra.ai/docs/browser/overview)

package/.docs/docs/capabilities/{channels/overview.md → channels.md}

@@ -8,14 +8,15 @@ Channels connect agents to messaging and collaboration platforms like Slack, Mic
 
 Start with the page for your platform:
 
-- [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)
-- [iMessage](https://mastra.ai/docs/capabilities/channels/imessage)
+- [Slack](https://mastra.ai/integrations/channels/slack)
+- [Microsoft Teams](https://mastra.ai/integrations/channels/teams)
+- [Discord](https://mastra.ai/integrations/channels/discord)
+- [Telegram](https://mastra.ai/integrations/channels/telegram)
+- [WhatsApp](https://mastra.ai/integrations/channels/whatsapp)
+- [iMessage](https://mastra.ai/integrations/channels/imessage)
+- [GitHub](https://mastra.ai/integrations/channels/github)
 
-[More](https://mastra.ai/docs/capabilities/channels/other-adapters) lists additional platforms. Mastra channels work with compatible [Chat SDK adapters](https://chat-sdk.dev/adapters) beyond the platforms listed here, and the same Mastra configuration pattern applies across adapters.
+[Other adapters](#other-adapters) lists additional platforms. Mastra channels work with compatible [Chat SDK adapters](https://chat-sdk.dev/adapters) beyond the platforms listed here, and the same Mastra configuration pattern applies across adapters.
 
 ## When to use channels
 
@@ -274,6 +275,68 @@ export const mastra = new Mastra({
 
 Vercel's managed Redis integration and Upstash Redis both work well. For more on when a distributed pub/sub is needed, see the [PubSub guide](https://mastra.ai/docs/server/pubsub) and the [`RedisStreamsPubSub` reference](https://mastra.ai/reference/pubsub/redis-streams).
 
+## Other adapters
+
+Mastra channels use Chat SDK adapters, so the platform guides aren't 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 a snapshot and may not always be up to date.
+
+At the time of writing, Chat SDK lists adapters for:
+
+- AgentPhone
+- Baileys WhatsApp
+- Discord
+- GitHub
+- Google Chat
+- iMessage
+- Kapso
+- Lark / Feishu
+- Linear
+- Liveblocks
+- Matrix
+- Mattermost
+- Messenger
+- 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 follows the same setup. Install the adapter package and add its factory to `channels.adapters`. Then configure the platform credentials and point its webhook to the generated Mastra route.
+
+Use one of the platform guides as a reference for the Mastra wiring:
+
+- [Discord](https://mastra.ai/integrations/channels/discord)
+- [Microsoft Teams](https://mastra.ai/integrations/channels/teams)
+- [Slack](https://mastra.ai/integrations/channels/slack)
+- [Telegram](https://mastra.ai/integrations/channels/telegram)
+- [WhatsApp](https://mastra.ai/integrations/channels/whatsapp)
+
+### Check the adapter docs
+
+Before wiring a new adapter into Mastra, check the adapter docs for:
+
+- Attachment, card, and rich message support.
+- Credential environment variables.
+- Required platform permissions or scopes.
+- Whether regular messages require long-running listeners or polling.
+- Whether the platform needs separate routes for setup, events, or interactions.
+- Webhook verification behavior.
+
 ## Related
 
 - [Channels reference](https://mastra.ai/reference/agents/channels)

package/.docs/docs/capabilities/subagents.md

@@ -16,7 +16,7 @@ Common use cases:
 - Multi-step tasks that need different expertise at each stage
 - Tasks where you need fine-grained control over delegation behavior
 
-> **Note:** A parent agent that coordinates subagents is often called a supervisor. The supervisor pattern is one approach to building multi-agent systems in Mastra. For other patterns, read the [conceptual overview](https://mastra.ai/guides/concepts/multi-agent-systems).
+> **Note:** A parent agent that coordinates subagents is often called a supervisor. The supervisor pattern is one approach to building multi-agent systems in Mastra. For other patterns, read the [conceptual overview](https://mastra.ai/docs/guides/multi-agent-systems).
 
 ## Quickstart
 
@@ -453,5 +453,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/docs/guides/multi-agent-systems)
 - 📹 [Mastra supervisor agents workshop](https://www.youtube.com/watch?v=FNb2fL9WhQg\&t=1872s)

package/.docs/docs/deployment/cloud-providers.md

@@ -12,12 +12,12 @@ Mastra provides a platform to deploy your server to the cloud. Read the [Mastra
 
 The following guides show how to deploy Mastra to specific cloud providers:
 
-- [Amazon Bedrock AgentCore](https://mastra.ai/guides/deployment/aws-bedrock-agentcore)
-- [Amazon EC2](https://mastra.ai/guides/deployment/amazon-ec2)
-- [AWS Lambda](https://mastra.ai/guides/deployment/aws-lambda)
-- [Azure App Services](https://mastra.ai/guides/deployment/azure-app-services)
-- [Cloudflare](https://mastra.ai/guides/deployment/cloudflare)
-- [Digital Ocean](https://mastra.ai/guides/deployment/digital-ocean)
-- [Kubernetes](https://mastra.ai/guides/deployment/kubernetes)
-- [Netlify](https://mastra.ai/guides/deployment/netlify)
-- [Vercel](https://mastra.ai/guides/deployment/vercel)
+- [Amazon Bedrock AgentCore](https://mastra.ai/integrations/deploy/aws-bedrock-agentcore)
+- [Amazon EC2](https://mastra.ai/integrations/deploy/amazon-ec2)
+- [AWS Lambda](https://mastra.ai/integrations/deploy/aws-lambda)
+- [Azure App Services](https://mastra.ai/integrations/deploy/azure-app-services)
+- [Cloudflare](https://mastra.ai/integrations/deploy/cloudflare)
+- [Digital Ocean](https://mastra.ai/integrations/deploy/digital-ocean)
+- [Kubernetes](https://mastra.ai/integrations/deploy/kubernetes)
+- [Netlify](https://mastra.ai/integrations/deploy/netlify)
+- [Vercel](https://mastra.ai/integrations/deploy/vercel)

package/.docs/docs/deployment/overview.md

@@ -43,14 +43,14 @@ Mastra applications can be deployed to cloud providers and serverless platforms.
 
 Use this option for auto-scaling, minimal infrastructure management, or when you're already using one of these platforms.
 
-- [Amazon EC2](https://mastra.ai/guides/deployment/amazon-ec2)
-- [AWS Lambda](https://mastra.ai/guides/deployment/aws-lambda)
-- [Azure App Services](https://mastra.ai/guides/deployment/azure-app-services)
-- [Cloudflare](https://mastra.ai/guides/deployment/cloudflare)
-- [Digital Ocean](https://mastra.ai/guides/deployment/digital-ocean)
-- [Kubernetes](https://mastra.ai/guides/deployment/kubernetes)
-- [Netlify](https://mastra.ai/guides/deployment/netlify)
-- [Vercel](https://mastra.ai/guides/deployment/vercel)
+- [Amazon EC2](https://mastra.ai/integrations/deploy/amazon-ec2)
+- [AWS Lambda](https://mastra.ai/integrations/deploy/aws-lambda)
+- [Azure App Services](https://mastra.ai/integrations/deploy/azure-app-services)
+- [Cloudflare](https://mastra.ai/integrations/deploy/cloudflare)
+- [Digital Ocean](https://mastra.ai/integrations/deploy/digital-ocean)
+- [Kubernetes](https://mastra.ai/integrations/deploy/kubernetes)
+- [Netlify](https://mastra.ai/integrations/deploy/netlify)
+- [Vercel](https://mastra.ai/integrations/deploy/vercel)
 
 ### Sandbox
 
@@ -72,7 +72,7 @@ Use these guides when adding Mastra to an existing Next.js or Astro application.
 
 Mastra workflows run using the built-in execution engine by default. For production workloads requiring managed infrastructure, workflows can also be deployed to specialized platforms like [Inngest](https://www.inngest.com) that provide step memoization, automatic retries, and real-time monitoring.
 
-Visit the [Workflow Runners guide](https://mastra.ai/docs/deployment/workflow-runners) for execution options and the [Inngest deployment guide](https://mastra.ai/guides/deployment/inngest) for setup instructions.
+Visit the [Workflow Runners guide](https://mastra.ai/docs/deployment/workflow-runners) for execution options and the [Inngest deployment guide](https://mastra.ai/integrations/deploy/inngest) for setup instructions.
 
 ## Workers
 

package/.docs/docs/deployment/sandbox.md

@@ -17,9 +17,9 @@ Sandboxes have provider-enforced runtime caps and expire. For production hosting
 
 The deployer works with any workspace sandbox that supports networking (public port URLs):
 
-- [Vercel Sandbox](https://mastra.ai/reference/workspace/vercel-sandbox) (`@mastra/vercel`)
-- [E2B](https://mastra.ai/reference/workspace/e2b-sandbox) (`@mastra/e2b`)
-- [Daytona](https://mastra.ai/reference/workspace/daytona-sandbox) (`@mastra/daytona`)
+- [Vercel Sandbox](https://mastra.ai/integrations/sandboxes/vercel) (`@mastra/vercel`)
+- [E2B](https://mastra.ai/integrations/sandboxes/e2b) (`@mastra/e2b`)
+- [Daytona](https://mastra.ai/integrations/sandboxes/daytona) (`@mastra/daytona`)
 
 Provider authors can add support by implementing the optional `networking` capability on [`WorkspaceSandbox`](https://mastra.ai/reference/workspace/sandbox).
 

package/.docs/docs/deployment/web-framework.md

@@ -4,16 +4,16 @@
 
 When Mastra is integrated with a web framework, it deploys alongside your application using the framework's standard deployment process. Follow the instructions below to ensure your Mastra integration deploys correctly.
 
-> **Warning:** If you're deploying to a cloud provider, remove any usage of [LibSQLStore](https://mastra.ai/reference/storage/libsql) from your Mastra configuration. LibSQLStore requires filesystem access and isn't compatible with serverless platforms.
+> **Warning:** If you're deploying to a cloud provider, remove any usage of [LibSQLStore](https://mastra.ai/integrations/databases/libsql) from your Mastra configuration. LibSQLStore requires filesystem access and isn't compatible with serverless platforms.
 
 Integration guides:
 
-- [With Next.js](https://mastra.ai/guides/getting-started/next-js)
-- [With Astro](https://mastra.ai/guides/getting-started/astro)
+- [With Next.js](https://mastra.ai/integrations/frameworks/next-js)
+- [With Astro](https://mastra.ai/integrations/frameworks/astro)
 
 ## With Next.js on Vercel
 
-If you've integrated Mastra with Next.js [by following our guide](https://mastra.ai/guides/getting-started/next-js) and plan to deploy to Vercel, add `serverExternalPackages: ["@mastra/*"]` to your `next.config.ts`:
+If you've integrated Mastra with Next.js [by following our guide](https://mastra.ai/integrations/frameworks/next-js) and plan to deploy to Vercel, add `serverExternalPackages: ["@mastra/*"]` to your `next.config.ts`:
 
 ```typescript
 import type { NextConfig } from 'next'
@@ -27,7 +27,7 @@ export default nextConfig
 
 ## With Astro on Vercel
 
-If you've integrated Mastra with Astro [by following our guide](https://mastra.ai/guides/getting-started/astro) and plan to deploy to Vercel, add the Vercel adapter and server output to your `astro.config.mjs`:
+If you've integrated Mastra with Astro [by following our guide](https://mastra.ai/integrations/frameworks/astro) and plan to deploy to Vercel, add the Vercel adapter and server output to your `astro.config.mjs`:
 
 ```javascript
 import { defineConfig } from 'astro/config'
@@ -41,7 +41,7 @@ export default defineConfig({
 
 ## With Astro on Netlify
 
-If you've integrated Mastra with Astro [by following our guide](https://mastra.ai/guides/getting-started/astro) and plan to deploy to Netlify, add the Netlify adapter and server output to your `astro.config.mjs`:
+If you've integrated Mastra with Astro [by following our guide](https://mastra.ai/integrations/frameworks/astro) and plan to deploy to Netlify, add the Netlify adapter and server output to your `astro.config.mjs`:
 
 ```javascript
 import { defineConfig } from 'astro/config'

package/.docs/docs/deployment/workflow-runners.md

@@ -8,10 +8,10 @@ Mastra [workflows](https://mastra.ai/docs/workflows/overview) can be executed us
 
 Inngest is a developer platform for running background workflows without managing infrastructure. Mastra workflows can be deployed to Inngest, which provides step memoization, automatic retries, real-time monitoring, and suspend/resume capabilities.
 
-Visit the [Inngest deployment guide](https://mastra.ai/guides/deployment/inngest) for setup instructions and the [Inngest workflow example](https://github.com/mastra-ai/mastra/tree/main/examples/inngest) for a complete implementation.
+Visit the [Inngest deployment guide](https://mastra.ai/integrations/deploy/inngest) for setup instructions and the [Inngest workflow example](https://github.com/mastra-ai/mastra/tree/main/examples/inngest) for a complete implementation.
 
 ## Temporal
 
 Temporal is a durable execution platform for orchestrating long-running workflows. Mastra workflows can run on Temporal workers, with each `createStep` mapped to a Temporal activity for automatic retries and durable state.
 
-The `@mastra/temporal` package is experimental and not ready for production use. Visit the [Temporal deployment guide](https://mastra.ai/guides/deployment/temporal) for setup instructions.
+The `@mastra/temporal` package is experimental and not ready for production use. Visit the [Temporal deployment guide](https://mastra.ai/integrations/deploy/temporal) for setup instructions.

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

@@ -388,7 +388,7 @@ channels: {
 
 Controller channel sessions and auto-approval state are held in memory, so use a long-lived server. Pending approvals and live Session state don't survive process restarts. Adapters that can't render approval controls automatically run tools without an approval prompt so the run doesn't remain suspended.
 
-See [Channels](https://mastra.ai/docs/capabilities/channels/overview) for adapter setup and platform-specific webhook configuration.
+See [Channels](https://mastra.ai/docs/capabilities/channels) for adapter setup and platform-specific webhook configuration.
 
 ## Connect a UI
 
@@ -414,4 +414,4 @@ Subscriptions are isolated by Session. Events from another Session on the same c
 - [Agents](https://mastra.ai/docs/agents/overview)
 - [Workspace](https://mastra.ai/docs/workspace/overview)
 - [Observational memory](https://mastra.ai/docs/memory/observational-memory)
-- [Channels](https://mastra.ai/docs/capabilities/channels/overview)
+- [Channels](https://mastra.ai/docs/capabilities/channels)

package/.docs/docs/index.md

@@ -153,14 +153,14 @@ You can open [Studio](https://mastra.ai/docs/studio/overview) immediately, which
 
 Add Mastra to an existing project, or create a new app with your preferred framework:
 
-- [Next.js](https://mastra.ai/guides/getting-started/next-js)
-- [React](https://mastra.ai/guides/getting-started/vite-react)
-- [Astro](https://mastra.ai/guides/getting-started/astro)
-- [Express](https://mastra.ai/guides/getting-started/express)
-- [SvelteKit](https://mastra.ai/guides/getting-started/sveltekit)
-- [Hono](https://mastra.ai/guides/getting-started/hono)
-
-For other frameworks, see the [framework integration guides](https://mastra.ai/guides/getting-started/next-js).
+- [Next.js](https://mastra.ai/integrations/frameworks/next-js)
+- [React](https://mastra.ai/integrations/frameworks/vite-react)
+- [Astro](https://mastra.ai/integrations/frameworks/astro)
+- [Express](https://mastra.ai/integrations/frameworks/express)
+- [SvelteKit](https://mastra.ai/integrations/frameworks/sveltekit)
+- [Hono](https://mastra.ai/integrations/frameworks/hono)
+
+For other frameworks, see the [framework integration guides](https://mastra.ai/integrations/frameworks/next-js).
 
 ## Templates
 

package/.docs/docs/long-running-agents/durable-agents.md

@@ -15,7 +15,7 @@ Use a durable agent when any of the following apply:
 - The client may drop and reconnect mid-stream (mobile, spotty networks, long-running calls).
 - The agentic loop may outlive a single HTTP request (background research, multi-step tool use).
 - You need an observe/reconnect API where a second client picks up a stream that a first client started.
-- You want [Inngest-powered execution](https://mastra.ai/guides/deployment/inngest) with step memoization, retries, and monitoring.
+- You want [Inngest-powered execution](https://mastra.ai/integrations/deploy/inngest) with step memoization, retries, and monitoring.
 
 For short-lived, request-scoped calls where the client stays connected, a regular `Agent` with `stream()` or `generate()` is simpler.
 
@@ -268,6 +268,6 @@ 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)
-- [Inngest deployment guide](https://mastra.ai/guides/deployment/inngest)
+- [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/signal-providers.md

@@ -45,7 +45,7 @@ export const supportAgent = new Agent({
 })
 ```
 
-> **Note:** Notification delivery requires a storage adapter with notification support, such as [libSQL](https://mastra.ai/reference/storage/libsql), [PostgreSQL](https://mastra.ai/reference/storage/postgresql), or [MongoDB](https://mastra.ai/reference/storage/mongodb). Configure storage on the Mastra instance so `notify()` can store notification records.
+> **Note:** Notification delivery requires a storage adapter with notification support, such as [libSQL](https://mastra.ai/integrations/databases/libsql), [PostgreSQL](https://mastra.ai/integrations/databases/postgresql), or [MongoDB](https://mastra.ai/integrations/databases/mongodb). Configure storage on the Mastra instance so `notify()` can store notification records.
 
 ## Quickstart
 
@@ -200,20 +200,7 @@ A provider can support more than event ingestion. Add only the capabilities your
 - **Lifecycle hooks:** Override [`start()`](https://mastra.ai/reference/signals/signal-provider) for async setup and [`stop()`](https://mastra.ai/reference/signals/signal-provider) for cleanup. Call `super.stop()` when overriding `stop()` so the base provider can stop polling and clear its registry.
 - **Processors and tools:** Return processors from [`getInputProcessors()`](https://mastra.ai/reference/signals/signal-provider) or [`getOutputProcessors()`](https://mastra.ai/reference/signals/signal-provider), and return agent-callable tools from [`getTools()`](https://mastra.ai/reference/signals/signal-provider).
 
-The `@mastra/github-signals` package is a production signal provider that watches GitHub pull requests and notifies threads about comments, review state, continuous integration status, and merges. Use it as a reference for polling, durable subscriptions, tools, processors, and lifecycle hooks.
-
-```typescript
-import { Agent } from '@mastra/core/agent'
-import { GithubSignals } from '@mastra/github-signals'
-
-export const devAgent = new Agent({
-  id: 'dev-agent',
-  name: 'Dev Agent',
-  instructions: 'Help triage pull request activity.',
-  model: 'openai/gpt-5.6-sol',
-  signals: [new GithubSignals()],
-})
-```
+For a production provider that watches GitHub pull requests, see the [GitHub Channels integration](https://mastra.ai/integrations/channels/github).
 
 ## Related
 

package/.docs/docs/long-running-agents/signals.md

@@ -147,7 +147,7 @@ Use XML-safe `tagName` and attribute names. They can contain letters, numbers, s
 
 #### Storage support
 
-Notification inbox storage is available in the storage adapters that support richer memory and signal workflows: [libSQL](https://mastra.ai/reference/storage/libsql), [PostgreSQL](https://mastra.ai/reference/storage/postgresql), and [MongoDB](https://mastra.ai/reference/storage/mongodb). These adapters expose notification records through `getStore('notifications')`.
+Notification inbox storage is available in the storage adapters that support richer memory and signal workflows: [libSQL](https://mastra.ai/integrations/databases/libsql), [PostgreSQL](https://mastra.ai/integrations/databases/postgresql), and [MongoDB](https://mastra.ai/integrations/databases/mongodb). These adapters expose notification records through `getStore('notifications')`.
 
 ### Send processor context
 

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

@@ -99,7 +99,7 @@ When a database is `ready`, the provider has finished provisioning and the platf
 
 ### Turso (LibSQL)
 
-Turso exposes two environment variables: `TURSO_DATABASE_URL` and `TURSO_AUTH_TOKEN`. The following example connects a [LibSQLStore](https://mastra.ai/reference/storage/libsql) using those variables.
+Turso exposes two environment variables: `TURSO_DATABASE_URL` and `TURSO_AUTH_TOKEN`. The following example connects a [LibSQLStore](https://mastra.ai/integrations/databases/libsql) using those variables.
 
 ```ts
 import { LibSQLStore } from '@mastra/libsql'
@@ -139,7 +139,7 @@ bun add @mastra/libsql@latest
 
 ### PostgreSQL
 
-PostgreSQL exposes a single `DATABASE_URL` connection string. The following example connects a [PostgresStore](https://mastra.ai/reference/storage/postgresql) using that variable.
+PostgreSQL exposes a single `DATABASE_URL` connection string. The following example connects a [PostgresStore](https://mastra.ai/integrations/databases/postgresql) using that variable.
 
 ```ts
 import { PostgresStore } from '@mastra/pg'

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

@@ -132,6 +132,33 @@ mastra deploy --env staging --env-file .env.staging
 
 To change variables on a running service without a redeploy, update them in the dashboard and run [`mastra env restart`](https://mastra.ai/reference/cli/mastra).
 
+## Private npm packages
+
+Projects that depend on packages from a private registry install them during the deploy using the standard `NPM_TOKEN` contract.
+
+1. Store a read-only registry token as `NPM_TOKEN` on the project or environment through the dashboard.
+
+2. Commit a token-free `.npmrc` that points your scope at the registry and reads the token from the environment:
+
+   ```ini
+   @your-org:registry=https://npm.pkg.github.com
+   //npm.pkg.github.com/:_authToken=${NPM_TOKEN}
+   ```
+
+   Keep the `${NPM_TOKEN}` reference literal. The package manager resolves it at install time, so the token itself never lands in your repository.
+
+3. Deploy as usual:
+
+   ```bash
+   mastra deploy
+   ```
+
+In a monorepo, a `.npmrc` in your project directory takes precedence over one at the repository root.
+
+`NPM_TOKEN` is available during dependency installation. Mastra redacts its value from the Mastra source-build logs that it streams. The generated Dockerfile receives it as a build argument, so the runtime image stays free of the token. `NPM_TOKEN` is also injected into the running service as a regular environment variable, so treat it as a secret your application can read.
+
+Projects without a private-registry `.npmrc` need no changes. When your `.npmrc` references `${NPM_TOKEN}`, set the variable or the dependency install fails.
+
 ## Project resolution
 
 Every deploy resolves its target project in this order:

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

@@ -8,7 +8,7 @@ You get a stable API endpoint, environment variable management, custom domain su
 
 > **Note:** `mastra server deploy` is the earlier split deploy path. New projects should use the unified [`mastra deploy`](https://mastra.ai/docs/mastra-platform/deploy) command, which adds preflight validation, environments, and CLI-managed databases.
 
-> **Note:** Server deploy provisions hosted storage automatically. If you override storage with [LibSQLStore](https://mastra.ai/reference/storage/libsql) and a file URL, switch to a remotely hosted database because Mastra platform uses an ephemeral filesystem.
+> **Note:** Server deploy provisions hosted storage automatically. If you override storage with [LibSQLStore](https://mastra.ai/integrations/databases/libsql) and a file URL, switch to a remotely hosted database because Mastra platform uses an ephemeral filesystem.
 
 ## Quickstart
 

package/.docs/docs/mastra-platform/trace-intelligence.md

@@ -56,12 +56,9 @@ The flow chart connects themes in adjacent trace signal columns:
 
 The flow shows association, not causation or execution order. For example, a ribbon between a Goal and an Outcome means that both themes occurred in the same traces. It doesn't show that the goal caused the outcome.
 
-### Distributions, Other, and Noise
+### Other and Noise
 
-The cards below the flow show each trace signal's theme distribution:
-
-- **Trace count**: The number of distinct traces assigned to a theme in the selected snapshot.
-- **Stage share**: The percentage of analyzed traces for that trace signal assigned to the theme.
+Each node shows its trace count: the number of distinct traces assigned to that theme in the selected snapshot. A theme's details also state its share, for example "28 of 70 traces in this snapshot (40%)".
 
 Studio shows the most common themes for each trace signal type. It may combine smaller themes into **Other** to preserve totals without overcrowding the chart.
 
@@ -69,26 +66,25 @@ Studio shows the most common themes for each trace signal type. It may combine s
 
 ### Snapshots
 
-A snapshot is a moving analysis window over a set of traces. Snapshots can overlap, so don't add their trace counts together. Compare trace count and stage share together because traffic volume can change between windows.
+A snapshot is a moving analysis window over a set of traces. Snapshots can overlap, so don't add their trace counts together. Compare a theme's trace count and its share of the snapshot together because traffic volume can change between windows.
 
 A theme can persist, disappear, split, merge, or return across snapshots. Treat theme names and descriptions as generated summaries, not fixed taxonomies.
 
 ## Use the Trace Intelligence page
 
 1. Use the **Agent** selector to switch between agents with available analysis. An agent doesn't appear until its first themes are ready.
-2. Select a theme in the flow to filter every column to traces containing that theme.
-3. Select **View theme details** to inspect its description, trace count, stage share, generated examples, and history.
+2. Select a theme in the flow to open its details and filter every column to traces containing that theme.
+3. The details panel shows the theme's description, its share of the snapshot, paged example summaries, and a trend of its trace count over time.
 4. Select **Clear filter** to restore the complete flow.
 
 You can also:
 
-- Select a theme in a distribution card to open its details and generated example summaries.
-- Select **Noise** in a distribution card to inspect its distribution and generated example summaries.
-- Drag the distribution cards to reorder the trace signal columns and see a different relationship perspective.
+- Select **Noise** in the flow to inspect its share and generated example summaries.
+- Drag the column headers above the chart to reorder the trace signal columns and see a different relationship perspective.
 - Use the timeline to select a snapshot, or select **Play** to watch themes change over time.
-- Open a theme's history to see whether it persisted and how its coverage changed.
+- Switch to **Compare** to see which themes grew, shrank, entered the range, or left the range between two points in time, or **Lifelines** to follow each theme's share across the whole selected range.
 
-Filtering the flow by a theme is unavailable for snapshots with more than 2,000 traces. Choose another snapshot or clear the active filter to return to the full flow. Theme and Noise details remain available from the distribution cards.
+Filtering the flow by a theme is unavailable for snapshots with more than 2,000 traces. Selecting a theme still opens its details there without filtering the flow.
 
 ## Troubleshooting
 

package/.docs/docs/mcp/overview.md

@@ -202,6 +202,48 @@ export const mastra = new Mastra({
 
 Visit the [`MCPServer` reference](https://mastra.ai/reference/tools/mcp-server) for prompts, resources, transports, and other server options.
 
+### Publish a stdio server package
+
+Package a server that uses the standard input/output (stdio) transport when you want clients to run it locally through a command such as `npx`. Create a separate executable entry point that starts the server:
+
+```typescript
+#!/usr/bin/env node
+import { mcpServer } from './server'
+
+mcpServer.startStdio().catch(error => {
+  console.error('Failed to start MCP server:', error)
+  process.exit(1)
+})
+```
+
+Build the entry point as an executable Node.js file, then point the package's `bin` field to that output. Include the built file in the published package and keep the shebang as its first line:
+
+```json
+{
+  "bin": {
+    "my-mcp-server": "dist/stdio.js"
+  },
+  "files": ["dist"]
+}
+```
+
+After publishing the package, configure clients to run it by package name:
+
+```typescript
+import { MCPClient } from '@mastra/mcp'
+
+const mcpClient = new MCPClient({
+  servers: {
+    myServer: {
+      command: 'npx',
+      args: ['-y', '@your-org/my-mcp-server@1.0.0'],
+    },
+  },
+})
+```
+
+Visit the [npm package publishing documentation](https://docs.npmjs.com/creating-and-publishing-scoped-public-packages) for package naming, authentication, and publication commands.
+
 ## Build MCP Apps
 
 The [MCP Apps extension](https://github.com/modelcontextprotocol/ext-apps) lets MCP tools serve interactive HTML interfaces through `ui://` resources. Mastra Studio renders these apps in sandboxed iframes on tool pages and in agent chat.