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

package/.docs/docs/mastra-platform/observability.md

@@ -2,9 +2,7 @@
 
 # Observability on Mastra platform
 
-Observability on Mastra platform is a standalone hosted product for searchable traces, logs, and metrics across Mastra projects and deploys. Use it when you want observability without deploying Studio first or setting up local storage.
-
-Use `mastra init` to configure platform observability while adding Mastra to an existing application, or configure it manually in a newly created Mastra project.
+Mastra Platform Observability collects traces, logs, metrics, scores, and feedback from Mastra applications. Use it for hosted observability without deploying Studio or Server or configuring local observability storage.
 
 ## Quickstart
 
@@ -12,7 +10,7 @@ Choose the setup path that matches your project.
 
 ### New project
 
-Create a managed Mastra project. When prompted, opt into Mastra Platform Observability to configure it automatically:
+Create a managed Mastra project and enable Mastra Platform Observability when prompted:
 
 **npm**:
 
@@ -38,11 +36,11 @@ yarn create mastra
 bunx create-mastra
 ```
 
-When you select observability, the create command authenticates with Mastra Platform, provisions a platform project, and writes the credentials to your project. If you skip platform setup or use a prompt-free creation flow, follow the [manual setup](#manual-setup) steps instead.
+The create command authenticates with Mastra Platform, creates an observability project, mints an access token, and writes `MASTRA_PLATFORM_ACCESS_TOKEN` and `MASTRA_PROJECT_ID` to `.env`.
 
-### Existing non-Mastra projects
+### Existing project
 
-If you already have an application, such as a Next.js app, but haven't added Mastra yet, run `mastra init` and enable Mastra Observability when prompted:
+If you're adding Mastra to an existing application, run `mastra init` and enable Mastra Observability when prompted:
 
 **npm**:
 
@@ -68,21 +66,33 @@ yarn dlx mastra init
 bun x mastra init
 ```
 
-The CLI can select an existing platform project or create a new one.
+The init command lets you select an existing platform project or create one. It then creates an access token and writes the credentials to `.env`.
+
+## Configure manually
 
-### Manual setup
+Use manual configuration if you skipped platform setup or automatic provisioning failed.
 
