@mastra/mcp-docs-server 1.2.11 → 1.2.12-alpha.0

package/.docs/reference/workspace/platform-filesystem.md

@@ -112,7 +112,7 @@ await fs.writeFile('/analyses/repo.md', 'x') // throws WorkspaceReadOnlyError
 
 ### Appending files
 
-`appendFile` is a read-modify-write and is not atomic. Concurrent appends to the same path can overwrite each other. For concurrent writers, use `writeFile` with distinct keys.
+`appendFile` is a read-modify-write and isn't atomic. Concurrent appends to the same path can overwrite each other. For concurrent writers, use `writeFile` with distinct keys.
 
 ## Constructor parameters
 
@@ -150,7 +150,7 @@ await fs.writeFile('/analyses/repo.md', 'x') // throws WorkspaceReadOnlyError
 
 Filesystem-specific errors match the standard workspace error types:
 
-- `FileNotFoundError`: The path does not exist. Thrown by `readFile`, `stat`, and `deleteFile` (unless `force: true` is set).
+- `FileNotFoundError`: The path doesn't exist. Thrown by `readFile`, `stat`, and `deleteFile` (unless `force: true` is set).
 - `FileExistsError`: `writeFile` was called with `overwrite: false` and the destination already exists.
 - `WorkspaceReadOnlyError`: A mutating call was made on a read-only filesystem.
 
@@ -173,7 +173,7 @@ try {
 }
 ```
 
-`code` and `proxyMessage` are `undefined` when the response body is not JSON, for example an HTML 502 from a load balancer.
+`code` and `proxyMessage` are `undefined` when the response body isn't JSON, for example an HTML 502 from a load balancer.
 
 ## Related
 

package/.docs/reference/workspace/platform-sandbox.md

@@ -114,7 +114,7 @@ await sandbox.start()
 const result = await sandbox.executeCommand('cat', ['/workspace/state.json'])
 ```
 
-When `sandboxId` is set, `environmentId` is not required because the sandbox already exists.
+When `sandboxId` is set, `environmentId` isn't required because the sandbox already exists.
 
 ### Executing commands
 
