@mastra/mcp-docs-server 1.0.0-beta.1 → 1.0.0-beta.3

package/.docs/organized/code-examples/openapi-spec-writer.md

@@ -29,7 +29,7 @@
   "devDependencies": {
     "@libsql/client": "^0.15.4",
     "@types/js-yaml": "^4.0.9",
-    "@types/node": "^20.17.57",
+    "@types/node": "22.13.17",
     "@types/react": "^19.1.9",
     "@types/react-dom": "^19.1.7",
     "@types/react-syntax-highlighter": "^15.5.13",

package/.docs/organized/code-examples/quick-start.md

@@ -3,7 +3,7 @@
 {
   "name": "examples-quick-start",
   "devDependencies": {
-    "@types/node": "^20.17.57",
+    "@types/node": "22.13.17",
     "tsx": "^4.19.3",
     "typescript": "^5.8.3",
     "zod": "^3.25.76"

package/.docs/organized/code-examples/stock-price-tool.md

@@ -8,10 +8,7 @@
     "zod": "^3.25.76"
   },
   "devDependencies": {
-    "@jest/globals": "^29.7.0",
-    "jest": "^29.7.0",
-    "mastra": "latest",
-    "ts-jest": "^29.2.6"
+    "mastra": "latest"
   }
 }
 ```
@@ -93,20 +90,3 @@ export const stockPrices = createTool({
 });
 
 ```
-
-### mastra/tools/tools.test.ts
-```typescript
-import { describe, it, expect } from 'vitest';
-
-import { getStockPrice } from './stock-price';
-
-describe('Test Tools', () => {
-  it('should run the stockPrices', async () => {
-    const result = await getStockPrice('AAPL');
-
-    console.log(result);
-    expect(result).toBeDefined();
-  });
-});
-
-```

package/.docs/organized/code-examples/workflow-ai-recruiter.md

@@ -3,7 +3,7 @@
 {
   "name": "examples-workflow-ai-recruiter",
   "devDependencies": {
-    "@types/node": "^20.17.57",
+    "@types/node": "22.13.17",
     "mastra": "latest",
     "tsx": "^4.19.3",
     "typescript": "^5.8.3",

package/.docs/organized/code-examples/workflow-with-inline-steps.md

@@ -3,7 +3,7 @@
 {
   "name": "workflow-with-inline-steps",
   "devDependencies": {
-    "@types/node": "^20.17.57",
+    "@types/node": "22.13.17",
     "mastra": "latest",
     "tsx": "^4.19.3",
     "typescript": "^5.8.3",

package/.docs/organized/code-examples/workflow-with-memory.md

@@ -3,7 +3,7 @@
 {
   "name": "examples-workflow-with-memory",
   "devDependencies": {
-    "@types/node": "^20.17.57",
+    "@types/node": "22.13.17",
     "tsx": "^4.19.3",
     "typescript": "^5.8.3",
     "zod": "^3.25.76"

package/.docs/organized/code-examples/workflow-with-separate-steps.md

@@ -3,7 +3,7 @@
 {
   "name": "examples-workflow-with-separate-steps",
   "devDependencies": {
-    "@types/node": "^20.17.57",
+    "@types/node": "22.13.17",
     "mastra": "latest",
     "tsx": "^4.19.3",
     "typescript": "^5.8.3",

package/.docs/organized/code-examples/workflow-with-suspend-resume.md

@@ -3,7 +3,7 @@
 {
   "name": "examples-workflow-with-suspend-resume",
   "devDependencies": {
-    "@types/node": "^20.17.57",
+    "@types/node": "22.13.17",
     "mastra": "latest",
     "tsx": "^4.19.3",
     "typescript": "^5.8.3",

package/.docs/raw/agents/adding-voice.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Adding Voice to Agents | Agents | Mastra Docs"
+title: "Adding Voice to Agents | Agents"
 ---
 
 # Adding Voice to Agents

package/.docs/raw/agents/agent-memory.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Agent Memory | Agents | Mastra Docs"
+title: "Agent Memory | Agents"
 description: Learn how to add memory to agents to store conversation history and maintain context across interactions.
 ---
 

package/.docs/raw/agents/guardrails.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Guardrails | Agents | Mastra Docs"
+title: "Guardrails | Agents"
 description: "Learn how to implement guardrails using input and output processors to secure and control AI interactions."
 ---
 

package/.docs/raw/agents/human-in-the-loop-with-tools.mdx

@@ -0,0 +1,90 @@
+---
+title: "Human in the Loop with Tools | Agents"
+description: Learn how to require approvals and suspend tool execution while keeping humans in control of agent workflows.
+---
+
+# Human in the Loop with Tools
+
+Sometimes agents need human oversight before they can run potentially sensitive tools or long-running workflows. Mastra lets you pause tool execution to wait for approval, decline a tool call entirely, or suspend a tool mid-flight until the required data is available.
+
+## Tool approvals
+
+### Enforcing approval on every tool
+
+Pass `requireToolApproval: true` when calling `stream` (or `generate`) to automatically pause execution whenever the agent tries to invoke a tool. The stream closes until you explicitly approve or decline the tool call using the original run’s `runId`.
+
+```typescript {2,6} title="Require approval before executing any tool" showLineNumbers copy
+const stream = await myAgent.stream("Find the user with name - John Smith", {
+  requireToolApproval: true,
+});
+
+const approvedToolCallStream = await myAgent.approveToolCall({ runId: stream.runId });
+const declinedToolCallStream = await myAgent.declineToolCall({ runId: stream.runId });
+```
+
+### Requiring approval per tool
+
+You can also enforce approval on specific tools. Set `requireApproval: true` when creating a tool so the agent pauses only when it tries to invoke that tool.
+
+```typescript {8} title="Mark a tool as approval-only" showLineNumbers copy
+const findUserTool = createTool({
+  id: "Find user tool",
+  description: "Returns the name and email for a matching user",
+  inputSchema: z.object({
+    name: z.string(),
+  }),
+  execute: async (inputData) => {
+    return mockFindUser(inputData);
+  },
+  requireApproval: true,
+});
+```
+
+When the agent reaches this tool, it emits a tool-call event you can approve or decline with the same `approveToolCall` or `declineToolCall` helpers.
+
+## Tool suspension
+
+Sometimes a tool can’t finish immediately—maybe it’s waiting for external confirmation or extra input. You can suspend and later resume execution using `workflow.suspend`, `resumeStream`, and optional schemas that define what data is required at each step.
+
+```typescript {10,14} title="Suspend and resume a tool" showLineNumbers copy
+const findUserTool = createTool({
+  id: "Find user tool",
+  description: "Returns the name and email for a matching user",
+  inputSchema: z.object({
+    name: z.string(),
+  }),
+  suspendSchema: z.object({
+    message: z.string(),
+  }),
+  resumeSchema: z.object({
+    name: z.string(),
+  }),
+  execute: async (inputData, { workflow }) => {
+    if (!workflow.resumeData) {
+      return workflow.suspend({ message: "Please provide the name of the user" });
+    }
+
+    return {
+      name: workflow?.resumeData?.name,
+      email: "test@test.com",
+    };
+  },
+});
+```
+
+To continue execution, call `resumeStream` with the run’s `runId` and the `resumeData` that satisfies the `resumeSchema`. The workflow resumes from the suspension point and the tool completes with the new data.
+
+```typescript {1} title="Resume a suspended tool call" showLineNumbers copy
+const resumedStream = await myAgent.resumeStream(
+  { name: "John Smith" },
+  { runId: stream.runId },
+);
+```
+
+## Related
+
+- [Using Tools](./using-tools)
+- [Agent Overview](./overview)
+- [Tools Overview](../mcp/overview)
+- [Agent Memory](./agent-memory)
+- [Request Context](/docs/v1/server-db/request-context)

package/.docs/raw/agents/networks.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Agent Networks | Agents | Mastra Docs"
+title: "Agent Networks | Agents"
 description: Learn how to coordinate multiple agents, workflows, and tools using agent networks for complex, non-deterministic task execution.
 ---
 

package/.docs/raw/agents/overview.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Using Agents | Agents | Mastra Docs"
+title: "Using Agents | Agents"
 description: Overview of agents in Mastra, detailing their capabilities and how they interact with tools, workflows, and external systems.
 ---
 
@@ -187,13 +187,11 @@ You can call agents from workflow steps, tools, the Mastra Client, or the comman
 const testAgent = mastra.getAgent("testAgent");
 ```
 
-:::info
+::::info
 
 `mastra.getAgent()` is preferred over a direct import, since it provides access to the Mastra instance configuration (logger, telemetry, storage, registered agents, and vector stores).
 
-See [Calling agents](/examples/v1/agents/calling-agents) for more information.
-
-:::
+::::
 
 ## Generating responses
 
@@ -388,15 +386,13 @@ const response = await testAgent.generate([
 console.log(response.text);
 ```
 
-For a detailed guide to creating and configuring tools, see the [Tools Overview](../tools-mcp/overview) page.
-
 ### Using `maxSteps`
 
 The `maxSteps` parameter controls the maximum number of sequential LLM calls an agent can make. Each step includes generating a response, executing any tool calls, and processing the result. Limiting steps helps prevent infinite loops, reduce latency, and control token usage for agents that use tools. The default is 1, but can be increased:
 
 ```typescript showLineNumbers copy
 const response = await testAgent.generate("Help me organize my day", {
-  maxSteps: 5,
+  maxSteps: 10,
 });
 
 console.log(response.text);
@@ -429,7 +425,7 @@ export const testAgent = new Agent({
 });
 ```
 
-> See [Using Tools](./using-tools) for more information.
+> See [Using Tools](/docs/v1/agents/using-tools) for more information.
 
 ## Using `RequestContext`
 
@@ -462,7 +458,6 @@ Use [Studio](/docs/v1/getting-started/studio) to test agents with different mess
 
 ## Related
 
-- [Using Tools](./using-tools)
-- [Agent Memory](./agent-memory)
-- [Request Context](/examples/v1/agents/request-context)
-- [Calling Agents](/examples/v1/agents/calling-agents)
+- [Using Tools](/docs/v1/agents/using-tools)
+- [Agent Memory](/docs/v1/agents/agent-memory)
+- [Request Context](/docs/v1/server-db/request-context)

package/.docs/raw/agents/using-tools.mdx

@@ -1,11 +1,11 @@
 ---
-title: "Using Tools | Agents | Mastra Docs"
+title: "Using Tools | Agents"
 description: Learn how to create tools and add them to agents to extend capabilities beyond text generation.
 ---
 
 # Using Tools
 
-Agents use tools to call APIs, query databases, or run custom functions from your codebase. [Tools](../tools-mcp/overview) give agents capabilities beyond language generation by providing structured access to data and performing clearly defined operations. You can also load tools from remote [MCP servers](../tools-mcp/mcp-overview) to expand an agent’s capabilities.
+Agents use tools to call APIs, query databases, or run custom functions from your codebase. Tools give agents capabilities beyond language generation by providing structured access to data and performing clearly defined operations. You can also load tools from remote [MCP servers](/docs/v1/mcp/overview) to expand an agent's capabilities.
 
 ## When to use tools
 
@@ -13,6 +13,8 @@ Use tools when an agent needs additional context or information from remote reso
 
 ## Creating a tool
 
+When creating tools, keep descriptions simple and focused on what the tool does, emphasizing its primary use case. Descriptive schema names can also help guide the agent on how to use the tool.
+
 This example shows how to create a tool that fetches weather data from an API. When the agent calls the tool, it provides the required input as defined by the tool's `inputSchema`. The tool accesses this data through its `inputData` parameter, which in this example includes the `location` used in the weather API query.
 
 ```typescript {14} title="src/mastra/tools/weather-tool.ts" showLineNumbers copy
@@ -41,7 +43,9 @@ export const weatherTool = createTool({
 
 ## Adding tools to an agent
 
-To make a tool available to an agent, add it to the `tools` option and reference it by name in the agent’s instructions.
+To make a tool available to an agent, add it to `tools`. Mentioning available tools and their general purpose in the agent's system prompt helps the agent decide when to call a tool and when not to.
+
+An agent can use multiple tools to handle more complex tasks by delegating specific parts to individual tools. The agent decides which tools to use based on the user's message, the agent's instructions, and the tool descriptions and schemas.
 
 ```typescript {9,11} title="src/mastra/agents/weather-agent.ts" showLineNumbers copy
 import { openai } from "@ai-sdk/openai";
@@ -73,9 +77,7 @@ const result = await agent.generate("What's the weather in London?");
 
 ## Using multiple tools
 
-An agent can use multiple tools to handle more complex tasks by delegating specific parts to individual tools. The agent decides which tools to use based on the user’s message, the agent’s instructions, and the tool descriptions and schemas.
-
-When multiple tools are available, the agent may choose to use one, several, or none, depending on what’s needed to answer the query.
+When multiple tools are available, the agent may choose to use one, several, or none, depending on what's needed to answer the query.
 
 ```typescript {6} title="src/mastra/agents/weather-agent.ts" showLineNumbers copy
 import { weatherTool } from "../tools/weather-tool";
@@ -91,7 +93,6 @@ export const weatherAgent = new Agent({
 
 ## Related
 
-- [Tools Overview](../tools-mcp/overview)
-- [Agent Memory](./agent-memory)
+- [MCP Overview](/docs/v1/mcp/overview)
+- [Agent Memory](/docs/v1/agents/agent-memory)
 - [Request Context](/docs/v1/server-db/request-context)
-- [Calling Agents](/examples/v1/agents/calling-agents)

package/.docs/raw/auth/auth0.mdx

@@ -1,5 +1,5 @@
 ---
-title: "MastraAuthAuth0 Class | Auth | Mastra Docs"
+title: "MastraAuthAuth0 Class | Auth"
 description: "Documentation for the MastraAuthAuth0 class, which authenticates Mastra applications using Auth0 authentication."
 ---
 

package/.docs/raw/auth/clerk.mdx

@@ -1,5 +1,5 @@
 ---
-title: "MastraAuthClerk Class | Auth | Mastra Docs"
+title: "MastraAuthClerk Class | Auth"
 description: "Documentation for the MastraAuthClerk class, which authenticates Mastra applications using Clerk authentication."
 ---
 

package/.docs/raw/auth/firebase.mdx

@@ -1,5 +1,5 @@
 ---
-title: "MastraAuthFirebase Class | Auth | Mastra Docs"
+title: "MastraAuthFirebase Class | Auth"
 description: "Documentation for the MastraAuthFirebase class, which authenticates Mastra applications using Firebase Authentication."
 ---
 

package/.docs/raw/auth/index.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Auth Overview | Auth | Mastra Docs"
+title: "Auth Overview | Auth"
 description: Learn about different Auth options for your Mastra applications
 ---
 

package/.docs/raw/auth/jwt.mdx

@@ -1,5 +1,5 @@
 ---
-title: "MastraJwtAuth Class | Auth | Mastra Docs"
+title: "MastraJwtAuth Class | Auth"
 description: "Documentation for the MastraJwtAuth class, which authenticates Mastra applications using JSON Web Tokens."
 ---
 

package/.docs/raw/auth/supabase.mdx

@@ -1,5 +1,5 @@
 ---
-title: "MastraAuthSupabase Class | Auth | Mastra Docs"
+title: "MastraAuthSupabase Class | Auth"
 description: "Documentation for the MastraAuthSupabase class, which authenticates Mastra applications using Supabase Auth."
 ---
 

package/.docs/raw/auth/workos.mdx

@@ -1,5 +1,5 @@
 ---
-title: "MastraAuthWorkos Class | Auth | Mastra Docs"
+title: "MastraAuthWorkos Class | Auth"
 description: "Documentation for the MastraAuthWorkos class, which authenticates Mastra applications using WorkOS authentication."
 ---
 

package/.docs/raw/community/contributing-templates.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Contributing Templates | Community | Mastra Docs"
+title: "Contributing Templates | Community"
 description: "How to contribute your own templates to the Mastra ecosystem"
 ---
 

package/.docs/raw/community/discord.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Discord Community | Community | Mastra Docs"
+title: "Discord Community | Community"
 description: Information about the Mastra Discord community and MCP bot.
 ---
 
@@ -9,4 +9,4 @@ The Discord server has over 1000 members and serves as the main discussion forum
 
 ## Discord MCP Bot
 
-In addition to community members, we have an (experimental!) Discord bot that can also help answer questions. It uses [Model Context Protocol (MCP)](/docs/v1/tools-mcp/mcp-overview). You can ask it a question with `/ask` (either in public channels or DMs) and clear history (in DMs only) with `/cleardm`.
+In addition to community members, we have an (experimental!) Discord bot that can also help answer questions. It uses [Model Context Protocol (MCP)](/docs/v1/mcp/overview). You can ask it a question with `/ask` (either in public channels or DMs) and clear history (in DMs only) with `/cleardm`.

package/.docs/raw/community/licensing.mdx

@@ -1,5 +1,5 @@
 ---
-title: "License | Community | Mastra Docs"
+title: "License | Community"
 description: "Mastra License"
 ---
 

package/.docs/raw/deployment/{server-deployment.mdx → building-mastra.mdx}

@@ -1,15 +1,15 @@
 ---
-title: "Deploy a Mastra Server | Deployment | Mastra Docs"
-description: "Learn how to deploy a Mastra server with build settings and deployment options."
+title: "Building Mastra | Deployment"
+description: "Learn how to build a Mastra server with build settings and deployment options."
 ---
 
-# Deploy a Mastra Server
+# Building Mastra
 
 Mastra runs as a standard Node.js server and can be deployed across a wide range of environments.
 
 ## Default project structure
 
-The [getting started guide](/docs/v1/getting-started/installation) scaffolds a project with sensible defaults to help you begin quickly. By default, the CLI organizes application files under the `src/mastra/` directory, resulting in a structure similar to the following:
+The [getting started guide](/guides/v1/quickstarts/standalone-server) scaffolds a project with sensible defaults to help you begin quickly. By default, the CLI organizes application files under the `src/mastra/` directory, resulting in a structure similar to the following:
 
 ```
 src/

package/.docs/raw/deployment/cloud-providers/amazon-ec2.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Amazon EC2 | Deployment | Mastra Docs"
+title: "Amazon EC2 | Deployment"
 description: "Deploy your Mastra applications to Amazon EC2."
 ---
 
@@ -16,7 +16,7 @@ Deploy your Mastra applications to Amazon EC2 (Elastic Cloud Compute).
 This guide assumes your Mastra application has been created using the default
 `npx create-mastra@beta` command.
 For more information on how to create a new Mastra application,
-refer to our [getting started guide](/docs/v1/getting-started/installation)
+refer to our [getting started guide](/guides/v1/quickstarts/standalone-server)
 :::
 
 ## Prerequisites

package/.docs/raw/deployment/cloud-providers/aws-lambda.mdx

@@ -1,5 +1,5 @@
 ---
-title: "AWS Lambda | Deployment | Mastra Docs"
+title: "AWS Lambda | Deployment"
 description: "Deploy your Mastra applications to AWS Lambda using Docker containers and the AWS Lambda Web Adapter."
 ---
 
@@ -15,7 +15,7 @@ This approach allows you to run your Mastra server as a containerized Lambda fun
 This guide assumes your Mastra application has been created using the default
 `npx create-mastra@beta` command.
 For more information on how to create a new Mastra application,
-refer to our [getting started guide](/docs/v1/getting-started/installation)
+refer to our [getting started guide](/guides/v1/quickstarts/standalone-server)
 :::
 
 ## Prerequisites
@@ -216,7 +216,7 @@ Once deployed, test your Lambda function:
 2. Visit the URL in your browser to see your Mastra's server home screen
 3. Test your agents and workflows using the generated API endpoints
 
-For more information about available API endpoints, see the [Server documentation](/docs/v1/deployment/server-deployment).
+For more information about available API endpoints, see the [Server documentation](/docs/v1/deployment/building-mastra).
 
 ## Connecting your client
 

package/.docs/raw/deployment/cloud-providers/azure-app-services.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Azure App Services | Deployment | Mastra Docs"
+title: "Azure App Services | Deployment"
 description: "Deploy your Mastra applications to Azure App Services."
 ---
 
@@ -14,7 +14,7 @@ Deploy your Mastra applications to Azure App Services.
 This guide assumes your Mastra application has been created using the default
 `npx create-mastra@beta` command.
 For more information on how to create a new Mastra application,
-refer to our [getting started guide](/docs/v1/getting-started/installation)
+refer to our [getting started guide](/guides/v1/quickstarts/standalone-server)
 :::
 
 ## Prerequisites

package/.docs/raw/deployment/{serverless-platforms → cloud-providers}/cloudflare-deployer.mdx

@@ -1,5 +1,5 @@
 ---
-title: "CloudflareDeployer | Deployment | Mastra Docs"
+title: "CloudflareDeployer | Deployment"
 description: "Learn how to deploy a Mastra application to Cloudflare using the Mastra CloudflareDeployer"
 ---
 

package/.docs/raw/deployment/cloud-providers/digital-ocean.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Digital Ocean | Deployment | Mastra Docs"
+title: "Digital Ocean | Deployment"
 description: "Deploy your Mastra applications to Digital Ocean."
 ---
 
@@ -16,7 +16,7 @@ Deploy your Mastra applications to Digital Ocean's App Platform and Droplets.
 This guide assumes your Mastra application has been created using the default
 `npx create-mastra@beta` command.
 For more information on how to create a new Mastra application,
-refer to our [getting started guide](./../../getting-started/installation)
+refer to our [getting started guide](/guides/v1/quickstarts/standalone-server)
 :::
 
 <Tabs>

package/.docs/raw/deployment/cloud-providers/index.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Cloud Providers | Deployment | Mastra Docs"
+title: "Cloud Providers | Deployment"
 description: "Deploy your Mastra applications to popular cloud providers."
 ---
 
@@ -9,16 +9,20 @@ Standalone Mastra applications can be deployed to popular cloud providers, see o
 
 - [Amazon EC2](/docs/v1/deployment/cloud-providers/amazon-ec2)
 - [AWS Lambda](/docs/v1/deployment/cloud-providers/aws-lambda)
-- [Digital Ocean](/docs/v1/deployment/cloud-providers/digital-ocean)
 - [Azure App Services](/docs/v1/deployment/cloud-providers/azure-app-services)
+- [Cloudflare](/docs/v1/deployment/cloud-providers/cloudflare-deployer)
+- [Digital Ocean](/docs/v1/deployment/cloud-providers/digital-ocean)
+- [Netlify](/docs/v1/deployment/cloud-providers/netlify-deployer)
+- [Vercel](/docs/v1/deployment/cloud-providers/vercel-deployer)
+
 
-For self-hosted Node.js server deployment, see the [Creating A Mastra Server](/docs/v1/deployment/server-deployment) guide.
+For self-hosted Node.js server deployment, see the [Creating A Mastra Server](/docs/v1/deployment/building-mastra) guide.
 
 ## Prerequisites
 
 Before deploying to a cloud provider, ensure you have:
 
-- A [Mastra application](/docs/v1/getting-started/installation)
+- A [Mastra application](/guides/v1/quickstarts/standalone-server)
 - Node.js `v22.13.0` or later
 - A GitHub repository for your application (required for most CI/CD setups)
 - Domain name management access (for SSL and HTTPS)

package/.docs/raw/deployment/{serverless-platforms → cloud-providers}/netlify-deployer.mdx

@@ -1,5 +1,5 @@
 ---
-title: "NetlifyDeployer | Deployment | Mastra Docs"
+title: "NetlifyDeployer | Deployment"
 description: "Learn how to deploy a Mastra application to Netlify using the Mastra NetlifyDeployer"
 ---
 

package/.docs/raw/deployment/{serverless-platforms → cloud-providers}/vercel-deployer.mdx

@@ -1,5 +1,5 @@
 ---
-title: "VercelDeployer | Deployment | Mastra Docs"
+title: "VercelDeployer | Deployment"
 description: "Learn how to deploy a Mastra application to Vercel using the Mastra VercelDeployer"
 ---
 

package/.docs/raw/{mastra-cloud → deployment/mastra-cloud}/dashboard.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Navigating the Dashboard | Mastra Cloud | Mastra Docs"
+title: "Navigating the Dashboard | Mastra Cloud"
 description: Details of each feature available in Mastra Cloud
 ---
 
@@ -7,7 +7,7 @@ import { MastraCloudCallout } from "@site/src/components/MastraCloudCallout";
 
 # Navigating the Dashboard
 
-This page explains how to navigate the Mastra Cloud dashboard, where you can configure your project, view deployment details, and interact with agents and workflows using the built-in [Studio](/docs/v1/mastra-cloud/dashboard#studio).
+This page explains how to navigate the Mastra Cloud dashboard, where you can configure your project, view deployment details, and interact with agents and workflows using the built-in [Studio](/docs/v1/deployment/mastra-cloud/dashboard#studio).
 
 <MastraCloudCallout />
 
@@ -97,4 +97,4 @@ Each MCP Server includes API endpoints for HTTP and SSE, along with IDE configur
 
 ## Next steps
 
-- [Understanding Tracing and Logs](/docs/v1/mastra-cloud/observability)
+- [Understanding Tracing and Logs](/docs/v1/deployment/mastra-cloud/observability)

package/.docs/raw/{mastra-cloud → deployment/mastra-cloud}/observability.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Understanding Tracing and Logs | Mastra Cloud | Mastra Docs"
+title: "Understanding Tracing and Logs | Mastra Cloud"
 description: Monitoring and debugging tools for Mastra Cloud deployments
 ---
 
@@ -13,7 +13,7 @@ Mastra Cloud captures execution data to help you monitor your application's beha
 
 ## Logs
 
-You can view detailed logs for debugging and monitoring your application's behavior on the [Logs](/docs/v1/mastra-cloud/dashboard#logs) page of the Dashboard.
+You can view detailed logs for debugging and monitoring your application's behavior on the [Logs](/docs/v1/deployment/mastra-cloud/dashboard#logs) page of the Dashboard.
 
 ![Dashboard logs](/img/mastra-cloud/mastra-cloud-dashboard-logs.jpg)
 

package/.docs/raw/{mastra-cloud → deployment/mastra-cloud}/overview.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Mastra Cloud | Mastra Cloud | Mastra Docs"
+title: "Mastra Cloud | Mastra Cloud"
 description: Deployment and monitoring service for Mastra applications
 ---
 
@@ -7,7 +7,7 @@ import { MastraCloudCallout } from "@site/src/components/MastraCloudCallout";
 
 # Mastra Cloud
 
-[Mastra Cloud](https://mastra.ai/cloud) is a platform for deploying, managing, monitoring, and debugging Mastra applications. When you [deploy](/docs/v1/mastra-cloud/setting-up) your application, Mastra Cloud exposes your agents, tools, and workflows as REST API endpoints.
+[Mastra Cloud](https://mastra.ai/cloud) is a platform for deploying, managing, monitoring, and debugging Mastra applications. When you [deploy](/docs/v1/deployment/mastra-cloud/setting-up) your application, Mastra Cloud exposes your agents, tools, and workflows as REST API endpoints.
 
 <MastraCloudCallout />
 
@@ -62,4 +62,4 @@ Mastra Cloud is purpose-built for Mastra agents, tools, and workflows. It handle
 
 ## Next steps
 
-- [Setting Up and Deploying](/docs/v1/mastra-cloud/setting-up)
+- [Setting Up and Deploying](/docs/v1/deployment/mastra-cloud/setting-up)