@mastra/mcp-docs-server 1.1.35-alpha.6 → 1.1.35-alpha.8

package/.docs/guides/guide/web-search.md

@@ -17,7 +17,7 @@ Some LLM providers include built-in web search capabilities that can be used dir
 
 1. Install dependencies
 
-   **Open AI**:
+   **OpenAI**:
 
    **npm**:
 
@@ -119,7 +119,7 @@ Some LLM providers include built-in web search capabilities that can be used dir
 
 2. Create a new file `src/mastra/agents/searchAgent.ts` and define your agent:
 
-   **Open AI**:
+   **OpenAI**:
 
    ```ts
    import { Agent } from '@mastra/core/agent'
@@ -128,7 +128,7 @@ Some LLM providers include built-in web search capabilities that can be used dir
      id: 'search-agent',
      name: 'Search Agent',
      instructions: 'You are a search agent that can search the web for information.',
-     model: 'openai/gpt-5.4',
+     model: 'openai/gpt-5.5',
    })
    ```
 
@@ -147,7 +147,7 @@ Some LLM providers include built-in web search capabilities that can be used dir
 
 3. Setup the tool:
 
-   **Open AI**:
+   **OpenAI**:
 
    ```ts
    import { openai } from '@ai-sdk/openai'
@@ -157,7 +157,7 @@ Some LLM providers include built-in web search capabilities that can be used dir
      id: 'search-agent',
      name: 'Search Agent',
      instructions: 'You are a search agent that can search the web for information.',
-     model: 'openai/gpt-5.4',
+     model: 'openai/gpt-5.5',
      tools: {
        webSearch: openai.tools.webSearch(),
      },
@@ -241,7 +241,7 @@ For more control over search behavior, you can integrate external search APIs as
      id: 'search-agent',
      name: 'Search Agent',
      instructions: 'You are a search agent that can search the web for information.',
-     model: 'openai/gpt-5.4',
+     model: 'openai/gpt-5.5',
    })
    ```
 
@@ -293,7 +293,7 @@ For more control over search behavior, you can integrate external search APIs as
      id: 'search-agent',
      name: 'Search Agent',
      instructions: 'You are a search agent that can search the web for information.',
-     model: 'openai/gpt-5.4',
+     model: 'openai/gpt-5.5',
      tools: {
        webSearch,
      },

package/.docs/models/gateways/azure-openai.md

@@ -13,7 +13,7 @@ const agent = new Agent({
   id: "my-agent",
   name: "My Agent",
   instructions: "You are a helpful assistant",
-  model: "azure-openai/my-gpt4-deployment"  // Use your Azure deployment name (autocompleted in dev mode)
+  model: "azure-openai/my-gpt-5-4-deployment"  // Use your Azure deployment name (autocompleted in dev mode)
 });
 
 // Generate a response
@@ -34,9 +34,9 @@ Azure model IDs follow this pattern: `azure-openai/your-deployment-name`
 
 The deployment name is **specific to your Azure account** and chosen when you create a deployment in Azure Portal. Common examples:
 
-- `azure-openai/my-gpt4-deployment`
-- `azure-openai/production-gpt-35-turbo`
-- `azure-openai/staging-gpt-4o`
+- `azure-openai/my-gpt-5-4-deployment`
+- `azure-openai/production-gpt-5-4`
+- `azure-openai/staging-gpt-5-4-mini`
 
 ## Setup
 
@@ -44,7 +44,7 @@ Create deployments in [Azure OpenAI Studio](https://oai.azure.com/). The resourc
 
 ## Configuration
 
-Instantiate the gateway and pass it to Mastra. Three configuration modes are available.
+Instantiate the gateway and pass it to Mastra. The common configuration modes are shown below.
 
 ### Static Deployments
 
@@ -59,7 +59,7 @@ export const mastra = new Mastra({
     new AzureOpenAIGateway({
       resourceName: "my-openai-resource",
       apiKey: process.env.AZURE_API_KEY!,
-      deployments: ["gpt-4-prod", "gpt-35-turbo-dev"],
+      deployments: ["gpt-5-4-prod", "gpt-5-4-mini-dev"],
     }),
   ],
 });
