@mastra/mcp-docs-server 0.13.39 → 0.13.40-alpha.0

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.
 ---
 
@@ -177,9 +177,9 @@ export const mastra = new Mastra({
 });
 ```
 
-## Referencing an agent
+## Calling an agent
 
-You can call agents from workflow steps, tools, the Mastra Client, or the command line. Get a reference by calling `.getAgent()` on your `mastra` or `mastraClient` instance, depending on your setup:
+You can call agents from workflow steps, tools, or the Mastra Client. Get a reference by calling `.getAgent()` on your `mastra` or `mastraClient` instance, depending on your setup:
 
 ```typescript showLineNumbers copy
 const testAgent = mastra.getAgent("testAgent");
@@ -187,12 +187,71 @@ const testAgent = mastra.getAgent("testAgent");
 
 :::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/agents/calling-agents) for more information.
+`mastra.getAgent()` is preferred over directly importing an agent in to your file, since it provides access to the Mastra instance configuration (logger, telemetry, storage, registered agents, and vector stores).
 
 :::
 
+### From a workflow step
+
+The `mastra` instance is passed as an argument to a workflow step’s `execute` function. It provides access to registered agents using `getAgent()`. Use this method to retrieve your agent, then call `generate()` with a prompt.
+
+```typescript filename="src/mastra/workflows/test-workflow.ts" showLineNumbers copy
+const step1 = createStep({
+  // ...
+  execute: async ({ mastra }) => {
+
+    const agent = mastra.getAgent("testAgent");
+    const response = await agent.generate("Help me organize my day");
+
+    console.log(response.text);
+  }
+});
+```
+
+### From a tool
+
+The `mastra` instance is available within a tool’s `execute` function. Use `getAgent()` to retrieve a registered agent and call `generate()` with a prompt.
+
+```typescript filename="src/mastra/tools/test-tool.ts" showLineNumbers copy
+export const testTool = createTool({
+  // ...
+  execute: async ({ mastra }) => {
+
+    const agent = mastra.getAgent("testAgent");
+    const response = await agent.generate("Help me organize my day");
+
+    console.log(response!.text);
+  }
+});
+```
+
+### Using HTTP or curl
+
+You can interact with a registered agent by sending a `POST` request to your Mastra application's `/generate` endpoint. Include a `messages` array of role/content pairs.
+
+```bash
+curl -X POST http://localhost:4111/api/agents/testAgent/generate \
+  -H "Content-Type: application/json" \
+  -d '{
+    "messages": [
+      {
+        "role": "user",
+        "content": "Help me organize my day"
+      }
+    ]
+  }'| jq -r '.text'
+```
+
+**Example output**
+
+```text
+1. What time do you plan to start your day?
+2. Do you have any specific tasks or appointments scheduled for today?
+3. Are there any personal goals or activities you want to include (e.g., exercise, reading, hobbies)?
+4. How much time do you want to allocate for work versus personal time?
+5. Do you have any deadlines or priorities that need to be addressed?
+```
+
 ## Generating responses
 
 Agents can return results in two ways: generating the full output before returning it or streaming tokens in real time. Choose the approach that fits your use case: generate for short, internal responses or debugging, and stream to deliver pixels to end users as quickly as possible.
