@mastra/mcp-docs-server 1.0.0-beta.5 → 1.0.0-beta.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mastra/mcp-docs-server",
-  "version": "1.0.0-beta.5",
+  "version": "1.0.0-beta.7",
   "description": "MCP server for accessing Mastra.ai documentation, changelogs, and news.",
   "type": "module",
   "main": "dist/index.js",
@@ -28,8 +28,8 @@
     "@modelcontextprotocol/sdk": "^1.17.5",
     "jsdom": "^26.1.0",
     "zod": "^3.25.76",
-    "@mastra/core": "1.0.0-beta.5",
-    "@mastra/mcp": "^1.0.0-beta.3"
+    "@mastra/core": "1.0.0-beta.7",
+    "@mastra/mcp": "^1.0.0-beta.5"
   },
   "devDependencies": {
     "@hono/node-server": "^1.19.6",
@@ -46,7 +46,7 @@
     "typescript": "^5.8.3",
     "vitest": "4.0.12",
     "@internal/lint": "0.0.53",
-    "@mastra/core": "1.0.0-beta.5"
+    "@mastra/core": "1.0.0-beta.7"
   },
   "homepage": "https://mastra.ai",
   "repository": {

package/.docs/raw/agents/human-in-the-loop-with-tools.mdx

@@ -1,91 +0,0 @@
----
-title: "Human in the Loop with Tools | Agents"
-description: Learn how to require approvals and suspend tool execution while keeping humans in control of agent workflows.
----
-
-# Human in the Loop with Tools
-
-Sometimes agents need human oversight before they can run potentially sensitive tools or long-running workflows. Mastra lets you pause tool execution to wait for approval, decline a tool call entirely, or suspend a tool mid-flight until the required data is available.
-
-## Tool approvals
-
-### Enforcing approval on every tool
-
-Pass `requireToolApproval: true` when calling `stream` (or `generate`) to automatically pause execution whenever the agent tries to invoke a tool. The stream closes until you explicitly approve or decline the tool call using the original run’s `runId`.
-
-```typescript {2,6} title="Require approval before executing any tool" showLineNumbers copy
-const stream = await myAgent.stream("Find the user with name - John Smith", {
-  requireToolApproval: true,
-});
-
-const approvedToolCallStream = await myAgent.approveToolCall({ runId: stream.runId });
-const declinedToolCallStream = await myAgent.declineToolCall({ runId: stream.runId });
-```
-
-### Requiring approval per tool
-
-You can also enforce approval on specific tools. Set `requireApproval: true` when creating a tool so the agent pauses only when it tries to invoke that tool.
-
-```typescript {8} title="Mark a tool as approval-only" showLineNumbers copy
-const findUserTool = createTool({
-  id: "Find user tool",
-  description: "Returns the name and email for a matching user",
-  inputSchema: z.object({
-    name: z.string(),
-  }),
-  execute: async (inputData) => {
-    return mockFindUser(inputData);
-  },
-  requireApproval: true,
-});
-```
-
-When the agent reaches this tool, it emits a tool-call event you can approve or decline with the same `approveToolCall` or `declineToolCall` helpers.
-
-## Tool suspension
-
-Sometimes a tool can’t finish immediately—maybe it’s waiting for external confirmation or extra input. You can suspend and later resume execution using `workflow.suspend`, `resumeStream`, and optional schemas that define what data is required at each step.
-
-```typescript {10,14} title="Suspend and resume a tool" showLineNumbers copy
-const findUserTool = createTool({
-  id: "Find user tool",
-  description: "Returns the name and email for a matching user",
-  inputSchema: z.object({
-    name: z.string(),
-  }),
-  suspendSchema: z.object({
-    message: z.string(),
-  }),
-  resumeSchema: z.object({
-    name: z.string(),
-  }),
-  execute: async (inputData, { agent }) => {
-    if (!agent.resumeData) {
-      return agent.suspend({ message: "Please provide the name of the user" });
-    }
-
-    return {
-      name: agent?.resumeData?.name,
-      email: "test@test.com",
-    };
-  },
-});
-```
-
-To continue execution, call `resumeStream` with the run’s `runId` and the `resumeData` that satisfies the `resumeSchema`. The workflow resumes from the suspension point and the tool completes with the new data.
-When using `suspend` directly in the tool, you don't need to add `requireToolApproval: true` to the agent `stream`/`generate` call, nor `requireApproval: true` to the tool creation.
-
-```typescript {1} title="Resume a suspended tool call" showLineNumbers copy
-const resumedStream = await myAgent.resumeStream(
-  { name: "John Smith" },
-  { runId: stream.runId }
-);
-```
-
-## Related
-
-- [Using Tools](./using-tools)
-- [Agent Overview](./overview)
-- [Tools Overview](../mcp/overview)
-- [Agent Memory](./agent-memory)
-- [Request Context](/docs/v1/server-db/request-context)

package/.docs/raw/reference/streaming/workflows/observeStreamVNext.mdx

@@ -1,47 +0,0 @@
----
-title: "Reference: Run.observeStreamVNext() (Experimental) | Streaming"
-description: Documentation for the `Run.observeStreamVNext()` method in workflows, which enables reopening the stream of an already active workflow run.
----
-
-# Run.observeStreamVNext() (Experimental)
-
-The `.observeStreamVNext()` method opens a new `ReadableStream` to a workflow run that is currently running, allowing you to observe the stream of events if the original stream is no longer available.
-
-## Usage example
-
-```typescript showLineNumbers copy
-const run = await workflow.createRun();
-
-run.streamVNext({
-  inputData: {
-    value: "initial data",
-  },
-});
-
-const stream = await run.observeStreamVNext();
-
-for await (const chunk of stream) {
-  console.log(chunk);
-}
-```
-
-## Returns
-
-`ReadableStream<ChunkType>`
-
-## Stream Events
-
-The stream emits various event types during workflow execution. Each event has a `type` field and a `payload` containing relevant data:
-
-- **`workflow-start`**: Workflow execution begins
-- **`workflow-step-start`**: A step begins execution
-- **`workflow-step-output`**: Custom output from a step
-- **`workflow-step-result`**: A step completes with results
-- **`workflow-finish`**: Workflow execution completes with usage statistics
-
-## Related
-
-- [Workflows overview](/docs/v1/workflows/overview#running-workflows)
-- [Workflow.createRun()](/reference/v1/workflows/workflow-methods/create-run)
-- [Run.streamVNext()](./streamVNext)
-- [Run.resumeStreamVNext()](./resumeStreamVNext)

package/.docs/raw/reference/streaming/workflows/streamVNext.mdx

@@ -1,153 +0,0 @@
----
-title: "Reference: Run.streamVNext() (Experimental) | Streaming"
-description: Documentation for the `Run.streamVNext()` method in workflows, which enables real-time streaming of responses.
----
-
-# Run.streamVNext() (Experimental)
-
-:::caution Experimental Feature
-This is an experimental API that may change in future versions. The `streamVNext()` method will eventually replace the current `stream()` method. Use with caution in production environments.
-:::
-
-The `.streamVNext()` method enables real-time streaming of responses from a workflow. This enhanced streaming capability will eventually replace the current `stream()` method.
-
-## Usage example
-
-```typescript showLineNumbers copy
-const run = await workflow.createRun();
-
-const stream = run.streamVNext({
-  inputData: {
-    value: "initial data",
-  },
-});
-```
-
-## Parameters
-
-<PropertiesTable
-  content={[
-    {
-      name: "inputData",
-      type: "z.infer<TInput>",
-      description: "Input data that matches the workflow's input schema",
-      isOptional: true,
-    },
-    {
-      name: "requestContext",
-      type: "RequestContext",
-      description: "Request Context data to use during workflow execution",
-      isOptional: true,
-    },
-    {
-      name: "tracingContext",
-      type: "TracingContext",
-      isOptional: true,
-      description:
-        "Tracing context for creating child spans and adding metadata.",
-      properties: [
-        {
-          parameters: [
-            {
-              name: "currentSpan",
-              type: "Span",
-              isOptional: true,
-              description:
-                "Current span for creating child spans and adding metadata.",
-            },
-          ],
-        },
-      ],
-    },
-    {
-      name: "tracingOptions",
-      type: "TracingOptions",
-      isOptional: true,
-      description: "Options for Tracing configuration.",
-      properties: [
-        {
-          parameters: [
-            {
-              name: "metadata",
-              type: "Record<string, any>",
-              isOptional: true,
-              description: "Metadata to add to the root trace span.",
-            },
-          ],
-        },
-      ],
-    },
-    {
-      name: "closeOnSuspend",
-      type: "boolean",
-      description:
-        "Whether to close the stream when the workflow is suspended, or to keep the stream open until the workflow is finished (by success or error). Default value is true.",
-      isOptional: true,
-    },
-  ]}
-/>
-
-## Returns
-
-<PropertiesTable
-  content={[
-    {
-      name: "stream",
-      type: "MastraWorkflowStream<ChunkType>",
-      description:
-        "A custom stream that extends ReadableStream<ChunkType> with additional workflow-specific properties",
-    },
-    {
-      name: "stream.status",
-      type: "Promise<RunStatus>",
-      description: "A promise that resolves to the current workflow run status",
-    },
-    {
-      name: "stream.result",
-      type: "Promise<WorkflowResult<TState, TOutput, TSteps>>",
-      description: "A promise that resolves to the final workflow result",
-    },
-    {
-      name: "stream.usage",
-      type: "Promise<{ inputTokens: number; outputTokens: number; totalTokens: number, reasoningTokens?: number, cacheInputTokens?: number }>",
-      description: "A promise that resolves to token usage statistics",
-    },
-    {
-      name: "stream.traceId",
-      type: "string",
-      isOptional: true,
-      description:
-        "The trace ID associated with this execution when Tracing is enabled.",
-    },
-  ]}
-/>
-
-## Extended usage example
-
-```typescript showLineNumbers copy
-const run = await workflow.createRun();
-
-const stream = run.streamVNext({
-  inputData: {
-    value: "initial data",
-  },
-});
-
-const result = await stream.result;
-```
-
-## Stream Events
-
-The stream emits various event types during workflow execution. Each event has a `type` field and a `payload` containing relevant data:
-
-- **`workflow-start`**: Workflow execution begins
-- **`workflow-step-start`**: A step begins execution
-- **`workflow-step-output`**: Custom output from a step
-- **`workflow-step-result`**: A step completes with results
-- **`workflow-finish`**: Workflow execution completes with usage statistics
-
-## Related
-
-- [Workflows overview](/docs/v1/workflows/overview#running-workflows)
-- [Workflow.createRun()](/reference/v1/workflows/workflow-methods/create-run)
-- [Run.resumeStreamVNext()](./resumeStreamVNext)