@@ -111,7 +111,7 @@ export const mastra = new Mastra({
         type: "entraId",
         credential: new DefaultAzureCredential(),
       },
-      deployments: ["gpt-4-prod", "gpt-35-turbo-dev"],
+      deployments: ["gpt-5-4-prod", "gpt-5-4-mini-dev"],
     }),
   ],
 });
@@ -145,23 +145,94 @@ export const mastra = new Mastra({
 });
 ```
 
+### Azure Responses API
+
+Azure OpenAI supports the Responses API through the `v1` API path used by the AI SDK Azure provider. Set `useResponsesAPI: true` when your Azure resource and deployment support that route. The gateway then uses `apiVersion: "v1"` and `useDeploymentBasedUrls: false` by default.
+
+```typescript
+import { Mastra } from "@mastra/core";
+import { AzureOpenAIGateway } from "@mastra/core/llm";
+
+export const mastra = new Mastra({
+  gateways: [
+    new AzureOpenAIGateway({
+      resourceName: "my-openai-resource",
+      apiKey: process.env.AZURE_API_KEY!,
+      useResponsesAPI: true,
+      deployments: ["my-gpt-5-4-deployment"],
+    }),
+  ],
+});
+```
+
+Keep `useResponsesAPI` omitted or set it to `false` for the existing Azure chat completions route. That path keeps `apiVersion: "2024-04-01-preview"` and deployment-based URLs by default for compatibility.
+
+You can still configure `apiVersion` and `useDeploymentBasedUrls` directly. For example, set `useDeploymentBasedUrls: false` to use the Azure `v1` URL shape with the chat model constructor; the gateway defaults `apiVersion` to `"v1"` for that route. Passing `apiVersion: "v1"` by itself keeps the existing deployment-based URL default for compatibility.
+
+Do not combine `useResponsesAPI: true` with `useDeploymentBasedUrls: true`; the gateway rejects that configuration because Responses API support uses the Azure `v1` route.
+
+Use `apiVersion: "v1"` for the GA `v1` route. Microsoft currently exposes preview `v1` features through feature-specific headers, such as `"aoai-evals": "preview"`, or through preview/alpha API paths. The gateway still accepts `apiVersion: "preview"` with `useDeploymentBasedUrls: false` for Azure provider configurations that require the preview query value. Date-based API versions are only for the legacy deployment-based route, so the gateway rejects them when `useResponsesAPI` is `true` or `useDeploymentBasedUrls` is `false`.
+
+The same API key and Microsoft Entra ID authentication modes work with the `v1` route.
+
+### Azure Responses WebSocket transport
+
+Azure OpenAI also supports WebSocket mode on the Responses API. Use it for agent or tool loops with many model-tool round trips. Keep the standard HTTP transport for single-shot requests and short conversations.
+
+WebSocket transport requires `useResponsesAPI: true`, because Azure exposes it on the `v1` Responses path. Then opt in per stream request with `providerOptions.azure.transport: "websocket"`.
+
+```typescript
+import { Agent } from "@mastra/core/agent";
+
+const agent = new Agent({
+  id: "azure-ws-agent",
+  name: "Azure WebSocket Agent",
+  instructions: "Use tools when they are useful.",
+  model: "azure-openai/my-gpt-5-4-deployment",
+});
+
+const stream = await agent.stream("Find and improve the slow function.", {
+  providerOptions: {
+    azure: {
+      transport: "websocket",
+      store: false,
+      websocket: {
+        closeOnFinish: false,
+      },
+    },
+  },
+});
+
+for await (const chunk of stream.textStream) {
+  process.stdout.write(chunk);
+}
+
+stream.transport?.close();
+```
+
+Set `closeOnFinish: false` when you want to keep the socket open across follow-up turns. Azure keeps one response chain in connection-local memory, so continuing from the most recent `previous_response_id` can reduce continuation latency. The connection runs one response at a time and does not multiplex parallel runs.
+
+Do not send overlapping follow-up requests with `previous_response_id` on the same WebSocket transport. Mastra rejects overlapping continuation requests because Azure only keeps one in-flight response per connection. Wait for the active stream to finish before continuing the response chain.
+
 ## Configuration Reference
 
-| Option                      | Type              | Required | Description                                                           |
-| --------------------------- | ----------------- | -------- | --------------------------------------------------------------------- |
-| `resourceName`              | `string`          | Yes      | Azure OpenAI resource name                                            |
-| `apiKey`                    | `string`          | Yes\*    | API key from "Keys and Endpoint"                                      |
-| `authentication`            | `object`          | No       | Microsoft Entra ID authentication                                     |
-| `authentication.type`       | `"entraId"`       | Yes\*    | Authentication mode                                                   |
-| `authentication.credential` | `TokenCredential` | Yes\*    | Azure SDK-compatible credential for `entraId` authentication mode     |
-| `authentication.scope`      | `string`          | No       | Token scope (default: `https://cognitiveservices.azure.com/.default`) |
-| `apiVersion`                | `string`          | No       | API version (default: `2024-04-01-preview`)                           |
-| `deployments`               | `string[]`        | No       | Deployment names for static mode                                      |
-| `management`                | `object`          | No       | Management API credentials                                            |
-| `management.tenantId`       | `string`          | Yes\*    | Azure AD tenant ID                                                    |
-| `management.clientId`       | `string`          | Yes\*    | Service Principal client ID                                           |
-| `management.clientSecret`   | `string`          | Yes\*    | Service Principal secret                                              |
-| `management.subscriptionId` | `string`          | Yes\*    | Azure subscription ID                                                 |
-| `management.resourceGroup`  | `string`          | Yes\*    | Resource group name                                                   |
+| Option                      | Type              | Required | Description                                                                                                                  |
+| --------------------------- | ----------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------- |
+| `resourceName`              | `string`          | Yes      | Azure OpenAI resource name                                                                                                   |
+| `apiKey`                    | `string`          | Yes\*    | API key from "Keys and Endpoint"                                                                                             |
+| `authentication`            | `object`          | No       | Microsoft Entra ID authentication                                                                                            |
+| `authentication.type`       | `"entraId"`       | Yes\*    | Authentication mode                                                                                                          |
+| `authentication.credential` | `TokenCredential` | Yes\*    | Azure SDK-compatible credential for `entraId` authentication mode                                                            |
+| `authentication.scope`      | `string`          | No       | Token scope (default: `https://cognitiveservices.azure.com/.default`)                                                        |
+| `apiVersion`                | `string`          | No       | API version (default: `2024-04-01-preview`, or `v1` when `useResponsesAPI` is `true` or `useDeploymentBasedUrls` is `false`) |
+| `useResponsesAPI`           | `boolean`         | No       | Resolve deployments through the Azure OpenAI Responses API (default: `false`)                                                |
+| `useDeploymentBasedUrls`    | `boolean`         | No       | Use Azure deployment-based URLs (default: `true`, or `false` when `useResponsesAPI` is `true`)                               |
+| `deployments`               | `string[]`        | No       | Deployment names for static mode                                                                                             |
+| `management`                | `object`          | No       | Management API credentials                                                                                                   |
+| `management.tenantId`       | `string`          | Yes\*    | Azure AD tenant ID                                                                                                           |
+| `management.clientId`       | `string`          | Yes\*    | Service Principal client ID                                                                                                  |
+| `management.clientSecret`   | `string`          | Yes\*    | Service Principal secret                                                                                                     |
+| `management.subscriptionId` | `string`          | Yes\*    | Azure subscription ID                                                                                                        |
+| `management.resourceGroup`  | `string`          | Yes\*    | Resource group name                                                                                                          |
 
 \* Provide either `apiKey` or `authentication.type: "entraId"`. Management fields are required if `management` is provided.