@@ -361,59 +420,6 @@ const response = await testAgentThatDoesntSupportStructuredOutput.generate(
 console.log(response.object);
 ```
 
-## Working with images
-
-Agents can analyze and describe images by processing both the visual content and any text within them. To enable image analysis, pass an object with `type: 'image'` and the image URL in the `content` array. You can combine image content with text prompts to guide the agent's analysis.
-
-```typescript showLineNumbers copy
-const response = await testAgent.generate([
-  {
-    role: "user",
-    content: [
-      {
-        type: "image",
-        image: "https://placebear.com/cache/395-205.jpg",
-        mimeType: "image/jpeg",
-      },
-      {
-        type: "text",
-        text: "Describe the image in detail, and extract all the text in the image.",
-      },
-    ],
-  },
-]);
-
-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,
-});
-
-console.log(response.text);
-```
-
-### Using `onStepFinish`
-
-You can monitor the progress of multi-step operations using the `onStepFinish` callback. This is useful for debugging or providing progress updates to users.
-
-`onStepFinish` is only available when streaming or generating text without structured output.
-
-```typescript showLineNumbers copy
-const response = await testAgent.generate("Help me organize my day", {
-  onStepFinish: ({ text, toolCalls, toolResults, finishReason, usage }) => {
-    console.log({ text, toolCalls, toolResults, finishReason, usage });
-  },
-});
-```
-
 ## Using tools
 
 Agents can use tools to go beyond language generation, enabling structured interactions with external APIs and services. Tools allow agents to access data and perform clearly defined operations in a reliable, repeatable way.
@@ -425,7 +431,7 @@ export const testAgent = new Agent({
 });
 ```
 
-> See [Using Tools](./using-tools) for more information.
+> See [Using Tools](/docs/agents/using-tools) for more information.
 
 ## Using `RuntimeContext`
 
