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

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

@@ -62,7 +62,7 @@ export const testMcpClient = new MCPClient({
 })
 ```
 
-Visit [MCPClient](https://mastra.ai/reference/tools/mcp-client) for a full list of configuration options.
+> **Info:** Visit [MCPClient](https://mastra.ai/reference/tools/mcp-client) for a full list of configuration options.
 
 > **Authentication:** For connecting to OAuth-protected MCP servers, see the [OAuth Authentication](https://mastra.ai/reference/tools/mcp-client) section.
 
@@ -89,7 +89,7 @@ export const testAgent = new Agent({
 })
 ```
 
-Visit [Agent Class](https://mastra.ai/reference/agents/agent) for a full list of configuration options.
+> **Info:** Visit [Agent Class](https://mastra.ai/reference/agents/agent) for a full list of configuration options.
 
 ## Tool approval
 
@@ -129,7 +129,7 @@ export const testMcpServer = new MCPServer({
 })
 ```
 
-Visit [MCPServer](https://mastra.ai/reference/tools/mcp-server) for a full list of configuration options.
+> **Info:** Visit [MCPServer](https://mastra.ai/reference/tools/mcp-server) for a full list of configuration options.
 
 > **Authentication:** To protect your MCP server with OAuth, see the [OAuth Protection](https://mastra.ai/reference/tools/mcp-server) section.
 
@@ -160,7 +160,9 @@ export const mastra = new Mastra({
 
 ### Static tools
 
-Use the `.listTools()` method to fetch tools from all configured MCP servers. This is suitable when configuration (such as API keys) is static and consistent across users or requests. Call it once and pass the result to the `tools` property when defining your agent. Visit [listTools()](https://mastra.ai/reference/tools/mcp-client) for more information.
+Use the `.listTools()` method to fetch tools from all configured MCP servers. This is suitable when configuration (such as API keys) is static and consistent across users or requests. Call it once and pass the result to the `tools` property when defining your agent.
+
+> **Info:** Visit [listTools()](https://mastra.ai/reference/tools/mcp-client) for more information.
 
 ```typescript
 import { Agent } from '@mastra/core/agent'
@@ -209,7 +211,7 @@ async function handleRequest(userPrompt: string, userApiKey: string) {
 }
 ```
 
-Visit [listToolsets()](https://mastra.ai/reference/tools/mcp-client) for more information.
+> **Info:** Visit [listToolsets()](https://mastra.ai/reference/tools/mcp-client) for more information.
 
 ## Connecting to an MCP registry
 
@@ -410,7 +412,9 @@ As an alternative to MCP, Ampersand's AI SDK also has an adapter for Mastra, so
 
 ## MCP Apps
 
-MCP servers can serve interactive HTML UIs via the MCP Apps extension. Tools with associated `ui://` resources render sandboxed iframes in Studio — both on tool detail pages and inline in agent chat. The app iframe can call server tools and inject messages into the conversation. Visit [MCP Apps](https://mastra.ai/docs/mcp/mcp-apps) for setup instructions and the app bridge API.
+MCP servers can serve interactive HTML UIs via the MCP Apps extension. Tools with associated `ui://` resources render sandboxed iframes in Studio — both on tool detail pages and inline in agent chat. The app iframe can call server tools and inject messages into the conversation.
+
+> **Note:** Visit [MCP Apps](https://mastra.ai/docs/mcp/mcp-apps) for setup instructions and the app bridge API.
 
 ## Related
 

package/.docs/docs/memory/observational-memory.md

@@ -714,5 +714,4 @@ In practical terms, OM replaces both working memory and message history, and has
 - [Memory Overview](https://mastra.ai/docs/memory/overview)
 - [Message History](https://mastra.ai/docs/memory/message-history)
 - [Memory Processors](https://mastra.ai/docs/memory/memory-processors)
-- [Mastra Code](https://code.mastra.ai/): A coding agent using Observational Memory
-- 📹 [Mastra processors and Observational Memory workshop](https://www.youtube.com/watch?v=4Vpp7xQYvl0)
+- [Mastra Code](https://code.mastra.ai/): A coding agent using Observational Memory

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

@@ -15,8 +15,6 @@ If the combined memory exceeds the model's context limit, [memory processors](ht
 
 Memory results will be stored in one or more of your configured [storage providers](https://mastra.ai/docs/storage/overview).
 
-> **📹 Watch:** Watch [Mastra memory concepts](https://www.youtube.com/watch?v=18iIHQtIPmc) for a conceptual overview of the memory layers agents can use.
-
 ## When to use memory
 
 Use memory when your agent needs to maintain multi-turn conversations that reference prior exchanges, recall user preferences or facts from earlier in a session, or build context over time within a conversation thread. Skip memory for single-turn requests where each interaction is independent.
@@ -77,7 +75,7 @@ Use memory when your agent needs to maintain multi-turn conversations that refer
    bun add @mastra/libsql@latest
    ```
 
-   For more details on available providers and how storage works in Mastra, visit the [storage](https://mastra.ai/docs/storage/overview) documentation.
+   > **Note:** For more details on available providers and how storage works in Mastra, visit the [storage](https://mastra.ai/docs/storage/overview) documentation.
 
 3. Add the storage provider to your main Mastra instance to enable memory across all configured agents.
 
@@ -110,7 +108,7 @@ Use memory when your agent needs to maintain multi-turn conversations that refer
    })
    ```
 
-   Visit [Memory Class](https://mastra.ai/reference/memory/memory-class) for a full list of configuration options.
+   > **Note:** Visit [Memory Class](https://mastra.ai/reference/memory/memory-class) for a full list of configuration options.
 
 5. Call your agent, for example in [Studio](https://mastra.ai/docs/studio/overview). Inside Studio, start a new chat with your agent and take a look at the right sidebar. It'll now display various memory-related information.
 
@@ -166,7 +164,7 @@ export const memoryAgent = new Agent({
 })
 ```
 
-See [Observational Memory](https://mastra.ai/docs/memory/observational-memory) for details on how observations and reflections work, and [the reference](https://mastra.ai/reference/memory/observational-memory) for all configuration options.
+> **Note:** See [Observational Memory](https://mastra.ai/docs/memory/observational-memory) for details on how observations and reflections work, and [the reference](https://mastra.ai/reference/memory/observational-memory) for all configuration options.
 
 ## Memory in multi-agent systems
 
@@ -238,7 +236,7 @@ export const memoryAgent = new Agent({
 })
 ```
 
-Visit [Request Context](https://mastra.ai/docs/server/request-context) for more information.
+> **Note:** Visit [Request Context](https://mastra.ai/docs/server/request-context) for more information.
 
 ## Related
 

package/.docs/docs/memory/semantic-recall.md

@@ -4,7 +4,7 @@
 
 If you ask your friend what they did last weekend, they will search in their memory for events associated with "last weekend" and then tell you what they did. That's sort of like how semantic recall works in Mastra.
 
-> **📹 Watch:** Watch [Mastra semantic recall](https://www.youtube.com/watch?v=UVZtK8cK8xQ\&pp=ygUVbWFzdHJhIHdvcmtpbmcgbWVtb3J5) to see how agents retrieve relevant messages from past conversations.
+> **Watch 📹:** What semantic recall is, how it works, and how to configure it in Mastra → [YouTube (5 minutes)](https://youtu.be/UVZtK8cK8xQ)
 
 ## How semantic recall works
 

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

@@ -10,8 +10,6 @@ This is useful for maintaining ongoing state that's always relevant and should a
 
 If you use [Observational Memory](https://mastra.ai/docs/memory/observational-memory), `observationalMemory.observation.manageWorkingMemory` lets OM update working memory for the agent.
 
-> **📹 Watch:** Watch [Mastra working memory](https://www.youtube.com/watch?v=UMy_JHLf1n8\&pp=ygUVbWFzdHJhIHdvcmtpbmcgbWVtb3J5) to see how agents keep persistent user context available across interactions.
-
 Working memory can persist at two different scopes:
 
 - **Resource-scoped** (default): Memory persists across all conversation threads for the same user
@@ -45,7 +43,9 @@ const agent = new Agent({
 
 ## How it works
 
-Working memory is a block of Markdown text that the agent is able to update over time to store continuously relevant information.
+Working memory is a block of Markdown text that the agent is able to update over time to store continuously relevant information:
+
+[YouTube video player](https://www.youtube-nocookie.com/embed/UMy_JHLf1n8)
 
 ## Memory persistence scopes
 

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

@@ -126,7 +126,9 @@ If you prefer, rely entirely on environment variables:
 new MastraPlatformExporter()
 ```
 
-With `MASTRA_PLATFORM_ACCESS_TOKEN` and `MASTRA_PROJECT_ID` set, `MastraPlatformExporter` sends data to the Mastra platform project you configured. If you also set `MASTRA_PLATFORM_OBSERVABILITY_ENDPOINT`, it sends data to that collector instead. Visit [MastraPlatformExporter reference](https://mastra.ai/reference/observability/tracing/exporters/mastra-platform-exporter) for the full list of configuration options.
+With `MASTRA_PLATFORM_ACCESS_TOKEN` and `MASTRA_PROJECT_ID` set, `MastraPlatformExporter` sends data to the Mastra platform project you configured. If you also set `MASTRA_PLATFORM_OBSERVABILITY_ENDPOINT`, it sends data to that collector instead.
+
+> **Note:** Visit [MastraPlatformExporter reference](https://mastra.ai/reference/observability/tracing/exporters/mastra-platform-exporter) for the full list of configuration options.
 
 ## Recommended configuration
 

package/.docs/docs/observability/logging.md

@@ -22,7 +22,7 @@ export const mastra = new Mastra({
 })
 ```
 
-Visit [PinoLogger](https://mastra.ai/reference/logging/pino-logger) for all available configuration options.
+> **Info:** Visit [PinoLogger](https://mastra.ai/reference/logging/pino-logger) for all available configuration options.
 
 ## Logging to observability storage
 

package/.docs/docs/observability/tracing/overview.md

@@ -325,7 +325,7 @@ const result = await agent.generate([{ role: 'user', content: 'Sensitive operati
 })
 ```
 
-For more granular control over sensitive data, consider using the [Sensitive Data Filter](https://mastra.ai/docs/observability/integrations/processors/sensitive-data-filter) processor, which can redact specific fields (like passwords, tokens, and keys) while preserving the rest of the input/output.
+> **Tip:** For more granular control over sensitive data, consider using the [Sensitive Data Filter](https://mastra.ai/docs/observability/integrations/processors/sensitive-data-filter) processor, which can redact specific fields (like passwords, tokens, and keys) while preserving the rest of the input/output.
 
 #### Child spans and metadata extraction
 

package/.docs/docs/server/auth/auth0.md

@@ -105,7 +105,7 @@ const auth0Provider = new MastraAuthAuth0({
 })
 ```
 
-Visit [MastraAuthAuth0](https://mastra.ai/reference/auth/auth0) for all available configuration options.
+> **Info:** Visit [MastraAuthAuth0](https://mastra.ai/reference/auth/auth0) for all available configuration options.
 
 ## Client-side setup
 

package/.docs/docs/server/auth/better-auth.md

@@ -87,7 +87,7 @@ export const mastra = new Mastra({
 })
 ```
 
-Visit [MastraAuthBetterAuth](https://mastra.ai/reference/auth/better-auth) for all available configuration options.
+> **Info:** Visit [MastraAuthBetterAuth](https://mastra.ai/reference/auth/better-auth) for all available configuration options.
 
 ## Custom authorization
 
@@ -180,7 +180,7 @@ export const mastraClient = new MastraClient({
 })
 ```
 
-Visit [Mastra Client SDK](https://mastra.ai/docs/server/mastra-client) for more configuration options.
+> **Info:** Visit [Mastra Client SDK](https://mastra.ai/docs/server/mastra-client) for more configuration options.
 
 ### Making authenticated requests
 

package/.docs/docs/server/auth/clerk.md

@@ -88,7 +88,7 @@ export const useClerkAuth = () => {
 }
 ```
 
-Refer to the [Clerk documentation](https://clerk.com/docs) for more information.
+> **Info:** Refer to the [Clerk documentation](https://clerk.com/docs) for more information.
 
 ## Configuring `MastraClient`
 

package/.docs/docs/server/auth/firebase.md

@@ -118,7 +118,7 @@ const firebaseAuth = new MastraAuthFirebase({
 })
 ```
 
-Visit [MastraAuthFirebase](https://mastra.ai/reference/auth/firebase) for all available configuration options.
+> **Info:** Visit [MastraAuthFirebase](https://mastra.ai/reference/auth/firebase) for all available configuration options.
 
 ## Client-side setup
 

package/.docs/docs/server/auth/google.md

@@ -168,7 +168,7 @@ export const mastra = new Mastra({
 })
 ```
 
-Visit [MastraAuthGoogle](https://mastra.ai/reference/auth/google) for all available configuration options.
+> **Info:** Visit [MastraAuthGoogle](https://mastra.ai/reference/auth/google) for all available configuration options.
 
 ## Role mapping
 
@@ -242,7 +242,7 @@ export const createMastraClient = (idToken: string) => {
 }
 ```
 
-Visit [Mastra Client SDK](https://mastra.ai/docs/server/mastra-client) for more configuration options.
+> **Info:** Visit [Mastra Client SDK](https://mastra.ai/docs/server/mastra-client) for more configuration options.
 
 ### Making authenticated requests
 

package/.docs/docs/server/auth/jwt.md

@@ -61,7 +61,7 @@ export const mastra = new Mastra({
 })
 ```
 
-Visit [MastraJwtAuth](https://mastra.ai/reference/auth/jwt) for all available configuration options.
+> **Info:** Visit [MastraJwtAuth](https://mastra.ai/reference/auth/jwt) for all available configuration options.
 
 Inside [Studio](https://mastra.ai/docs/studio/overview), go to **Settings** and under **Headers** select the **"Add Header"** button. Enter `Authorization` as the header name and `Bearer <your-jwt>` as the value.
 
@@ -80,7 +80,7 @@ export const mastraClient = new MastraClient({
 })
 ```
 
-Visit [Mastra Client SDK](https://mastra.ai/docs/server/mastra-client) for more configuration options.
+> **Info:** Visit [Mastra Client SDK](https://mastra.ai/docs/server/mastra-client) for more configuration options.
 
 ### Making authenticated requests
 

package/.docs/docs/server/auth/okta.md

@@ -120,7 +120,7 @@ export const mastra = new Mastra({
 
 > **Note:** To link users between providers, store the Okta user ID in the other provider's user metadata. Mastra uses this ID to fetch groups from Okta.
 
-Visit [MastraAuthOkta](https://mastra.ai/reference/auth/okta) for all available configuration options.
+> **Info:** Visit [MastraAuthOkta](https://mastra.ai/reference/auth/okta) for all available configuration options.
 
 ## Role mapping
 
@@ -194,7 +194,7 @@ export const createMastraClient = (accessToken: string) => {
 }
 ```
 
-Visit [Mastra Client SDK](https://mastra.ai/docs/server/mastra-client) for more configuration options.
+> **Info:** Visit [Mastra Client SDK](https://mastra.ai/docs/server/mastra-client) for more configuration options.
 
 ### Making authenticated requests
 

package/.docs/docs/server/auth/workos.md

@@ -149,7 +149,7 @@ const workosAuth = new AdminOnlyWorkosAuth({
 })
 ```
 
-Visit [MastraAuthWorkos](https://mastra.ai/reference/auth/workos) for all available configuration options.
+> **Info:** Visit [MastraAuthWorkos](https://mastra.ai/reference/auth/workos) for all available configuration options.
 
 ## Client-side setup
 

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

@@ -134,7 +134,7 @@ export const mastraClient = new MastraClient({
 })
 ```
 
-Visit [MastraClient](https://mastra.ai/reference/client-js/mastra-client) for more configuration options.
+> **Info:** Visit [MastraClient](https://mastra.ai/reference/client-js/mastra-client) for more configuration options.
 
 ## Credentials and session cookies
 

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

@@ -32,7 +32,7 @@ export const mastra = new Mastra({
 })
 ```
 
-Visit the [configuration reference](https://mastra.ai/reference/configuration) for a full list of available server options.
+> **Info:** Visit the [configuration reference](https://mastra.ai/reference/configuration) for a full list of available server options.
 
 ## Deploy your server
 

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

@@ -116,7 +116,7 @@ export const mastra = new Mastra({
 })
 ```
 
-Visit the [PubSub reference](https://mastra.ai/reference/pubsub/base) for the full delivery contract and the configuration options for each backend.
+> **Note:** Visit the [PubSub reference](https://mastra.ai/reference/pubsub/base) for the full delivery contract and the configuration options for each backend.
 
 ## Related
 

package/.docs/docs/server/request-context.md

@@ -82,7 +82,7 @@ export const mastra = new Mastra({
 })
 ```
 
-Visit [Middleware](https://mastra.ai/docs/server/middleware) for how to use server middleware.
+> **Info:** Visit [Middleware](https://mastra.ai/docs/server/middleware) for how to use server middleware.
 
 ## Studio
 
@@ -188,7 +188,7 @@ export const registryAgent = new Agent({
 })
 ```
 
-Visit [Agent](https://mastra.ai/reference/agents/agent) for a full list of configuration options.
+> **Info:** Visit [Agent](https://mastra.ai/reference/agents/agent) for a full list of configuration options.
 
 ## Accessing values from workflow steps
 
@@ -210,7 +210,7 @@ const stepOne = createStep({
 })
 ```
 
-Visit [createStep()](https://mastra.ai/reference/workflows/step) for a full list of configuration options.
+> **Info:** Visit [createStep()](https://mastra.ai/reference/workflows/step) for a full list of configuration options.
 
 ## Accessing values with tools
 
@@ -232,7 +232,7 @@ export const weatherTool = createTool({
 })
 ```
 
-Visit [createTool()](https://mastra.ai/reference/tools/create-tool) for a full list of configuration options.
+> **Info:** Visit [createTool()](https://mastra.ai/reference/tools/create-tool) for a full list of configuration options.
 
 ## Reserved keys
 

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

@@ -303,7 +303,7 @@ app.listen(4111, () => {
 })
 ```
 
-See the [Express Adapter](https://mastra.ai/reference/server/express-adapter) documentation for full configuration options.
+> **Info:** See the [Express Adapter](https://mastra.ai/reference/server/express-adapter) documentation for full configuration options.
 
 **Hono**:
 
@@ -324,7 +324,7 @@ serve({ fetch: app.fetch, port: 4111 }, () => {
 })
 ```
 
-See the [Hono Adapter](https://mastra.ai/reference/server/hono-adapter) documentation for full configuration options.
+> **Info:** See the [Hono Adapter](https://mastra.ai/reference/server/hono-adapter) documentation for full configuration options.
 
 **Fastify**:
 
@@ -352,7 +352,7 @@ app.listen({ port }, () => {
 })
 ```
 
-See the [Fastify Adapter](https://mastra.ai/reference/server/fastify-adapter) documentation for full configuration options.
+> **Info:** See the [Fastify Adapter](https://mastra.ai/reference/server/fastify-adapter) documentation for full configuration options.
 
 **Koa**:
 
@@ -387,7 +387,7 @@ app.listen(port, () => {
 })
 ```
 
-See the [Koa Adapter](https://mastra.ai/reference/server/koa-adapter) documentation for full configuration options.
+> **Info:** See the [Koa Adapter](https://mastra.ai/reference/server/koa-adapter) documentation for full configuration options.
 
 **NestJS**:
 
@@ -418,7 +418,7 @@ async function bootstrap() {
 bootstrap()
 ```
 
-See the [NestJS Adapter](https://mastra.ai/reference/server/nestjs-adapter) documentation for full configuration options.
+> **Info:** See the [NestJS Adapter](https://mastra.ai/reference/server/nestjs-adapter) documentation for full configuration options.
 
 ## Initialization flow
 
@@ -460,7 +460,7 @@ You can add your own routes to the app alongside Mastra's routes.
 - When you want Mastra-managed auth and route metadata such as `requiresAuth`, prefer `registerApiRoute()`.
 - When you mount routes directly on the framework app, use the adapter's exported `createAuthMiddleware()` helper if those routes need Mastra auth.
 
-Visit "Adding custom routes" for [Express](https://mastra.ai/reference/server/express-adapter) and [Hono](https://mastra.ai/reference/server/hono-adapter) for more information.
+> **Info:** Visit "Adding custom routes" for [Express](https://mastra.ai/reference/server/express-adapter) and [Hono](https://mastra.ai/reference/server/hono-adapter) for more information.
 
 ## Route prefixes
 
@@ -513,7 +513,7 @@ const server = new MastraServer({
 })
 ```
 
-See [MastraServer](https://mastra.ai/reference/server/mastra-server) for full configuration options.
+> **Info:** See [MastraServer](https://mastra.ai/reference/server/mastra-server) for full configuration options.
 
 ## Per-route auth overrides
 
@@ -540,7 +540,7 @@ const server = new MastraServer({
 })
 ```
 
-See [MastraServer](https://mastra.ai/reference/server/mastra-server) for full configuration options.
+> **Info:** See [MastraServer](https://mastra.ai/reference/server/mastra-server) for full configuration options.
 
 ## Accessing the app
 

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

@@ -35,7 +35,9 @@ 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.
+
+> **Note:** Visit the [Auth docs](https://mastra.ai/docs/server/auth) for a full list of supported providers.
 
 ## How it works
 

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

@@ -4,7 +4,7 @@
 
 Studio provides an interactive UI for building, testing, and managing your agents, workflows, and tools. Run it locally during development, add [authentication](https://mastra.ai/docs/studio/auth), or [deploy it](https://mastra.ai/docs/studio/deployment) to production so your team can manage agents, monitor performance, and gain insights through built-in observability.
 
-> **📹 Watch:** Watch [Mastra Studio overview](https://youtu.be/ojGu6Bi4wYk) for a short walkthrough of building, testing, and managing agents in Studio.
+[YouTube video player](https://www.youtube-nocookie.com/embed/ojGu6Bi4wYk)
 
 ## Start Studio
 

package/.docs/docs/voice/livekit.md

@@ -162,45 +162,6 @@ export default createLiveKitWorker({
 
 See the [LiveKit turn detection docs](https://docs.livekit.io/agents/logic/turns/) for all options.
 
-## Per-call voices and transcription
-
-The top-level `stt` and `tts` options apply to every call. To pick them per call — one voice or language per tenant — set the `configuration.stt` and `configuration.tts` resolvers instead. Each resolver runs once per call with the dispatch metadata, request context, room name, and job context, and returns anything the matching top-level option accepts: a plugin instance or an inference model string. Return `undefined` to fall back to the top-level option.
-
-The following example gives each tenant its own text-to-speech voice, keyed off the `tenant` entry in the dispatch metadata:
-
-```typescript
-import * as cartesia from '@livekit/agents-plugin-cartesia'
-
-// One voice id per tenant, resolved from the dispatch metadata on each call.
-const tenantVoices: Record<string, string> = {
-  meridian: 'your-cartesia-voice-id-1',
-  coastal: 'your-cartesia-voice-id-2',
-}
-// The resolver runs during call setup, so cache plugin instances across calls.
-const ttsByVoice = new Map<string, cartesia.TTS>()
-
-export default createLiveKitWorker({
-  mastra,
-  agent: 'support',
-  stt: 'deepgram/nova-3',
-  tts: 'cartesia/sonic-3',
-  configuration: {
-    tts: ({ requestContext }) => {
-      const voice = tenantVoices[requestContext?.tenant as string]
-      if (!voice) return undefined // fall back to the top-level `tts`
-      let tts = ttsByVoice.get(voice)
-      if (!tts) {
-        tts = new cartesia.TTS({ voice })
-        ttsByVoice.set(voice, tts)
-      }
-      return tts
-    },
-  },
-})
-```
-
-`configuration.stt` works the same way for per-call transcription, for example a different transcription model or language per tenant. The greeting has a matching per-call form: `configuration.greeting.text` accepts a resolver with the same call context, so one worker can open with each tenant's own phrasing.
-
 ## Memory and threads
 
 When the resolved Mastra agent has memory configured, each call becomes one memory thread:
@@ -211,7 +172,7 @@ When the resolved Mastra agent has memory configured, each call becomes one memo
 
 Each turn sends only the new user input; Mastra Memory supplies history, semantic recall, and working memory. Pin a session to an existing thread by passing `threadId` in the connection request body, which is useful for continuing a text conversation by voice. In Studio, starting a call from an open chat binds the call to that thread, and the transcript fills into the chat after each exchange.
 
-When a user interrupts the agent, the in-flight generation aborts and nothing from that turn is persisted at that moment. LiveKit keeps the part the user actually heard in its transcript, and on the next turn the worker re-sends that heard-only fragment so the thread backfills to match the call. A user who hangs up right after interrupting leaves that final fragment unrecorded; see [interrupted turns](https://mastra.ai/reference/voice/livekit) for the details and a reconciliation recipe.
+One caveat: when a user interrupts the agent, Mastra Memory stores the full generated reply even though the user only heard part of it. LiveKit's own transcript is truncated to what was spoken.
 
 ## Speak while tools run
 
@@ -228,13 +189,13 @@ export default createLiveKitWorker({
 })
 ```
 
-The phrase is spoken as part of the reply and recorded in the transcript.
+The phrase is spoken as part of the reply and shown in the transcript.
 
 ## Generate replies with a workflow
 
 By default the worker generates each reply with a Mastra agent. To run multi-step logic per turn (for example classify intent, route, call tools in sequence, then compose a reply), generate replies with a Mastra [workflow](https://mastra.ai/docs/workflows/overview) instead. Set `workflow` in place of `agent`.
 
-LiveKit still owns the audio loop and calls into Mastra once per turn, so the workflow runs to completion each turn. The workflow can't suspend or resume, and no conversation state carries between turns. Pass the transcript in through `workflowInput` so the workflow stays stateless:
+LiveKit still owns the audio loop and calls into Mastra once per turn, so the workflow runs to completion each turn. Suspend and resume aren't available, and conversation state isn't carried between turns. Pass the transcript in through `workflowInput` so the workflow stays stateless:
 
 ```typescript
 import { createLiveKitWorker, chatContextToMessages } from '@mastra/livekit/worker'
@@ -272,64 +233,6 @@ const generateResponse = createStep({
 
 With a workflow, the worker doesn't persist turns automatically the way an agent's `stream()` does. Persist conversation history inside the workflow, or keep the LiveKit transcript as the source of truth and pass it in each turn.
 
-## Use Mastra as the LLM component
-
-`createLiveKitWorker()` owns the LiveKit session for you. To own the session yourself, use [`MastraLLM`](https://mastra.ai/reference/voice/livekit) instead: a standard LiveKit LLM plugin that puts a Mastra agent in the `llm` slot of your own `voice.AgentSession`. The Mastra app — agent loop, tools, memory, observability — runs on your Mastra server, and the worker reaches it over HTTP. The worker process needs no Mastra app, database, or model provider keys.
-
-```typescript
-import { fileURLToPath } from 'node:url'
-import { defineAgent, voice } from '@livekit/agents'
-import * as silero from '@livekit/agents-plugin-silero'
-import { MastraLLM } from '@mastra/livekit/plugin'
-import { runLiveKitWorker } from '@mastra/livekit/worker'
-
-export default defineAgent({
-  entry: async ctx => {
-    await ctx.connect()
-
-    const session = new voice.AgentSession({
-      llm: new MastraLLM({
-        remote: { baseUrl: process.env.MASTRA_URL!, agentId: 'support' },
-        memory: { thread: ctx.room.name!, resource: 'user-7' },
-      }),
-      stt: 'deepgram/nova-3',
-      tts: 'cartesia/sonic-3',
-      vad: await silero.VAD.load(),
-      // Required with `memory`: LiveKit enables preemptive generation by default.
-      turnHandling: { preemptiveGeneration: { enabled: false } },
-    })
-
-    await session.start({
-      // These instructions never reach the Mastra agent; its own instructions apply.
-      agent: new voice.Agent({ instructions: 'Replies come from the Mastra agent.' }),
-      room: ctx.room,
-    })
-
-    session.say('Hi! How can I help you today?')
-  },
-})
-
-if (process.argv[1] === fileURLToPath(import.meta.url)) {
-  runLiveKitWorker({ entry: import.meta.url, agentName: 'mastra-voice' })
-}
-```
-
-Both paths share the same reply pipeline underneath; choose by who should own the session:
-
-|                           | `createLiveKitWorker()`                                                                    | `MastraLLM`                                                                                 |
-| ------------------------- | ------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------- |
-| Session ownership         | The worker helper builds and manages the `AgentSession`                                    | Your code builds the session; every LiveKit option and hook is yours                        |
-| Where the Mastra app runs | In the worker process                                                                      | On your Mastra server, reached over HTTP (or in-process via `agent`)                        |
-| Worker process needs      | Your Mastra app, storage, and model provider keys                                          | Only the LiveKit SDK and network access to your server                                      |
-| Built-in conveniences     | Greeting, consent gating, agent-initiated hang-up, thread bootstrap, observability roll-up | Rebuild what you need with the [session helpers](https://mastra.ai/reference/voice/livekit) |
-| Best for                  | Fastest path to a working voice agent; Studio voice mode                                   | Existing LiveKit apps and full control over the session                                     |
-
-Tools stay on the Mastra agent and execute on the server; LiveKit-side tools passed to the session are ignored. Tool activity reaches the worker through `toolFeedback` (spoken filler), `onToolCall` (fires as each tool call starts), and `onTurnComplete` (fires after each reply with the text, tool calls, and token usage). Agent-initiated hang-up takes a few lines: pair `onToolCall` with [`runEndCall()`](https://mastra.ai/reference/voice/livekit).
-
-> **Warning:** Don't combine the `memory` option with LiveKit's `preemptiveGeneration`, which LiveKit enables by default in sessions you build yourself. A speculative turn that completes before LiveKit discards it persists a user message and a never-spoken reply to the thread. Set `turnHandling: { preemptiveGeneration: { enabled: false } }` as shown above, or run without `memory` and pass the full transcript each turn.
-
-`MastraLLM` also accepts an in-process Mastra `agent` instance — session ownership without a second deployment — or a custom `generate` function. The remote transport is available standalone as [`createRemoteAgentReplyGenerator()`](https://mastra.ai/reference/voice/livekit), which also plugs into `createLiveKitWorker`'s `generate` option to run the batteries-included worker against a remote server.
-
 ## Server-initiated sessions
 
 Use `dispatchVoiceSession()` to add a voice agent to a room from your own code, for example to join an existing room or to drive an outbound [SIP call](https://docs.livekit.io/sip/):

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

@@ -57,7 +57,7 @@ export const testWorkflow = createWorkflow({})
   .commit()
 ```
 
-Visit [Input Data Mapping](https://mastra.ai/docs/workflows/control-flow) for more information.
+> **Info:** Visit [Input Data Mapping](https://mastra.ai/docs/workflows/control-flow) for more information.
 
 When no `structuredOutput` option is provided, Mastra agents use a default schema that expects a `prompt` string as input and returns a `text` string as output:
 
@@ -106,7 +106,9 @@ export const testWorkflow = createWorkflow({})
   .commit()
 ```
 
-The `structuredOutput.schema` option accepts any Standard JSON Schema. The agent will generate output conforming to this schema, and the step's `outputSchema` will be automatically set to match. Visit [Structured Output](https://mastra.ai/docs/agents/structured-output) for more options like error handling strategies and streaming with structured output.
+The `structuredOutput.schema` option accepts any Standard JSON Schema. The agent will generate output conforming to this schema, and the step's `outputSchema` will be automatically set to match.
+
+> **Info:** Visit [Structured Output](https://mastra.ai/docs/agents/structured-output) for more options like error handling strategies and streaming with structured output.
 
 ## Using tools in workflows
 
@@ -155,7 +157,7 @@ export const testWorkflow = createWorkflow({})
   .commit()
 ```
 
-Visit [Input Data Mapping](https://mastra.ai/docs/workflows/control-flow) for more information.
+> **Info:** Visit [Input Data Mapping](https://mastra.ai/docs/workflows/control-flow) for more information.
 
 ## Related
 

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

@@ -101,6 +101,8 @@ export const testWorkflow = createWorkflow({
   .commit()
 ```
 
+> **📹 Watch:** How to run steps in parallel and optimize your Mastra workflow → [YouTube (3 minutes)](https://youtu.be/GQJxve5Hki4)
+
 ### Output structure
 
 When steps run in parallel, the output is an object where each key is the step's `id` and the value is that step's output. This allows you to access each parallel step's result independently.
@@ -208,7 +210,7 @@ const writerStep = createStep({
 })
 ```
 
-Visit [Choosing the right pattern](#choosing-the-right-pattern) to understand when to use `.parallel()` vs `.foreach()`.
+> **Info:** Visit [Choosing the right pattern](#choosing-the-right-pattern) to understand when to use `.parallel()` vs `.foreach()`.
 
 ## Conditional logic with `.branch()`