@mastra/mcp-docs-server 1.1.8 → 1.1.9-alpha.1

package/.docs/docs/workflows/time-travel.md

@@ -1,6 +1,6 @@
-# Time Travel
+# Time travel
 
-Time travel allows you to re-execute a workflow starting from any specific step, using either stored snapshot data or custom context you provide. This is useful for debugging failed workflows, testing individual steps with different inputs, or recovering from errors without re-running the entire workflow. You can also use time travel to execute a workflow that has not been run yet, starting from any specific step.
+Time travel allows you to re-execute a workflow starting from any specific step, using either stored snapshot data or custom context you provide. This is useful for debugging failed workflows, testing individual steps with different inputs, or recovering from errors without re-running the entire workflow. You can also use time travel to execute a workflow that hasn't been run yet, starting from any specific step.
 
 ## How time travel works
 
@@ -193,7 +193,7 @@ Time travel throws errors in specific situations:
 
 ### Running workflow
 
-You cannot time travel to a workflow that is currently running:
+You can't time travel to a workflow that's currently running:
 
 ```typescript
 try {

package/.docs/docs/workflows/workflow-state.md

@@ -1,4 +1,4 @@
-# Workflow State
+# Workflow state
 
 Workflow state lets you share values across steps without passing them through every step's inputSchema and outputSchema. This is useful for tracking progress, accumulating results, or sharing configuration across the entire workflow.
 

package/.docs/docs/workspace/filesystem.md

@@ -101,9 +101,9 @@ const workspace = new Workspace({
 })
 ```
 
-When read-only, write tools (`write_file`, `edit_file`, `delete`, `mkdir`) are not added to the agent's toolset. The agent can still read and list files.
+When read-only, write tools (`write_file`, `edit_file`, `delete`, `mkdir`) aren't added to the agent's toolset. The agent can still read and list files.
 
-## Mounts and CompositeFilesystem
+## Mounts and `CompositeFilesystem`
 
 When you use the `mounts` option on a workspace, Mastra creates a `CompositeFilesystem` that routes file operations to the correct provider based on path prefix.
 
@@ -140,7 +140,7 @@ With this configuration:
 
 All file paths must start with a mount prefix. Operations on paths that don't match any mount will fail. Listing the root directory (`/`) returns virtual directory entries for each mount point.
 
-Mount paths cannot be nested — for example, you cannot mount at both `/data` and `/data/sub`.
+Mount paths can't be nested — for example, you can't mount at both `/data` and `/data/sub`.
 
 ### `filesystem` vs `mounts`
 

package/.docs/docs/workspace/overview.md