@@ -450,13 +456,63 @@ export const testAgent = new Agent({
 
 > See [Runtime Context](/docs/server-db/runtime-context) for more information.
 
+## 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 5, but can be increased:
+
+```typescript showLineNumbers copy
+const response = await testAgent.generate("Help me organize my day", {
+  maxSteps: 10,
+});
+
+console.log(response.text);
+```
+
+## Using `onStepFinish`
+
+You can monitor the progress of multi-step operations using the `onStepFinish` callback. This is useful for debugging or providing progress updates to users.
+
+`onStepFinish` is only available when streaming or generating text without structured output.
+
+```typescript showLineNumbers copy
+const response = await testAgent.generate("Help me organize my day", {
+  onStepFinish: ({ text, toolCalls, toolResults, finishReason, usage }) => {
+    console.log({ text, toolCalls, toolResults, finishReason, usage });
+  },
+});
+```
+
+## Working with images
+
+Agents can analyze and describe images by processing both the visual content and any text within them. To enable image analysis, pass an object with `type: 'image'` and the image URL in the `content` array. You can combine image content with text prompts to guide the agent's analysis.
+
+```typescript showLineNumbers copy
+const response = await testAgent.generate([
+  {
+    role: "user",
+    content: [
+      {
+        type: "image",
+        image: "https://placebear.com/cache/395-205.jpg",
+        mimeType: "image/jpeg",
+      },
+      {
+        type: "text",
+        text: "Describe the image in detail, and extract all the text in the image.",
+      },
+    ],
+  },
+]);
+
+console.log(response.text);
+```
+
 ## Testing with Studio
 
 Use [Studio](/docs/getting-started/studio) to test agents with different messages, inspect tool calls and responses, and debug agent behavior.
 
 ## Related
 
-- [Using Tools](./using-tools)
-- [Agent Memory](./agent-memory)
-- [Runtime Context](/examples/agents/runtime-context)
-- [Calling Agents](/examples/agents/calling-agents)
+- [Using Tools](/docs/agents/using-tools)
+- [Agent Memory](/docs/agents/agent-memory)
+- [Runtime Context](/docs/server-db/runtime-context)

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

@@ -1,11 +1,22 @@
 ---
-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. Tool 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/mcp/overview) to expand an agent’s capabilities.
+
+Each tool typically defines:
+
+- **Inputs:** What information the tool needs to run (defined with an `inputSchema`).
+- **Outputs:** The structure of the data the tool returns (defined with an `outputSchema`).
+- **Execution Logic:** The code that performs the tool's action.
+- **Description:** Text that helps the agent understand what the tool does and when to use it.
+
+You can also load tools from remote [MCP servers](/docs/mcp/overview) to expand an agent's capabilities.
+
+Use [Studio](/docs/getting-started/studio) to test tools with different inputs, inspect execution results, and verify tool behavior.
 
 ## When to use tools
 
@@ -13,6 +24,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 `context` argument, which in this example includes the `location` used in the weather API query.
 
 ```typescript {14,16} title="src/mastra/tools/weather-tool.ts" showLineNumbers copy
@@ -21,7 +34,7 @@ import { z } from "zod";
 
 export const weatherTool = createTool({
   id: "weather-tool",
-  description: "Fetches weather for a location",
+  description: "Fetches weather for a location.",
   inputSchema: z.object({
     location: z.string(),
   }),
@@ -41,7 +54,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";
@@ -62,7 +77,7 @@ export const weatherAgent = new Agent({
 
 The agent uses the tool’s `inputSchema` to infer what data the tool expects. In this case, it extracts `London` as the `location` from the message and makes it available to the tool’s context.
 
-```typescript {5} title="src/test-tool.ts" showLineNumbers copy
+```typescript {5} showLineNumbers copy
 import { mastra } from "./mastra";
 
 const agent = mastra.getAgent("weatherAgent");
@@ -70,25 +85,133 @@ const agent = mastra.getAgent("weatherAgent");
 const result = await agent.generate("What's the weather in London?");
 ```
 
-## Using multiple tools
+## Using `RuntimeContext`
+
+Use [RuntimeContext](/docs/server-db/runtime-context) to access request-specific values. This lets you conditionally adjust behavior based on the context of the request.
+
+```typescript title="src/mastra/tools/test-tool.ts" showLineNumbers
+export type UserTier = {
+  "user-tier": "enterprise" | "pro";
+};
+
+const advancedTools = () => {
+  // ...
+};
+
+const baseTools =  () => {
+  // ...
+};
+
+export const testTool = createTool({
+  // ...
+  execute: async ({ runtimeContext }) => {
+    const userTier = runtimeContext.get("user-tier") as UserTier["user-tier"];
+
+    return userTier === "enterprise"
+      ? advancedTools
+      : baseTools;
+  }
+});
+```
+
+> See [Runtime Context](/docs/server-db/runtime-context) for more information.
+
+## Cancelling tool execution with `AbortSignal`
+
+When you initiate an agent interaction using `.generate()` or `.stream()`, you can provide an `AbortSignal`. Mastra automatically forwards this signal to any tool executions that occur during that interaction.
+
+```typescript showLineNumbers
+const controller = new AbortController();
+
+try {
+  const result = await agent.generate("What's the weather in London?", {
+  abortSignal: controller.signal
+});
+  console.log(result.text);
+} catch (error) {
+  if (error.name === "AbortError") {
+    console.log("Agent generation was aborted.");
+  } else {
+    console.error(error);
+  }
+}
+```
+
+This allows you to cancel long-running operations within your tools, such as network requests or intensive computations, if the parent agent call is aborted.
+
+You access the `abortSignal` in the second parameter of the tool's `execute` function.
+
+```typescript {3} title="src/mastra/tools/weather-tool.ts" showLineNumbers
+export const weatherTool = createTool({
+  // ...
+  execute: async ({ context }, { abortSignal }) => {
+    const { location } = context
+    const response = await fetch(`https://wttr.in/${location}?format=3`, {
+      signal: abortSignal
+    });
+
+    if (abortSignal?.aborted) {
+      throw new Error("Aborted");
+    }
+
+    const weather = await response.text();
+    return { weather };
+  }
+});
+```
+
+## AI SDK Tool Format
+
+Mastra maintains compatibility with the tool format used by the Vercel AI SDK (`ai` package). You can define tools using the `tool` function from the `ai` package and use them directly within your Mastra agents alongside tools created with Mastra's `createTool`.
+
+First, ensure you have the `ai` package installed:
+
+```bash copy
+npm install ai
+```
+
+Here's an example of a tool defined using the Vercel AI SDK format:
+
+```typescript title="src/mastra/tools/vercel-weather-tool.ts" copy
+import { tool } from "ai";
+import { z } from "zod";
+
+export const vercelWeatherTool = tool({
+  description: "Fetches weather for a location.",
+  parameters: z.object({
+    location: z.string(),
+  }),
+  execute: async ({ location }) => {
+
+    const response = await fetch(`https://wttr.in/${location}?format=3`);
+    const weather = await response.text();
 
-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.
+    return { weather };
+  },
+});
+```
 
-When multiple tools are available, the agent may choose to use one, several, or none, depending on what’s needed to answer the query.
+You can then add this tool to your Mastra agent just like any other tool:
 
-```typescript {6} title="src/mastra/agents/weather-agent.ts" showLineNumbers copy
+```typescript {3-4,11} title="src/mastra/agents/test-agent.ts" showLineNumbers copy
+import { Agent } from "@mastra/core/agent";
+import { openai } from "@ai-sdk/openai";
 import { weatherTool } from "../tools/weather-tool";
-import { activitiesTool } from "../tools/activities-tool";
+import { vercelWeatherTool } from "../tools/vercel-weather-tool";
 
-export const weatherAgent = new Agent({
-  // ..
-  tools: { weatherTool, activitiesTool },
+
+export const testAgent = new Agent({
+  name: "weather-agent",
+  instructions: "You are a helpful weather assistant.",
+  model: openai("gpt-4o-mini"),
+  tools: { weatherTool, vercelWeatherTool }
 });
 ```
 
