@mastra/mcp-docs-server 1.2.7-alpha.1 → 1.2.7-alpha.10

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

@@ -4,9 +4,7 @@
 
 **Added in:** `@mastra/core@1.1.0`
 
-Stores files in a directory on the local filesystem.
-
-> **Info:** For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
+Stores files in a directory on the local filesystem. For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
 
 ## Usage
 

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

@@ -4,9 +4,7 @@
 
 **Added in:** `@mastra/core@1.1.0`
 
-Executes commands on the local system.
-
-> **Info:** For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
+Executes commands on the local system. For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
 
 ## Usage
 

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

@@ -8,7 +8,7 @@ Use `MesaFilesystem` when agents need versioned file storage. For a local direct
 
 > **Info:** `MesaFilesystem` runs in the Mastra process.
 >
-> [Mesa's POSIX mount](https://docs.mesa.dev/content/mesafs/posix-mount) (for using a Mesa filesystem within a sandbox) is not yet part of the `@mastra/mesa` package. Support is coming soon.
+> [Mesa's POSIX mount](https://docs.mesa.dev/content/mesafs/posix-mount) (for using a Mesa filesystem within a sandbox) isn't yet part of the `@mastra/mesa` package. Support is coming soon.
 
 ## Installation
 
@@ -252,14 +252,14 @@ Methods expect absolute paths. For `MesaFilesystem`, paths are rooted at the Mes
 await filesystem.readFile('/acme/docs/README.md')
 ```
 
-Do not omit the leading slash:
+Don't omit the leading slash:
 
 ```typescript
 await filesystem.readFile('acme/docs/README.md') // Incorrect
 await filesystem.readFile('/acme/docs/README.md') // Correct
 ```
 
-The org comes from `org` in the constructor, or from the Mesa SDK's default org inference when `org` is omitted. It still appears as the first path segment.
+The org comes from `org` in the constructor, or from the Mesa SDK's default org inference when `org` is omitted. It remains the first path segment.
 
 When you mount multiple repos, each repo is available under the org segment:
 
@@ -311,7 +311,7 @@ Read operations still work. Write operations throw `WorkspaceReadOnlyError`.
 
 ## Concurrency
 
-`overwrite: false` and `expectedMtime` use preflight checks before writing. These checks are not atomic unless Mesa adds native conditional writes for app mounts.
+`overwrite: false` and `expectedMtime` use preflight checks before writing. These checks aren't atomic unless Mesa adds native conditional writes for app mounts.
 
 ## Related
 

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

@@ -2,9 +2,7 @@
 
 # ModalSandbox
 
-Executes commands in isolated [Modal](https://modal.com) cloud sandboxes. Provides secure, ephemeral environments backed by Modal's infrastructure.
-
-> **Info:** For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
+Executes commands in isolated [Modal](https://modal.com) cloud sandboxes. Provides secure, ephemeral environments backed by Modal's infrastructure. For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
 
 ## Installation
 

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

@@ -2,9 +2,7 @@
 
 # RailwaySandbox
 
-Executes commands in ephemeral, isolated [Railway](https://docs.railway.com/sandboxes) sandboxes. Each sandbox is an isolated Debian Linux VM provisioned on demand through the Railway TypeScript SDK. Supports command execution with streaming output, command timeouts, configurable idle timeout, `ISOLATED`/`PRIVATE` network isolation, custom base images via the Railway template builder, forking a running sandbox, and reattaching to an existing sandbox by ID.
-
-> **Info:** For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
+Executes commands in ephemeral, isolated [Railway](https://docs.railway.com/sandboxes) sandboxes. Each sandbox is an isolated Debian Linux VM provisioned on demand through the Railway TypeScript SDK. Supports command execution with streaming output, command timeouts, configurable idle timeout, `ISOLATED`/`PRIVATE` network isolation, custom base images via the Railway template builder, forking a running sandbox, and reattaching to an existing sandbox by ID. For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
 
 ## Installation
 
@@ -213,7 +211,7 @@ console.log(handle.stdout)
 await handle.kill()
 ```
 
-Railway's `exec` API does not stream stdin, so `sendStdin()` is not supported.
+Railway's `exec` API doesn't stream stdin, so `sendStdin()` isn't supported.
 
 See [`SandboxProcessManager` reference](https://mastra.ai/reference/workspace/process-manager) for the full API.
 

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

@@ -2,9 +2,7 @@
 
 # S3Filesystem
 
-Stores files in Amazon S3 or S3-compatible storage services like Cloudflare R2, MinIO, DigitalOcean Spaces, and Tigris.
-
-> **Info:** For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
+Stores files in Amazon S3 or S3-compatible storage services like Cloudflare R2, MinIO, DigitalOcean Spaces, and Tigris. For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
 
 ## Installation
 

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

@@ -2,9 +2,7 @@
 
 # VercelSandbox
 
-Executes commands inside [Vercel Sandbox](https://vercel.com/docs/vercel-sandbox) which is an ephemeral [Firecracker](https://firecracker-microvm.github.io/) MicroVM running Amazon Linux 2023. Provides a persistent in-session filesystem, `sudo` access, exposed ports, and background processes.
-
-> **Info:** For interface details, see the [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
+Executes commands inside [Vercel Sandbox](https://vercel.com/docs/vercel-sandbox) which is an ephemeral [Firecracker](https://firecracker-microvm.github.io/) MicroVM running Amazon Linux 2023. Provides a persistent in-session filesystem, `sudo` access, exposed ports, and background processes. For interface details, see the [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
 
 > **Note:** This is distinct from [`VercelServerlessSandbox`](https://mastra.ai/reference/workspace/vercel-serverless), which runs commands as stateless Vercel serverless **Functions**. `VercelSandbox` runs a full Linux MicroVM with a persistent filesystem and long-running processes.
 
@@ -148,7 +146,7 @@ Both callbacks are optional and can be used independently.
 
 **resources** (`{ vcpus?: number }`): Resource allocation. Each vCPU comes with 2048 MB of memory.
 
-**ports** (`number[]`): Ports to expose from the sandbox (up to 4). Public HTTPS domains are available via getInfo().metadata.domains.
+**ports** (`number[]`): Ports to expose from the sandbox (up to 15). Public HTTPS domains are available via getInfo().metadata.domains.
 
 **env** (`Record<string, string>`): Default environment variables inherited by all commands. (Default: `{}`)
 
@@ -199,9 +197,9 @@ See the [`SandboxProcessManager` reference](https://mastra.ai/reference/workspac
 
 ## Limits
 
-- Up to 8 vCPUs, with 2048 MB of memory per vCPU.
-- Up to 4 exposed ports.
+- 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.
-- Maximum runtime is plan-dependent (45 minutes on Hobby, up to 5 hours on Pro/Enterprise), with a default of 5 minutes.
+- 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/vercel-serverless.md

@@ -2,11 +2,9 @@
 
 # VercelServerlessSandbox
 
-Executes commands as [Vercel](https://vercel.com) serverless functions. Provides globally distributed, zero-infrastructure execution with automatic scaling.
+Executes commands as [Vercel](https://vercel.com) serverless functions. Provides globally distributed, zero-infrastructure execution with automatic scaling. For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
 
-> **Info:** For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
-
-> **Warning:** VercelServerlessSandbox is stateless. It doesn't provide a persistent filesystem, interactive shell, or long-running background processes. Only `/tmp` is writable, and it is ephemeral between invocations.
+> **Warning:** VercelServerlessSandbox is stateless. It doesn't provide a persistent filesystem, interactive shell, or long-running background processes. Only `/tmp` is writable, and it's ephemeral between invocations.
 
 > **Note:** For a full Linux MicroVM with a persistent filesystem, `sudo` access, exposed ports, and background processes, use [`VercelSandbox`](https://mastra.ai/reference/workspace/vercel-sandbox), which is backed by the [Vercel Sandbox](https://vercel.com/docs/vercel-sandbox) product.
 

package/CHANGELOG.md

@@ -1,5 +1,34 @@
 # @mastra/mcp-docs-server
 
+## 1.2.7-alpha.9
+
+### Patch Changes
+
+- Updated dependencies [[`a5c6337`](https://github.com/mastra-ai/mastra/commit/a5c6337d23c7686c81a32ce62f550f610543a240), [`eb70da9`](https://github.com/mastra-ai/mastra/commit/eb70da98e1007b18e1463d75121bc07db55f8e09), [`8b97958`](https://github.com/mastra-ai/mastra/commit/8b979589f9aa59ba67cac565949475f2ffeb4ac3), [`8410541`](https://github.com/mastra-ai/mastra/commit/84105412c60ecd3bb33a9838146f59c4b588228f), [`01b338c`](https://github.com/mastra-ai/mastra/commit/01b338c56271f0219606710e3e8b26dee27ac6c2), [`8b7361d`](https://github.com/mastra-ai/mastra/commit/8b7361d35de68b80d05d30a74e0c69e7218fd612), [`85fb642`](https://github.com/mastra-ai/mastra/commit/85fb642f4d112d0da9f39808617397f7e47fe622), [`481c112`](https://github.com/mastra-ai/mastra/commit/481c1125b752489673ec671fcb7ca80f9c86ffb1), [`c43f3a9`](https://github.com/mastra-ai/mastra/commit/c43f3a9d1efde99b38789364ba4d0ba670f430e3), [`c43f3a9`](https://github.com/mastra-ai/mastra/commit/c43f3a9d1efde99b38789364ba4d0ba670f430e3)]:
+  - @mastra/core@1.51.0-alpha.4
+  - @mastra/mcp@1.14.0-alpha.0
+
+## 1.2.7-alpha.7
+
+### Patch Changes
+
+- Updated dependencies [[`177010f`](https://github.com/mastra-ai/mastra/commit/177010ff096d2e4b28d89803be5b1a4cad2a0d6b), [`54a51e0`](https://github.com/mastra-ai/mastra/commit/54a51e0a484fe1ebad3fb1f7ef5282a075709eb7)]:
+  - @mastra/core@1.51.0-alpha.3
+
+## 1.2.7-alpha.5
+
+### Patch Changes
+
+- Updated dependencies [[`e955965`](https://github.com/mastra-ai/mastra/commit/e955965dce575a903e37cf054d28ea99aa48785e), [`860ef7e`](https://github.com/mastra-ai/mastra/commit/860ef7e77d92b63469cbe5857aa1e626197e43e9), [`17e818c`](https://github.com/mastra-ai/mastra/commit/17e818c51a958ba90641b1a959dc38faf8c034e9), [`4451dfe`](https://github.com/mastra-ai/mastra/commit/4451dfe857428e7abcc0261a507a2e186dae6d47), [`1d39058`](https://github.com/mastra-ai/mastra/commit/1d39058e548efd691799985d5c8af2737f1c3bd2)]:
+  - @mastra/core@1.51.0-alpha.2
+
+## 1.2.7-alpha.2
+
+### Patch Changes
+
+- Updated dependencies:
+  - @mastra/core@1.50.2-alpha.1
+
 ## 1.2.7-alpha.0
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mastra/mcp-docs-server",
-  "version": "1.2.7-alpha.1",
+  "version": "1.2.7-alpha.10",
   "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.50.2-alpha.0",
-    "@mastra/mcp": "^1.13.1"
+    "@mastra/core": "1.51.0-alpha.4",
+    "@mastra/mcp": "^1.14.0-alpha.0"
   },
   "devDependencies": {
     "@hono/node-server": "^1.19.11",
@@ -46,8 +46,8 @@
     "typescript": "^6.0.3",
     "vitest": "4.1.9",
     "@internal/lint": "0.0.113",
-    "@mastra/core": "1.50.2-alpha.0",
-    "@internal/types-builder": "0.0.88"
+    "@internal/types-builder": "0.0.88",
+    "@mastra/core": "1.51.0-alpha.4"
   },
   "homepage": "https://mastra.ai",
   "repository": {

package/.docs/docs/agents/channels.md

@@ -1,225 +0,0 @@
-> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
-
-# Channels
-
-**Added in:** `@mastra/core@1.22.0`
-
-Channels connect your agents to messaging platforms like Slack, Discord, and Telegram. When a user sends a message on a platform, the agent receives it, processes it through the normal agent pipeline, and streams the response back to the conversation.
-
-## When to use channels
-
-Use channels when you want your agent to:
-
-- Respond to messages in Slack workspaces, Discord servers, or Telegram chats
-- Handle both direct messages and mentions in group conversations
-
-## Quickstart
-
-Configure channels directly on your agent using adapters from the [Chat SDK](https://chat-sdk.dev/adapters):
-
-```typescript
-import { Agent } from '@mastra/core/agent'
-import { createSlackAdapter } from '@chat-adapter/slack'
-
-export const supportAgent = new Agent({
-  id: 'support-agent',
-  name: 'Support Agent',
-  instructions: 'You are a helpful support assistant.',
-  model: 'openai/gpt-5.5',
-  channels: {
-    adapters: {
-      slack: createSlackAdapter(),
-    },
-  },
-})
-```
-
-Register the agent in your Mastra instance with storage so channel state persists across restarts:
-
-```typescript
-import { Mastra } from '@mastra/core'
-import { LibSQLStore } from '@mastra/libsql'
-import { supportAgent } from './agents/support-agent'
-
-export const mastra = new Mastra({
-  agents: { supportAgent },
-  storage: new LibSQLStore({
-    url: process.env.DATABASE_URL,
-  }),
-})
-```
-
-Each adapter reads credentials from environment variables by default.
-
-## Platform setup
-
-Each platform requires credentials and event configuration. See the Chat SDK adapter docs for full setup: [Slack](https://chat-sdk.dev/adapters/slack), [Discord](https://chat-sdk.dev/adapters/discord), [Telegram](https://chat-sdk.dev/adapters/telegram).
-
-Mastra generates a webhook route for each platform at:
-
-```text
-/api/agents/{agentId}/channels/{platform}/webhook
-```
-
-For example: `/api/agents/support-agent/channels/slack/webhook`
-
-Point your platform's webhook or interactions URL to this path.
-
-### Local development
-
-Platform webhooks need a public URL to reach your local server. Use a tunnel to expose `localhost:4111`:
-
-```bash
-# ngrok
-ngrok http 4111
-
-# cloudflared
-npx cloudflared tunnel --url http://localhost:4111
-```
-
-Copy the generated URL and use it as the base for your webhook paths (e.g. `https://abc123.ngrok.io/api/agents/support-agent/channels/slack/webhook`).
-
-## Thread context
-
-When a user mentions the agent mid-conversation in a channel thread, the agent may not have prior context. By default, Mastra fetches the last 10 messages from the platform on the first mention.
-
-1. On the **first mention** in a thread, the agent fetches recent messages from the platform.
-2. These messages are prepended to the user's message as conversation context.
-3. After responding, the agent subscribes to the thread and has full history via Mastra's memory.
-4. Subsequent messages in that thread **don't** re-fetch from the platform.
-
-Set `threadContext: { maxMessages: 0 }` to disable this behavior. This only applies to non-DM threads.
-
-Mastra also adds a short system message telling the agent which channel and platform the request came from (DM vs public channel, platform name, bot display name). Set `threadContext: { addSystemMessage: false }` to skip it.
-
-## Tool approval
-
-Tools with `requireApproval: true` render as interactive cards with Approve and Deny buttons:
-
-```typescript
-import { createTool } from '@mastra/core/tools'
-import { z } from 'zod'
-
-const deleteFile = createTool({
-  id: 'delete-file',
-  description: 'Delete a file from the system',
-  inputSchema: z.object({
-    path: z.string().describe('Path to the file to delete'),
-  }),
-  requireApproval: true,
-  execute: async ({ path }) => {
-    await fs.unlink(path)
-    return { deleted: path }
-  },
-})
-```
-
-When the agent calls this tool, users see a card with the tool name, arguments, and Approve/Deny buttons. The tool only executes after approval.
-
-Set `toolDisplay: 'text'` on an adapter to render tool calls as plain text instead of interactive cards. In `'hidden'` mode the agent uses `autoResumeSuspendedTools` to let the LLM decide based on the conversation context, since hidden mode doesn't post approval buttons.
-
-## Multi-user awareness
-
-In group conversations, Mastra automatically prefixes each message with the sender's name and platform ID so the agent can distinguish between speakers:
-
-```text
-[Alice (@U123ABC)]: Can you help me with this?
-[Bob (@U456DEF)]: I have a question too.
-```
-
-## Multimodal content
-
-Models like Gemini can natively process images, video, and audio. Combine `inlineMedia` and `inlineLinks` to let users share rich content with your agent across platforms:
-
-```typescript
-import { Agent } from '@mastra/core/agent'
-import { createDiscordAdapter } from '@chat-adapter/discord'
-import { google } from '@ai-sdk/google'
-
-export const visionAgent = new Agent({
-  id: 'vision-agent',
-  name: 'Vision Agent',
-  instructions: 'You can see images, watch videos, and listen to audio.',
-  model: google('gemini-3.1-flash-image-preview'),
-  channels: {
-    adapters: {
-      discord: createDiscordAdapter(),
-    },
-    inlineMedia: ['image/*', 'video/*', 'audio/*'],
-    inlineLinks: [
-      // Gemini treats YouTube URLs as native video file parts
-      { match: 'youtube.com', mimeType: 'video/*' },
-      { match: 'youtu.be', mimeType: 'video/*' },
-      'imgur.com', // HEAD-check imgur links; inline as file part if mimeType matches inlineMedia
-    ],
-  },
-})
-```
-
-With this configuration:
-
-- A user uploads a screenshot and the agent describes what it sees
-- A user uploads an `.mp4` clip and the agent summarizes the video
-- A user pastes a YouTube link and the agent watches and discusses the video
-- A user pastes an imgur link and the agent sees the image directly
-
-By default, only images are sent inline (`inlineMedia: ['image/*']`). Unsupported types are described as text summaries so the agent knows about the file without crashing models that reject them.
-
-> **Note:** See [Channels reference](https://mastra.ai/reference/agents/channels) for all `inlineMedia` patterns and [inlineLinks reference](https://mastra.ai/reference/agents/channels) for domain matching, HEAD detection, and forced mime types.
-
-## Serverless deployment
-
-On serverless platforms like Vercel, each request runs in a separate, short-lived instance. Channels need two things to work reliably in that environment: a way to keep the function alive while the agent responds, and a shared pub/sub so instances can coordinate.
-
-### Keep the function alive with `waitUntil`
-
-A channel webhook returns a `200` response right away, then the agent runs in the background to post its reply. On most serverless platforms the function is frozen as soon as it responds, which kills the run before the agent answers. Pass a `waitUntil` function so the platform keeps the instance alive until the run finishes.
-
-On Vercel, pass `waitUntil` from `@vercel/functions`:
-
-```typescript
-import { Agent } from '@mastra/core/agent'
-import { createSlackAdapter } from '@chat-adapter/slack'
-import { waitUntil } from '@vercel/functions'
-
-export const agent = new Agent({
-  id: 'agent',
-  channels: {
-    adapters: {
-      slack: createSlackAdapter(),
-    },
-    waitUntil,
-  },
-})
-```
-
-Vercel and AWS Lambda require `waitUntil`, since they freeze the function as soon as the response is sent. Cloudflare Workers and Netlify Functions are detected automatically from the request context, so they don't need it. For runtimes where `waitUntil` lives on the request context but isn't detected automatically, use `resolveWaitUntil`. See the [Channels reference](https://mastra.ai/reference/agents/channels) for details.
-
-### Coordinate instances with a shared pub/sub
-
-Channels route messages through the agent's signal pipeline, and each run acquires a lease on its thread so a single run owns the conversation at a time. The default in-memory pub/sub can't cross instance boundaries, so on serverless a follow-up message can land on a different instance than the one running the agent. Without a shared pub/sub, that instance can't reach the active run and starts its own, leaving the original run untouched and the thread processed twice.
-
-Configure a shared pub/sub backed by Redis Streams on the `Mastra` instance so leases and signals coordinate across instances:
-
-```typescript
-import { Mastra } from '@mastra/core'
-import { RedisStreamsPubSub } from '@mastra/redis-streams'
-
-export const mastra = new Mastra({
-  agents: { agent },
-  pubsub: new RedisStreamsPubSub({
-    url: process.env.REDIS_URL,
-    keyPrefix: 'mastra:my-app',
-  }),
-})
-```
-
-Vercel's one-click Redis integration and Upstash Redis both work well. For more on when a distributed pub/sub is needed, see the [PubSub guide](https://mastra.ai/docs/server/pubsub) and the [`RedisStreamsPubSub` reference](https://mastra.ai/reference/pubsub/redis-streams).
-
-## Related
-
-- [Guide: Building a Slack assistant](https://mastra.ai/guides/guide/slack-assistant)
-- [Agent overview](https://mastra.ai/docs/agents/overview)
-- [Tool approval](https://mastra.ai/docs/agents/agent-approval)
-- [Channels reference](https://mastra.ai/reference/agents/channels)
-- [Chat SDK adapters](https://chat-sdk.dev/adapters)