@@ -7,7 +7,7 @@ A Mastra workspace gives agents a persistent environment for storing files and e
 A workspace supports the following features:
 
 - **[Filesystem](https://mastra.ai/docs/workspace/filesystem)**: File storage (read, write, list, delete, copy, move, grep)
-- **[Sandbox](https://mastra.ai/docs/workspace/sandbox)**: Command execution (shell commands)
+- **[Sandbox](https://mastra.ai/docs/workspace/sandbox)**: Command execution (shell commands) and background processes
 - **[Search](https://mastra.ai/docs/workspace/search)**: BM25, vector, or hybrid search over indexed content
 - **[Skills](https://mastra.ai/docs/workspace/skills)**: Reusable instructions for agents
 
@@ -117,7 +117,7 @@ Under the hood, `mounts` creates a [CompositeFilesystem](https://mastra.ai/docs/
 
 You can mount multiple providers at different paths. Each mount path must be unique and non-overlapping.
 
-> **Note:** `filesystem` and `mounts` are mutually exclusive — you cannot use both in the same workspace. Use `filesystem` for a single provider without a sandbox, or `mounts` when you need to combine cloud storage with a sandbox.
+> **Note:** `filesystem` and `mounts` are mutually exclusive — you can't use both in the same workspace. Use `filesystem` for a single provider without a sandbox, or `mounts` when you need to combine cloud storage with a sandbox.
 
 ### Filesystem only
 
@@ -190,11 +190,56 @@ const workspace = new Workspace({
 
 ### Tool options
 
-| Option                   | Type      | Description                                                                 |
-| ------------------------ | --------- | --------------------------------------------------------------------------- |
-| `enabled`                | `boolean` | Whether the tool is available (default: `true`)                             |
-| `requireApproval`        | `boolean` | Whether the tool requires user approval before execution (default: `false`) |
-| `requireReadBeforeWrite` | `boolean` | For write tools: require reading the file first (default: `false`)          |
+| Option                   | Type      | Description                                                                                                |
+| ------------------------ | --------- | ---------------------------------------------------------------------------------------------------------- |
+| `enabled`                | `boolean` | Whether the tool is available (default: `true`)                                                            |
+| `requireApproval`        | `boolean` | Whether the tool requires user approval before execution (default: `false`)                                |
+| `requireReadBeforeWrite` | `boolean` | For write tools: require reading the file first (default: `false`)                                         |
+| `name`                   | `string`  | Custom name for the tool. Replaces the default `mastra_workspace_*` name.                                  |
+| `maxOutputTokens`        | `number`  | Maximum tokens for tool output (default: `2000`). Output exceeding this limit is truncated using tiktoken. |
+
+### Tool name remapping
+
+Rename workspace tools to match the conventions your agent expects. The config key remains the original `WORKSPACE_TOOLS` constant — only the exposed name changes.
+
+```typescript
+import { Workspace, LocalFilesystem, LocalSandbox, WORKSPACE_TOOLS } from '@mastra/core/workspace'
+
+const workspace = new Workspace({
+  filesystem: new LocalFilesystem({ basePath: './workspace' }),
+  sandbox: new LocalSandbox({ workingDirectory: './workspace' }),
+  tools: {
+    [WORKSPACE_TOOLS.FILESYSTEM.READ_FILE]: { name: 'view' },
+    [WORKSPACE_TOOLS.FILESYSTEM.GREP]: { name: 'search_content' },
+    [WORKSPACE_TOOLS.FILESYSTEM.LIST_FILES]: { name: 'find_files' },
+    [WORKSPACE_TOOLS.SANDBOX.EXECUTE_COMMAND]: { name: 'execute_command' },
+  },
+})
+```
+
+The agent sees `view`, `search_content`, `find_files`, and `execute_command` instead of the default `mastra_workspace_*` names. Tool names must be unique — duplicate names or conflicts with other default names throw an error.
+
+### Output truncation
+
+Workspace tools automatically truncate large outputs to avoid exceeding LLM context limits. Two layers of truncation apply:
+
+1. **Line-based tail**: Command output is limited to the last 200 lines by default (configurable per-command via the `tail` parameter)
+2. **Token-based limit**: Tool output is capped at 2000 tokens by default
+
+Set `maxOutputTokens` per tool to adjust the token limit:
+
+```typescript
+const workspace = new Workspace({
+  // ...
+  tools: {
+    [WORKSPACE_TOOLS.SANDBOX.EXECUTE_COMMAND]: {
+      maxOutputTokens: 5000,
+    },
+  },
+})
+```
+
+ANSI escape codes (colors, cursor sequences) are automatically stripped from command output before it reaches the model.
 
 ### Read-before-write
 
@@ -220,7 +265,7 @@ const workspace = new Workspace({
 await workspace.init()
 ```
 
-### What init() does
+### What `init()` does
 
 Initialization runs setup logic for each configured provider:
 

package/.docs/docs/workspace/sandbox.md

@@ -6,21 +6,19 @@ Sandbox providers give agents the ability to execute shell commands. When you co
 
 A sandbox provider executes commands in a controlled environment:
 
-- **Command execution** - Run shell commands with arguments
-- **Working directory** - Commands run from a specific directory
-- **Environment variables** - Control what variables are available
-- **Timeouts** - Prevent long-running commands from hanging
-- **Isolation** - Optional OS-level sandboxing for security
-
-When you assign a workspace with a sandbox to an agent, Mastra automatically includes the `execute_command` tool in the agent's toolset.
+- **Command execution**: Run shell commands with arguments
+- **Background processes**: Spawn long-running processes like dev servers and watchers
+- **Working directory**: Commands run from a specific directory
+- **Environment variables**: Control what variables are available
+- **Timeouts**: Prevent long-running commands from hanging
+- **Isolation**: Optional OS-level sandboxing for security
 
 ## Supported providers
 
-Available providers:
-
-- [`LocalSandbox`](https://mastra.ai/reference/workspace/local-sandbox) - Executes commands on the local machine
-- [`DaytonaSandbox`](https://mastra.ai/reference/workspace/daytona-sandbox) - Executes commands in isolated Daytona cloud sandboxes
-- [`E2BSandbox`](https://mastra.ai/reference/workspace/e2b-sandbox) - Executes commands in isolated E2B cloud sandboxes
+- [`LocalSandbox`](https://mastra.ai/reference/workspace/local-sandbox): Executes commands on the local machine
+- [`BlaxelSandbox`](https://mastra.ai/reference/workspace/blaxel-sandbox): Executes commands in isolated Blaxel cloud sandboxes
+- [`DaytonaSandbox`](https://mastra.ai/reference/workspace/daytona-sandbox): Executes commands in isolated Daytona cloud sandboxes
+- [`E2BSandbox`](https://mastra.ai/reference/workspace/e2b-sandbox): Executes commands in isolated E2B cloud sandboxes
 
 ## Basic usage
 
@@ -54,10 +52,71 @@ See [`LocalSandbox` reference](https://mastra.ai/reference/workspace/local-sandb
 
 ## Agent tools
 
-When you configure a sandbox on a workspace, agents receive the `execute_command` tool for running shell commands. See [workspace class reference](https://mastra.ai/reference/workspace/workspace-class) for details.
+When you configure a sandbox on a workspace, agents receive the `execute_command` tool for running shell commands.
+
+If your sandbox provider supports running processes in the background, the `execute_command` tool also accepts `background: true` for starting long-running processes, and two additional tools are registered:
+
+| Tool                 | Description                                                                                                                                |
+| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
+| `execute_command`    | Run a shell command. Returns stdout, stderr, and exit code. Supports `background: true` to spawn a long-running process and return a PID.  |
+| `get_process_output` | Get stdout, stderr, and status of a background process by PID. Supports `tail` to limit output lines and `wait: true` to block until exit. |
+| `kill_process`       | Stop a background process by PID. Returns recent output.                                                                                   |
+
+These tools are registered automatically. See [Workspace class reference](https://mastra.ai/reference/workspace/workspace-class) for the full tool name list.
+
+## Background process callbacks
+
+When agents start background processes through the `execute_command` tool, you can receive lifecycle callbacks for stdout, stderr, and process exit. Configure these through the `backgroundProcesses` option on the `execute_command` tool:
+
+```typescript
+import { Workspace, LocalSandbox, WORKSPACE_TOOLS } from '@mastra/core/workspace'
+
+const workspace = new Workspace({
+  sandbox: new LocalSandbox({ workingDirectory: './workspace' }),
+  tools: {
+    [WORKSPACE_TOOLS.SANDBOX.EXECUTE_COMMAND]: {
+      backgroundProcesses: {
+        onStdout: (data, { pid }) => console.log(`[${pid}] ${data}`),
+        onStderr: (data, { pid }) => console.error(`[${pid}] ${data}`),
+        onExit: ({ pid, exitCode }) => console.log(`Process ${pid} exited: ${exitCode}`),
+      },
+    },
+  },
+})
+```
+
+These callbacks fire for all background processes started by the agent through the `execute_command` tool.
+
+### Abort signal
+
+By default, background processes inherit the agent's abort signal and are killed when the agent disconnects. Control this behavior with the `abortSignal` option:
+
+- **`undefined`** (default): Uses the agent's abort signal
+- **`AbortSignal`**: Uses a custom signal
+- **`null` or `false`**: Disables abort — processes persist after agent shutdown
+
+```typescript
+import { Workspace, LocalSandbox, WORKSPACE_TOOLS } from '@mastra/core/workspace'
+
+const workspace = new Workspace({
+  sandbox: new LocalSandbox({ workingDirectory: './workspace' }),
+  tools: {
+    [WORKSPACE_TOOLS.SANDBOX.EXECUTE_COMMAND]: {
+      backgroundProcesses: {
+        abortSignal: null, // Processes survive agent disconnection
+      },
+    },
+  },
+})
+```
+
+Use `null` or `false` for cloud sandboxes (for example, E2B or Daytona) where processes should outlive the agent.
+
+> **Note:** For the full `SandboxProcessManager` API (spawning processes programmatically, reading output, sending stdin), see the [`SandboxProcessManager` reference](https://mastra.ai/reference/workspace/process-manager).
 
 ## Related
 
+- [`SandboxProcessManager` reference](https://mastra.ai/reference/workspace/process-manager)
 - [`LocalSandbox` reference](https://mastra.ai/reference/workspace/local-sandbox)
 - [`DaytonaSandbox` reference](https://mastra.ai/reference/workspace/daytona-sandbox)
 - [`E2BSandbox` reference](https://mastra.ai/reference/workspace/e2b-sandbox)

package/.docs/docs/workspace/search.md

@@ -1,4 +1,4 @@
-# Search and Indexing
+# Search and indexing
 
 **Added in:** `@mastra/core@1.1.0`
 

package/.docs/docs/workspace/skills.md

@@ -1,4 +1,4 @@
-# Workspace Skills
+# Workspace skills
 
 **Added in:** `@mastra/core@1.1.0`
 
@@ -24,7 +24,7 @@ A skill is a folder containing:
 
 When skills are configured on a workspace, agents can discover and activate them during conversations.
 
-## SKILL.md format
+## `SKILL.md` format
 
 Follow the official [skill specification](https://agentskills.io/specification) when creating your skill. Here is an example `SKILL.md` for a code review skill:
 
@@ -123,7 +123,7 @@ The agent has three skill tools:
 
 - **`skill`** — Loads a skill's full instructions and returns them in the tool result. The agent calls this whenever it needs a skill's guidance.
 - **`skill_read`** — Reads a file from a skill's `references/`, `scripts/`, or `assets/` directory.
-- **`skill_search`** — Searches across all skill content. Uses BM25 or vector search when configured, otherwise falls back to simple text matching.
+- **`skill_search`** — Searches across all skill content. Uses BM25 or vector search when configured, otherwise falls back to basic text matching.
 
 This design is stateless — there is no activation state to track. If the skill instructions leave the conversation context (due to context window limits or compaction), the agent can call `skill` again to reload them.
 
@@ -162,7 +162,7 @@ const workspace = new Workspace({
 - **`blobStore`** (`BlobStore`) — A content-addressable blob store instance that holds the actual file contents referenced by hash.
 - **`versionCreatedAt`** (`Date`) — The timestamp when this skill version was published. Used as the modification time for all files in the version.
 
-When `skillSource` is provided, it is used instead of the workspace filesystem for skill discovery.
+When `skillSource` is provided, it's used instead of the workspace filesystem for skill discovery.
 
 ## Related
 

package/.docs/guides/build-your-ui/ai-sdk-ui.md

@@ -6,7 +6,7 @@
 
 > **Tip:** Want to see more examples? Visit Mastra's [**UI Dojo**](https://ui-dojo.mastra.ai/) or the [Next.js quickstart guide](https://mastra.ai/guides/getting-started/next-js).
 
-## Getting Started
+## Getting started
 
 Use Mastra and AI SDK UI together by installing the `@mastra/ai-sdk` package. `@mastra/ai-sdk` provides custom API routes and utilities for streaming Mastra agents in AI SDK-compatible formats. This includes chat, workflow, and network route handlers, along with utilities and exported types for UI integrations.
 
@@ -40,7 +40,7 @@ bun add @mastra/ai-sdk@latest @ai-sdk/react ai
 
 You're now ready to follow the integration guides and recipes below!
 
-## Integration Guides
+## Integration guides
 
 Typically, you'll set up API routes that stream Mastra content in AI SDK-compatible format, and then use those routes in AI SDK UI hooks like `useChat()`. Below you'll find two main approaches to achieve this:
 

package/.docs/guides/build-your-ui/assistant-ui.md

@@ -6,7 +6,7 @@
 
 > **Tip:** Visit Mastra's [**"UI Dojo"**](https://ui-dojo.mastra.ai/) to see real-world examples of Assistant UI integrated with Mastra.
 
-## Integration Guide
+## Integration guide
 
 Run Mastra as a standalone server and connect your Next.js frontend (with Assistant UI) to its API endpoints.
 

package/.docs/guides/build-your-ui/copilotkit.md

@@ -8,7 +8,7 @@ Visit the [CopilotKit documentation](https://docs.copilotkit.ai/) to learn more
 
 > **Tip:** Visit Mastra's [**"UI Dojo"**](https://ui-dojo.mastra.ai/) to see real-world examples of CopilotKit integrated with Mastra.
 
-## Integration Guide
+## Integration guide
 
 Run Mastra as a standalone server and connect your Next.js frontend (with CopilotKit) to its API endpoints.
 
@@ -274,7 +274,7 @@ Congratulations! You have successfully integrated Mastra with CopilotKit using a
 
 ## Deployment
 
-When deploying your Mastra server with CopilotKit, you must exclude `@copilotkit/runtime` from the bundle. This package contains dependencies that are not compatible with bundling and will cause 500 errors if included.
+When deploying your Mastra server with CopilotKit, you must exclude `@copilotkit/runtime` from the bundle. This package contains dependencies that aren't compatible with bundling and will cause 500 errors if included.
 
 > **Note:** This issue doesn't occur during development with `mastra dev` since it doesn't require bundling. However, anyone running `mastra build` for deployment will encounter this issue.
 

package/.docs/guides/deployment/digital-ocean.md

@@ -10,7 +10,7 @@ You'll need a [Mastra application](https://mastra.ai/guides/getting-started/quic
 
 The **App Platform** uses an ephemeral filesystem, so any storage you configure (including observability storage) must be hosted externally. If you're using [LibSQLStore](https://mastra.ai/reference/storage/libsql) with a file URL, switch to a remotely hosted database.
 
-## App Platform
+## App platform
 
 After setting up your project, push it to your remote Git provider of choice (e.g. GitHub).
 

package/.docs/guides/deployment/inngest.md

@@ -105,7 +105,7 @@ const incrementStep = createStep({
 
 ### Creating the workflow
 
-Compose the steps into a workflow using the `dountil` loop pattern. The `createWorkflow()` function creates a function on Inngest server that is invocable.
+Compose the steps into a workflow using the `dountil` loop pattern. The `createWorkflow()` function creates a function on Inngest server that's invocable.
 
 ```ts
 // workflow that is registered as a function on inngest server
@@ -169,7 +169,7 @@ export const mastra = new Mastra({
 
 3. Open the Inngest Dashboard at <http://localhost:8288> and go to the **Apps** section in the sidebar to verify your Mastra workflow is registered
 
-4. Invoke the workflow by going to **Functions**, selecting your workflow, and clicking **Invoke** with the following input:
+4. Invoke the workflow by going to **Functions**, selecting your workflow, and selecting **Invoke** with the following input:
 
    ```json
    {
@@ -227,9 +227,9 @@ Before you begin, make sure you have:
    vercel --prod
    ```
 
-5. Sync with the [Inngest dashboard](https://app.inngest.com/env/production/apps) by clicking **Sync new app with Vercel** and following the instructions
+5. Sync with the [Inngest dashboard](https://app.inngest.com/env/production/apps) by selecting **Sync new app with Vercel** and following the instructions
 
-6. Invoke the workflow by going to **Functions**, selecting `workflow.increment-workflow`, clicking **All actions** > **Invoke**, and providing the following input:
+6. Invoke the workflow by going to **Functions**, selecting `workflow.increment-workflow`, selecting **All actions** > **Invoke**, and providing the following input:
 
    ```json
    {

package/.docs/guides/getting-started/astro.md

@@ -123,7 +123,7 @@ This creates a `src/mastra` folder with an example weather agent and the followi
 
 You'll call `weather-agent.ts` from your Astro routes in the next steps.
 
-## Install AI SDK UI & AI Elements
+## Install AI SDK UI & AI elements
 
 Install AI SDK UI along with the Mastra adapter:
 

package/.docs/guides/getting-started/electron.md

@@ -109,7 +109,7 @@ This creates a `src/mastra` folder with an example weather agent and the followi
 
 You'll call `weather-agent.ts` from your chat UI in the next steps.
 
-## Install AI SDK UI & AI Elements
+## Install AI SDK UI & AI elements
 
 Install AI SDK UI along with the Mastra adapter:
 

package/.docs/guides/getting-started/next-js.md

@@ -95,7 +95,7 @@ You'll call `weather-agent.ts` from your Next.js routes in the next steps.
 >
 > Relative paths resolve based on each process's working directory, which differs between `next dev` and `mastra dev`.
 
-## Install AI SDK UI & AI Elements
+## Install AI SDK UI & AI elements
 
 Install AI SDK UI along with the Mastra adapter:
 

package/.docs/guides/getting-started/vite-react.md

@@ -166,7 +166,7 @@ This creates a `src/mastra` folder with an example weather agent and the followi
 
 You'll call `weather-agent.ts` from your chat UI in the next steps.
 
-## Install AI SDK UI & AI Elements
+## Install AI SDK UI & AI elements
 
 Install AI SDK UI along with the Mastra adapter:
 

package/.docs/guides/guide/ai-recruiter.md

@@ -1,4 +1,4 @@
-# Building an AI Recruiter
+# Building an AI recruiter
 
 In this guide, you'll learn how Mastra helps you build workflows with LLMs.
 
@@ -10,7 +10,7 @@ You'll create a workflow that gathers information from a candidate's resume, the
 - An API key from a supported [Model Provider](https://mastra.ai/models)
 - An existing Mastra project (Follow the [installation guide](https://mastra.ai/guides/getting-started/quickstart) to set up a new project)
 
-## Building the Workflow
+## Building the workflow
 
 Set up the Workflow, define steps to extract and classify candidate data, and then ask suitable follow-up questions.
 
@@ -176,7 +176,7 @@ Set up the Workflow, define steps to extract and classify candidate data, and th
    })
    ```
 
-## Testing the Workflow
+## Testing the workflow
 
 You can test your workflow inside [Studio](https://mastra.ai/docs/getting-started/studio) by starting the development server:
 
@@ -223,4 +223,4 @@ Now, run the workflow and get output in your terminal:
 npx tsx src/test-workflow.ts
 ```
 
-You've just built a workflow to parse a resume and decide which question to ask based on the candidate's technical abilities. Congrats and happy hacking!
+You've built a workflow to parse a resume and decide which question to ask based on the candidate's technical abilities. Congrats and happy hacking!

package/.docs/guides/guide/chef-michel.md

@@ -1,4 +1,4 @@
-# Building an AI Chef Assistant
+# How to build an AI chef assistant
 
 In this guide, you'll create a "Chef Assistant" agent that helps users cook meals with available ingredients.
 
@@ -12,7 +12,7 @@ You'll learn how to create the agent and register it with Mastra. Next, you'll i
 - An API key from a supported [Model Provider](https://mastra.ai/models)
 - An existing Mastra project (Follow the [installation guide](https://mastra.ai/guides/getting-started/quickstart) to set up a new project)
 
-## Creating the Agent
+## Create the agent
 
 To create an agent in Mastra use the `Agent` class to define it and then register it with Mastra.
 
@@ -42,7 +42,7 @@ To create an agent in Mastra use the `Agent` class to define it and then registe
    })
    ```
 
-## Interacting with the Agent
+## Interact with the agent
 
 Depending on your requirements you can interact and get responses from the agent in different formats. In the following steps you'll learn how to generate, stream, and get structured output.
 
@@ -169,7 +169,7 @@ Depending on your requirements you can interact and get responses from the agent
    }
    ```
 
-## Running the Agent Server
+## Run the agent server
 
 Learn how to interact with your agent through Mastra's API.
 

package/.docs/guides/guide/code-review-bot.md

@@ -1,4 +1,4 @@
-# Building a Code Review Bot
+# Building a code review bot
 
 In this guide, you'll build a code review bot that automatically reviews pull requests using workspace skills. The bot loads coding standards from skill files and provides structured feedback. You'll learn how to create a workspace with a skills directory, define an [Agent Skill](https://agentskills.io) with review instructions and reference files, and connect it to an agent that performs automated reviews.
 
@@ -75,7 +75,7 @@ Inside `workspace/skills/code-standards`, create a `references` folder to hold r
 - Files: `kebab-case.ts`
 - Booleans: Start with `is`, `has`, `should`
 
-## Code Organization
+## Code organization
 
 ```typescript
 // 1. Imports
@@ -96,7 +96,7 @@ function doSomething() {}
 export { doSomething }
 ```
 
-## Error Handling
+## Error handling
 
 Always handle errors explicitly - never silently catch.
 

package/.docs/guides/guide/dev-assistant.md

@@ -1,4 +1,4 @@
-# Building a Dev Assistant
+# Building a dev assistant
 
 In this guide, you'll build a complete development assistant that combines all workspace features:
 
@@ -123,7 +123,7 @@ description: Project coding standards and testing guidelines
 
 # Coding Standards
 
-## Code Quality
+## Code quality
 
 - Functions under 50 lines
 - Use descriptive variable names
@@ -135,7 +135,7 @@ description: Project coding standards and testing guidelines
 - Use AAA pattern: Arrange, Act, Assert
 - Cover happy paths and edge cases
 
-## Before Committing
+## Before committing
 
 1. Write implementation
 2. Write comprehensive tests
@@ -148,7 +148,7 @@ Create a reference file at `workspace/skills/coding-standards/references/testing
 ````markdown
 # Testing Guide
 
-## AAA Pattern
+## AAA pattern
 
 ```typescript
 it('descriptive test name', () => {
@@ -163,7 +163,7 @@ it('descriptive test name', () => {
 })
 ```
 
-## What to Test
+## What to test
 
 - Happy paths (normal inputs)
 - Edge cases (empty, null, boundary values)

package/.docs/guides/guide/docs-manager.md

@@ -1,4 +1,4 @@
-# Building a Docs Manager
+# Building a docs manager
 
 In this guide, you'll build a documentation manager that maintains your project's docs. It creates well-structured markdown files, keeps documentation organized, and prevents accidental overwrites. You'll learn how to set up a workspace filesystem, create an agent with document management instructions, and use it to generate and update documentation through conversational prompts.
 
@@ -65,7 +65,7 @@ Quick start guide for the project.
 npm install example-package
 ```
 
-## Quick Example
+## Quick example
 
 ```typescript
 import { Example } from 'example-package'
@@ -193,7 +193,7 @@ export const authConfig = {
 }
 ```
 
-## Basic Example
+## Basic example
 
 ```typescript
 import { createAuth } from '@example/auth'

package/.docs/guides/guide/github-actions-pr-description.md

@@ -1,4 +1,4 @@
-# Building a PR Description Agent for GitHub Actions
+# Building a PR description agent for GitHub Actions
 
 In this guide, you'll build a [GitHub Action](https://docs.github.com/en/actions) that uses a Mastra agent to read pull request diffs, generate multi-language summaries, and write them directly to the PR description in the GitHub UI. The action runs whenever a pull request is created or updated and regenerates the description as the diff changes.
 
@@ -10,7 +10,7 @@ The setup consists of three parts:
 - A GitHub Actions workflow that triggers on pull requests
 - A Node.js script that connects the workflow to the agent
 
-The finished action writes a description with summaries in English, Spanish, and Japanese, each marked with a flag emoji for easy scanning. For example:
+The finished action writes a description with summaries in English, Spanish, and Japanese, each marked with a flag emoji for quick scanning. For example:
 
 ```text
 🇬🇧 English
@@ -49,7 +49,7 @@ The workflow references this secret as `${{ secrets.OPENAI_API_KEY }}` and makes
 
 The PR description agent is responsible for turning a git diff into a clear, reviewer-friendly pull request description.
 
-This agent receives the raw diff from a pull request. It generates descriptions in the configured languages and formats the output using emoji flags so each language section is easy to scan in the PR.
+This agent receives the raw diff from a pull request. It generates descriptions in the configured languages and formats the output using emoji flags so each language section is quick to scan in the PR.
 
 ```ts
 import { Agent } from '@mastra/core/agent'
@@ -117,7 +117,7 @@ Before deploying the workflow, you can test the agent in [Mastra Studio](https:/
 
 The agent will return a formatted description with sections in English, Spanish, and Japanese.
 
-## GitHub Actions
+## GitHub actions
 
 GitHub Actions run your workflows in short-lived environments on GitHub's infrastructure. Each run starts with a clean virtual machine, checks out your code, installs dependencies, runs your workflow steps, and then shuts down. Nothing persists between runs unless you explicitly save it as an artifact or cache.
 

package/.docs/guides/guide/notes-mcp-server.md

@@ -1,4 +1,4 @@
-# Building a Notes MCP Server
+# Building a notes MCP server
 
 In this guide, you'll learn how to build a complete MCP (Model Context Protocol) server from scratch. This server will manage a collection of markdown notes and has these features:
 
@@ -99,7 +99,7 @@ Before you can create an MCP server you first need to install additional depende
            └── tools/
    ```
 
-## Creating the MCP Server
+## Creating the MCP server
 
 Let's add the MCP server!
 
@@ -401,7 +401,7 @@ Let's add the MCP server!
    })
    ```
 
-## Run the Server
+## Run the server
 
 Great, you've authored your first MCP server! Now you can try it out by starting the Mastra dev server and opening [Studio](https://mastra.ai/docs/getting-started/studio):
 
@@ -413,4 +413,4 @@ Open [`http://localhost:4111`](http://localhost:4111) in your browser. In the le
 
 You'll now be presented with instructions on how to add the MCP server to your IDE. You're able to use this MCP server with any MCP Client. On the right side under **Available Tools** you can also select the **write** tool.
 
-Inside the **write** tool, try it out by providing `test` as a name and `this is a test` for the markdown content. After clicking on **Submit** you'll have a new `test.md` file inside `notes`.
+Inside the **write** tool, try it out by providing `test` as a name and `this is a test` for the markdown content. After selecting **Submit** you'll have a new `test.md` file inside `notes`.