@mastra/mcp-docs-server 1.1.35 → 1.1.36-alpha.3

package/.docs/{guides/deployment/mastra-platform.md → docs/mastra-platform/server.md}

@@ -1,46 +1,42 @@
-# Deploy to Mastra platform
+# Server on Mastra platform
 
-Mastra Server deploys your application as a production API server on cloud infrastructure. You get a stable API endpoint, environment variable management, custom domain support, and deploy history out of the box.
+Server on Mastra platform is a production deployment target that runs your Mastra application as an API server. Use it when you want the platform to build, deploy, host, and manage your Mastra server.
 
-> **Tip:** This guide covers deploying the standalone server generated by `mastra build`. If you need to deploy Studio to the Mastra platform, see [Studio deployment](https://mastra.ai/docs/studio/deployment) instead.
+You get a stable API endpoint, environment variable management, custom domain support, and deploy history out of the box.
 
-## Before you begin
+> **Note:** Server deploy provisions hosted storage automatically. If you override storage with [LibSQLStore](https://mastra.ai/reference/storage/libsql) and a file URL, switch to a remotely hosted database because Mastra platform uses an ephemeral filesystem.
 
-You'll need a [Mastra application](https://mastra.ai/guides/getting-started/quickstart) and a [Mastra platform](https://projects.mastra.ai) account.
+## Quickstart
 
-> **Warning:** Mastra platform uses an ephemeral filesystem, so any storage you configure (including observability storage) must be hosted externally. If you're using [LibSQLStore](https://mastra.ai/reference/storage/libsql) with a file URL, switch to a remotely hosted database.
+1. Follow the [get started guide](https://mastra.ai/docs) to create your first Mastra project.
 
-## Installation
+2. Install the `mastra` CLI globally:
 
-Install the `mastra` CLI globally:
+   **npm**:
 
-**npm**:
-
-```bash
-npm install -g mastra
-```
-
-**pnpm**:
+   ```bash
+   npm install -g mastra
+   ```
 
-```bash
-pnpm add -g mastra
-```
+   **pnpm**:
 
-**Yarn**:
+   ```bash
+   pnpm add -g mastra
+   ```
 
-```bash
-yarn global add mastra
-```
+   **Yarn**:
 
-**Bun**:
+   ```bash
+   yarn global add mastra
+   ```
 
-```bash
-bun add --global mastra
-```
+   **Bun**:
 
-## Deploy
+   ```bash
+   bun add --global mastra
+   ```
 
-1. Deploy your project:
+3. Deploy your project:
 
    ```bash
    mastra server deploy
@@ -54,7 +50,7 @@ bun add --global mastra
 
    See the [CLI reference](https://mastra.ai/reference/cli/mastra) for the full list of flags.
 
-2. Verify your deployment at the URL printed by the CLI. Append `/api/agents` to confirm it returns a JSON list of your agents.
+4. Verify your deployment at the URL printed by the CLI. Append `/api/agents` to confirm it returns a JSON list of your agents.
 
    > **Warning:** Set up [authentication](https://mastra.ai/docs/server/auth) before exposing your endpoints publicly.
 
@@ -181,11 +177,8 @@ The CLI reads `organizationId` and `projectId` from `.mastra-project.json` by de
 
 ## Related
 
-- [CLI reference: `mastra server deploy`](https://mastra.ai/reference/cli/mastra)
-- [CLI reference: `mastra server pause`](https://mastra.ai/reference/cli/mastra)
-- [CLI reference: `mastra server restart`](https://mastra.ai/reference/cli/mastra)
-- [CLI reference: `mastra studio deploy`](https://mastra.ai/reference/cli/mastra)
-- [CLI reference: `mastra auth tokens`](https://mastra.ai/reference/cli/mastra)
-- [Mastra platform overview](https://mastra.ai/docs/mastra-platform/overview)
-- [Studio deployment](https://mastra.ai/docs/studio/deployment)
-- [Deployment overview](https://mastra.ai/docs/deployment/overview)
+- [`mastra server deploy`](https://mastra.ai/reference/cli/mastra)
+- [`mastra server pause`](https://mastra.ai/reference/cli/mastra)
+- [`mastra server restart`](https://mastra.ai/reference/cli/mastra)
+- [`mastra studio deploy`](https://mastra.ai/reference/cli/mastra)
+- [`mastra auth tokens`](https://mastra.ai/reference/cli/mastra)

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

@@ -0,0 +1,81 @@
+# Studio on Mastra platform
+
+Studio on Mastra platform is a hosted visual environment for testing agents, running workflows, and inspecting traces. Use it when you want to share Studio with your team without hosting the Studio UI yourself.
+
+## Quickstart
+
+1. Follow the [get started guide](https://mastra.ai/docs) to create your first Mastra project.
+
+2. Install the `mastra` CLI globally:
+
+   **npm**:
+
+   ```bash
+   npm install -g mastra
+   ```
+
+   **pnpm**:
+
+   ```bash
+   pnpm add -g mastra
+   ```
+
+   **Yarn**:
+
+   ```bash
+   yarn global add mastra
+   ```
+
+   **Bun**:
+
+   ```bash
+   bun add --global mastra
+   ```
+
+3. Deploy Studio with a single command:
+
+   ```bash
+   mastra studio deploy
+   ```
+
+   On a successful deploy, the CLI outputs the URL of your deployed Studio instance.
+
+On your first deploy, the CLI prompts you to create a new project or select an existing one. It then creates a `.mastra-project.json` file in your project directory. This file links your local project to a platform project. It contains the `projectId`, `projectName`, and `organizationId`. Commit this file to your repository so CI/CD knows which project to deploy to.
+
+## How deploy works
+
+The `mastra studio deploy` command builds your project, compiles `src/mastra/` into `.mastra/output`, packages the output as an artifact ZIP, uploads it, and deploys it to a cloud sandbox.
+
+A deploy transitions through **queued → uploading → starting → running** or **failed** if something goes wrong. If a sandbox is already running for your project, the platform updates it in place with no downtime. Otherwise, it creates a fresh sandbox. Your instance URL is assigned per project slug and remains stable across deploys.
+
+See the [`mastra studio deploy` CLI reference](https://mastra.ai/reference/cli/mastra) for the full list of flags and CI/CD usage.
+
+## Environment files
+
+The deploy bundles environment variables from a `.env` or `.env.*` file in the project directory. If no env file is present, the deploy errors with `No env file found for deploy.` after the build step. Add at least an empty `.env` file before running the command.
+
+When multiple env files are present, the CLI prompts you to pick one. To select non-interactively, pass `--env-file`:
+
+```bash
+mastra studio deploy --env-file .env.production --yes
+```
+
+This is also how you target multiple environments from a single codebase: maintain one env file per environment, such as `.env.staging` and `.env.production`, and pass the right one to each deploy. Each environment still requires its own Mastra platform project. See [Configuration](https://mastra.ai/docs/mastra-platform/configuration) for the multi-environment pattern.
+
+## Create a new project non-interactively
+
+`mastra studio deploy` can create a project on first run. If `--project <name>` doesn't match an existing project, the CLI uses the value as the new project name and creates it after confirmation. Combined with `--yes`, this is fully scriptable:
+
+```bash
+mastra studio deploy --project "my-new-project" --yes
+```
+
+Use this from CI or AI coding agents instead of `mastra studio projects create`, which is interactive only.
+
+## Self-host Studio
+
+To deploy Studio on your own infrastructure, see [Studio deployment](https://mastra.ai/docs/studio/deployment).
+
+## Related
+
+- [`mastra studio deploy`](https://mastra.ai/reference/cli/mastra)

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

@@ -1,6 +1,6 @@
 # Observability overview
 
-Mastra's observability system gives you visibility into every agent run, workflow step, tool call, and model interaction. It captures three complementary signals that work together to help you understand what your application is doing and why.
+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 three complementary signals that work together to help you understand what your application is doing and why.
 
 - [**Tracing**](https://mastra.ai/docs/observability/tracing/overview): Records every operation as a hierarchical timeline of spans, capturing inputs, outputs, token usage, and timing.
 - [**Logging**](https://mastra.ai/docs/observability/logging): Forwards structured log entries from your application and Mastra internals to observability storage, correlated to traces automatically.
@@ -24,9 +24,9 @@ Logs are correlated to traces automatically. Every `logger.info()`, `logger.warn
 
 All three signals share correlation IDs (trace ID, span ID, entity type, entity name), so you can jump between a metric spike, the traces behind it, and the logs within those traces.
 
-## Get started
+## Quickstart
 
-Install `@mastra/observability` and a storage backend:
+Install `@mastra/observability` and storage backends that support traces and metrics:
 
 **npm**:
 
@@ -83,7 +83,7 @@ export const mastra = new Mastra({
         serviceName: 'mastra',
         exporters: [
           new MastraStorageExporter(), // Persists observability events to Mastra Storage
-          new MastraPlatformExporter(), // Sends observability events to Mastra Platform (if MASTRA_CLOUD_ACCESS_TOKEN is set)
+          new MastraPlatformExporter(), // Sends observability events to Mastra platform (if MASTRA_PLATFORM_ACCESS_TOKEN is set)
         ],
         spanOutputProcessors: [
           new SensitiveDataFilter(), // Redacts sensitive data like passwords, tokens, keys
@@ -96,6 +96,10 @@ export const mastra = new Mastra({
 
 This enables tracing, log forwarding, and metrics. Mastra also supports external tracing providers like Langfuse, Datadog, and any OpenTelemetry-compatible platform. See [Tracing](https://mastra.ai/docs/observability/tracing/overview) for configuration details.
 
+## Mastra platform
+
+For hosted traces, logs, and metrics across projects and deploys, see [Observability on Mastra platform](https://mastra.ai/docs/mastra-platform/observability).
+
 ## Storage
 
 Not all storage backends support every signal. Traces and logs work with most backends, but metrics require an OLAP-capable store like DuckDB (development) or ClickHouse (production). For the full compatibility list, see [storage provider support](https://mastra.ai/docs/observability/tracing/exporters/mastra-storage).
@@ -108,4 +112,5 @@ For production environments with high traffic, use composite storage to route th
 - [Logging](https://mastra.ai/docs/observability/logging)
 - [Metrics](https://mastra.ai/docs/observability/metrics/overview)
 - [Mastra Studio](https://mastra.ai/docs/studio/observability)
-- [Automatic metrics reference](https://mastra.ai/reference/observability/metrics/automatic-metrics)
+- [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/exporters/mastra-platform.md

@@ -1,10 +1,10 @@
-# Mastra Platform exporter
+# Mastra platform exporter
 
 The `MastraPlatformExporter` sends traces, logs, metrics, scores, and feedback to the Mastra platform. Use it to route observability data from any Mastra app to a hosted project in the Mastra platform.
 
 > **Note:** `MastraPlatformExporter` was previously called `CloudExporter`. The original `CloudExporter` class is still exported from `@mastra/observability` for backward compatibility, but it is deprecated. New code should use `MastraPlatformExporter`.
 
-> **Self-hosted or standalone apps:** If you host your Mastra application on your own infrastructure (not on Mastra Platform), you still need a deployed Studio project to view traces, logs, and metrics. `MastraPlatformExporter` sends data to a Studio project, so one must exist before you can use it.
+> **Self-hosted or standalone apps:** If you host your Mastra application on your own infrastructure (not on Mastra platform), you still need a deployed Studio project to view traces, logs, and metrics. `MastraPlatformExporter` sends data to a Studio project, so one must exist before you can use it.
 >
 > 1. [Create a Mastra project](https://mastra.ai/guides/getting-started/quickstart) if you don't have one yet.
 > 2. [Deploy Studio](https://mastra.ai/docs/studio/deployment) to the Mastra platform with `mastra studio deploy`.
@@ -13,8 +13,8 @@ The `MastraPlatformExporter` sends traces, logs, metrics, scores, and feedback t
 ## Version compatibility
 
 - `MastraPlatformExporter` is available starting in `@mastra/observability@1.12.0`. In `1.8.0` through `1.11.x` the same exporter ships only as `CloudExporter`; the constructor signature and environment variables are identical.
-- In `@mastra/observability@1.8.0` through `1.9.1`, set `MASTRA_CLOUD_TRACES_ENDPOINT=https://observability.mastra.ai` in addition to `MASTRA_CLOUD_ACCESS_TOKEN` and `MASTRA_PROJECT_ID`.
-- Starting in `@mastra/observability@1.9.2`, the exporter defaults to `https://observability.mastra.ai`, so `MASTRA_CLOUD_TRACES_ENDPOINT` is only required when you want to send telemetry to a different collector.
+- In `@mastra/observability@1.8.0` through `1.9.1`, set `MASTRA_PLATFORM_OBSERVABILITY_ENDPOINT=https://observability.mastra.ai` in addition to `MASTRA_PLATFORM_ACCESS_TOKEN` and `MASTRA_PROJECT_ID`.
+- Starting in `@mastra/observability@1.9.2`, the exporter defaults to `https://observability.mastra.ai`, so `MASTRA_PLATFORM_OBSERVABILITY_ENDPOINT` is only required when you want to send telemetry to a different collector.
 
 ## Quickstart
 
@@ -28,7 +28,7 @@ Run the following command:
 mastra auth tokens create exporter-token
 ```
 
-This command prints a token secret that you can use as `MASTRA_CLOUD_ACCESS_TOKEN`.
+This command prints a token secret that you can use as `MASTRA_PLATFORM_ACCESS_TOKEN`.
 
 If you already have an access token, copy the **Observability** value from the Mastra platform instead. You can find it in either of these places:
 
@@ -38,7 +38,7 @@ If you already have an access token, copy the **Observability** value from the M
 Set the token as an environment variable:
 
 ```bash
-MASTRA_CLOUD_ACCESS_TOKEN=<your-cloud-access-token>
+MASTRA_PLATFORM_ACCESS_TOKEN=<your-platform-access-token>
 ```
 
 ### 2. Find your `projectId`
@@ -74,20 +74,20 @@ MASTRA_PROJECT_ID=<your-project-id>
 Set both values in your environment so `MastraPlatformExporter` can authenticate and route telemetry to the correct project:
 
 ```bash
-MASTRA_CLOUD_ACCESS_TOKEN=<your-cloud-access-token>
+MASTRA_PLATFORM_ACCESS_TOKEN=<your-platform-access-token>
 MASTRA_PROJECT_ID=<your-project-id>
 ```
 
 If you use `@mastra/observability@1.8.0` through `1.9.1`, also set the Mastra platform collector explicitly:
 
 ```bash
-MASTRA_CLOUD_TRACES_ENDPOINT=https://observability.mastra.ai
+MASTRA_PLATFORM_OBSERVABILITY_ENDPOINT=https://observability.mastra.ai
 ```
 
-If you want to send telemetry somewhere other than Mastra platform, set `MASTRA_CLOUD_TRACES_ENDPOINT` as well. Pass either a base origin or a full traces publish URL ending in `/spans/publish`.
+If you want to send telemetry somewhere other than Mastra platform, set `MASTRA_PLATFORM_OBSERVABILITY_ENDPOINT` as well. Pass either a base origin or a full traces publish URL ending in `/spans/publish`.
 
 ```bash
-MASTRA_CLOUD_TRACES_ENDPOINT=https://collector.example.com
+MASTRA_PLATFORM_OBSERVABILITY_ENDPOINT=https://collector.example.com
 ```
 
 When you pass a base origin, `MastraPlatformExporter` derives the matching publish URLs for traces, logs, metrics, scores, and feedback automatically.
@@ -124,7 +124,7 @@ If you prefer, rely entirely on environment variables:
 new MastraPlatformExporter()
 ```
 
-With `MASTRA_CLOUD_ACCESS_TOKEN` and `MASTRA_PROJECT_ID` set, `MastraPlatformExporter` sends data to the Mastra platform project you configured. If you also set `MASTRA_CLOUD_TRACES_ENDPOINT`, it sends data to that collector instead.
+With `MASTRA_PLATFORM_ACCESS_TOKEN` and `MASTRA_PROJECT_ID` set, `MastraPlatformExporter` sends data to the Mastra platform project you configured. If you also set `MASTRA_PLATFORM_OBSERVABILITY_ENDPOINT`, it sends data to that collector instead.
 
 > **Note:** Visit [MastraPlatformExporter reference](https://mastra.ai/reference/observability/tracing/exporters/mastra-platform-exporter) for the full list of configuration options.
 
@@ -156,10 +156,10 @@ export const mastra = new Mastra({
 
 ## Complete configuration
 
-`MastraPlatformExporter` defaults to Mastra platform. If you want to send telemetry to a different collector, set `MASTRA_CLOUD_TRACES_ENDPOINT` in your environment or pass `endpoint` in code.
+`MastraPlatformExporter` defaults to Mastra platform. If you want to send telemetry to a different collector, set `MASTRA_PLATFORM_OBSERVABILITY_ENDPOINT` in your environment or pass `endpoint` in code.
 
 ```bash
-MASTRA_CLOUD_TRACES_ENDPOINT=https://collector.example.com
+MASTRA_PLATFORM_OBSERVABILITY_ENDPOINT=https://collector.example.com
 ```
 
 The following example demonstrates how to override the collector endpoint and batching behavior in code:

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

@@ -61,7 +61,7 @@ export const mastra = new Mastra({
         serviceName: 'mastra',
         exporters: [
           new MastraStorageExporter(), // Persists observability events to Mastra Storage
-          new MastraPlatformExporter(), // Sends observability events to Mastra Platform (requires MASTRA_CLOUD_ACCESS_TOKEN)
+          new MastraPlatformExporter(), // Sends observability events to Mastra platform (requires MASTRA_PLATFORM_ACCESS_TOKEN)
         ],
         spanOutputProcessors: [new SensitiveDataFilter()],
       },

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

@@ -33,7 +33,7 @@ export const mastra = new Mastra({
         serviceName: 'mastra',
         exporters: [
           new MastraStorageExporter(), // Persists observability events to Mastra Storage
-          new MastraPlatformExporter(), // Sends observability events to Mastra Platform (if MASTRA_CLOUD_ACCESS_TOKEN is set)
+          new MastraPlatformExporter(), // Sends observability events to Mastra platform (if MASTRA_PLATFORM_ACCESS_TOKEN is set)
         ],
         spanOutputProcessors: [
           new SensitiveDataFilter(), // Redacts sensitive data like passwords, tokens, keys
@@ -57,7 +57,7 @@ This configuration includes:
 - **Exporters**:
 
   - `MastraStorageExporter` - Persists observability events to Mastra Storage
-  - `MastraPlatformExporter` - Sends observability events to Mastra Platform (requires `MASTRA_CLOUD_ACCESS_TOKEN`)
+  - `MastraPlatformExporter` - Sends observability events to Mastra platform (requires `MASTRA_PLATFORM_ACCESS_TOKEN`)
 
 - **Span Output Processors**: `SensitiveDataFilter` - Redacts sensitive fields
 
@@ -69,8 +69,8 @@ Exporters determine where your trace data is sent and how it's stored. They inte
 
 Mastra provides two built-in exporters:
 
-- **[Mastra Storage](https://mastra.ai/docs/observability/tracing/exporters/mastra-storage)** - Persists observability events to Mastra Storage for viewing in Studio
-- **[Mastra Platform](https://mastra.ai/docs/observability/tracing/exporters/mastra-platform)** - Sends observability events to Mastra Platform for production monitoring and collaboration
+- **[Mastra Storage](https://mastra.ai/docs/observability/tracing/exporters/mastra-storage)**: Persists observability events to Mastra Storage for viewing in Studio
+- **[Mastra platform](https://mastra.ai/docs/observability/tracing/exporters/mastra-platform)**: Sends observability events to Mastra platform for production monitoring and collaboration
 
 ### External Exporters
 

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

@@ -57,6 +57,7 @@ export const mastraClient = new MastraClient({
 The Mastra Client SDK exposes all resources served by the Mastra Server.
 
 - **[Agents](https://mastra.ai/reference/client-js/agents)**: Generate responses and stream conversations.
+- **[A2A](https://mastra.ai/docs/agents/a2a)**: Discover agents through agent cards and work with task-based A2A streams.
 - **[Memory](https://mastra.ai/reference/client-js/memory)**: Manage conversation threads and message history.
 - **[Tools](https://mastra.ai/reference/client-js/tools)**: Executed and managed tools.
 - **[Workflows](https://mastra.ai/reference/client-js/workflows)**: Trigger workflows and track their execution.

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

@@ -12,6 +12,7 @@ Mastra runs as an HTTP server that exposes your agents, workflows, and other fun
 - **[Server Adapters](https://mastra.ai/docs/server/server-adapters)**: Run Mastra with Express, Hono, or your own HTTP server instead of the generated server.
 - **[Custom Adapters](https://mastra.ai/docs/server/custom-adapters)**: Build adapters for frameworks not officially supported.
 - **[Mastra Client SDK](https://mastra.ai/docs/server/mastra-client)**: Type-safe client for calling agents, workflows, and tools from browser or server environments.
+- **[A2A](https://mastra.ai/docs/agents/a2a)**: Expose agents through A2A agent cards, task streams, and push notifications.
 - **[Authentication](https://mastra.ai/docs/server/auth)**: Secure endpoints with JWT, Clerk, Supabase, Firebase, Auth0, or WorkOS.
 
 ## Configuration
@@ -33,7 +34,7 @@ export const mastra = new Mastra({
 
 ## Deploy your server
 
-Mastra servers can be deployed to any Node.js-compatible environment. Deploy it to production using the [Mastra platform](https://mastra.ai/docs/mastra-platform/overview) or your own infastructure. Visit the [deployment docs](https://mastra.ai/docs/deployment/overview) to learn how.
+Mastra servers can be deployed to any Node.js-compatible environment. Deploy it to production using the [Mastra platform](https://mastra.ai/docs/mastra-platform/overview) or your own infrastructure. Visit the [deployment docs](https://mastra.ai/docs/deployment/overview) to learn how.
 
 ## Server architecture
 

package/.docs/docs/studio/deployment.md

@@ -61,43 +61,7 @@ The command uses Node's built-in `http` module and [`serve-handler`](https://www
 
 ## Mastra platform
 
-The [Mastra platform](https://mastra.ai/docs/mastra-platform/overview) allows you to deploy your Studio to the cloud. Run a single CLI command, and the platform handles provisioning, deployment, and hosting.
-
-Run the following command:
-
-```bash
-mastra studio deploy
-```
-
-> **Note:** See the [CLI reference](https://mastra.ai/reference/cli/mastra) for the full list of flags and CI/CD usage.
-
-This builds your project (compiling `src/mastra/` into `.mastra/output`), packages it as an artifact ZIP, uploads it, and deploys it to a cloud sandbox.
-
-If this is your first deploy, the CLI will prompt you to create a new project or select an existing one. The `.mastra-project.json` file is written automatically.
-
-A deploy transitions through **queued → uploading → starting → running** (or **failed** if something goes wrong). If a sandbox is already running for your project, the platform hot-updates it in place with no downtime. Otherwise it creates a fresh sandbox. Your instance URL is assigned per project slug and remains stable across deploys.
-
-### Env file requirement
-
-The deploy bundles environment variables from a `.env` or `.env.*` file in the project directory. If no env file is present, the deploy errors with `No env file found for deploy.` after the build step. Add at least an empty `.env` file before running the command.
-
-When multiple env files are present, the CLI prompts you to pick one. To select non-interactively, pass `--env-file`:
-
-```bash
-mastra studio deploy --env-file .env.production --yes
-```
-
-This is also how you target multiple environments from a single codebase: maintain one env file per environment (for example `.env.staging`, `.env.production`) and pass the right one to each deploy. Each environment still requires its own Mastra platform project — see [Configuration](https://mastra.ai/docs/mastra-platform/configuration) for the multi-environment pattern.
-
-### Create a new project non-interactively
-
-`mastra studio deploy` can create a project on first run. If `--project <name>` does not match an existing project, the CLI uses the value as the new project name and creates it after confirmation. Combined with `--yes`, this is fully scriptable:
-
-```bash
-mastra studio deploy --project "my-new-project" --yes
-```
-
-Use this from CI or AI coding agents instead of `mastra studio projects create`, which is interactive only.
+For hosted Studio on Mastra platform, see [Studio on Mastra platform](https://mastra.ai/docs/mastra-platform/studio).
 
 ## Running a server
 

package/.docs/docs/studio/observability.md

@@ -6,27 +6,7 @@ Studio includes these observability views:
 - **Traces** for individual request inspection
 - **Logs** for browsing internal and application logs
 
-All require an [observability storage backend](#quickstart) to be configured.
-
-## Metrics
-
-A dashboard that summarizes agent, workflow, and tool performance over a configurable time range (last 24 hours to 30 days). The top row shows total agent runs, model cost, token consumption, and average scorer performance. Below that, detailed cards break down model usage and cost per model, token usage per agent, trace volume with completed and error counts, latency percentiles (p50 and p95), and scorer trends over time.
-
-Visit the [metrics overview](https://mastra.ai/docs/observability/metrics/overview) for more details.
-
-> **Note:** Metrics require a separate OLAP store for observability. Relational databases like PostgreSQL, LibSQL, etc. are not supported for metrics. In-memory storage resets on restart.
-
-## Traces
-
-When you run an agent or workflow, the Observability tab displays traces that highlight the key AI operations such as model calls, tool executions, and workflow steps. Follow these traces to see how data moves, where time is spent, and what's happening under the hood.
-
-Tracing filters out low-level framework details so your traces stay focused and readable. Visit the [tracing overview](https://mastra.ai/docs/observability/tracing/overview) for more details.
-
-## Logs
-
-Browse internal Mastra logs forwarded to your observability storage. Logs provide full-text search (across message content, entity names, and trace IDs), date presets (last 24 hours to 30 days), and multi-select filters for level, entity type, and entity name. Selecting a log opens a detail panel showing the full message, structured data, and metadata. If the log is correlated with a trace, you can navigate directly to the trace and span timeline.
-
-Log forwarding is enabled by default when you configure observability. See [logging](https://mastra.ai/docs/observability/logging) for level configuration, query examples, and customization details.
+All require an observability storage backend to be configured.
 
 ## Quickstart
 
@@ -87,7 +67,7 @@ export const mastra = new Mastra({
         serviceName: 'mastra',
         exporters: [
           new MastraStorageExporter(), // Persists observability events to Mastra Storage
-          new MastraPlatformExporter(), // Sends observability events to Mastra Platform (if MASTRA_CLOUD_ACCESS_TOKEN is set)
+          new MastraPlatformExporter(), // Sends observability events to Mastra platform (if MASTRA_PLATFORM_ACCESS_TOKEN is set)
         ],
         spanOutputProcessors: [
           new SensitiveDataFilter(), // Redacts sensitive data like passwords, tokens, keys
@@ -98,9 +78,34 @@ export const mastra = new Mastra({
 })
 ```
 
+## Mastra platform
+
+For hosted traces, logs, and metrics across projects and deploys, see [Observability on Mastra platform](https://mastra.ai/docs/mastra-platform/observability).
+
+## Metrics
+
+A dashboard that summarizes agent, workflow, and tool performance over a configurable time range (last 24 hours to 30 days). The top row shows total agent runs, model cost, token consumption, and average scorer performance. Below that, detailed cards break down model usage and cost per model, token usage per agent, trace volume with completed and error counts, latency percentiles (p50 and p95), and scorer trends over time.
+
+Visit the [metrics overview](https://mastra.ai/docs/observability/metrics/overview) for more details.
+
+> **Note:** Metrics require a separate OLAP store for observability. Relational databases like PostgreSQL, LibSQL, etc. aren't supported for metrics. In-memory storage resets on restart.
+
+## Traces
+
+When you run an agent or workflow, the Observability tab displays traces that highlight the key AI operations such as model calls, tool executions, and workflow steps. Follow these traces to see how data moves, where time is spent, and what's happening under the hood.
+
+Tracing filters out low-level framework details so your traces stay focused and readable. Visit the [tracing overview](https://mastra.ai/docs/observability/tracing/overview) for more details.
+
+## Logs
+
+Browse internal Mastra logs forwarded to your observability storage. Logs provide full-text search (across message content, entity names, and trace IDs), date presets (last 24 hours to 30 days), and multi-select filters for level, entity type, and entity name. Selecting a log opens a detail panel showing the full message, structured data, and metadata. If the log is correlated with a trace, you can navigate directly to the trace and span timeline.
+
+Log forwarding is enabled by default when you configure observability. See [logging](https://mastra.ai/docs/observability/logging) for level configuration, query examples, and customization details.
+
 ## Related
 
 - [Observability overview](https://mastra.ai/docs/observability/overview)
 - [Metrics overview](https://mastra.ai/docs/observability/metrics/overview)
 - [Tracing overview](https://mastra.ai/docs/observability/tracing/overview)
-- [Logging](https://mastra.ai/docs/observability/logging)
+- [Logging](https://mastra.ai/docs/observability/logging)
+- [Mastra platform observability](https://mastra.ai/docs/mastra-platform/observability)

package/.docs/docs/studio/overview.md

@@ -34,14 +34,14 @@ bun run dev
 
 Once the server is running, you can:
 
-- Open the Studio UI at [http://localhost:4111](http://localhost:4111/) to interact with your agents, workflows, and tools.
-- Visit <http://localhost:4111/swagger-ui> to discover and interact with the underlying REST API.
+- Open the Studio UI at [`localhost:4111`](http://localhost:4111/) to interact with your agents, workflows, and tools.
+- Visit [`localhost:4111/swagger-ui`](http://localhost:4111/swagger-ui) to discover and interact with the underlying REST API.
 
 While Studio is running, you can edit your [agents](https://mastra.ai/docs/agents/overview), [workflows](https://mastra.ai/docs/workflows/overview), and other parts of your Mastra application in real time.
 
 ## Deploy Studio
 
-When you're ready to share Studio with your team, you can deploy it to production using the [Mastra platform](https://mastra.ai/docs/mastra-platform/overview) or your own infrastructure. Visit the [deployment docs](https://mastra.ai/docs/studio/deployment) to learn how.
+When you're ready to share Studio with your team, you can deploy it to production using [Studio on Mastra platform](https://mastra.ai/docs/mastra-platform/studio) or your own infrastructure. Visit the [deployment docs](https://mastra.ai/docs/studio/deployment) to learn how.
 
 ## Primitives
 

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

@@ -10,9 +10,7 @@ If you need more control over the setup, see the [manual installation guide](htt
 
 ## Initialize Mastra
 
-You can run `create mastra` anywhere on your machine.
-
-When prompted, choose a provider (e.g. OpenAI) and enter your key:
+You can run `create mastra` anywhere on your machine. Start the setup wizard:
 
 **npm**:
 
@@ -38,7 +36,9 @@ yarn create mastra
 bunx create-mastra
 ```
 
-This creates a new directory for your project with a `src/mastra` folder containing an example weather agent and the following files:
+You'll be prompted for various configuration options, including your LLM provider and whether to enable [Observability](https://mastra.ai/docs/mastra-platform/observability) on the Mastra platform.
+
+The wizard creates a new directory for your project with a `src/mastra` folder containing an example weather agent and the following files:
 
 - `index.ts`: Entry point for all Mastra-related code and configuration
 - `agents/weather-agent.ts`: A weather agent with a prompt that uses the tool

package/.docs/guides/migrations/mastra-cloud.md

@@ -254,7 +254,7 @@ export const mastra = new Mastra({
 ```
 
 - `MastraStorageExporter` persists observability events to Mastra Storage for [Studio](https://mastra.ai/docs/studio/observability).
-- `MastraPlatformExporter` sends observability events to Mastra Platform when `MASTRA_CLOUD_ACCESS_TOKEN` is set.
+- `MastraPlatformExporter` sends observability events to Mastra platform when `MASTRA_PLATFORM_ACCESS_TOKEN` is set.
 - `SensitiveDataFilter` redacts passwords, tokens, and keys from span data before export.
 
 See the [observability overview](https://mastra.ai/docs/observability/overview) for the full configuration, including composite storage with DuckDB for metrics.
@@ -295,7 +295,7 @@ MASTRA_PROJECT_ID="<staging-id>" mastra studio deploy --env-file .env.staging --
 MASTRA_PROJECT_ID="<production-id>" mastra studio deploy --env-file .env.production --yes
 ```
 
-Each environment ends up with its own Studio URL and its own observability data. Send `MASTRA_CLOUD_ACCESS_TOKEN` and `MASTRA_PROJECT_ID` per environment so `MastraPlatformExporter` routes traces to the correct project.
+Each environment ends up with its own Studio URL and its own observability data. Send `MASTRA_PLATFORM_ACCESS_TOKEN` and `MASTRA_PROJECT_ID` per environment so `MastraPlatformExporter` routes traces to the correct project.
 
 ## Deploy Server (optional)
 
@@ -305,7 +305,7 @@ If you need a production API endpoint, deploy a Server:
 mastra server deploy
 ```
 
-This creates a separate deployment with a stable API URL, environment variable management, and custom domain support. See the [Server deployment guide](https://mastra.ai/guides/deployment/mastra-platform) for the full walkthrough.
+This creates a separate deployment with a stable API URL, environment variable management, and custom domain support. See the [Server deployment guide](https://mastra.ai/docs/mastra-platform/server) for the full walkthrough.
 
 > **Note:** Environment variables from `.env`, `.env.local`, and `.env.production` are included automatically on first deploy. After that, manage env vars through the [web dashboard](https://projects.mastra.ai). Review and sanitize these files before first deploy to avoid uploading development-only or personal secrets.
 
@@ -387,8 +387,8 @@ Update any clients pointing to your old Mastra Cloud URL to the new Server or St
 
 ## Related
 
-- [Observability overview](https://mastra.ai/docs/observability/overview)
-- [Studio deployment](https://mastra.ai/docs/studio/deployment)
-- [Server deployment](https://mastra.ai/guides/deployment/mastra-platform)
-- [CLI reference](https://mastra.ai/reference/cli/mastra)
-- [Mastra platform overview](https://mastra.ai/docs/mastra-platform/overview)
+- [Mastra platform overview](https://mastra.ai/docs/mastra-platform/overview)
+- [Observability overview](https://mastra.ai/docs/mastra-platform/observability)
+- [Studio deployment](https://mastra.ai/docs/mastra-platform/studio)
+- [Server deployment](https://mastra.ai/docs/mastra-platform/server)
+- [CLI reference](https://mastra.ai/reference/cli/mastra)

package/.docs/guides/migrations/upgrade-to-v1/tracing.md

@@ -6,7 +6,7 @@ The observability system has been restructured in v1 with a dedicated `@mastra/o
 >
 > Complete this migration in the same change that bumps your Mastra packages, and verify traces appear in [Mastra Studio](https://mastra.ai/docs/studio/observability) before considering the upgrade complete. If you previously hosted on Mastra Cloud, also follow the [Mastra Cloud migration guide](https://mastra.ai/guides/migrations/mastra-cloud) — the new platform requires a new access token and a Studio project before `MastraPlatformExporter` can route data to it.
 
-> **Exporter rename:** `MastraPlatformExporter` (sends data to Mastra Platform) replaces the previous `CloudExporter`, and `MastraStorageExporter` (persists data to Mastra Storage) replaces the previous `DefaultExporter`. The original classes still ship from `@mastra/observability` and behave identically, but they are deprecated. New code should use `MastraPlatformExporter` and `MastraStorageExporter`; existing imports of `CloudExporter`/`DefaultExporter` continue to work until they are removed in a future major version.
+> **Exporter rename:** `MastraPlatformExporter` (sends data to Mastra platform) replaces the previous `CloudExporter`, and `MastraStorageExporter` (persists data to Mastra Storage) replaces the previous `DefaultExporter`. The original classes still ship from `@mastra/observability` and behave identically, but they are deprecated. New code should use `MastraPlatformExporter` and `MastraStorageExporter`; existing imports of `CloudExporter`/`DefaultExporter` continue to work until they are removed in a future major version.
 
 ## Migration paths
 
@@ -52,7 +52,7 @@ export const mastra = new Mastra({
         serviceName: 'mastra',
         exporters: [
           new MastraStorageExporter(), // Persists observability events to Mastra Storage
-          new MastraPlatformExporter(), // Sends observability events to Mastra Platform (if MASTRA_CLOUD_ACCESS_TOKEN is set)
+          new MastraPlatformExporter(), // Sends observability events to Mastra platform (if MASTRA_PLATFORM_ACCESS_TOKEN is set)
         ],
         spanOutputProcessors: [
           new SensitiveDataFilter(), // Redacts sensitive data like passwords, tokens, keys

package/.docs/models/index.md

@@ -1,6 +1,6 @@
 # Model Providers
 
-Mastra provides a unified interface for working with LLMs across multiple providers, giving you access to 3895 models from 110 providers through a single API.
+Mastra provides a unified interface for working with LLMs across multiple providers, giving you access to 3911 models from 112 providers through a single API.
 
 ## Features
 

package/.docs/models/providers/alibaba-cn.md

@@ -106,7 +106,7 @@ for await (const chunk of stream) {
 | `alibaba-cn/qwen3.5-flash`                      | 1.0M    |       |           |       |       |       | $0.17      | $2          |
 | `alibaba-cn/qwen3.5-plus`                       | 1.0M    |       |           |       |       |       | $0.57      | $3          |
 | `alibaba-cn/qwen3.6-max-preview`                | 246K    |       |           |       |       |       | $1         | $8          |
-| `alibaba-cn/qwen3.6-plus`                       | 1.0M    |       |           |       |       |       | $0.28      | $2          |
+| `alibaba-cn/qwen3.6-plus`                       | 1.0M    |       |           |       |       |       | $0.50      | $3          |
 | `alibaba-cn/qwq-32b`                            | 131K    |       |           |       |       |       | $0.29      | $0.86       |
 | `alibaba-cn/qwq-plus`                           | 131K    |       |           |       |       |       | $0.23      | $0.57       |
 | `alibaba-cn/siliconflow/deepseek-r1-0528`       | 164K    |       |           |       |       |       | $0.50      | $2          |