@@ -190,7 +190,7 @@ try {
 }
 ```
 
-`code` and `proxyMessage` are `undefined` when the response body is not JSON, for example an HTML 502 from a load balancer.
+`code` and `proxyMessage` are `undefined` when the response body isn't JSON, for example an HTML 502 from a load balancer.
 
 ## Related
 

package/.docs/reference/workspace/process-manager.md

@@ -123,7 +123,7 @@ Information about a tracked process, returned by `list()`.
 
 Handle to a spawned background process. Provides methods to read output, send stdin, wait for completion, and kill the process.
 
-You don't create `ProcessHandle` instances directly — they're returned by `spawn()` and `get()`.
+You don't create `ProcessHandle` instances directly. They're returned by `spawn()` and `get()`.
 
 ### Usage example
 

package/.docs/reference/workspace/railway-sandbox.md

@@ -103,7 +103,7 @@ The default `ISOLATED` mode allows outbound internet access only, with no privat
 
 ### Custom base image (templates)
 
-Pre-install packages and run setup steps so every sandbox starts ready. Pass a builder callback over the Railway template builder — the template is built once on the first `start()`:
+Pre-install packages and run setup steps so every sandbox starts ready. Pass a builder callback over the Railway template builder: the template is built once on the first `start()`:
 
 ```typescript
 const workspace = new Workspace({
@@ -117,7 +117,7 @@ You can also pass a pre-built `SandboxTemplate` to reuse it across sandboxes wit
 
 ### Forking a running sandbox
 
-Clone a running sandbox's filesystem into a new, independent sandbox — a fresh boot, not live processes. The returned `RailwaySandbox` is already started:
+Clone a running sandbox's filesystem into a new, independent sandbox: a fresh boot, not live processes. The returned `RailwaySandbox` is already started:
 
 ```typescript
 const child = await sandbox.fork({ idleTimeoutMinutes: 15 })
@@ -130,7 +130,7 @@ The forked sandbox inherits the parent's credentials and defaults unless overrid
 
 ### Checkpoint recovery
 
-Set `checkpointName` to preserve a sandbox filesystem across Railway sandbox replacement. On `start()`, `RailwaySandbox` first tries to create the sandbox from the named checkpoint. If the checkpoint is missing, it creates a sandbox from the configured template or default image, then captures the checkpoint.
+Set `checkpointName` to preserve a sandbox filesystem across Railway sandbox replacement. On `start()`, `RailwaySandbox` first tries to create the sandbox from the checkpoint. If the checkpoint is missing, it creates a sandbox from the configured template or default image, then captures the checkpoint.
 
 ```typescript
 const sandbox = new RailwaySandbox({
@@ -141,7 +141,7 @@ const sandbox = new RailwaySandbox({
 
 `RailwaySandbox` refreshes the checkpoint shortly before the idle timeout. Recovery restores the latest successful checkpoint. It doesn't restore running processes or filesystem writes made after the last checkpoint.
 
-Use one stable checkpoint name for each independent filesystem. Do not share a checkpoint name across unrelated sessions or projects.
+Use one stable checkpoint name for each independent filesystem. Don't share a checkpoint name across unrelated sessions or projects.
 
 ### Derived sandbox checkpoints
 

package/.docs/reference/workspace/s3-filesystem.md

@@ -154,7 +154,7 @@ const filesystem = new S3Filesystem({
 })
 ```
 
-Tigris uses virtual-hosted-style addressing, so `forcePathStyle` must be set to `false` (the default is `true` when a custom endpoint is provided). Create credentials from the [Tigris Dashboard](https://console.tigris.dev/) — access keys are prefixed `tid_` and secrets `tsec_`.
+Tigris uses virtual-hosted-style addressing, so `forcePathStyle` must be set to `false` (the default is `true` when a custom endpoint is provided). Create credentials from the [Tigris Dashboard](https://console.tigris.dev/). Access keys are prefixed `tid_` and secrets `tsec_`.
 
 ## Constructor parameters
 

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

@@ -14,7 +14,7 @@ The `WorkspaceSandbox` interface defines how workspaces execute commands and man
 
 ### `start()`
 
-Start the sandbox. Called automatically by `workspace.init()` or on first `executeCommand()` call.
+Starts the sandbox and is called automatically by `workspace.init()` or the first `executeCommand()` call.
 
 ```typescript
 await sandbox.start()

package/.docs/reference/workspace/vercel-sandbox.md

@@ -199,7 +199,7 @@ See the [`SandboxProcessManager` reference](https://mastra.ai/reference/workspac
 
 - Up to 32 vCPUs, with 2048 MB of memory per vCPU.
 - Up to 15 exposed ports.
-- The filesystem is ephemeral — persisted only within the session and lost when the sandbox stops.
+- The filesystem is ephemeral. It's persisted only within the session and lost when the sandbox stops.
 - Maximum runtime is plan-dependent (45 minutes on Hobby, up to 24 hours on Pro and Enterprise), with a default of 5 minutes.
 
 See the [Vercel Sandbox documentation](https://vercel.com/docs/vercel-sandbox) for current limits and pricing.

package/.docs/reference/workspace/workspace-class.md

@@ -104,7 +104,7 @@ See [workspace overview](https://mastra.ai/docs/workspace/overview) for more exa
 
 ### Tool name remapping
 
-Rename workspace tools by setting the `name` property on individual tool configs. The config key remains the original constant — only the name exposed to the agent changes.
+Rename workspace tools by setting the `name` property on individual tool configs. The config key remains the original constant: only the name exposed to the agent changes.
 
 ```typescript
 import { Workspace } from '@mastra/core/workspace'
@@ -148,7 +148,7 @@ const workspace = new Workspace({
 
 **afterToolCall** (`(context: WorkspaceToolAfterHookContext) => void | Promise<void>`): Runs after a workspace tool executes. Receives { toolName, workspaceToolName, input, context, output, error }. output is undefined when the tool throws, and error is set instead.
 
-If the owning agent also defines [tool hooks](https://mastra.ai/reference/agents/agent), workspace hooks run inside the agent hook wrapper: agent `beforeToolCall` runs first, then workspace `beforeToolCall`, then the tool, then workspace `afterToolCall`, then agent `afterToolCall`.
+If the owning agent also defines [tool hooks](https://mastra.ai/reference/agents/agent), workspace hooks run inside the agent hook wrapper. The order is agent `beforeToolCall` → workspace `beforeToolCall` → tool → workspace `afterToolCall` → agent `afterToolCall`.
 
 ## Properties
 
@@ -240,7 +240,7 @@ const info = await workspace.getInfo()
 // { id, name, status, createdAt, lastAccessedAt, filesystem?, sandbox? }
 ```
 
-Pass `resolveDynamicProviders: false` to report resolver-backed providers as dynamic without invoking their resolver.
+Pass `resolveDynamicProviders: false` to report resolver-backed providers as runtime-defined without invoking their resolver.
 
 ```typescript
 const info = await workspace.getInfo({ resolveDynamicProviders: false })
@@ -276,7 +276,7 @@ const instructions = workspace.getInstructions({ requestContext })
 
 #### `getInstructionsAsync(opts?)`
 
-Returns combined workspace instructions. Use this when the workspace uses resolver-backed providers. A dynamic filesystem is resolved per request; a dynamic sandbox contributes stable placeholder text unless `instructions.dynamicSandbox` is set to `'resolve'`.
+Returns combined workspace instructions. Use this when the workspace uses resolver-backed providers. A runtime-defined filesystem is resolved per request; a runtime-defined sandbox contributes stable placeholder text unless `instructions.dynamicSandbox` is set to `'resolve'`.
 
 ```typescript
 const instructions = await workspace.getInstructionsAsync({ requestContext })
@@ -302,7 +302,7 @@ const config = workspace.getToolsConfig()
 
 #### `setToolsConfig(config?)`
 
-Replace the per-tool configuration at runtime. This performs a full replacement — it doesn't merge with the previous config. Pass `undefined` to reset to defaults. Changes take effect on the next agent interaction (the next `createWorkspaceTools()` call).
+Replace the per-tool configuration at runtime. This performs a full replacement: it doesn't merge with the previous config. Pass `undefined` to reset to defaults. Changes take effect on the next agent interaction (the next `createWorkspaceTools()` call).
 
 ```typescript
 import { WORKSPACE_TOOLS } from '@mastra/core/workspace'
@@ -337,7 +337,7 @@ if (workspace.hasFilesystemConfig()) {
 
 #### `resolveFilesystem({ requestContext })`
 
-Resolve the filesystem for a given request context. When a resolver function is configured, calls it with the provided `requestContext`. When a static filesystem is configured, returns it directly. Returns `undefined` if no filesystem is configured.
+Resolve the filesystem for a request context. When a resolver function is configured, calls it with the provided `requestContext`. When a static filesystem is configured, returns it directly. Returns `undefined` if no filesystem is configured.
 
 ```typescript
 import { RequestContext } from '@mastra/core/request-context'
@@ -368,7 +368,7 @@ if (workspace.hasSandboxConfig()) {
 
 #### `resolveSandbox({ requestContext })`
 
-Resolve the sandbox for a given request context. When a resolver function is configured, calls it with the provided `requestContext`. When a static sandbox is configured, returns it directly. Returns `undefined` if no sandbox is configured.
+Resolve the sandbox for a request context. When a resolver function is configured, calls it with the provided `requestContext`. When a static sandbox is configured, returns it directly. Returns `undefined` if no sandbox is configured.
 
 ```typescript
 import { RequestContext } from '@mastra/core/request-context'
@@ -421,7 +421,7 @@ Added when a filesystem is configured:
 | `mastra_workspace_mkdir`      | Create a directory. Creates parent directories automatically if they don't exist.                                                                                                                                                |
 | `mastra_workspace_grep`       | Search file contents using regex patterns. Supports glob filtering, context lines, and case-insensitive search.                                                                                                                  |
 
-With a static filesystem, write tools (`write_file`, `edit_file`, `delete`, `mkdir`) are excluded when the filesystem is in read-only mode. With a [dynamic filesystem](https://mastra.ai/docs/workspace/filesystem), write tools are always included and read-only is enforced at runtime.
+With a static filesystem, write tools (`write_file`, `edit_file`, `delete`, `mkdir`) are excluded when the filesystem is in read-only mode. With a [runtime-defined filesystem](https://mastra.ai/docs/workspace/filesystem), write tools are always included and read-only is enforced at runtime.
 
 The `read_file` tool accepts `mediaTypes` and `maxMediaBytes` options to control which mime types are surfaced to the model as native media parts and how large those files can be:
 
@@ -453,7 +453,7 @@ Added when a sandbox is configured:
 | `mastra_workspace_get_process_output` | Get stdout, stderr, and status of a background process by PID. Accepts `tail` to limit output lines and `wait: true` to block until exit. Only available when the sandbox has a process manager. |
 | `mastra_workspace_kill_process`       | Kill a background process by PID. Returns the last 50 lines of output. Only available when the sandbox has a process manager.                                                                    |
 
-With a static sandbox, capability checks (`executeCommand`, `processes`) decide which tool variants are exposed. With a [dynamic sandbox](https://mastra.ai/docs/workspace/sandbox), all sandbox tools are registered and the runtime throws a clear error if the resolved sandbox doesn't implement a requested capability.
+With a static sandbox, capability checks (`executeCommand`, `processes`) decide which tool variants are exposed. With a [runtime-defined sandbox](https://mastra.ai/docs/workspace/sandbox), all sandbox tools are registered and the runtime throws a clear error if the resolved sandbox doesn't implement a requested capability.
 
 The `execute_command` tool accepts a `backgroundProcesses` option for lifecycle callbacks on background processes:
 
@@ -490,4 +490,4 @@ Added when skills are configured:
 | `skill_search` | Search across skill content. Accepts an optional list of skill names to filter and a `topK` parameter.    |
 | `skill_read`   | Read a specific file (reference, script, or asset) from a skill directory.                                |
 
-When multiple skills share the same name, `list()` returns all of them. `get()` with a name applies tie-breaking (local > managed > external). If two skills share the same name _and_ source type, `get()` throws an error. Pass a skill's full path to `get()` to bypass tie-breaking. See [Same-named skills](https://mastra.ai/docs/workspace/skills) for details.
+When multiple skills share the same name, `list()` returns all of them. `get()` with a name applies tie-breaking (local > managed > external). If two skills share the same name and source type, `get()` throws an error. Pass a skill's full path to `get()` to bypass tie-breaking. See [Skills with the same name](https://mastra.ai/docs/workspace/skills) for details.

package/CHANGELOG.md

@@ -1,5 +1,12 @@
 # @mastra/mcp-docs-server
 
+## 1.2.12-alpha.0
+
+### Patch Changes
+
+- Updated dependencies [[`3f472b4`](https://github.com/mastra-ai/mastra/commit/3f472b468892a1ff14ccb43cc0343b86f7d8fd7d), [`35b929b`](https://github.com/mastra-ai/mastra/commit/35b929b7abc3d20d85c7985880960ac2d04a6c86), [`9b3626a`](https://github.com/mastra-ai/mastra/commit/9b3626aeb1d16fcd34b0a8e94c114ddb80a3b240)]:
+  - @mastra/core@1.55.0-alpha.0
+
 ## 1.2.11
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mastra/mcp-docs-server",
-  "version": "1.2.11",
+  "version": "1.2.12-alpha.0",
   "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.54.0",
-    "@mastra/mcp": "^1.15.0"
+    "@mastra/mcp": "^1.15.0",
+    "@mastra/core": "1.55.0-alpha.0"
   },
   "devDependencies": {
     "@hono/node-server": "^1.19.14",
@@ -46,8 +46,8 @@
     "typescript": "^6.0.3",
     "vitest": "4.1.10",
     "@internal/lint": "0.0.118",
-    "@internal/types-builder": "0.0.93",
-    "@mastra/core": "1.54.0"
+    "@mastra/core": "1.55.0-alpha.0",
+    "@internal/types-builder": "0.0.93"
   },
   "homepage": "https://mastra.ai",
   "repository": {