+Mastra supports both tool formats, allowing you to mix and match as needed.
+
 ## Related
 
-- [Tools Overview](../tools-mcp/overview)
-- [Agent Memory](./agent-memory)
+- [Agent Memory](/docs/agents/agent-memory)
 - [Runtime Context](/docs/server-db/runtime-context)
 - [Calling Agents](/examples/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/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/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/course/02-agent-tools-mcp/04-initializing-mcp-tools.md

@@ -3,9 +3,9 @@
 Once you have the configuration set up, you need to initialize the MCP tools:
 
 ```typescript
-const mcpTools = await mcp.listTools();
+const mcpTools = await mcp.getTools();
 ```
 
-This asynchronous call fetches all the available tools from the configured MCP servers. The `listTools()` method connects to each server specified in your configuration, retrieves the available tools, and returns them in a format that can be used by your Mastra agent.
+This asynchronous call fetches all the available tools from the configured MCP servers. The `getTools()` method connects to each server specified in your configuration, retrieves the available tools, and returns them in a format that can be used by your Mastra agent.
 
 The `mcpTools` object will contain all the tools provided by the MCP servers you've configured. We'll add these tools to our agent in the next step.

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

@@ -1,9 +1,9 @@
 ---
-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.
 

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."
 ---
 

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."
 ---
 
@@ -214,7 +214,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/deployment/server-deployment).
+For more information about available API endpoints, see the [Server documentation](/docs/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."
 ---
 

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."
 ---
 

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,10 +9,13 @@ Standalone Mastra applications can be deployed to popular cloud providers, see o
 
 - [Amazon EC2](/docs/deployment/cloud-providers/amazon-ec2)
 - [AWS Lambda](/docs/deployment/cloud-providers/aws-lambda)
-- [Digital Ocean](/docs/deployment/cloud-providers/digital-ocean)
 - [Azure App Services](/docs/deployment/cloud-providers/azure-app-services)
+- [Cloudflare](/docs/deployment/cloud-providers/cloudflare-deployer)
+- [Digital Ocean](/docs/deployment/cloud-providers/digital-ocean)
+- [Netlify](/docs/deployment/cloud-providers/netlify-deployer)
+- [Vercel](/docs/deployment/cloud-providers/vercel-deployer)
 
-For self-hosted Node.js server deployment, see the [Creating A Mastra Server](/docs/deployment/server-deployment) guide.
+For self-hosted Node.js server deployment, see the [Creating A Mastra Server](/docs/deployment/building-mastra) guide.
 
 ## Prerequisites
 

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/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/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/mastra-cloud/observability)
+- [Understanding Tracing and Logs](/docs/deployment/mastra-cloud/observability)