@mastra/mcp-docs-server 0.13.38 → 0.13.39-alpha.0

package/.docs/raw/reference/storage/mssql.mdx

@@ -31,7 +31,7 @@ const storage = new MSSQLStore({
       name: "connectionString",
       type: "string",
       description:
-        "MSSQL connection string (e.g., mssql://user:pass@host:1433/dbname)",
+        "MSSQL connection string (e.g., Server=localhost,1433;Database=mydb;User Id=sa;Password=password;Encrypt=true;TrustServerCertificate=true)",
       isOptional: false,
     },
     {
@@ -53,12 +53,12 @@ import { MSSQLStore } from "@mastra/mssql";
 
 // Using a connection string only
 const store1 = new MSSQLStore({
-  connectionString: "mssql://user:password@localhost:1433/mydb",
+  connectionString: "Server=localhost,1433;Database=mydb;User Id=sa;Password=password;Encrypt=true;TrustServerCertificate=true",
 });
 
 // Using a connection string with a custom schema name
 const store2 = new MSSQLStore({
-  connectionString: "mssql://user:password@localhost:1433/mydb",
+  connectionString: "Server=localhost,1433;Database=mydb;User Id=sa;Password=password;Encrypt=true;TrustServerCertificate=true",
   schemaName: "custom_schema", // optional
 });
 

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

@@ -46,7 +46,7 @@ if (result!.status === "suspended") {
     {
       name: "runtimeContext",
       type: "RuntimeContext",
-      description: "Runtime context data to use during workflow execution",
+      description: "Request Context data to use during workflow execution",
       isOptional: true,
     },
     {

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

@@ -32,7 +32,7 @@ const { stream } = await run.stream({
     {
       name: "runtimeContext",
       type: "RuntimeContext",
-      description: "Runtime context data to use during workflow execution",
+      description: "Request Context data to use during workflow execution",
       isOptional: true,
     },
     {

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

@@ -36,7 +36,7 @@ const stream = run.streamVNext({
     {
       name: "runtimeContext",
       type: "RuntimeContext",
-      description: "Runtime context data to use during workflow execution",
+      description: "Request Context data to use during workflow execution",
       isOptional: true,
     },
     {

package/.docs/raw/reference/tools/mcp-client.mdx

@@ -129,23 +129,23 @@ Each server in the `servers` map is configured using the `MastraMCPServerDefinit
 
 ## Methods
 
-### getTools()
+### listTools()
 
 Retrieves all tools from all configured servers, with tool names namespaced by their server name (in the format `serverName_toolName`) to prevent conflicts.
 Intended to be passed onto an Agent definition.
 
 ```ts
-new Agent({ tools: await mcp.getTools() });
+new Agent({ tools: await mcp.listTools() });
 ```
 
-### getToolsets()
+### listToolsets()
 
 Returns an object mapping namespaced tool names (in the format `serverName.toolName`) to their tool implementations.
 Intended to be passed dynamically into the generate or stream method.
 
 ```typescript
 const res = await agent.stream(prompt, {
-  toolsets: await mcp.getToolsets(),
+  toolsets: await mcp.listToolsets(),
 });
 ```
 
@@ -627,7 +627,7 @@ await mcpClient.elicitation.onRequest("interactiveServer", async (request) => {
 
 ### Static Tool Configuration
 
-For tools where you have a single connection to the MCP server for you entire app, use `getTools()` and pass the tools to your agent:
+For tools where you have a single connection to the MCP server for you entire app, use `listTools()` and pass the tools to your agent:
 
 ```typescript
 import { MCPClient } from "@mastra/mcp";
@@ -658,7 +658,7 @@ const agent = new Agent({
   name: "Multi-tool Agent",
   instructions: "You have access to multiple tool servers.",
   model: openai("gpt-4"),
-  tools: await mcp.getTools(),
+  tools: await mcp.listTools(),
 });
 
 // Example of using resource methods
@@ -702,7 +702,7 @@ checkWeatherPrompt();
 
 ### Dynamic toolsets
 
-When you need a new MCP connection for each user, use `getToolsets()` and add the tools when calling stream or generate:
+When you need a new MCP connection for each user, use `listToolsets()` and add the tools when calling stream or generate:
 
 ```typescript
 import { Agent } from "@mastra/core/agent";
@@ -742,7 +742,7 @@ const mcp = new MCPClient({
 const response = await agent.stream(
   "How is AAPL doing and what is the weather?",
   {
-    toolsets: await mcp.getToolsets(),
+    toolsets: await mcp.listToolsets(),
   },
 );
 ```

package/.docs/raw/reference/voice/google-gemini-live.mdx

@@ -220,7 +220,7 @@ Establishes a connection to the Gemini Live API. Must be called before using spe
     {
       name: "runtimeContext",
       type: "object",
-      description: "Optional runtime context for the connection.",
+      description: "Optional request context for the connection.",
       isOptional: true,
     },
     {

package/.docs/raw/reference/workflows/step.mdx

@@ -140,7 +140,7 @@ const step1 = createStep({
       type: "RuntimeContext",
       isOptional: true,
       description:
-        "Runtime context for dependency injection and contextual information.",
+        "Runtime Context for dependency injection and contextual information.",
     },
     {
       name: "runCount",

package/.docs/raw/reference/workflows/workflow-methods/foreach.mdx

@@ -57,4 +57,4 @@ workflow.foreach(step1, { concurrency: 2 });
 
 ## Related
 
-- [Repeating with foreach](/docs/workflows/control-flow#repeating-with-foreach)
+- [Repeating with foreach](/docs/workflows/control-flow#looping-with-foreach)

package/.docs/raw/reference/workflows/workflow-methods/map.mdx

@@ -39,6 +39,76 @@ workflow.map(async ({ inputData }) => `${inputData.value} - map`
   ]}
 />
 
-## Related
+## Using `inputData`
 
-- [Input data mapping](/docs/workflows/input-data-mapping)
+Use `inputData` to access the full output of the previous step.
+
+```typescript {3} filename="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
+  .then(step1)
+  .map(({ inputData }) => {
+    console.log(inputData);
+  })
+```
+
+## Using `getStepResult()`
+
+Use `getStepResult()` to access the full output of a specific step by referencing the step's instance.
+
+```typescript {3} filename="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
+  .then(step1)
+  .map(async ({ getStepResult }) => {
+    console.log(getStepResult(step1));
+  })
+```
+
+## Using `getInitData()`
+
+Use `getInitData()` to access the initial input data provided to the workflow.
+
+```typescript {3} filename="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
+  .then(step1)
+  .map(async ({ getInitData }) => {
+      console.log(getInitData());
+  })
+```
+
+## Using `mapVariable()`
+
+The object form of `.map()` provides an alternative declarative syntax for mapping fields. Instead of writing a function, you define an object where each key is a new field name and each value uses `mapVariable()` to extract data from previous steps or workflow input.
+Import `mapVariable()` from the workflows module:
+
+```typescript filename="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
+import { mapVariable } from "@mastra/core/workflows";
+```
+### Extracting fields from step outputs
+
+Use `mapVariable()` with `step` to extract a specific field from a step's output and map it to a new field name. The `path` parameter specifies which field to extract.
+In this example, the `value` field from `step1`'s output is extracted and mapped to a new field called `details`:
+
+```typescript {3-6} filename="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
+  .then(step1)
+  .map({
+    details: mapVariable({
+      step: step1,
+      path: "value"
+    })
+  })
+```
+
+### Extracting fields from workflow input
+
+Use `mapVariable()` with `initData` to extract a specific field from the workflow's initial input data. This is useful when you need to pass the original workflow input to a later step.
+In this example, the `value` field from the workflow's input is extracted and mapped to a field called `details`:
+
+```typescript {6-9} filename="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
+export const testWorkflow = createWorkflow({...});
+
+testWorkflow
+  .then(step1)
+  .map({
+    details: mapVariable({
+      initData: testWorkflow,
+      path: "value"
+    })
+  })
+```

package/.docs/raw/reference/workflows/workflow.mdx

@@ -115,20 +115,6 @@ A workflow's `status` indicates its current execution state. The possible values
   ]}
 />
 
-## Extended usage example
-
-```typescript title="src/test-run.ts" showLineNumbers copy
-import { mastra } from "./mastra";
-
-const run = await mastra.getWorkflow("workflow").createRunAsync();
-
-const result = await run.start({...});
-
-if (result.status === "suspended") {
-  const resumedResult = await run.resume({...});
-}
-```
-
 ## Related
 
 - [Step Class](./step)

package/.docs/raw/scorers/overview.mdx

@@ -110,7 +110,7 @@ To score traces, you must first configure observability in your Mastra instance
 
 :::
 
-### Scoring traces with the playground
+### Scoring traces with Studio
 
 To score traces, you first need to register your scorers with your Mastra instance:
 
@@ -124,16 +124,16 @@ const mastra = new Mastra({
 });
 ```
 
-Once registered, you can score traces interactively within the Mastra playground under the Observability section. This provides a user-friendly interface for running scorers against historical traces.
+Once registered, you can score traces interactively within Studio under the Observability section. This provides a user-friendly interface for running scorers against historical traces.
 
 ## Testing scorers locally
 
-Mastra provides a CLI command `mastra dev` to test your scorers. The playground includes a scorers section where you can run individual scorers against test inputs and view detailed results.
+Mastra provides a CLI command `mastra dev` to test your scorers. Studio includes a scorers section where you can run individual scorers against test inputs and view detailed results.
 
-For more details, see the [Local Dev Playground](/docs/getting-started/studio) docs.
+For more details, see [Studio](/docs/getting-started/studio) docs.
 
 ## Next steps
 
 - Learn how to create your own scorers in the [Creating Custom Scorers](/docs/scorers/custom-scorers) guide
 - Explore built-in scorers in the [Off-the-shelf Scorers](/docs/scorers/off-the-shelf-scorers) section
-- Test scorers with the [Local Dev Playground](/docs/getting-started/studio)
+- Test scorers with [Studio](/docs/getting-started/studio)

package/.docs/raw/server-db/middleware.mdx

@@ -121,15 +121,15 @@ registerApiRoute("/my-custom-route", {
 ### Special Mastra headers
 
 When integrating with Mastra Cloud or custom clients the following headers can
-be inspected by middleware to tailor behaviour:
+be inspected by middleware to tailor behavior:
 
 ```typescript copy
 {
   handler: async (c, next) => {
     const isFromMastraCloud = c.req.header('x-mastra-cloud') === 'true';
     const clientType = c.req.header('x-mastra-client-type');
-    const isDevPlayground =
-      c.req.header('x-mastra-dev-playground') === 'true';
+    const isStudio =
+      c.req.header('x-studio') === 'true';
 
     if (isFromMastraCloud) {
       // Special handling
@@ -141,7 +141,7 @@ be inspected by middleware to tailor behaviour:
 
 - `x-mastra-cloud`: request originates from Mastra Cloud
 - `x-mastra-client-type`: identifies the client SDK, e.g. `js` or `python`
-- `x-mastra-dev-playground`: request triggered from a local playground
+- `x-studio`: request triggered from Studio
 
 ### Setting `runtimeContext`
 

package/.docs/raw/tools-mcp/overview.mdx

@@ -83,6 +83,6 @@ export const testTool = createTool({
 
 > See [Runtime Context](/docs/server-db/runtime-context) for more information.
 
-## Testing with Mastra Playground
+## Testing with Studio
 
-Use the Mastra [Playground](/docs/getting-started/studio) to test tools with different inputs, inspect execution results, and verify tool behavior.
+Use [Studio](/docs/getting-started/studio) to test tools with different inputs, inspect execution results, and verify tool behavior.

package/.docs/raw/workflows/agents-and-tools.mdx

@@ -39,8 +39,6 @@ const step1 = createStep({
 });
 ```
 
-> See [Calling Agents](/examples/agents/calling-agents) for more examples.
-
 ### Agents as steps
 
 Compose an agent as a step using `createStep()` when you don't need to modify the agent call. Use `.map()` to transform the previous step's output into a `prompt` the agent can use.
@@ -66,7 +64,7 @@ export const testWorkflow = createWorkflow({
   .commit();
 ```
 
-> See [Input Data Mapping](./input-data-mapping) for more information.
+> See [.map()](/reference/workflows/workflow-methods/map) for more information.
 
 Mastra agents use a default schema that expects a `prompt` string as input and returns a `text` string as output:
 
@@ -111,8 +109,6 @@ const step2 = createStep({
 });
 ```
 
-> See [Calling Tools](/examples/workflows_legacy/using-a-tool-as-a-step) for more examples.
-
 ### Tools as steps
 
 Compose a tool as a step using `createStep()` when the previous step's output matches the tool's input context. You can use `.map()` to transform the previous step's output if they don't.
@@ -138,7 +134,7 @@ export const testWorkflow = createWorkflow({
   .commit();
 ```
 
-> See [Input Data Mapping](./input-data-mapping) for more information.
+> See [.map()](/reference/workflows/workflow-methods/map) for more information.
 
 ## Related