-Create a project in [Mastra Platform](https://projects.mastra.ai), add `MASTRA_PLATFORM_ACCESS_TOKEN` and `MASTRA_PROJECT_ID` to `.env`, then register `MastraPlatformExporter` in your Mastra config. Add `MastraStorageExporter` if you also want to persist observability events to your configured Mastra Storage:
+1. In [Mastra Platform](https://projects.mastra.ai), create or open a project.
+2. Create an access token for the project's organization.
+3. Copy the project ID from the project page.
+4. Add both values to `.env`:
 
-```ts
+```bash
+MASTRA_PLATFORM_ACCESS_TOKEN=<your-platform-access-token>
+MASTRA_PROJECT_ID=<your-project-id>
+```
+
+Register [`MastraPlatformExporter`](https://mastra.ai/reference/observability/tracing/exporters/mastra-platform-exporter) in your observability configuration:
+
+```typescript
 import { Mastra } from '@mastra/core/mastra'
-import { Observability, MastraPlatformExporter } from '@mastra/observability'
+import { MastraPlatformExporter, Observability } from '@mastra/observability'
 
 export const mastra = new Mastra({
   observability: new Observability({
     configs: {
       default: {
-        serviceName: 'mastra',
+        serviceName: 'my-service',
         exporters: [new MastraPlatformExporter()],
       },
     },
@@ -90,11 +100,43 @@ export const mastra = new Mastra({
 })
 ```
 
-See [Mastra platform configuration](https://mastra.ai/docs/mastra-platform/configuration) for the environment variables used by platform observability.
+The exporter reads the access token and project ID from the environment. Keep `serviceName` stable so you can distinguish applications and deployments when filtering observability data.
+
+`MastraPlatformExporter` sends ended spans, logs, metrics, scores, and feedback. It buffers events and sends a batch when it reaches 1,000 events or has waited five seconds. Model chunk spans aren't exported.
+
+> **Note:** `MastraPlatformExporter` replaced `CloudExporter`. `CloudExporter` remains available for backward compatibility but is deprecated. Use `MastraPlatformExporter` for new code.
+
+### Store data locally
+
+Add `MastraStorageExporter` if you also want to persist observability data to your configured Mastra storage and inspect it in local Studio:
+
+```typescript
+import { Mastra } from '@mastra/core/mastra'
+import { MastraPlatformExporter, MastraStorageExporter, Observability } from '@mastra/observability'
+
+export const mastra = new Mastra({
+  observability: new Observability({
+    configs: {
+      default: {
+        serviceName: 'my-service',
+        exporters: [new MastraPlatformExporter(), new MastraStorageExporter()],
+      },
+    },
+  }),
+})
+```
+
+See [Mastra storage exporter](https://mastra.ai/docs/observability/integrations/exporters/mastra-storage) for storage requirements and configuration.
+
+## View observability data
+
+Open your project in [Mastra Platform](https://projects.mastra.ai) to inspect exported traces, logs, metrics, scores, and feedback. A Studio or Server deployment isn't required.
+
+Use a consistent `serviceName` to filter data from a specific application or deployment.
 
 ## Query observability data
 
-After your project is publishing traces, logs, or scores to Mastra Platform Observability, you can query that data from your terminal with the Mastra CLI or with `curl`.
+Query hosted observability data from the terminal with the Mastra CLI:
 
 **npm**:
 
@@ -120,8 +162,11 @@ yarn dlx mastra api trace list
 bun x mastra api trace list
 ```
 
-For observability commands, the CLI targets the hosted observability API and can infer credentials from your project environment. See the [`mastra api` CLI reference](https://mastra.ai/reference/cli/mastra) for available observability commands, filtering, pagination, credential resolution, and direct `curl` examples.
+The CLI can infer platform credentials from your project environment. See the [`mastra api` CLI reference](https://mastra.ai/reference/cli/mastra) for available commands, filtering, pagination, credential resolution, and `curl` examples.
 
-## Related
+## Next steps
 
-- 📹 [Mastra observability and Studio workshop](https://www.youtube.com/watch?v=dKO_a3RPra0)
+- 📹 [Mastra observability and Studio workshop](https://www.youtube.com/watch?v=dKO_a3RPra0)
+- [Configure Mastra Platform](https://mastra.ai/docs/mastra-platform/configuration)
+- [Learn about observability](https://mastra.ai/docs/observability/overview)
+- [Configure `MastraPlatformExporter`](https://mastra.ai/reference/observability/tracing/exporters/mastra-platform-exporter)

package/.docs/docs/mastra-platform/overview.md

@@ -40,4 +40,4 @@ Once you're ready to deploy your application to production, run [`mastra deploy`
 
 Follow the [Deploy](https://mastra.ai/docs/mastra-platform/deploy) docs for step-by-step instructions.
 
-If you host your Mastra application on your own infrastructure, you can still send observability data to Mastra platform using the [MastraPlatformExporter](https://mastra.ai/docs/observability/integrations/exporters/mastra-platform).
+If you host your Mastra application on your own infrastructure, you can still send observability data to Mastra platform using the [MastraPlatformExporter](https://mastra.ai/docs/mastra-platform/observability).

package/.docs/docs/mcp/overview.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# MCP overview
+# MCP
 
 Mastra supports the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction), an open standard for connecting AI agents to external tools and resources.
 

package/.docs/docs/memory/working-memory.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Working Memory
+# Working memory
 
 While [message history](https://mastra.ai/docs/memory/message-history) and [semantic recall](https://mastra.ai/docs/memory/semantic-recall) help agents remember conversations, working memory allows them to maintain persistent information about users across interactions.
 

package/.docs/docs/observability/integrations/exporters/mastra-storage.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Mastra Storage exporter
+# Storage exporter
 
 The `MastraStorageExporter` persists traces to your configured storage backend, making them accessible through Studio. It requires no external services.
 
@@ -242,6 +242,6 @@ new MastraStorageExporter({
 ## Related
 
 - [Tracing Overview](https://mastra.ai/docs/observability/tracing/overview)
-- [MastraPlatformExporter](https://mastra.ai/docs/observability/integrations/exporters/mastra-platform)
+- [MastraPlatformExporter](https://mastra.ai/docs/mastra-platform/observability)
 - [Composite Storage](https://mastra.ai/reference/storage/composite): Combine multiple storage providers
 - [Storage Configuration](https://mastra.ai/docs/storage/overview)

package/.docs/docs/observability/logging.md

@@ -10,7 +10,7 @@ When deploying to the Mastra platform, logs are shown in the dashboard. In self-
 
 ## Configuring logs with `PinoLogger`
 
-When [initializing a new Mastra project](https://mastra.ai/guides/getting-started/quickstart) using the CLI, `PinoLogger` is included by default.
+When [initializing a new Mastra project](https://mastra.ai/docs) using the CLI, `PinoLogger` is included by default.
 
 ```typescript
 import { Mastra } from '@mastra/core/mastra'

package/.docs/docs/observability/metrics/overview.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Metrics overview
+# Metrics
 
 Mastra automatically emits performance and usage metrics from traced execution. There's no manual instrumentation needed. Metrics are derived from spans as they complete.
 

package/.docs/docs/observability/overview.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Observability overview
+# Observability
 
 Mastra's observability system gives you visibility into every agent run, workflow step, tool call, and model interaction. Agent behavior depends on model responses, prompts, tools, memory, and workflow state, so observability helps you inspect runtime decisions from day one. It captures complementary signals that work together to help you understand what your application is doing and why.
 
@@ -10,7 +10,6 @@ Mastra's observability system gives you visibility into every agent run, workflo
 - [**Logging**](https://mastra.ai/docs/observability/logging): Forwards structured log entries from your application and Mastra internals to observability storage, correlated to traces automatically.
 - [**Metrics**](https://mastra.ai/docs/observability/metrics/overview): Extracts trace usage and cost data. No additional instrumentation is required.
 - [**Feedback**](https://mastra.ai/docs/observability/feedback): Stores ratings, comments, corrections, and other review signals linked to traces and spans.
-- [**Integrations**](https://mastra.ai/docs/observability/integrations/overview): Choose exporters, bridges, and span processors for Studio, hosted, or external observability workflows.
 
 ## When to use observability
 
@@ -121,8 +120,6 @@ An observability config usually contains:
 - `spanOutputProcessors`: Transformations that run before spans are exported.
 - `logging`: Log forwarding settings for observability storage.
 
-For destinations and processors, see [Integrations overview](https://mastra.ai/docs/observability/integrations/overview).
-
 ### Maintaining Studio access
 
 When you add external exporters, keep `MastraStorageExporter` for Studio observability and/or `MastraPlatformExporter` for hosted Mastra platform observability.
@@ -234,7 +231,6 @@ For hosted traces, logs, and metrics across projects and deploys, see [Observabi
 - [Logging](https://mastra.ai/docs/observability/logging)
 - [Metrics](https://mastra.ai/docs/observability/metrics/overview)
 - [Feedback](https://mastra.ai/docs/observability/feedback)
-- [Integrations overview](https://mastra.ai/docs/observability/integrations/overview)
 - [Mastra Studio](https://mastra.ai/docs/studio/observability)
 - [Automatic metrics reference](https://mastra.ai/reference/observability/metrics/automatic-metrics)
 - [Mastra platform observability](https://mastra.ai/docs/mastra-platform/observability)

package/.docs/docs/observability/tracing/overview.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Tracing
+# Traces
 
 Tracing is the observability signal that records how a request moves through agents, workflows, tools, and model calls. Mastra represents each operation as a span and groups related spans into a trace so you can inspect the full execution path.
 
@@ -21,7 +21,6 @@ To get started with tracing, configure observability in your Mastra instance and
 
 - [Configuration](https://mastra.ai/docs/observability/overview): Base observability config and multiple configs, plus serverless flushing
 - [Storage](https://mastra.ai/docs/observability/overview): Storage routing for traces, logs, and metrics
-- [Integrations overview](https://mastra.ai/docs/observability/integrations/overview): Exporters, bridges, and processors
 
 ## Sampling strategies
 
@@ -333,7 +332,7 @@ const result = await agent.generate([{ role: 'user', content: 'Sensitive operati
 })
 ```
 
-For more fine-grained control over sensitive data, consider using the [Sensitive Data Filter](https://mastra.ai/docs/observability/integrations/processors/sensitive-data-filter) processor, which can redact specific fields (like passwords, tokens, and keys) while preserving the rest of the input/output.
+For more fine-grained control over sensitive data, consider using the [Sensitive Data Filter](https://mastra.ai/reference/observability/tracing/processors/sensitive-data-filter) processor, which can redact specific fields (like passwords, tokens, and keys) while preserving the rest of the input/output.
 
 #### Child spans and metadata extraction
 
@@ -423,7 +422,7 @@ Span processors transform, filter, or enrich trace data before it's exported. Th
 
 #### Built-in processors
 
-- [Sensitive Data Filter](https://mastra.ai/docs/observability/integrations/processors/sensitive-data-filter) redacts sensitive information. It's enabled in the default observability config.
+- [Sensitive Data Filter](https://mastra.ai/reference/observability/tracing/processors/sensitive-data-filter) redacts sensitive information. It's enabled in the default observability config.
 
 #### Creating custom processors
 
@@ -466,8 +465,6 @@ Processors are executed in the order they're defined, allowing you to chain mult
 - Normalizing data formats
 - Enriching spans with business context
 
-For the broader exporter, bridge, and processor model, see [Integrations overview](https://mastra.ai/docs/observability/integrations/overview).
-
 ## Span filtering
 
 Span filtering lets you reduce noise and per-span costs before data reaches your observability platform. Configure it per observability instance, so different exporters or environments can keep different levels of detail.

package/.docs/docs/server/auth/workers.md

@@ -132,6 +132,6 @@ Your auth provider's `authenticateToken` callback must recognize whatever creden
 
 - [Auth overview](https://mastra.ai/docs/server/auth): Available auth providers and how they work
 - [Token-based auth](https://mastra.ai/docs/server/auth/simple-auth): Token-to-user mapping authentication
-- [Worker deployment](https://mastra.ai/guides/deployment/mastra-workers): Set up split worker processes
+- [Worker deployment](https://mastra.ai/docs/deployment/workers): Set up split worker processes
 - [Workers reference](https://mastra.ai/reference/workers/overview): Configuration details for all worker types
 - [CLI reference](https://mastra.ai/reference/cli/mastra): `mastra worker build` and `mastra worker start`

package/.docs/docs/server/auth.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Auth overview
+# Auth
 
 Mastra lets you choose how you handle authentication, so you can secure access to your API and [Studio](https://mastra.ai/docs/studio/overview) using the identity system that fits your stack.
 
@@ -25,8 +25,8 @@ See [Custom API Routes](https://mastra.ai/docs/server/custom-api-routes) for con
 
 ### Built-in
 
-- [Simple Auth](https://mastra.ai/docs/server/auth/simple-auth): Token-to-user mapping for development and API keys
-- [JSON Web Token (JWT)](https://mastra.ai/docs/server/auth/jwt): HMAC-signed JWT verification
+- [Simple Auth](https://mastra.ai/docs/server/auth/simple-auth)
+- [JSON Web Token](https://mastra.ai/docs/server/auth/jwt)
 
 ### Third-party integrations
 
@@ -41,5 +41,5 @@ See [Custom API Routes](https://mastra.ai/docs/server/custom-api-routes) for con
 
 ### Advanced
 
-- [Composite Auth](https://mastra.ai/docs/server/auth/composite-auth): Combine multiple auth providers
-- [Custom Auth Provider](https://mastra.ai/docs/server/auth/custom-auth-provider): Build your own provider
+- [Composite Auth](https://mastra.ai/docs/server/auth/composite-auth)
+- [Custom Provider](https://mastra.ai/docs/server/auth/custom-auth-provider)

package/.docs/docs/server/mastra-client.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Mastra client SDK
+# Mastra client
 
 The Mastra Client SDK provides a concise and type-safe interface for interacting with your [Mastra Server](https://mastra.ai/docs/server/mastra-server) from your client environment.
 

package/.docs/docs/server/mastra-server.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Server overview
+# Server
 
 Mastra runs as an HTTP server that exposes your agents, workflows, and other functionality as API endpoints. The server handles request routing, middleware execution, authentication, and streaming responses.
 

package/.docs/docs/storage/overview.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Storage overview
+# Storage
 
 Storage is the persistence layer for the Mastra runtime. It keeps memory, workflow state, observability data, eval results, schedules, and long-running agent state available after a process restarts.
 
@@ -188,25 +188,26 @@ You can also route `observability` to a dedicated analytics backend. See the [ob
 
 ## Supported providers
 
-Each provider page includes installation instructions, configuration parameters, and usage examples:
+Each provider page includes installation instructions, configuration parameters, and usage examples. libSQL is the fastest path for local development because it doesn't require running a separate database server.
 
+- [Aurora DSQL](https://mastra.ai/integrations/databases/aurora-dsql)
+- [ClickHouse](https://mastra.ai/integrations/databases/clickhouse)
 - [Cloudflare D1](https://mastra.ai/integrations/databases/cloudflare-d1)
-- [Cloudflare KV & Durable Objects](https://mastra.ai/integrations/databases/cloudflare-kv)
+- [Cloudflare KV](https://mastra.ai/integrations/databases/cloudflare-kv)
 - [Convex](https://mastra.ai/integrations/databases/convex)
+- [DuckDB](https://mastra.ai/integrations/databases/duckdb)
 - [DynamoDB](https://mastra.ai/integrations/databases/dynamodb)
 - [Google Cloud Spanner](https://mastra.ai/integrations/databases/spanner)
 - [LanceDB](https://mastra.ai/integrations/databases/lancedb)
 - [libSQL](https://mastra.ai/integrations/databases/libsql)
-- [Microsoft SQL Server](https://mastra.ai/integrations/databases/mssql)
 - [MongoDB](https://mastra.ai/integrations/databases/mongodb)
+- [MSSQL](https://mastra.ai/integrations/databases/mssql)
 - [Neon Postgres](https://mastra.ai/integrations/databases/neon)
 - [OracleDB](https://mastra.ai/integrations/databases/oracledb)
 - [PostgreSQL](https://mastra.ai/integrations/databases/postgresql)
 - [Redis](https://mastra.ai/integrations/databases/redis)
 - [Upstash](https://mastra.ai/integrations/databases/upstash)
 
-> **Tip:** libSQL is the fastest path for local development because it doesn't require running a separate database server.
-
 ## Next steps
 
 - [Composite storage](https://mastra.ai/reference/storage/composite)

package/.docs/docs/workflows/human-in-the-loop.md

@@ -1,12 +1,12 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Human-in-the-loop (HITL)
+# Human-in-the-loop
 
 Some workflows need to pause for human input before continuing. When a workflow is [suspended](https://mastra.ai/docs/workflows/suspend-and-resume), it can return a message explaining why it paused and what’s needed to proceed. The workflow can then either [resume](#resuming-workflows-with-human-input) or [bail](#handling-human-rejection-with-bail) based on the input received. This approach works well for manual approvals, rejections, gated decisions, or any step that requires human oversight.
 
 ## Pausing workflows for human input
 
-Human-in-the-loop input works much like [pausing a workflow](https://mastra.ai/docs/workflows/suspend-and-resume) using `suspend()`. The key difference is that when human input is required, you can return `suspend()` with a payload that provides context or guidance to the user on how to continue.
+Human-in-the-loop (HITL) input works much like [pausing a workflow](https://mastra.ai/docs/workflows/suspend-and-resume) using `suspend()`. The key difference is that when human input is required, you can return `suspend()` with a payload that provides context or guidance to the user on how to continue.
 
 ![Pausing a workflow with suspend()](/assets/images/workflows-suspend-4540783670f918109ac35beaf4db914b.jpg)
 

package/.docs/docs/workflows/overview.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Workflows overview
+# Workflows
 
 Workflows let you define complex sequences of tasks using clear, structured steps rather than relying on the reasoning of a single agent. They give you full control over how tasks are broken down and how data moves between them, plus what gets executed when. Workflows run using the built-in execution engine by default, or can be deployed to [workflow runners](https://mastra.ai/docs/deployment/workflow-runners) like Inngest for managed infrastructure.
 
@@ -539,7 +539,7 @@ Visit [Request Context](https://mastra.ai/docs/server/request-context) for more
 
 ## Related
 
-For a closer look at workflows, see our [Workflow Guide](https://mastra.ai/guides/guide/ai-recruiter), which walks through the core concepts with a practical example.
+For a closer look at workflows, see our [Workflow Guide](https://mastra.ai/blog/building-an-ai-recruiter), which walks through the core concepts with a practical example.
 
 - [Workflow State](https://mastra.ai/docs/workflows/workflow-state)
 - [Control Flow](https://mastra.ai/docs/workflows/control-flow)

package/.docs/docs/workspace/lsp.md

@@ -87,6 +87,7 @@ const workspace = new Workspace({
   lsp: {
     diagnosticTimeout: 4000,
     initTimeout: 8000,
+    maxOpenClients: 4,
     disableServers: ['eslint'],
     binaryOverrides: {
       typescript: '/custom/path/to/typescript-language-server --stdio',
@@ -99,10 +100,36 @@ const workspace = new Workspace({
 Use custom configuration when you need to:
 
 - Increase timeouts for large repositories
+- Limit retained language server processes
 - Disable specific language servers
 - Point Mastra at custom language server binaries
 - Add extra binary search paths in constrained environments
 
+### Limit retained clients
+
+Set `maxOpenClients` to a positive integer to limit the language server clients retained by a workspace. When the limit is reached, the workspace closes the least recently used client that has no active query lease. If every retained client is active, the next acquisition waits up to five seconds for a lease to be released. If no lease becomes available, `prepareQuery()` and `getDiagnostics()` return `null`, while `getDiagnosticsMulti()` omits the unavailable server.
+
+Workspaces retain an unlimited number of clients when `maxOpenClients` is omitted. Mastra Code sets `maxOpenClients` to `4` by default.
+
+### Release prepared queries
+
+When you call `prepareQuery()` directly, close the file before releasing the client lease. Use a `finally` block so the client can be evicted even if the query fails:
+
+```typescript
+const query = await workspace.lsp?.prepareQuery(filePath)
+
+if (query) {
+  try {
+    const hover = await query.client.queryHover(query.uri, position)
+  } finally {
+    query.client.notifyClose(filePath)
+    query.release()
+  }
+}
+```
+
+During workspace teardown, Mastra waits up to five seconds for active leases to be released before it forces language server shutdown.
+
 ## Custom language servers
 
 By default, Mastra includes built-in support for TypeScript, JavaScript, Python, Go, and Rust. To use LSP inspection with other languages (e.g. PHP, Ruby, Java, Kotlin, Swift, Elixir), register a custom language server via the `servers` field:

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

@@ -19,18 +19,17 @@ A sandbox provider executes commands in a controlled environment:
 
 ## Supported providers
 
-- [`LocalSandbox`](https://mastra.ai/reference/workspace/local-sandbox): Executes commands on the local machine
-- [`AgentCoreRuntimeSandbox`](https://mastra.ai/integrations/sandboxes/agentcore): Executes commands in AWS Bedrock AgentCore Runtime sessions
-- [`AppleContainerSandbox`](https://mastra.ai/integrations/sandboxes/apple-container): Executes commands in local OCI Linux containers using Apple's `container` CLI
-- [`BlaxelSandbox`](https://mastra.ai/integrations/sandboxes/blaxel): Executes commands in isolated Blaxel cloud sandboxes
-- [`DaytonaSandbox`](https://mastra.ai/integrations/sandboxes/daytona): Executes commands in isolated Daytona cloud sandboxes
-- [`DockerSandbox`](https://mastra.ai/integrations/sandboxes/docker): Executes commands in long-lived Docker containers on the local machine
-- [`E2BSandbox`](https://mastra.ai/integrations/sandboxes/e2b): Executes commands in isolated E2B cloud sandboxes
-- [`ModalSandbox`](https://mastra.ai/integrations/sandboxes/modal): Executes commands in isolated Modal cloud sandboxes
-- [`PlatformSandbox`](https://mastra.ai/reference/workspace/platform-sandbox): Executes commands in a sandbox tied to a Mastra Platform environment
-- [`RailwaySandbox`](https://mastra.ai/integrations/sandboxes/railway): Executes commands in ephemeral, isolated Railway cloud sandboxes
-- [`VercelSandbox`](https://mastra.ai/integrations/sandboxes/vercel): Executes commands in an ephemeral Vercel Sandbox Firecracker MicroVM
-- [`VercelServerlessSandbox`](https://mastra.ai/integrations/sandboxes/vercel): Executes commands as stateless Vercel serverless functions
+- [AgentCore](https://mastra.ai/integrations/sandboxes/agentcore)
+- [Apple Container](https://mastra.ai/integrations/sandboxes/apple-container)
+- [Blaxel](https://mastra.ai/integrations/sandboxes/blaxel)
+- [Daytona](https://mastra.ai/integrations/sandboxes/daytona)
+- [Docker](https://mastra.ai/integrations/sandboxes/docker)
+- [E2B](https://mastra.ai/integrations/sandboxes/e2b)
+- [LocalSandbox](https://mastra.ai/reference/workspace/local-sandbox)
+- [Mastra](https://mastra.ai/reference/workspace/platform-sandbox)
+- [Modal](https://mastra.ai/integrations/sandboxes/modal)
+- [Railway](https://mastra.ai/integrations/sandboxes/railway)
+- [Vercel](https://mastra.ai/integrations/sandboxes/vercel)
 
 ## Basic usage
 

package/.docs/integrations/agentic-ui/ai-sdk-ui.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Using AI SDK UI
+# AI SDK UI
 
 [AI SDK UI](https://sdk.vercel.ai) is a library of React utilities and components for building AI-powered interfaces. In this guide, you'll learn how to use `@mastra/ai-sdk` to convert Mastra's output to AI SDK-compatible formats, enabling you to use its hooks and components in your frontend.
 

package/.docs/integrations/agentic-ui/assistant-ui.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Using Assistant UI
+# Assistant UI
 
 [Assistant UI](https://assistant-ui.com) is the TypeScript/React library for AI Chat. Built on shadcn/ui and Tailwind CSS, it enables developers to create beautiful, enterprise-grade chat experiences in minutes.
 

package/.docs/integrations/agentic-ui/copilotkit.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Using CopilotKit
+# CopilotKit
 
 [CopilotKit](https://www.copilotkit.ai/) provides React components to quickly integrate customizable AI copilots into your application. Combined with Mastra, you can build AI apps with bidirectional state synchronization and interactive UIs.
 

package/.docs/integrations/agentic-ui/openui.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Using OpenUI
+# OpenUI
 
 [OpenUI](https://openui.com) is an open standard for generative UI. It pairs a compact streaming-first language (OpenUI Lang) with a React runtime and built-in component libraries, so model output can render as structured UI as it streams.
 

package/.docs/integrations/databases/postgresql.md

@@ -521,11 +521,11 @@ const stats = await storage.db.one(`
 
 PostgreSQL offers different index types optimized for specific scenarios:
 
-| Index Type          | Best For                                | Storage    | Speed                      |
-| ------------------- | --------------------------------------- | ---------- | -------------------------- |
-| **btree** (default) | Range queries, sorting, general purpose | Moderate   | Fast                       |
-| **hash**            | Equality comparisons only               | Small      | Very fast for `=`          |
-| **gin**             | JSONB, arrays, full-text search         | Large      | Fast for contains          |
-| **gist**            | Geometric data, full-text search        | Moderate   | Fast for nearest-neighbor  |
-| **spgist**          | Non-balanced data, text patterns        | Small      | Fast for specific patterns |
-| **brin**            | Large tables with natural ordering      | Very small | Fast for ranges            |
+| Index Type          | Best For                                | Storage size | Speed                      |
+| ------------------- | --------------------------------------- | ------------ | -------------------------- |
+| **btree** (default) | Range queries, sorting, general purpose | Moderate     | Fast                       |
+| **hash**            | Equality comparisons only               | Small        | Very fast for `=`          |
+| **gin**             | JSONB, arrays, full-text search         | Large        | Fast for contains          |
+| **gist**            | Geometric data, full-text search        | Moderate     | Fast for nearest-neighbor  |
+| **spgist**          | Non-balanced data, text patterns        | Small        | Fast for specific patterns |
+| **brin**            | Large tables with natural ordering      | Very small   | Fast for ranges            |

package/.docs/integrations/deploy/amazon-ec2.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Deploy Mastra to Amazon EC2
+# Amazon EC2
 
 Deploy your Mastra server to Amazon EC2. The server runs on infrastructure you manage and can support long-running agents and workflows.
 
@@ -10,7 +10,7 @@ Deploy your Mastra server to Amazon EC2. The server runs on infrastructure you m
 
 You'll need:
 
-- A [Mastra application](https://mastra.ai/guides/getting-started/quickstart)
+- A [Mastra application](https://mastra.ai/docs)
 - An [EC2](https://aws.amazon.com/ec2/) instance (Ubuntu or Amazon Linux) with Git and Node.js 22.13.0+ installed
 
 For production, you'll also need:

package/.docs/integrations/deploy/aws-bedrock-agentcore.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Deploy Mastra to Amazon Bedrock AgentCore
+# Amazon Bedrock AgentCore
 
 Deploy your Mastra application to [Amazon Bedrock AgentCore Runtime](https://docs.aws.amazon.com/bedrock-agentcore/) using the [AgentCore CLI](https://github.com/aws/agentcore-cli). The CLI scaffolds a bring-your-own-code (BYO) TypeScript project, builds the container with AWS CodeBuild, and provisions the runtime. A local Docker daemon isn't required for deployment.
 

package/.docs/integrations/deploy/aws-lambda.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Deploy Mastra to AWS Lambda
+# AWS Lambda
 
 Deploy your Mastra application to AWS Lambda using Docker containers and the [AWS Lambda Web Adapter](https://github.com/awslabs/aws-lambda-web-adapter). This approach runs your Mastra server as a containerized Lambda function with automatic scaling.
 
@@ -10,7 +10,7 @@ Deploy your Mastra application to AWS Lambda using Docker containers and the [AW
 
 You'll need:
 
-- A [Mastra application](https://mastra.ai/guides/getting-started/quickstart)
+- A [Mastra application](https://mastra.ai/docs)
 - An [AWS account](https://aws.amazon.com/) with permissions for Lambda, ECR, and IAM
 - **[AWS CLI](https://aws.amazon.com/cli/)** installed: Run `aws configure` to authenticate
 - **[Docker](https://www.docker.com/)** installed and running

package/.docs/integrations/deploy/azure-app-services.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Deploy Mastra to Azure App Services
+# Azure App Services
 
 Deploy your Mastra applications to Azure App Services.
 
@@ -10,7 +10,7 @@ Deploy your Mastra applications to Azure App Services.
 
 You'll need:
 
-- A [Mastra application](https://mastra.ai/guides/getting-started/quickstart)
+- A [Mastra application](https://mastra.ai/docs)
 - An [Azure account](https://azure.microsoft.com/) with an active subscription
 - A [GitHub repository](https://github.com/) containing your Mastra application
 

package/.docs/integrations/deploy/cloudflare.md

@@ -1,6 +1,6 @@
 > Discover all available pages from the documentation index: https://mastra.ai/llms.txt
 
-# Deploy Mastra to Cloudflare
+# Cloudflare
 
 Use `@mastra/deployer-cloudflare` to deploy your Mastra server to Cloudflare Workers. The deployer bundles your code and generates a `wrangler.jsonc` file conforming to Cloudflare's [wrangler configuration](https://developers.cloudflare.com/workers/wrangler/configuration/), ready to deploy with no additional configuration.
 
@@ -8,7 +8,7 @@ Use `@mastra/deployer-cloudflare` to deploy your Mastra server to Cloudflare Wor
 
 ## Before you begin
 
-You'll need a [Mastra application](https://mastra.ai/guides/getting-started/quickstart) and a [Cloudflare](https://cloudflare.com/) account.
+You'll need a [Mastra application](https://mastra.ai/docs) and a [Cloudflare](https://cloudflare.com/) account.
 
 > **Warning:** Cloudflare Workers 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.