@mastra/mcp-docs-server 1.2.15 → 1.2.16-alpha.1

package/.docs/integrations/deploy/kubernetes.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Deploy Mastra to Kubernetes
+# Kubernetes
 
 Run a Mastra application across multiple pods on [Kubernetes](https://kubernetes.io/), so it scales horizontally behind a load balancer. Because each pod is a separate process, the pods must share a pub/sub backend and a database, otherwise work started on one pod is invisible to the others.
 
@@ -12,7 +12,7 @@ Run a Mastra application across multiple pods on [Kubernetes](https://kubernetes
 
 You'll need:
 
-- A [Mastra application](https://mastra.ai/guides/getting-started/quickstart)
+- A [Mastra application](https://mastra.ai/docs)
 - A [Kubernetes](https://kubernetes.io/docs/setup/) cluster and [`kubectl`](https://kubernetes.io/docs/tasks/tools/)
 - A container registry your cluster can pull from
 - A shared [Redis](https://redis.io/) instance, reachable from every pod
@@ -295,6 +295,5 @@ The pod that handles the approval loads the suspended run from Postgres. It then
 - [PubSub](https://mastra.ai/docs/server/pubsub)
 - [Durable agents](https://mastra.ai/docs/long-running-agents/durable-agents)
 - [Workers](https://mastra.ai/docs/deployment/workers): Split background processing into separate containers on Kubernetes
-- [Worker deployment guide](https://mastra.ai/guides/deployment/mastra-workers): Full Kubernetes manifests for orchestration, scheduler, and background task workers
 - [Mastra server](https://mastra.ai/docs/server/mastra-server)
 - [Deployment overview](https://mastra.ai/docs/deployment/overview)

package/.docs/integrations/deploy/netlify.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Deploy Mastra to Netlify
+# Netlify
 
 Use `@mastra/deployer-netlify` to deploy your Mastra server on Netlify. The deployer bundles your code and generates a `.netlify` directory conforming to Netlify's [Frameworks API](https://docs.netlify.com/build/frameworks/frameworks-api/), ready to deploy. You can deploy as serverless functions (default) or as [edge functions](https://docs.netlify.com/build/edge-functions/overview/) for lower latency and longer execution times.
 
@@ -8,7 +8,7 @@ Use `@mastra/deployer-netlify` to deploy your Mastra server on Netlify. The depl
 
 ## Before you begin
 
-You'll need a [Mastra application](https://mastra.ai/guides/getting-started/quickstart) and a [Netlify](https://www.netlify.com/) account.
+You'll need a [Mastra application](https://mastra.ai/docs) and a [Netlify](https://www.netlify.com/) account.
 
 > **Warning:** Netlify Functions use an ephemeral filesystem, so any storage you configure (including observability storage) must be hosted externally. If you're using [LibSQLStore](https://mastra.ai/integrations/databases/libsql) with a file URL, switch to a remotely hosted database.
 

package/.docs/integrations/deploy/temporal.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Temporal workflow
+# Temporal
 
 [Temporal](https://temporal.io/) is a durable execution platform for orchestrating long-running, fault-tolerant workflows. The `@mastra/temporal` package lets you author workflows with the standard Mastra API and run them on a Temporal cluster.
 

package/.docs/integrations/deploy/vercel.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Deploy Mastra to Vercel
+# Vercel Deployer
 
 Use `@mastra/deployer-vercel` to deploy your Mastra server as serverless functions on Vercel. The deployer bundles your code and generates a `.vercel/output` directory conforming to Vercel's [Build Output API](https://vercel.com/docs/build-output-api/v3), ready to deploy with no additional configuration.
 
@@ -8,7 +8,7 @@ Use `@mastra/deployer-vercel` to deploy your Mastra server as serverless functio
 
 ## Before you begin
 
-You'll need a [Mastra application](https://mastra.ai/guides/getting-started/quickstart) and a [Vercel](https://vercel.com/) account.
+You'll need a [Mastra application](https://mastra.ai/docs) and a [Vercel](https://vercel.com/) account.
 
 > **Warning:** Vercel Functions use an ephemeral filesystem, so any storage you configure (including observability storage) must be hosted externally. If you're using [LibSQLStore](https://mastra.ai/integrations/databases/libsql) with a file URL, switch to a remotely hosted database.
 

package/.docs/integrations/file-storage/agentfs.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# AgentFSFilesystem
+# AgentFS
 
 Stores files in a Turso/SQLite database via the [AgentFS](https://github.com/nichochar/agentfs) SDK. Files are persisted across sessions in a local SQLite database, giving agents durable storage without external cloud services. For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
 

package/.docs/integrations/file-storage/amazon-s3.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# S3Filesystem
+# Amazon S3
 
 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).
 

package/.docs/integrations/file-storage/archil.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# ArchilFilesystem
+# Archil
 
 Stores files on [Archil](https://docs.archil.com) elastic, serverless disks. Combines an S3-compatible object API for fast reads/writes with `exec()` for POSIX shell operations and `grep()` for parallel server-side search. For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
 

package/.docs/integrations/file-storage/azure-blob.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# AzureBlobFilesystem
+# Azure Blob
 
 Stores files in Azure Blob Storage containers. For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
 

package/.docs/integrations/file-storage/google-cloud-storage.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# GCSFilesystem
+# Google Cloud Storage
 
 Stores files in Google Cloud Storage. For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
 

package/.docs/integrations/file-storage/google-drive.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# GoogleDriveFilesystem
+# Google Drive
 
 Stores files in a single Google Drive folder. Each directory maps to a Drive folder under the configured root, and paths use POSIX semantics (for example `/notes/todo.txt`). For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
 

package/.docs/integrations/file-storage/mesa.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# MesaFilesystem
+# Mesa
 
 Stores workspace files in [Mesa](https://docs.mesa.dev/content/getting-started/introduction) repos through the standard Mastra `WorkspaceFilesystem` interface.
 

package/.docs/integrations/file-storage/vercel-files.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# FilesSDKFilesystem
+# Vercel Files
 
 Stores files in any storage backend supported by [FilesSDK](https://files-sdk.dev): a unified abstraction over S3, Cloudflare R2, Google Cloud Storage, Azure Blob, Vercel Blob, MinIO, the local filesystem, and more. For interface details, see [WorkspaceFilesystem Interface](https://mastra.ai/reference/workspace/filesystem).
 

package/.docs/integrations/frameworks/astro.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Integrate Mastra in your Astro project
+# Astro
 
 In this guide, you'll build a tool-calling AI agent using Mastra, then connect it to Astro by importing and calling the agent directly from your routes.
 

package/.docs/integrations/frameworks/electron.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Integrate Mastra in your Electron project
+# Electron
 
 In this guide, you'll build a tool-calling AI agent using Mastra, then connect it to an Electron desktop app by calling the agent directly from Mastra's server.
 

package/.docs/integrations/frameworks/express.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Integrate Mastra in your Express project
+# Express
 
 In this guide, you'll build a tool-calling AI agent using Mastra and Express. Using the [Express server adapter](https://mastra.ai/reference/server/express-adapter), you can expose your agents as HTTP endpoints without writing the routing yourself or running a separate Mastra server.
 

package/.docs/integrations/frameworks/hono.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Integrate Mastra in your Hono project
+# Hono
 
 In this guide, you'll build a tool-calling AI agent using Mastra and Hono. Using the [Hono server adapter](https://mastra.ai/reference/server/hono-adapter), you can expose your agents as HTTP endpoints without writing the routing yourself or running a separate Mastra server.
 

package/.docs/integrations/frameworks/nestjs.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Integrate Mastra in Your NestJS Project
+# NestJS
 
 In this guide, you'll build a tool-calling AI agent using Mastra and NestJS. The [NestJS server adapter](https://mastra.ai/reference/server/nestjs-adapter) registers Mastra's agent and workflow routes as a NestJS module, so they run inside your existing NestJS application.
 

package/.docs/integrations/frameworks/next-js.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Integrate Mastra in your Next.js project
+# Next.js
 
 In this guide, you'll build a tool-calling AI agent using Mastra, then connect it to Next.js by importing and calling the agent directly from your routes.
 

package/.docs/integrations/frameworks/nuxt.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Integrate Mastra in your Nuxt project
+# Nuxt
 
 In this guide, you'll build a tool-calling AI agent using Mastra, then connect it to Nuxt by importing and calling the agent directly from your server routes.
 

package/.docs/integrations/frameworks/sveltekit.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Integrate Mastra in your SvelteKit project
+# SvelteKit
 
 In this guide, you'll build a tool-calling AI agent using Mastra, then connect it to SvelteKit by importing and calling the agent directly from your routes.
 

package/.docs/integrations/frameworks/vite-react.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Integrate Mastra in your React + Vite project
+# React + Vite
 
 In this guide, you'll build a tool-calling AI agent using Mastra, then connect it to React by calling the agent directly from Mastra's standalone server.
 

package/.docs/integrations/sandboxes/agentcore.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# AgentCoreRuntimeSandbox
+# AgentCore
 
 Executes shell commands in an [AWS Bedrock AgentCore Runtime](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-execute-command.html) session by using `InvokeAgentRuntimeCommand`.
 

package/.docs/integrations/sandboxes/apple-container.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# AppleContainerSandbox
+# Apple Container
 
 Executes commands inside local OCI Linux containers through Apple's [`container`](https://github.com/apple/container) CLI. The provider starts a long-lived container and uses `container exec` for workspace commands. For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
 

package/.docs/integrations/sandboxes/blaxel.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# BlaxelSandbox
+# Blaxel
 
 Executes commands in isolated [Blaxel](https://blaxel.ai/) cloud sandboxes. Provides secure, isolated code execution environments with support for mounting cloud storage (S3, GCS) via FUSE. For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
 

package/.docs/integrations/sandboxes/daytona.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# DaytonaSandbox
+# Daytona
 
 Executes commands in isolated [Daytona](https://www.daytona.io) cloud sandboxes. Supports multiple runtimes, resource configuration, volumes, snapshots, streaming output, sandbox reconnection, filesystem mounting (S3, GCS), and network isolation. For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
 

package/.docs/integrations/sandboxes/docker.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# DockerSandbox
+# Docker
 
 Executes commands inside Docker containers on the local machine. Uses long-lived containers with `docker exec` for command execution. Targets local development, CI/CD, air-gapped deployments, and cost-sensitive scenarios where cloud sandboxes are unnecessary. For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
 

package/.docs/integrations/sandboxes/e2b.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# E2BSandbox
+# E2B
 
 Executes commands in isolated [E2B](https://e2b.dev) cloud sandboxes. Provides secure, ephemeral environments with support for mounting cloud storage. For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
 

package/.docs/integrations/sandboxes/modal.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# ModalSandbox
+# Modal
 
 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).
 

package/.docs/integrations/sandboxes/railway.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# RailwaySandbox
+# Railway
 
 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, checkpoint-backed recovery, forking a running sandbox, and reattaching to an existing sandbox by ID. For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
 

package/.docs/integrations/sandboxes/vercel.md

@@ -1,6 +1,8 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Vercel sandboxes
+# Vercel Sandboxes
+
+Run commands in isolated Vercel environments with either persistent Sandbox microVMs or stateless Serverless Functions.
 
 ## Vercel Sandbox
 

package/.docs/integrations/tools/firecrawl.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Web scraping with Firecrawl
+# Firecrawl
 
 Firecrawl is a web data API that turns websites into clean markdown or structured JSON. In this guide, you will wire Firecrawl into Mastra tools so your agents and workflows can search and scrape live web data on demand.
 
@@ -9,7 +9,7 @@ Firecrawl is a web data API that turns websites into clean markdown or structure
 - Node.js `v22.13.0` or later installed
 - A Firecrawl API key (get one at <https://firecrawl.dev>)
 - 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)
+- An existing Mastra project. Follow [Get started](https://mastra.ai/docs) to create one.
 
 ## Installation
 

package/.docs/integrations/voice/livekit.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Realtime voice
+# LiveKit
 
 ## Quickstart
 
@@ -8,7 +8,7 @@ Realtime voice turns a Mastra agent into a live call a user can talk over, in th
 
 The [`@mastra/livekit`](#api-reference) package connects Mastra agents to the [LiveKit Agents framework](https://docs.livekit.io/agents/): LiveKit owns the audio loop like voice activity detection, streaming speech-to-text, semantic turn detection, barge-in, and text-to-speech. Your Mastra agent generates every reply with its own model, tools, and memory.
 
-Use realtime voice when you need low-latency, interruptible voice conversations. For provider-based speech-to-speech without LiveKit, see [Speech to Speech](https://mastra.ai/guides/voice/speech-to-speech).
+Use realtime voice when you need low-latency, interruptible voice conversations. For provider-based speech-to-speech without LiveKit, see [Speech to Speech](https://mastra.ai/reference/voice/speech-to-speech).
 
 These steps take you from an empty project to a voice agent you can talk to. A voice session has two moving parts you set up here: an API route on your Mastra server that hands out access tokens, and a separate worker process that runs the audio pipeline and calls your agent each turn.
 
@@ -399,7 +399,7 @@ Conversation history lives in Mastra Memory, so voice sessions and text chat can
 ### Related
 
 - [`@mastra/livekit` reference](#api-reference)
-- [Speech to Speech](https://mastra.ai/guides/voice/speech-to-speech)
+- [Speech to Speech](https://mastra.ai/reference/voice/speech-to-speech)
 - [Agent Memory](https://mastra.ai/docs/memory/overview)
 - [LiveKit Agents docs](https://docs.livekit.io/agents/)