package/.docs/reference/cli/mastra.md

@@ -550,6 +550,470 @@ See the [Storage migration guide](https://mastra.ai/guides/migrations/upgrade-to
 
 It accepts [common flags](#common-flags).
 
+## `mastra api`
+
+Calls a Mastra runtime server with JSON input and JSON output. Use it for local development servers, deployed Mastra Platform projects, or self-hosted Mastra servers.
+
+```bash
+mastra api agent list --pretty
+mastra api agent run weather-agent '{"messages":"What is the weather in London?"}'
+mastra api tool execute get-weather '{"location":"San Francisco"}'
+```
+
+Use `mastra api <resource> <action> --help` to see examples for a command.
+
+### Output
+
+Success responses are written to `stdout` as JSON. Single-resource commands return:
+
+```json
+{ "data": {} }
+```
+
+List commands return a `data` array and pagination metadata:
+
+```json
+{ "data": [], "page": { "total": 0, "page": 0, "perPage": 0, "hasMore": false } }
+```
+
+Errors are written to `stderr` as JSON and return a non-zero exit code:
+
+```json
+{
+  "error": {
+    "code": "SERVER_UNREACHABLE",
+    "message": "Could not connect to target server",
+    "details": {}
+  }
+}
+```
+
+### Target resolution
+
+The command resolves the target server in this order:
+
+1. `--url <url>` for an explicit remote or self-hosted server.
+2. `http://localhost:4111` for a local `mastra dev` server.
+3. `.mastra-project.json` for a Mastra Platform project.
+
+Automatic platform auth is only used when the CLI resolves a Mastra Platform target from `.mastra-project.json`. Localhost targets and explicit `--url` targets do not receive automatic credentials. Headers passed with `--header` are sent to any target, including localhost.
+
+### Flags
+
+#### `--url <url>`
+
+Target a specific Mastra server URL.
+
+```bash
+mastra api --url https://example.com agent list
+```
+
+#### `--header <"Key: Value">`
+
+Send a custom HTTP header. Repeat the flag to send multiple headers.
+
+```bash
+mastra api --url https://example.com --header "Authorization: Bearer $TOKEN" agent list
+```
+
+#### `--timeout <ms>`
+
+Set the request timeout in milliseconds. Defaults to `30000`. Workflow run start and resume commands default to `120000`.
+
+#### `--pretty`
+
+Pretty-print JSON output. Defaults to `false`.
+
+#### `--schema`
+
+Print the CLI-oriented request schema for a command that accepts JSON input. The schema comes from the target server's route contracts and includes the command shape, positionals, examples, request schemas, and response shape.
+
+`--schema` is available on leaf commands that accept JSON input. It is not available as a top-level `mastra api` flag.
+
+```bash
+mastra api agent run --schema
+mastra api tool execute --schema
+```
+
+### Input model
+
+Commands that accept input take one inline JSON argument. Do not pass file paths or stdin.
+
+```bash
+mastra api workflow run start data-pipeline '{"inputData":{"source":"s3://bucket/data.csv"}}'
+```
+
+Use positional arguments for stable IDs and JSON for filters or payloads. For routes that require both query parameters and a request body, pass one JSON object. The CLI splits the input according to the server route schema.
+
+```bash
+mastra api thread create '{"agentId":"weather-agent","resourceId":"user_123","threadId":"thread_abc123","title":"Support conversation"}'
+```
+
+List commands accept `page` and `perPage` in the JSON input when the target route supports pagination:
+
+```bash
+mastra api score list '{"page":0,"perPage":50}'
+```
+
+### Get command-specific help
+
+Each `mastra api` leaf command includes command-specific examples in its help output. Use `--help` on the exact command you want to call:
+
+```bash
+mastra api agent run --help
+mastra api tool execute --help
+mastra api memory current update --help
+mastra api workflow run resume --help
+```
+
+Use `--schema` on commands that accept JSON input to inspect the request shape returned by the target server:
+
+```bash
+mastra api agent run --schema
+mastra api thread create --schema
+mastra api score create --schema
+```
+
+Some commands have important runtime requirements. For example, `mastra api memory current update` requires working memory to be enabled for the memory instance, and `mastra api workflow run resume` only works for suspended workflow runs.
+
+### Commands
+
+#### `mastra api agent list`
+
+Lists the agents registered on the target server. Pass optional JSON input for route-supported filters.
+
+```bash
+mastra api agent list [input]
+```
+
+#### `mastra api agent get`
+
+Gets metadata for one registered agent.
+
+```bash
+mastra api agent get <agentId>
+```
+
+#### `mastra api agent run`
+
+Runs an agent with JSON input. Use command help to see examples for text prompts, chat messages, and memory thread options.
+
+```bash
+mastra api agent run <agentId> <input>
+```
+
+#### `mastra api workflow list`
+
+Lists workflows registered on the target server. Pass optional JSON input for route-supported filters.
+
+```bash
+mastra api workflow list [input]
+```
+
+#### `mastra api workflow get`
+
+Gets metadata for one registered workflow.
+
+```bash
+mastra api workflow get <workflowId>
+```
+
+#### `mastra api workflow run start`
+
+Starts a workflow run with JSON input. Workflow start commands use a longer default timeout than most commands because runs can take longer to complete.
+
+```bash
+mastra api workflow run start <workflowId> <input>
+```
+
+#### `mastra api workflow run list`
+
+Lists runs for a workflow. Pass optional JSON input for route-supported filters or pagination.
+
+```bash
+mastra api workflow run list <workflowId> [input]
+```
+
+#### `mastra api workflow run get`
+
+Gets one workflow run by ID.
+
+```bash
+mastra api workflow run get <workflowId> <runId>
+```
+
+#### `mastra api workflow run resume`
+
+Resumes a suspended workflow run with JSON input. The run must be in a suspended state.
+
+```bash
+mastra api workflow run resume <workflowId> <runId> <input>
+```
+
+#### `mastra api workflow run cancel`
+
+Cancels a workflow run.
+
+```bash
+mastra api workflow run cancel <workflowId> <runId>
+```
+
+#### `mastra api tool list`
+
+Lists tools registered on the target server. Pass optional JSON input for route-supported filters.
+
+```bash
+mastra api tool list [input]
+```
+
+#### `mastra api tool get`
+
+Gets metadata and schemas for one tool.
+
+```bash
+mastra api tool get <toolId>
+```
+
+#### `mastra api tool execute`
+
+Executes a tool with JSON input. Raw tool input is wrapped as the route `data` field unless you pass an explicit `data` object.
+
+```bash
+mastra api tool execute <toolId> <input>
+```
+
+#### `mastra api mcp list`
+
+Lists Model Context Protocol (MCP) servers registered on the target server. Pass optional JSON input for route-supported filters.
+
+```bash
+mastra api mcp list [input]
+```
+
+#### `mastra api mcp get`
+
+Gets metadata for one MCP server.
+
+```bash
+mastra api mcp get <id>
+```
+
+#### `mastra api mcp tool list`
+
+Lists tools exposed by an MCP server. Pass optional JSON input for route-supported filters.
+
+```bash
+mastra api mcp tool list <serverId> [input]
+```
+
+#### `mastra api mcp tool get`
+
+Gets metadata and schemas for one MCP tool.
+
+```bash
+mastra api mcp tool get <serverId> <toolId>
+```
+
+#### `mastra api mcp tool execute`
+
+Executes an MCP tool with JSON input. Raw tool input is wrapped as the route `data` field unless you pass an explicit `data` object.
+
+```bash
+mastra api mcp tool execute <serverId> <toolId> <input>
+```
+
+#### `mastra api thread list`
+
+Lists memory threads. Pass optional JSON input for route-supported filters.
+
+```bash
+mastra api thread list [input]
+```
+
+#### `mastra api thread get`
+
+Gets one memory thread by ID.
+
+```bash
+mastra api thread get <threadId>
+```
+
+#### `mastra api thread create`
+
+Creates a memory thread. Pass one JSON input object; the CLI splits fields such as `agentId` into query parameters when required by the server route.
+
+```bash
+mastra api thread create <input>
+```
+
+#### `mastra api thread update`
+
+Updates a memory thread. Pass one JSON input object for fields such as `agentId`, `resourceId`, `title`, or `metadata`.
+
+```bash
+mastra api thread update <threadId> <input>
+```
+
+#### `mastra api thread delete`
+
+Deletes a memory thread. Pass JSON input for route-required query parameters such as `agentId` and `resourceId`.
+
+```bash
+mastra api thread delete <threadId> <input>
+```
+
+#### `mastra api thread messages`
+
+Lists messages for a memory thread. Pass optional JSON input for route-supported filters or pagination.
+
+```bash
+mastra api thread messages <threadId> [input]
+```
+
+#### `mastra api memory search`
+
+Searches long-term memory. Use `--help` or `--schema` to inspect required fields such as `agentId`, `resourceId`, and `searchQuery`.
+
+```bash
+mastra api memory search <input>
+```
+
+#### `mastra api memory current get`
+
+Reads current working memory for a thread.
+
+```bash
+mastra api memory current get <input>
+```
+
+#### `mastra api memory current update`
+
+Updates current working memory for a thread. Working memory must be enabled for the memory instance.
+
+```bash
+mastra api memory current update <input>
+```
+
+#### `mastra api memory status`
+
+Gets memory status for an agent and optional thread or resource context.
+
+```bash
+mastra api memory status <input>
+```
+
+#### `mastra api trace list`
+
+Lists observability traces. Pass optional JSON input for route-supported filters or pagination.
+
+```bash
+mastra api trace list [input]
+```
+
+#### `mastra api trace get`
+
+Gets one observability trace by ID.
+
+```bash
+mastra api trace get <traceId>
+```
+
+#### `mastra api log list`
+
+Lists observability logs. Pass optional JSON input for route-supported filters or pagination.
+
+```bash
+mastra api log list [input]
+```
+
+#### `mastra api score create`
+
+Creates an observability score. The input uses the server score body shape; inspect it with `--schema`.
+
+```bash
+mastra api score create <input>
+```
+
+#### `mastra api score list`
+
+Lists observability scores. Pass optional JSON input for filters such as run ID or pagination.
+
+```bash
+mastra api score list [input]
+```
+
+#### `mastra api score get`
+
+Gets one observability score by ID.
+
+```bash
+mastra api score get <scoreId>
+```
+
+#### `mastra api dataset list`
+
+Lists datasets. Pass optional JSON input for route-supported filters or pagination.
+
+```bash
+mastra api dataset list [input]
+```
+
+#### `mastra api dataset get`
+
+Gets one dataset by ID.
+
+```bash
+mastra api dataset get <datasetId>
+```
+
+#### `mastra api dataset create`
+
+Creates a dataset with JSON input.
+
+```bash
+mastra api dataset create <input>
+```
+
+#### `mastra api dataset items`
+
+Lists items in a dataset. Pass optional JSON input for route-supported filters or pagination.
+
+```bash
+mastra api dataset items <datasetId> [input]
+```
+
+#### `mastra api experiment list`
+
+Lists experiments for a dataset. Pass optional JSON input for route-supported filters or pagination.
+
+```bash
+mastra api experiment list <datasetId> [input]
+```
+
+#### `mastra api experiment get`
+
+Gets one experiment by ID.
+
+```bash
+mastra api experiment get <datasetId> <experimentId>
+```
+
+#### `mastra api experiment run`
+
+Starts an experiment for a dataset with JSON input.
+
+```bash
+mastra api experiment run <datasetId> <input>
+```
+
+#### `mastra api experiment results`
+
+Lists results for an experiment. Pass optional JSON input for route-supported filters or pagination.
+
+```bash
+mastra api experiment results <datasetId> <experimentId> [input]
+```
+
 ## Common flags
 
 ### `--dir`

package/.docs/reference/streaming/agents/stream.md

@@ -333,9 +333,9 @@ await agent.stream('message for agent', {
 })
 ```
 
-## OpenAI WebSocket transport
+## Responses WebSocket transport
 
-Opt into OpenAI Responses WebSocket streaming via `providerOptions.openai.transport`. This only applies to streaming calls and is currently supported for direct OpenAI models (for example, `openai/gpt-5.4`). If WebSocket streaming is unavailable, Mastra falls back to HTTP streaming. By default, Mastra closes the WebSocket when the stream finishes.
+Opt into Responses WebSocket streaming with provider options. This only applies to streaming calls and is supported for direct OpenAI models and Azure OpenAI Responses deployments. If WebSocket streaming is unavailable, Mastra falls back to HTTP streaming. By default, Mastra closes the WebSocket when the stream finishes.
 
 ```ts
 const stream = await agent.stream('Hello', {
@@ -351,6 +351,20 @@ const stream = await agent.stream('Hello', {
 })
 ```
 
+For Azure OpenAI, configure the gateway with `useResponsesAPI: true`, then use `providerOptions.azure.transport`.
+
+```ts
+const stream = await agent.stream('Hello', {
+  providerOptions: {
+    azure: {
+      transport: 'websocket',
+      store: false,
+      websocket: { closeOnFinish: true },
+    },
+  },
+})
+```
+
 To keep the connection open after the stream finishes, set `closeOnFinish: false` and close it manually.
 
 ```ts
@@ -367,6 +381,8 @@ const stream = await agent.stream('Hello', {
 stream.transport?.close()
 ```
 
+Responses WebSocket connections run one response at a time. Mastra rejects overlapping continuation requests that include `previous_response_id` on the same WebSocket transport. Wait for the active stream to finish before sending the next turn in the response chain.
+
 ## Related
 
 - [Generating responses](https://mastra.ai/docs/agents/overview)

package/CHANGELOG.md

@@ -1,5 +1,12 @@
 # @mastra/mcp-docs-server
 
+## 1.1.35-alpha.7
+
+### Patch Changes
+
+- Updated dependencies [[`087e413`](https://github.com/mastra-ai/mastra/commit/087e4133e5d6efa36619e9556c16750e4179c047), [`087e413`](https://github.com/mastra-ai/mastra/commit/087e4133e5d6efa36619e9556c16750e4179c047), [`087e413`](https://github.com/mastra-ai/mastra/commit/087e4133e5d6efa36619e9556c16750e4179c047)]:
+  - @mastra/core@1.33.0-alpha.3
+
 ## 1.1.35-alpha.6
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mastra/mcp-docs-server",
-  "version": "1.1.35-alpha.6",
+  "version": "1.1.35-alpha.8",
   "description": "MCP server for accessing Mastra.ai documentation, changelogs, and news.",
   "type": "module",
   "main": "dist/index.js",
@@ -29,8 +29,8 @@
     "jsdom": "^26.1.0",
     "local-pkg": "^1.1.2",
     "zod": "^4.3.6",
-    "@mastra/mcp": "^1.7.0",
-    "@mastra/core": "1.33.0-alpha.2"
+    "@mastra/core": "1.33.0-alpha.3",
+    "@mastra/mcp": "^1.7.0"
   },
   "devDependencies": {
     "@hono/node-server": "^1.19.11",
@@ -47,8 +47,8 @@
     "typescript": "^6.0.3",
     "vitest": "4.1.5",
     "@internal/lint": "0.0.92",
-    "@mastra/core": "1.33.0-alpha.2",
-    "@internal/types-builder": "0.0.67"
+    "@internal/types-builder": "0.0.67",
+    "@mastra/core": "1.33.0-alpha.3"
   },
   "homepage": "https://mastra.ai",
   "repository": {