@mastra/mcp-docs-server 1.1.18-alpha.1 → 1.1.18

package/.docs/reference/observability/metrics/automatic-metrics.md

@@ -0,0 +1,132 @@
+# Automatic metrics reference
+
+Mastra automatically extracts performance and usage metrics from traced execution. This page is the complete reference for every metric name, label, and context field that Mastra emits.
+
+For setup instructions, see the [Metrics overview](https://mastra.ai/docs/observability/metrics/overview).
+
+## When Mastra emits automatic metrics
+
+Metrics are extracted from spans when they end. The observability layer inspects each completed span, calculates duration, and (for model generation spans) reads token usage data. No manual instrumentation is needed.
+
+Metrics are routed through an internal event bus to the `DefaultExporter`, which batches and flushes them to storage. Only DuckDB and in-memory storage backends support metrics persistence today.
+
+### What affects whether a metric is available
+
+Two conditions must be true for a metric to reach storage:
+
+1. `DefaultExporter` is configured as an exporter.
+2. The storage backend supports metrics (`DuckDB` or `InMemory`).
+
+If metrics aren't appearing, see [troubleshooting](#troubleshooting).
+
+## Duration metrics
+
+Duration metrics record execution time in milliseconds, calculated from the span's start and end timestamps. Each duration metric includes a `status` label set to `ok` or `error`, derived from the span's status.
+
+| Metric name                    | Span type                    | Description                                             |
+| ------------------------------ | ---------------------------- | ------------------------------------------------------- |
+| `mastra_agent_duration_ms`     | `AGENT_RUN`                  | Execution time of an agent run                          |
+| `mastra_tool_duration_ms`      | `TOOL_CALL`, `MCP_TOOL_CALL` | Execution time of a tool call, including MCP tool calls |
+| `mastra_workflow_duration_ms`  | `WORKFLOW_RUN`               | Execution time of a workflow run                        |
+| `mastra_model_duration_ms`     | `MODEL_GENERATION`           | Execution time of a model generation                    |
+| `mastra_processor_duration_ms` | `PROCESSOR_RUN`              | Execution time of a processor run                       |
+
+## Token usage metrics
+
+Token metrics are emitted only from `MODEL_GENERATION` spans that include `usage` data. If the provider doesn't report usage, no token metrics are emitted for that span.
+
+### Input token metrics
+
+| Metric name                             | Description                                    |
+| --------------------------------------- | ---------------------------------------------- |
+| `mastra_model_total_input_tokens`       | Total input tokens                             |
+| `mastra_model_input_text_tokens`        | Text tokens in the input prompt                |
+| `mastra_model_input_cache_read_tokens`  | Tokens read from prompt cache (e.g. Anthropic) |
+| `mastra_model_input_cache_write_tokens` | Tokens written to prompt cache                 |
+| `mastra_model_input_audio_tokens`       | Audio tokens in the input (multimodal models)  |
+| `mastra_model_input_image_tokens`       | Image tokens in the input (vision models)      |
+
+### Output token metrics
+
+| Metric name                            | Description                                                |
+| -------------------------------------- | ---------------------------------------------------------- |
+| `mastra_model_total_output_tokens`     | Total output tokens                                        |
+| `mastra_model_output_text_tokens`      | Text tokens in the model's output                          |
+| `mastra_model_output_reasoning_tokens` | Reasoning / chain-of-thought tokens (e.g. OpenAI o-series) |
+| `mastra_model_output_audio_tokens`     | Audio tokens in the model's output                         |
+| `mastra_model_output_image_tokens`     | Output image tokens                                        |
+
+### Provider-reported detailed token categories
+
+The detailed breakdown metrics (everything except `total_input` and `total_output`) are only emitted when the provider reports them. If a category has zero tokens, the metric is skipped for that span. Different providers report different levels of detail. For example, not all providers report cache or audio tokens.
+
+## Cost-related context
+
+### When cost context is attached
+
+Cost context is attached to token metrics when the embedded pricing registry has a matching entry for the provider and model. The registry ships with Mastra and covers common providers and models. If no match is found, token metrics are still emitted but without cost fields.
+
+### What cost fields may be included
+
+| Field           | Description                                                                  |
+| --------------- | ---------------------------------------------------------------------------- |
+| `provider`      | Provider name (e.g. `openai`, `anthropic`)                                   |
+| `model`         | Model identifier (e.g. `gpt-4o`, `claude-sonnet-4-20250514`)                 |
+| `estimatedCost` | Estimated cost for this metric, calculated from token count and pricing tier |
+| `costUnit`      | Currency unit (e.g. `USD`)                                                   |
+| `costMetadata`  | Additional pricing context (tier information, error details)                 |
+
+## Correlation with traces
+
+### How metrics relate to spans and trace context
+
+Each metric carries a `CorrelationContext` snapshot from the span that produced it. This context is stored alongside the metric value and lets you navigate from a metric to the exact span and trace.
+
+The correlation fields are grouped into four categories:
+
+**Trace correlation**
+
+- `traceId`: trace identifier
+- `spanId`: span identifier
+- `tags`: tags from the span
+
+**Entity hierarchy**
+
+- `entityType`, `entityId`, `entityName`: The entity that produced the metric (e.g. agent, workflow)
+- `parentEntityType`, `parentEntityId`, `parentEntityName`: The parent entity
+- `rootEntityType`, `rootEntityId`, `rootEntityName`: The root entity in the call chain
+
+**Identity**
+
+- `userId`, `organizationId`, `resourceId`: Identity context from the request
+- `runId`, `sessionId`, `threadId`, `requestId`: Correlation IDs
+
+**Deployment**
+
+- `environment`: Deployment environment (e.g. `production`, `staging`)
+- `source`: Source identifier
+- `serviceName`: Service name from the observability config
+- `experimentId`: Experiment identifier, if applicable
+
+### Why correlation helps with debugging
+
+When you spot a spike in latency or token usage on the Metrics dashboard, correlation context lets you drill directly into the trace that produced the metric. From there you can inspect the individual span to find the root cause: a slow tool call, a large prompt, or an unexpected error.
+
+## Troubleshooting
+
+### No metrics are appearing
+
+- **Observability is configured**: Verify that your `Mastra` instance has an `observability` config with at least one exporter.
+- **`DefaultExporter` is present**: Other exporters (Datadog, Langfuse, etc.) don't persist metrics to Mastra storage. `DefaultExporter` is required for the Studio dashboard.
+- **Storage supports metrics**: 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.
+- **Sampling isn't 0%**: If sampling probability is `0` or strategy is `never`, all spans become no-ops and no metrics are extracted.
+
+### Duration metrics are missing
+
+- **Span has timestamps**: Duration is calculated from `startTime` and `endTime`. If either is missing, the metric is skipped.
+- **Span type maps to a metric**: Only `AGENT_RUN`, `TOOL_CALL`, `MCP_TOOL_CALL`, `WORKFLOW_RUN`, `MODEL_GENERATION`, and `PROCESSOR_RUN` spans produce duration metrics.
+
+### Token metrics are missing
+
+- **Span is a model generation**: Token metrics are only emitted from `MODEL_GENERATION` spans.
+- **Provider reports usage**: The model provider must include `usage` data in its response. If usage is absent, no token metrics are emitted.

package/.docs/reference/storage/cloudflare-d1.md

@@ -2,7 +2,7 @@
 
 The Cloudflare D1 storage implementation provides a serverless SQL database solution using Cloudflare D1, supporting relational operations and transactional consistency.
 
-> **Observability Not Supported:** Cloudflare D1 storage **doesn't support the observability domain**. Traces from the `DefaultExporter` can't be persisted to D1, and Mastra Studio's observability features won't work with D1 as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
+> **Observability Not Supported:** Cloudflare D1 storage **doesn't support the observability domain**. Traces from the `DefaultExporter` can't be persisted to D1, and [Studio's](https://mastra.ai/docs/studio/overview) observability features won't work with D1 as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
 
 > **Row Size Limit:** Cloudflare D1 enforces a **1 MiB maximum row size**. This limit can be exceeded when storing messages with base64-encoded attachments such as images. See [Handling large attachments](https://mastra.ai/docs/memory/storage) for workarounds including uploading attachments to external storage.
 

package/.docs/reference/storage/cloudflare.md

@@ -2,10 +2,10 @@
 
 Mastra provides two Cloudflare storage implementations:
 
-- **Cloudflare KV** (`CloudflareKVStorage`) - A globally distributed, eventually consistent key-value store
-- **Cloudflare Durable Objects** (`CloudflareDOStorage`) - A strongly consistent, SQLite-based storage using Durable Objects
+- **Cloudflare KV** (`CloudflareKVStorage`): A globally distributed, eventually consistent key-value store
+- **Cloudflare Durable Objects** (`CloudflareDOStorage`): A strongly consistent, SQLite-based storage using Durable Objects
 
-> **Observability Not Supported:** Cloudflare storage **does not support the observability domain**. Traces from the `DefaultExporter` cannot be persisted, and Mastra Studio's observability features won't work with Cloudflare as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
+> **Observability Not Supported:** Cloudflare storage **doesn't support the observability domain**. Traces from the `DefaultExporter` can't be persisted, and [Studio's](https://mastra.ai/docs/studio/overview) observability features won't work with Cloudflare as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
 
 ## Installation
 

package/.docs/reference/storage/convex.md

@@ -2,7 +2,7 @@
 
 The Convex storage implementation provides a serverless storage solution using [Convex](https://convex.dev), a full-stack TypeScript development platform with real-time sync and automatic caching.
 
-> **Observability Not Supported:** Convex storage **doesn't support the observability domain**. Traces from the `DefaultExporter` can't be persisted to Convex, and Mastra Studio's observability features won't work with Convex as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
+> **Observability Not Supported:** Convex storage **doesn't support the observability domain**. Traces from the `DefaultExporter` can't be persisted to Convex, and [Studio's](https://mastra.ai/docs/studio/overview) observability features won't work with Convex as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
 
 > **Record Size Limit:** Convex enforces a **1 MiB maximum record size**. This limit can be exceeded when storing messages with base64-encoded attachments such as images. See [Handling large attachments](https://mastra.ai/docs/memory/storage) for workarounds including uploading attachments to external storage like S3, Cloudflare R2, or [Convex file storage](https://docs.convex.dev/file-storage).
 

package/.docs/reference/storage/dynamodb.md

@@ -2,7 +2,7 @@
 
 The DynamoDB storage implementation provides a scalable and performant NoSQL database solution for Mastra, leveraging a single-table design pattern with [ElectroDB](https://electrodb.dev/).
 
-> **Observability Not Supported:** DynamoDB storage **doesn't support the observability domain**. Traces from the `DefaultExporter` can't be persisted to DynamoDB, and Mastra Studio's observability features won't work with DynamoDB as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
+> **Observability Not Supported:** DynamoDB storage **doesn't support the observability domain**. Traces from the `DefaultExporter` can't be persisted to DynamoDB, and [Studio's](https://mastra.ai/docs/studio/overview) observability features won't work with DynamoDB as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
 
 > **Item Size Limit:** DynamoDB enforces a **400 KB maximum item size**. This limit can be exceeded when storing messages with base64-encoded attachments such as images. See [Handling large attachments](https://mastra.ai/docs/memory/storage) for workarounds including uploading attachments to external storage.
 

package/.docs/reference/storage/lance.md

@@ -2,7 +2,7 @@
 
 The LanceDB storage implementation provides a high-performance storage solution using the LanceDB database system, which excels at handling both traditional data storage and vector operations.
 
-> **Observability Not Supported:** LanceDB storage **doesn't support the observability domain**. Traces from the `DefaultExporter` can't be persisted to LanceDB, and Mastra Studio's observability features won't work with LanceDB as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
+> **Observability Not Supported:** LanceDB storage **doesn't support the observability domain**. Traces from the `DefaultExporter` can't be persisted to LanceDB, and [Studio's](https://mastra.ai/docs/studio/overview) observability features won't work with LanceDB as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
 
 ## Installation
 

package/.docs/reference/storage/upstash.md

@@ -4,7 +4,7 @@ The Upstash storage implementation provides a serverless-friendly storage soluti
 
 > **Pricing:** When using Mastra with Upstash, the pay-as-you-go model can result in unexpectedly high costs due to the high volume of Redis commands generated during agent conversations. We strongly recommend using a **fixed pricing plan** for predictable costs. See [Upstash pricing](https://upstash.com/pricing/redis) for details and [GitHub issue #5850](https://github.com/mastra-ai/mastra/issues/5850) for context.
 
-> **Observability Not Supported:** Upstash storage **doesn't support the observability domain**. Traces from the `DefaultExporter` can't be persisted to Upstash, and Mastra Studio's observability features won't work with Upstash as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
+> **Observability Not Supported:** Upstash storage **doesn't support the observability domain**. Traces from the `DefaultExporter` can't be persisted to Upstash, and [Studio's](https://mastra.ai/docs/studio/overview) observability features won't work with Upstash as your only storage provider. To enable observability, use [composite storage](https://mastra.ai/reference/storage/composite) to route observability data to a supported provider like ClickHouse or PostgreSQL.
 
 ## Installation
 

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

@@ -0,0 +1,118 @@
+# VercelSandbox
+
+Executes commands as [Vercel](https://vercel.com) serverless functions. Provides globally-distributed, zero-infrastructure execution with automatic scaling.
+
+> **Info:** For interface details, see [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox).
+
+> **Warning:** VercelSandbox is stateless. There is no persistent filesystem, no interactive shell, and no support for long-running or background processes. Only `/tmp` is writable and is ephemeral between invocations.
+
+## Installation
+
+**npm**:
+
+```bash
+npm install @mastra/vercel
+```
+
+**pnpm**:
+
+```bash
+pnpm add @mastra/vercel
+```
+
+**Yarn**:
+
+```bash
+yarn add @mastra/vercel
+```
+
+**Bun**:
+
+```bash
+bun add @mastra/vercel
+```
+
+## Usage
+
+Add a `VercelSandbox` to a workspace and assign it to an agent:
+
+```typescript
+import { Agent } from '@mastra/core/agent'
+import { Workspace } from '@mastra/core/workspace'
+import { VercelSandbox } from '@mastra/vercel'
+
+const workspace = new Workspace({
+  sandbox: new VercelSandbox({
+    token: process.env.VERCEL_TOKEN,
+  }),
+})
+
+const agent = new Agent({
+  name: 'dev-agent',
+  model: 'anthropic/claude-sonnet-4-6',
+  workspace,
+})
+```
+
+### Team-scoped deployment with custom resources
+
+```typescript
+const workspace = new Workspace({
+  sandbox: new VercelSandbox({
+    token: process.env.VERCEL_TOKEN,
+    teamId: 'team_abc123',
+    regions: ['iad1', 'sfo1'],
+    maxDuration: 120,
+    memory: 3008,
+    env: {
+      NODE_ENV: 'production',
+    },
+  }),
+})
+```
+
+## Constructor parameters
+
+**token** (`string`): Vercel API token. Falls back to \`VERCEL\_TOKEN\` environment variable.
+
+**teamId** (`string`): Vercel team ID for team-scoped deployments.
+
+**projectName** (`string`): Existing Vercel project name. Auto-generated if omitted.
+
+**regions** (`string[]`): Deployment regions. (Default: `['iad1']`)
+
+**maxDuration** (`number`): Function maximum duration in seconds. (Default: `60`)
+
+**memory** (`number`): Function memory in MB. (Default: `1024`)
+
+**env** (`Record<string, string>`): Environment variables baked into the deployed function source. These are embedded at deploy time, not set dynamically.
+
+**commandTimeout** (`number`): Per-invocation command timeout in milliseconds. (Default: `55000`)
+
+**instructions** (`string | ((opts) => string)`): Custom instructions that override the default instructions returned by \`getInstructions()\`. Pass a string to fully replace, or a function to extend the defaults.
+
+## Properties
+
+**id** (`string`): Unique identifier for this sandbox instance.
+
+**name** (`'VercelSandbox'`): Human-readable name.
+
+**provider** (`'vercel'`): Provider type identifier.
+
+**status** (`ProviderStatus`): Current lifecycle status: \`'pending'\`, \`'starting'\`, \`'running'\`, \`'stopping'\`, \`'stopped'\`, \`'destroying'\`, \`'destroyed'\`, or \`'error'\`.
+
+## Limitations
+
+VercelSandbox uses serverless functions under the hood, which means:
+
+- **No persistent filesystem**: Files written to `/tmp` are ephemeral and cleared between invocations.
+- **No interactive shell**: Commands run via `/bin/sh -c` with no stdin streaming.
+- **No background processes**: No process manager, PIDs, or long-running tasks.
+- **No mounting**: Cloud storage mounting (S3, GCS) is not supported.
+- **Timeout limits**: Maximum execution time is bounded by `maxDuration` (default 60s).
+
+## Related
+
+- [WorkspaceSandbox interface](https://mastra.ai/reference/workspace/sandbox)
+- [Workspace class](https://mastra.ai/reference/workspace/workspace-class)
+- [E2BSandbox](https://mastra.ai/reference/workspace/e2b-sandbox) — full-featured cloud sandbox with persistent filesystem and process management

package/CHANGELOG.md

@@ -1,5 +1,28 @@
 # @mastra/mcp-docs-server
 
+## 1.1.18
+
+### Patch Changes
+
+- Updated dependencies [[`180aaaf`](https://github.com/mastra-ai/mastra/commit/180aaaf4d0903d33a49bc72de2d40ca69a5bc599), [`9140989`](https://github.com/mastra-ai/mastra/commit/91409890e83f4f1d9c1b39223f1af91a6a53b549), [`d7c98cf`](https://github.com/mastra-ai/mastra/commit/d7c98cfc9d75baba9ecbf1a8835b5183d0a0aec8), [`acf5fbc`](https://github.com/mastra-ai/mastra/commit/acf5fbcb890dc7ca7167bec386ce5874dfadb997), [`24ca2ae`](https://github.com/mastra-ai/mastra/commit/24ca2ae57538ec189fabb9daee6175ad27035853), [`0762516`](https://github.com/mastra-ai/mastra/commit/07625167e029a8268ea7aaf0402416e6d8832874), [`9c57f2f`](https://github.com/mastra-ai/mastra/commit/9c57f2f7241e9f94769aa99fc86c531e8207d0f9), [`5bfc691`](https://github.com/mastra-ai/mastra/commit/5bfc69104c07ba7a9b55c2f8536422c0878b9c57), [`2de3d36`](https://github.com/mastra-ai/mastra/commit/2de3d36932b7f73ad26bc403f7da26cfe89e903e), [`d3736cb`](https://github.com/mastra-ai/mastra/commit/d3736cb9ce074d2b8e8b00218a01f790fe81a1b4), [`c627366`](https://github.com/mastra-ai/mastra/commit/c6273666f9ef4c8c617c68b7d07fe878a322f85c), [`66a7412`](https://github.com/mastra-ai/mastra/commit/66a7412ec0550f3dfa01cd05b057d8c6e5b062bc)]:
+  - @mastra/core@1.19.0
+  - @mastra/mcp@1.4.0
+
+## 1.1.18-alpha.4
+
+### Patch Changes
+
+- Updated dependencies [[`9c57f2f`](https://github.com/mastra-ai/mastra/commit/9c57f2f7241e9f94769aa99fc86c531e8207d0f9), [`5bfc691`](https://github.com/mastra-ai/mastra/commit/5bfc69104c07ba7a9b55c2f8536422c0878b9c57)]:
+  - @mastra/core@1.19.0-alpha.2
+
+## 1.1.18-alpha.2
+
+### Patch Changes
+
+- Updated dependencies [[`9140989`](https://github.com/mastra-ai/mastra/commit/91409890e83f4f1d9c1b39223f1af91a6a53b549), [`d7c98cf`](https://github.com/mastra-ai/mastra/commit/d7c98cfc9d75baba9ecbf1a8835b5183d0a0aec8), [`acf5fbc`](https://github.com/mastra-ai/mastra/commit/acf5fbcb890dc7ca7167bec386ce5874dfadb997), [`24ca2ae`](https://github.com/mastra-ai/mastra/commit/24ca2ae57538ec189fabb9daee6175ad27035853), [`0762516`](https://github.com/mastra-ai/mastra/commit/07625167e029a8268ea7aaf0402416e6d8832874), [`2de3d36`](https://github.com/mastra-ai/mastra/commit/2de3d36932b7f73ad26bc403f7da26cfe89e903e), [`d3736cb`](https://github.com/mastra-ai/mastra/commit/d3736cb9ce074d2b8e8b00218a01f790fe81a1b4), [`c627366`](https://github.com/mastra-ai/mastra/commit/c6273666f9ef4c8c617c68b7d07fe878a322f85c), [`66a7412`](https://github.com/mastra-ai/mastra/commit/66a7412ec0550f3dfa01cd05b057d8c6e5b062bc)]:
+  - @mastra/core@1.18.1-alpha.1
+  - @mastra/mcp@1.4.0-alpha.0
+
 ## 1.1.18-alpha.0
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mastra/mcp-docs-server",
-  "version": "1.1.18-alpha.1",
+  "version": "1.1.18",
   "description": "MCP server for accessing Mastra.ai documentation, changelogs, and news.",
   "type": "module",
   "main": "dist/index.js",
@@ -29,8 +29,8 @@
     "jsdom": "^26.1.0",
     "local-pkg": "^1.1.2",
     "zod": "^4.3.6",
-    "@mastra/core": "1.18.1-alpha.0",
-    "@mastra/mcp": "^1.3.2"
+    "@mastra/core": "1.19.0",
+    "@mastra/mcp": "^1.4.0"
   },
   "devDependencies": {
     "@hono/node-server": "^1.19.11",
@@ -46,9 +46,9 @@
     "tsx": "^4.21.0",
     "typescript": "^5.9.3",
     "vitest": "4.0.18",
-    "@internal/lint": "0.0.75",
-    "@internal/types-builder": "0.0.50",
-    "@mastra/core": "1.18.1-alpha.0"
+    "@internal/lint": "0.0.76",
+    "@mastra/core": "1.19.0",
+    "@internal/types-builder": "0.0.51"
   },
   "homepage": "https://mastra.ai",
   "repository": {

package/.docs/docs/getting-started/studio.md

@@ -1,113 +0,0 @@
-# Studio
-
-Studio provides an interactive UI for building, testing, and managing your agents, workflows, and tools. Run it locally during development, or [deploy it](https://mastra.ai/docs/deployment/studio) to production so your team can manage agents, monitor performance, and gain insights through built-in observability.
-
-Add [authentication](https://mastra.ai/docs/server/auth) to protect your deployed Studio with login screens, role-based access control, and permission-based UI rendering so you can control what each team member can see and do. You can also [create a project in Mastra Cloud](https://mastra.ai/docs/mastra-cloud/setup) for a hosted option.
-
-[YouTube video player](https://www.youtube-nocookie.com/embed/ojGu6Bi4wYk)
-
-## Start Studio
-
-If you created your application with `create mastra`, start the development server using the `dev` script. You can also run it directly with `mastra dev`.
-
-**npm**:
-
-```bash
-npm run dev
-```
-
-**pnpm**:
-
-```bash
-pnpm run dev
-```
-
-**Yarn**:
-
-```bash
-yarn dev
-```
-
-**Bun**:
-
-```bash
-bun run dev
-```
-
-Once the server is running, you can:
-
-- Open the Studio UI at <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.
-
-To run Studio in production, see [Deploy Studio](https://mastra.ai/docs/deployment/studio).
-
-## Studio UI
-
-The Studio UI lets you interact with your agents, workflows, and tools, observe exactly what happens under the hood with each interaction, and tweak things as you go.
-
-### Agents
-
-Chat with your agent directly, dynamically switch [models](https://mastra.ai/models), and tweak settings like temperature and top-p to understand how they affect the output.
-
-When you interact with your agent, you can follow each step of its reasoning, view tool call outputs, and [observe](#observability) traces and logs to see how responses are generated. You can also attach [scorers](#scorers) to measure and compare response quality over time.
-
-### Workflows
-
-Visualize your workflow as a graph and run it step by step with a custom input. During execution, the interface updates in real time to show the active step and the path taken.
-
-When running a workflow, you can also view detailed traces showing tool calls, raw JSON outputs, and any errors that might have occurred along the way.
-
-### Tools
-
-Run tools in isolation to observe their behavior. Test them before assigning them to your agent, or isolate them to debug issues should something go wrong.
-
-### Processors
-
-View the input and output processors attached to each agent. The agent detail panel lists every processor by name and type, so you can verify your guardrails, token limiters, and custom processors are wired up correctly before testing.
-
-See [Processors](https://mastra.ai/docs/agents/processors) and [Guardrails](https://mastra.ai/docs/agents/guardrails) for configuration details.
-
-### MCP
-
-List the MCP servers attached to your Mastra instance and explore their available tools.
-
-### Observability
-
-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.
-
-### Scorers
-
-The Scorers tab displays the results of your agent's scorers as they run. When messages pass through your agent, the defined scorers evaluate each output asynchronously and render their results here. This allows you to understand how your scorers respond to different interactions, compare performance across test cases, and identify areas for improvement.
-
-### Datasets
-
-Create and manage collections of test cases to evaluate your agents and workflows. Import items from CSV or JSON, define input and ground-truth schemas, and pin to specific versions so you can reproduce experiments exactly. Run experiments with [scorers](https://mastra.ai/docs/evals/overview) to compare quality across prompts, models, or code changes.
-
-See [Datasets overview](https://mastra.ai/docs/observability/datasets/overview) for the full API and versioning details.
-
-## REST API
-
-Studio is backed by a complete set of REST API routes that let you programmatically interact with your agents, workflows, and tools. These are the same routes exposed by the [Mastra Server](https://mastra.ai/docs/server/mastra-server), so everything you build against locally works identically in production.
-
-You can explore all available endpoints in the OpenAPI specification at <http://localhost:4111/api/openapi.json>, which details every endpoint and its request and response schemas.
-
-To explore the API interactively, visit the Swagger UI at <http://localhost:4111/swagger-ui>. Here, you can discover endpoints and test them directly from your browser.
-
-> **Note:** The OpenAPI and Swagger endpoints are disabled in production by default. To enable them, set [`server.build.openAPIDocs`](https://mastra.ai/reference/configuration) and [`server.build.swaggerUI`](https://mastra.ai/reference/configuration) to `true` respectively.
-
-## Configuration
-
-By default, Studio runs at <http://localhost:4111>. You can change the [`host`](https://mastra.ai/reference/configuration), [`port`](https://mastra.ai/reference/configuration), and [`studioBase`](https://mastra.ai/reference/configuration) in the Mastra server configuration.
-
-For production deployments, see [Deploy Studio](https://mastra.ai/docs/deployment/studio) to learn about hosting Studio alongside your server, as a standalone SPA, or on a CDN.
-
-Add [authentication](https://mastra.ai/docs/server/auth) to control who can access Studio in production. Studio displays the appropriate login UI, which can be an SSO button, an email/password form, or both. All API routes require authentication. This applies to any request made to your Mastra API, whether from Studio or a direct API call.
-
-Mastra also supports HTTPS development through the [`--https`](https://mastra.ai/reference/cli/mastra) flag, which automatically creates and manages certificates for your project. When you run `mastra dev --https`, a private key and certificate are generated for localhost (or your configured host). Visit the [HTTPS reference](https://mastra.ai/reference/configuration) to learn more.
-
-## Next steps
-
-- Learn more about Mastra's suggested [project structure](https://mastra.ai/docs/getting-started/project-structure).
-- Integrate Mastra with your frontend framework of choice - [Next.js](https://mastra.ai/guides/getting-started/next-js), [React](https://mastra.ai/guides/getting-started/vite-react), or [Astro](https://mastra.ai/guides/getting-started/astro).

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

@@ -1,24 +0,0 @@
-# Studio
-
-[YouTube video player](https://www.youtube-nocookie.com/embed/ojGu6Bi4wYk)
-
-Mastra Cloud provides a hosted version of [Studio](https://mastra.ai/docs/getting-started/studio) that gives your team a shared environment for interacting with and testing your agents. Team members can chat with agents, review traces, give feedback, and tweak system prompts - without needing to run the project locally.
-
-[Set up your project](https://mastra.ai/docs/mastra-cloud/setup) to access Studio in the cloud.
-
-See the [Studio documentation](https://mastra.ai/docs/getting-started/studio) for details on features like the Agents playground, Workflows runner, Tools testing, and MCP Servers.
-
-> **Note:** You don't need to deploy your agent to use Studio. Studio runs in a sandbox environment separate from your production deployment
-
-## Sharing access
-
-To invite team members, go to [Mastra Cloud](https://cloud.mastra.ai), select **Team Settings**, then **Members** to add them. Once invited, they can sign in and access your project's Studio.
-
-![Invite team members](/assets/images/mastra-cloud-invite-c91b5a0fff03de5ecba3e0162484c819.png)
-
-> **Warning:** Team members can view environment variables and delete projects. Only invite people you trust.
-
-## Next steps
-
-- [Deployment](https://mastra.ai/docs/mastra-cloud/deployment) - Manage deployments and settings
-- [Observability](https://mastra.ai/docs/mastra-cloud/observability) - Monitor traces and logs