@mastra/mcp-docs-server 1.1.42-alpha.7 → 1.1.42-alpha.8

package/.docs/docs/agents/signals.md

@@ -233,9 +233,24 @@ Existing stored signal rows and older clients continue to load through the compa
 
 > **Note:** Visit [Agent signals reference](https://mastra.ai/reference/agents/agent) for the full message, signal, and subscription types.
 
+## Approve tool calls
+
+When a subscribed run pauses for tool approval, approve or decline the tool call with the subscription-native methods. The call returns a JSON acknowledgement. The resumed chunks arrive through the existing thread subscription.
+
+```typescript
+await agent.sendToolApproval({
+  resourceId: 'user_123',
+  threadId: 'thread_456',
+  toolCallId: 'tool-call_456',
+  approved: true,
+})
+```
+
+Pass `approved: false` to decline the same pending tool call. Use the older `approveToolCall()` and `declineToolCall()` methods only when you are rendering the separate continuation stream directly.
+
 ## Use HTTP routes
 
-If you call Mastra over HTTP directly, use `POST /api/agents/:agentId/send-message` for immediate messages and `POST /api/agents/:agentId/queue-message` for next-turn messages. See [Server routes reference](https://mastra.ai/reference/server/routes) for request and response schemas.
+If you call Mastra over HTTP directly, use `POST /api/agents/:agentId/send-message` for immediate messages and `POST /api/agents/:agentId/queue-message` for next-turn messages. For subscription-native tool approval, use `POST /api/agents/:agentId/send-tool-approval`. See [Server routes reference](https://mastra.ai/reference/server/routes) for request and response schemas.
 
 ## Use the client SDK
 
@@ -294,4 +309,5 @@ Use heartbeats together with client-side reconnect logic. Heartbeats reduce idle
 - [`Agent.subscribeToThread()`](https://mastra.ai/reference/agents/agent)
 - [Server agent routes](https://mastra.ai/reference/server/routes)
 - [`client.getAgent().sendSignal()`](https://mastra.ai/reference/client-js/agents)
-- [`client.getAgent().subscribeToThread()`](https://mastra.ai/reference/client-js/agents)
+- [`client.getAgent().subscribeToThread()`](https://mastra.ai/reference/client-js/agents)
+- [`client.getAgent().sendToolApproval()`](https://mastra.ai/reference/client-js/agents)

package/.docs/reference/client-js/agents.md

@@ -326,7 +326,7 @@ response.processDataStream({
 
 ### `approveToolCall()`
 
-Approve a pending tool call that requires human confirmation:
+Approve a pending tool call and return a continuation stream. Use this when you are rendering the resumed chunks from the approval response.
 
 ```typescript
 const response = await agent.approveToolCall({
@@ -341,9 +341,26 @@ response.processDataStream({
 })
 ```
 
+### `sendToolApproval()`
+
+Approve or decline a pending tool call for a subscribed thread. Use this with `subscribeToThread()` when the resumed chunks should arrive through the existing thread subscription instead of a separate continuation stream.
+
+```typescript
+const result = await agent.sendToolApproval({
+  resourceId: 'user-123',
+  threadId: 'thread-456',
+  toolCallId: 'tool-call-456',
+  approved: true,
+})
+
+console.log(result.accepted)
+```
+
+Returns `{ accepted: true, runId: string, toolCallId?: string }`.
+
 ### `declineToolCall()`
 
-Decline a pending tool call that requires human confirmation:
+Decline a pending tool call and return a continuation stream. Use this when you are rendering the resumed chunks from the decline response.
 
 ```typescript
 const response = await agent.declineToolCall({

package/.docs/reference/server/routes.md

@@ -4,19 +4,20 @@ Server adapters register these routes when you call `server.init()`. All routes
 
 ## Agents
 
-| Method | Path                                         | Description                                           |
-| ------ | -------------------------------------------- | ----------------------------------------------------- |
-| `GET`  | `/api/agents`                                | List all agents                                       |
-| `GET`  | `/api/agents/:agentId`                       | Get agent by ID (supports version query params)       |
-| `POST` | `/api/agents/:agentId/generate`              | Generate agent response                               |
-| `POST` | `/api/agents/:agentId/stream`                | Stream agent response                                 |
-| `POST` | `/api/agents/:agentId/send-message`          | Send a user message to an active or idle thread       |
-| `POST` | `/api/agents/:agentId/queue-message`         | Queue a user message for the next thread turn         |
-| `POST` | `/api/agents/:agentId/signals`               | Send a lower-level signal to an active or idle thread |
-| `POST` | `/api/agents/:agentId/subscribe-thread`      | Subscribe to a thread stream                          |
-| `POST` | `/api/agents/:agentId/resume-stream`         | Resume a suspended agent stream with custom data      |
-| `GET`  | `/api/agents/:agentId/tools`                 | List agent tools                                      |
-| `POST` | `/api/agents/:agentId/tools/:toolId/execute` | Execute agent tool                                    |
+| Method | Path                                         | Description                                                             |
+| ------ | -------------------------------------------- | ----------------------------------------------------------------------- |
+| `GET`  | `/api/agents`                                | List all agents                                                         |
+| `GET`  | `/api/agents/:agentId`                       | Get agent by ID (supports version query params)                         |
+| `POST` | `/api/agents/:agentId/generate`              | Generate agent response                                                 |
+| `POST` | `/api/agents/:agentId/stream`                | Stream agent response                                                   |
+| `POST` | `/api/agents/:agentId/send-message`          | Send a user message to an active or idle thread                         |
+| `POST` | `/api/agents/:agentId/queue-message`         | Queue a user message for the next thread turn                           |
+| `POST` | `/api/agents/:agentId/signals`               | Send a lower-level signal to an active or idle thread                   |
+| `POST` | `/api/agents/:agentId/threads/subscribe`     | Subscribe to a thread stream                                            |
+| `POST` | `/api/agents/:agentId/send-tool-approval`    | Approve or decline a tool call and resume through a thread subscription |
+| `POST` | `/api/agents/:agentId/resume-stream`         | Resume a suspended agent stream with custom data                        |
+| `GET`  | `/api/agents/:agentId/tools`                 | List agent tools                                                        |
+| `POST` | `/api/agents/:agentId/tools/:toolId/execute` | Execute agent tool                                                      |
 
 ### Get agent query parameters
 
@@ -140,6 +141,32 @@ Both routes return:
 }
 ```
 
+### Subscription tool approval routes
+
+Use `POST /api/agents/:agentId/send-tool-approval` when the client already has an active thread subscription. The route resumes the run and returns a JSON acknowledgement. Resumed stream chunks are delivered through `POST /api/agents/:agentId/threads/subscribe`.
+
+The route accepts this request body:
+
+```typescript
+{
+  resourceId: string;
+  threadId: string;
+  toolCallId: string;
+  approved: boolean;
+  requestContext?: Record<string, unknown>;
+}
+```
+
+The route returns:
+
+```typescript
+{
+  accepted: true;
+  runId: string;
+  toolCallId?: string;
+}
+```
+
 ## Workflows
 
 | Method | Path                                      | Description                     |

package/.docs/reference/voice/google-gemini-live.md

@@ -242,7 +242,9 @@ The GeminiLiveVoice class emits the following events:
 
 **speaking** (`event`): Emitted with audio metadata. Callback receives { audioData?: Int16Array, sampleRate?: number }.
 
-**writing** (`event`): Emitted when transcribed text is available. Callback receives { text: string, role: 'assistant' | 'user' }.
+**writing** (`event`): Emitted when transcribed text is available. Callback receives { text: string, role: 'assistant' | 'user' }. On native-audio models the assistant transcript is driven by the server's \`output\_audio\_transcription\` channel rather than \`modelTurn.parts.text\`.
+
+**thinking** (`event`): Emitted on native-audio models with the model's chain-of-thought / reasoning text from \`modelTurn.parts.text\`. Callback receives { text: string }. Does not fire on non-native-audio models, where \`modelTurn.parts.text\` is the spoken response and is emitted as \`writing\` instead.
 
 **session** (`event`): Emitted on session state changes. Callback receives { state: 'connecting' | 'connected' | 'disconnected' | 'disconnecting' | 'updated', config?: object }.
 
@@ -254,7 +256,18 @@ The GeminiLiveVoice class emits the following events:
 
 **error** (`event`): Emitted when an error occurs. Callback receives { message: string, code?: string, details?: unknown }.
 
-**interrupt** (`event`): Interrupt events. Callback receives { type: 'user' | 'model', timestamp: number }.
+**interrupt** (`event`): Emitted on barge-in when the user starts speaking over an in-flight model response. The server cancels any further audio for the current turn. Callback receives { type: 'user', timestamp: number }.
+
+## Native-audio behavior
+
+Native-audio Gemini Live models — any model whose ID contains `native-audio`, such as `gemini-2.5-flash-native-audio-preview-12-2025` — split text output across two channels:
+
+- The model's spoken reply is delivered as audio plus an `output_audio_transcription` transcript and surfaced as `writing` with `role: 'assistant'`.
+- The model's internal reasoning is delivered as `modelTurn.parts.text` and surfaced as `thinking`.
+
+On non-native-audio models there is no `output_audio_transcription` channel, so `modelTurn.parts.text` is the spoken response itself and is emitted as `writing`; the `thinking` event does not fire.
+
+Input transcription, output transcription, and barge-in detection (`realtime_input_config.activity_handling = 'START_OF_ACTIVITY_INTERRUPTS'`) are enabled automatically in the setup payload — no extra configuration is required.
 
 ## Available models
 

package/CHANGELOG.md

@@ -1,5 +1,12 @@
 # @mastra/mcp-docs-server
 
+## 1.1.42-alpha.8
+
+### Patch Changes
+
+- Updated dependencies [[`19a8658`](https://github.com/mastra-ai/mastra/commit/19a86589c788ef48bb6c1b0612cc82a201857379), [`a659a77`](https://github.com/mastra-ai/mastra/commit/a659a779bdebe3a52a518c56d2260592d0240fe0), [`3332be9`](https://github.com/mastra-ai/mastra/commit/3332be9701ecd77aba840959d9a1d1ce7aef02d3)]:
+  - @mastra/core@1.38.0-alpha.6
+
 ## 1.1.42-alpha.7
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mastra/mcp-docs-server",
-  "version": "1.1.42-alpha.7",
+  "version": "1.1.42-alpha.8",
   "description": "MCP server for accessing Mastra.ai documentation, changelogs, and news.",
   "type": "module",
   "main": "dist/index.js",
@@ -28,8 +28,8 @@
     "jsdom": "^26.1.0",
     "local-pkg": "^1.1.2",
     "zod": "^4.4.3",
-    "@mastra/core": "1.38.0-alpha.5",
-    "@mastra/mcp": "^1.9.0-alpha.0"
+    "@mastra/mcp": "^1.9.0-alpha.0",
+    "@mastra/core": "1.38.0-alpha.6"
   },
   "devDependencies": {
     "@hono/node-server": "^1.19.11",
@@ -45,9 +45,9 @@
     "tsx": "^4.21.0",
     "typescript": "^6.0.3",
     "vitest": "4.1.5",
+    "@internal/lint": "0.0.99",
     "@internal/types-builder": "0.0.74",
-    "@mastra/core": "1.38.0-alpha.5",
-    "@internal/lint": "0.0.99"
+    "@mastra/core": "1.38.0-alpha.6"
   },
   "homepage": "https://mastra.ai",
   "repository": {