@mastra/mcp-docs-server 1.0.0-beta.2 → 1.0.0-beta.4

package/.docs/raw/getting-started/quickstart.mdx

@@ -0,0 +1,27 @@
+---
+title: "Quickstart | Getting Started"
+description: Choose how to get started with Mastra - standalone server or Next.js integration.
+---
+
+import { CardGrid, CardGridItem } from "@site/src/components/cards/card-grid";
+
+# Quickstart
+
+Choose how you want to get started with Mastra:
+
+<CardGrid columns={2}>
+  <CardGridItem
+    title="Standalone Server (Recommended)"
+    href="/guides/v1/quickstarts/standalone-server"
+  >
+    The fastest way to get started - spin up a standalone Mastra server and interact with your agents in Studio
+  </CardGridItem>
+  <CardGridItem
+    title="Next.js"
+    href="/guides/v1/quickstarts/nextjs"
+  >
+    Integrate Mastra into a Next.js app and use the AI SDK UI to build an in-app chat interface for your agents
+  </CardGridItem>
+</CardGrid>
+
+For more control over setup, or to add Mastra to an existing project, see the [manual installation guide](/guides/v1/guide/manual-install). You can also use [`mastra init`](/reference/v1/cli/mastra#mastra-init) for existing projects.

package/.docs/raw/getting-started/studio.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Studio | Getting Started | Mastra Docs"
+title: "Studio | Getting Started"
 description: Guide on installing Mastra and setting up the necessary prerequisites for running it with various LLM providers.
 ---
 
@@ -73,7 +73,7 @@ Visualize your workflow as a graph and run it step by step with a custom input.
 
 <VideoPlayer src="https://res.cloudinary.com/mastra-assets/video/upload/v1751406027/local-dev-workflows-playground_100_rbc466.mp4" />
 
-When running a workflow, you can also view detailed traces showing tool calls, raw JSON outputs, and any errors that might have occured along the way.
+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
 
@@ -99,7 +99,7 @@ The Scorers tab displays the results of your agent's scorers as they run. When m
 
 ## REST API
 
-The local development server exposes a complete set of REST API routes, allowing you to programmatically interact with your agents, workflows, and tools during development. This is particularly helpful if you plan to deploy the Mastra server, since the local development server uses the exact same API routes as the [production server](/docs/v1/server-db/production-server), allowing you to develop and test against it with full parity.
+The local development server exposes a complete set of REST API routes, allowing you to programmatically interact with your agents, workflows, and tools during development. This is particularly helpful if you plan to deploy the Mastra server, since the local development server uses the exact same API routes as the [Mastra Server](/docs/v1/server-db/mastra-server), allowing you to develop and test against it with full parity.
 
 You can explore all available endpoints in the OpenAPI specification at http://localhost:4111/openapi.json, which details every endpoint and its request and response schemas.
 

package/.docs/raw/getting-started/templates.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Templates | Getting Started | Mastra Docs"
+title: "Templates | Getting Started"
 description: Pre-built project structures that demonstrate common Mastra use cases and patterns
 ---
 

package/.docs/raw/guides/guide/ai-recruiter.mdx

@@ -16,7 +16,7 @@ You'll create a workflow that gathers information from a candidate's resume, the
 
 - Node.js `v22.13.0` or later installed
 - An API key from a supported [Model Provider](/models/v1)
-- An existing Mastra project (Follow the [installation guide](/docs/v1/getting-started/installation) to set up a new project)
+- An existing Mastra project (Follow the [installation guide](/guides/v1/quickstarts/standalone-server) to set up a new project)
 
 ## Building the Workflow
 

package/.docs/raw/guides/guide/chef-michel.mdx

@@ -19,7 +19,7 @@ You'll learn how to create the agent and register it with Mastra. Next, you'll i
 
 - Node.js `v22.13.0` or later installed
 - An API key from a supported [Model Provider](/models/v1)
-- An existing Mastra project (Follow the [installation guide](/docs/v1/getting-started/installation) to set up a new project)
+- An existing Mastra project (Follow the [installation guide](/guides/v1/quickstarts/standalone-server) to set up a new project)
 
 ## Creating the Agent
 

package/.docs/raw/{getting-started/installation.mdx → guides/guide/manual-install.mdx}

@@ -1,94 +1,20 @@
 ---
-title: "Install Mastra | Getting Started | Mastra Docs"
-description: Guide on installing Mastra and setting up the necessary prerequisites for running it with various LLM providers.
+title: "Manual Install | Guides"
+description: Set up a Mastra project manually without using the create mastra CLI.
 ---
 
 import Tabs from "@theme/Tabs";
 import TabItem from "@theme/TabItem";
 import Steps from "@site/src/components/Steps";
 import StepItem from "@site/src/components/StepItem";
-import { VideoPlayer } from "@site/src/components/video-player";
 
-# Install Mastra
-
-The `create mastra` CLI command is the quickest way to start a new Mastra project. It walks you through setup and creates example agents, workflows, and tools for you to learn from or adapt.
-
-For more control over setup, or to add Mastra to an existing project, see the [manual installation guide](#install-manually). You can also use [`mastra init`](/reference/v1/cli/mastra#mastra-init) for existing projects.
-
-## Before you start
-
-- You'll need an API key from a [model provider](/models/v1) to complete setup. We suggest starting with [OpenAI](https://platform.openai.com/api-keys), but if you need a provider that doesn't require a credit card, Google's [Gemini](https://aistudio.google.com/app/api-keys) is also an option.
-- [Install](https://nodejs.org/en/download) Node.js 22.13.0 or later.
-
-## Install with `create mastra`
-
-You can run `create mastra` anywhere on your machine.
-
-The wizard will guide you through setup, create a new directory for your project, and generate a weather agent with example workflows and tools to get you started.
-
-<Tabs>
-<TabItem value="npm" label="npm">
-
-```bash copy
-npm create mastra@beta
-```
-
-</TabItem>
-<TabItem value="pnpm" label="pnpm">
-
-```bash copy
-pnpm create mastra@beta
-```
-
-</TabItem>
-<TabItem value="yarn" label="yarn">
-
-```bash copy
-yarn create mastra@beta
-```
-
-</TabItem>
-<TabItem value="bun" label="bun">
-
-```bash copy
-bun create mastra@beta
-```
-
-</TabItem>
-</Tabs>
-
-:::note
-
-You can use flags with `create mastra` like `--no-example` to skip the example weather agent or `--template` to start from a specific [template](/docs/v1/getting-started/templates). Read the [CLI reference](/reference/v1/cli/create-mastra) for all options.
-
-:::
-
-### Test your agent
-
-Once setup is complete, follow the instructions in your terminal to start the Mastra dev server, then open Studio at http://localhost:4111.
-
-Try asking about the weather. If your API key is set up correctly, you'll get a response:
-
-<VideoPlayer src="https://res.cloudinary.com/mastra-assets/video/upload/v1751406022/local-dev-agents-playground_100_m3begx.mp4" />
-
-:::note
-
-If you encounter an error, your API key may not be configured correctly. Double-check your setup and try again. Need more help? [Join our Discord](https://discord.gg/BTYqqHKUrf) and talk to the team directly.
+# Manual Install
 
+:::info
+Use this guide to manually build a standalone Mastra server step by step. In most cases, it's quicker to follow the [Standalone Server Quickstart](/guides/v1/quickstarts/standalone-server), which achieves the same result using the [`mastra create`](/reference/v1/cli/create-mastra) command. For existing projects, you can also use [`mastra init`](/reference/v1/cli/mastra#mastra-init).
 :::
 
-[Studio](/docs/v1/getting-started/studio) lets you rapidly build and prototype agents without needing to build a UI. Once you're ready, you can integrate your Mastra agent into your application using the guides below.
-
-### Next steps
-
-- Read more about [Mastra's features](/docs/v1#why-mastra).
-- Integrate Mastra with your frontend framework: [Next.js](/docs/v1/frameworks/web-frameworks/next-js), [React](/docs/v1/frameworks/web-frameworks/vite-react), or [Astro](/docs/v1/frameworks/web-frameworks/astro).
-- Build an agent from scratch following one of our [guides](/guides/v1).
-- Watch conceptual guides on our [YouTube channel](https://www.youtube.com/@mastra-ai) and [subscribe](https://www.youtube.com/@mastra-ai?sub_confirmation=1)!
-
-## Install manually
-
-If you prefer not to use our automatic `create mastra` CLI tool, you can set up your project yourself by following the guide below.
+If you prefer not to use our automatic CLI tool, you can set up your project yourself by following the guide below.
 
 <Steps>
 

package/.docs/raw/guides/guide/notes-mcp-server.mdx

@@ -18,7 +18,7 @@ In this guide, you'll learn how to build a complete MCP (Model Context Protocol)
 
 - Node.js `v22.13.0` or later installed
 - An API key from a supported [Model Provider](/models/v1)
-- An existing Mastra project (Follow the [installation guide](/docs/v1/getting-started/installation) to set up a new project)
+- An existing Mastra project (Follow the [installation guide](/guides/v1/quickstarts/standalone-server) to set up a new project)
 
 ## Adding necessary dependencies & files
 
@@ -38,7 +38,7 @@ npm install @mastra/mcp@beta
 
 <StepItem>
 
-After following the default [installation guide](/docs/v1/getting-started/installation) your project will include files that are not relevant for this guide. You can safely remove them:
+After following the default [installation guide](/guides/v1/quickstarts/standalone-server) your project will include files that are not relevant for this guide. You can safely remove them:
 
 ```bash copy
 rm -rf src/mastra/agents src/mastra/workflows src/mastra/tools/weather-tool.ts

package/.docs/raw/guides/guide/research-assistant.mdx

@@ -16,7 +16,7 @@ You'll use the foundational Transformer paper ["Attention Is All You Need"](http
 
 - Node.js `v22.13.0` or later installed
 - An API key from a supported [Model Provider](/models/v1)
-- An existing Mastra project (Follow the [installation guide](/docs/v1/getting-started/installation) to set up a new project)
+- An existing Mastra project (Follow the [installation guide](/guides/v1/quickstarts/standalone-server) to set up a new project)
 
 ## How RAG works
 
@@ -57,7 +57,7 @@ Let's define the agent's behavior, connect it to your Mastra project, and create
 
 Install additional dependencies
 
-After running the [installation guide](/docs/v1/getting-started/installation) you'll need to install additional dependencies:
+After running the [installation guide](/guides/v1/quickstarts/standalone-server) you'll need to install additional dependencies:
 
 ```bash copy
 npm install @mastra/rag@beta ai@^4.0.0

package/.docs/raw/guides/guide/stock-agent.mdx

@@ -17,7 +17,7 @@ In this guide, you're going to create a simple agent that fetches the last day's
 
 - Node.js `v22.13.0` or later installed
 - An API key from a supported [Model Provider](/models/v1)
-- An existing Mastra project (Follow the [installation guide](/docs/v1/getting-started/installation) to set up a new project)
+- An existing Mastra project (Follow the [installation guide](/guides/v1/quickstarts/standalone-server) to set up a new project)
 
 ## Creating the Agent
 

package/.docs/raw/guides/guide/web-search.mdx

@@ -19,7 +19,7 @@ When building a web search agent, you have two main strategies to consider:
 
 - Node.js `v22.13.0` or later installed
 - An API key from a supported [Model Provider](/models/v1)
-- An existing Mastra project (Follow the [installation guide](/docs/v1/getting-started/installation) to set up a new project)
+- An existing Mastra project (Follow the [installation guide](/guides/v1/quickstarts/standalone-server) to set up a new project)
 
 ## Using native search tools
 

package/.docs/raw/guides/migrations/ai-sdk-v4-to-v5.mdx

@@ -0,0 +1,119 @@
+---
+title: "Migration: AI SDK v4 to v5 | Migration Guide"
+description: "Mastra-specific guidance for upgrading from AI SDK v4 to v5."
+---
+
+# Migrate from AI SDK v4 to v5
+
+Looking for integration docs? See [Using AI SDK](/docs/v1/frameworks/agentic-uis/ai-sdk).
+
+Follow the official [AI SDK v5 Migration Guide](https://v5.ai-sdk.dev/docs/migration-guides/migration-guide-5-0) for all AI SDK core breaking changes, package updates, and API changes.
+
+This guide covers only the Mastra-specific aspects of the migration.
+
+- **Data compatibility**: New data stored in v5 format will no longer work if you downgrade from v5 to v4
+- **Backup recommendation**: Keep DB backups from before you upgrade to v5
+
+### Memory and Storage
+
+Mastra automatically handles AI SDK v4 data using its internal `MessageList` class, which manages format conversion—including v4 to v5. No database migrations are required; your existing messages are translated on the fly and continue working after you upgrade.
+
+### Message Format Conversion
+
+For cases where you need to manually convert messages between AI SDK and Mastra formats, use the `convertMessages()` utility:
+
+```typescript
+import { convertMessages } from "@mastra/core/agent";
+
+// Convert AI SDK v4 messages to v5
+const aiv5Messages = convertMessages(aiv4Messages).to("AIV5.UI");
+
+// Convert Mastra messages to AI SDK v5
+const aiv5Messages = convertMessages(mastraMessages).to("AIV5.Core");
+
+// Supported output formats:
+// 'Mastra.V2', 'AIV4.UI', 'AIV5.UI', 'AIV5.Core', 'AIV5.Model'
+```
+
+This utility is helpful when you want to fetch messages directly from your storage DB and convert them for use in AI SDK.
+
+### Type Inference for Tools
+
+When using tools with TypeScript in AI SDK v5, Mastra provides type inference helpers to ensure type safety for your tool inputs and outputs.
+
+#### `InferUITool`
+
+The `InferUITool` type helper infers the input and output types of a single Mastra tool:
+
+```typescript title="app/types.ts" copy
+import { InferUITool, createTool } from "@mastra/core/tools";
+import { z } from "zod";
+
+const weatherTool = createTool({
+  id: "get-weather",
+  description: "Get the current weather",
+  inputSchema: z.object({
+    location: z.string().describe("The city and state"),
+  }),
+  outputSchema: z.object({
+    temperature: z.number(),
+    conditions: z.string(),
+  }),
+  execute: async (inputData) => {
+    return {
+      temperature: 72,
+      conditions: "sunny",
+    };
+  },
+});
+
+// Infer the types from the tool
+type WeatherUITool = InferUITool<typeof weatherTool>;
+// This creates:
+// {
+//   input: { location: string };
+//   output: { temperature: number; conditions: string };
+// }
+```
+
+#### `InferUITools`
+
+The `InferUITools` type helper infers the input and output types of multiple tools:
+
+```typescript title="app/mastra/tools.ts" copy
+import { InferUITools, createTool } from "@mastra/core/tools";
+import { z } from "zod";
+
+// Using weatherTool from the previous example
+const tools = {
+  weather: weatherTool,
+  calculator: createTool({
+    id: "calculator",
+    description: "Perform basic arithmetic",
+    inputSchema: z.object({
+      operation: z.enum(["add", "subtract", "multiply", "divide"]),
+      a: z.number(),
+      b: z.number(),
+    }),
+    outputSchema: z.object({
+      result: z.number(),
+    }),
+    execute: async (inputData) => {
+      // implementation...
+      return { result: 0 };
+    },
+  }),
+};
+
+// Infer types from the tool set
+export type MyUITools = InferUITools<typeof tools>;
+// This creates:
+// {
+//   weather: { input: { location: string }; output: { temperature: number; conditions: string } };
+//   calculator: { input: { operation: "add" | "subtract" | "multiply" | "divide"; a: number; b: number }; output: { result: number } };
+// }
+```
+
+These type helpers provide full TypeScript support when using Mastra tools with AI SDK v5 UI components, ensuring type safety across your application.
+
+

package/.docs/raw/guides/migrations/upgrade-to-v1/mastra.mdx

@@ -134,7 +134,7 @@ npx @mastra/codemod@beta v1/mastra-plural-apis .
 
 :::
 
-### Each primtive has a `getById` and a `get` function
+### Each primitive has a `getById` and a `get` function
 
 ```typescript
 mastra.getMCPServer('myServer');          // Works (registry key)

package/.docs/raw/guides/migrations/upgrade-to-v1/overview.mdx

@@ -13,10 +13,18 @@ Need help with the migration? Join our [Discord community](https://discord.gg/BT
 
 ## Migration Strategy
 
-### Update all Mastra packages
+### Update all Mastra packages to `beta` tag
 
 Use your package manager to update your project's versions. Be sure to update **all** Mastra packages at the same time to ensure compatibility.
 
+Here's how you update the most commonly used packages:
+
+```shell
+npm install @mastra/core@beta mastra@beta @mastra/loggers@beta @mastra/memory@beta
+```
+
+Install any other Mastra package with the `@beta` tag and you'll get the latest beta version available. Be sure to update all Mastra packages (especially if you're in a monorepo) to avoid version mismatches.
+
 ### Update Node.js version
 
 Mastra v1 requires Node.js **22.13.0** or higher. Update your development and production environments accordingly.

package/.docs/raw/guides/migrations/upgrade-to-v1/tools.mdx

@@ -113,3 +113,63 @@ npx @mastra/codemod@beta v1/runtime-context .
 ```
 
 :::
+
+This applies to all tool executions, whether called directly or through agents and workflows. The type narrowing ensures you handle validation errors appropriately and prevents runtime errors when accessing output properties.
+
+### Tool output validation with `outputSchema`
+
+Tools with an `outputSchema` now validate their return values at runtime. Previously, `outputSchema` was only used for type inference - the output was never validated.
+
+If your tool returns data that doesn't match its `outputSchema`, it will now return a `ValidationError` instead of the invalid data.
+
+To fix validation errors, ensure the tool's output matches the schema definition:
+
+```diff
+  const getUserTool = createTool({
+    id: "get-user",
+    outputSchema: z.object({
+      id: z.string(),
+      name: z.string(),
+      email: z.string().email(),
+    }),
+    execute: async (inputData) => {
+-     return { id: "123", name: "John" }; // Missing email
++     return { id: "123", name: "John", email: "john@example.com" };
+    },
+  });
+```
+
+When validation fails, the tool returns a `ValidationError`:
+
+```diff
++ // Before v1 - invalid output would silently pass through
+  await getUserTool.execute({});
+- // { id: "123", name: "John" } - missing email
++ // {
++ //   error: true,
++ //   message: "Tool output validation failed for get-user. The tool returned invalid output:\n- email: Required\n\nReturned output: {...}",
++ //   validationErrors: { ... }
++ // }
+```
+
+### `tool.execute` return type includes `ValidationError`
+
+The return type of `tool.execute` now includes `ValidationError` to handle validation failures. You must narrow the result type before accessing output schema properties to satisfy TypeScript's type checking.
+
+When calling `tool.execute`, check if the result contains an error before accessing output properties:
+
+```typescript
+const result = await getUserTool.execute({});
+
+// Type-safe check for validation errors
+if ('error' in result && result.error) {
+  console.error('Validation failed:', result.message);
+  console.error('Details:', result.validationErrors);
+  return;
+}
+
+// TypeScript knows result is valid here
+console.log(result.id, result.name, result.email);
+```
+
+Alternatively, update the `outputSchema` to match your actual output, or remove `outputSchema` entirely if you don't need validation.

package/.docs/raw/guides/migrations/upgrade-to-v1/workflows.mdx

@@ -124,6 +124,18 @@ npx @mastra/codemod@beta v1/workflow-list-runs .
 
 :::
 
+### Inputs are validated by default
+
+Previously, inputs weren't validated by default. The [`validateInputs`](/reference/v1/workflows/workflow#workflowoptions) flag determines whether to validate the workflow inputs or not. This boolean has been flipped to `true`. If you want the old behavior or have workflows whose schemas don't need to be validated, set `validateInputs: false`.
+
+```diff
+createWorkflow({
++  options: {
++    validateInputs: false
++  }
+})
+```
+
 ## Removed
 
 ### Legacy workflows export

package/.docs/raw/guides/quickstarts/nextjs.mdx

@@ -5,11 +5,11 @@ description: "Get started with Mastra, Next.js, and AS SDK UI. Quickly."
 
 # Next.js Quickstart
 
-In this quickstart, you'll build an AI agent with tool-calling capabilities using [Mastra](/docs/v1), then connect it to Next.js by importing and calling the agent directly within your routes. 
+In this quickstart, you'll build a tool-calling AI agent using Mastra, then connect it to Next.js by importing and calling the agent directly from your routes.
 
-You'll use [AI SDK UI](https://ai-sdk.dev/docs/ai-sdk-ui/overview) and [AI Elements](https://ai-sdk.dev/elements) to create a beautiful, interactive chat experience. 
+You'll use [AI SDK UI](https://ai-sdk.dev/docs/ai-sdk-ui/overview) and [AI Elements](https://ai-sdk.dev/elements) to create a beautiful, interactive chat experience.
 
-In ~5 minutes, you'll have a functional AI-powered app ready to extend with your own tools and logic.
+In about 5 minutes, you'll have a functional AI-powered app ready to extend with your own tools and logic.
 
 <figure>
 ![Screenshot of a chat-style web app displaying a completed "weatherTool" tool call, answering "What is the weather in London?" with a JSON result. A message suggests offering activity ideas, and a text input field is at the bottom.](/img/nextjs-quickstart.png)
@@ -18,7 +18,7 @@ In ~5 minutes, you'll have a functional AI-powered app ready to extend with your
 
 ## Before you begin
 
-* You'll need an API key from a supported [model provider](/models/v1). If you don't have a preference, use [OpenAI](https://platform.openai.com/api-keys).
+* You'll need an API key from a supported [model provider](/models/v1). If you don't have a preference, use [OpenAI](/models/v1/providers/openai).
 
 ## Create a new Next.js app
 
@@ -41,7 +41,7 @@ npx create-next-app \
 This creates a project called `my-nextjs-agent`, but you can replace it with any name you want.
 
 ## Initialize Mastra
-`cd` and run [`mastra init`](/reference/v1/cli/create-mastra). 
+`cd` and run [`mastra init`](/reference/v1/cli/create-mastra).
 
 When prompted, choose a provider (e.g. OpenAI) and enter your key:
 
@@ -58,14 +58,15 @@ This creates a `src/mastra` folder with an example weather agent and the followi
 You'll call `weather-agent.ts` from your Next.js routes in the next steps.
 
 
-## Install AI SDK UI and AI Elements
+## Install AI SDK and AI Elements
 
-Install AI SDK UI along with the Mastra adapter:
+Install AI SDK along with the Mastra adapter:
 
 ```bash
 npm install \
     @mastra/ai-sdk \
-    @ai-sdk/react 
+    @ai-sdk/react \
+    ai
 ```
 
 Next, initialize AI Elements. When prompted, choose the default options:
@@ -112,7 +113,7 @@ export async function GET() {
     resourceId: "weather-chat",
   });
 
-  const uiMessages = 
+  const uiMessages =
     convertMessages(response?.uiMessages ?? []).to("AIV5.UI");
   return NextResponse.json(uiMessages);
 }
@@ -190,8 +191,8 @@ function Chat() {
                 {message.parts?.map((part: any, i: number) => {
                   if (part.type === 'text') {
                     return (
-                      <Message 
-                        key={`${message.id}-${i}`} 
+                      <Message
+                        key={`${message.id}-${i}`}
                         from={message.role}>
                           <MessageContent>
                             <MessageResponse>{part.text}</MessageResponse>
@@ -251,16 +252,16 @@ This component connects [`useChat()`](https://ai-sdk.dev/docs/reference/ai-sdk-u
 It renders the response text using the [`<MessageResponse>`](https://ai-sdk.dev/elements/components/message#messageresponse-) component, and shows any tool invocations with the [`<Tool>`](https://ai-sdk.dev/elements/components/tool) component.
 
 
-## Test your agent 
+## Test your agent
 1. Run your Next.js app with `npm run dev`
 
 2. Open the chat at http://localhost:3000/chat
 
-3. Try asking about the weather. If your API key is set up correctly, you'll get a response.
+3. Try asking about the weather. If your API key is set up correctly, you'll get a response
 
 ## Next steps
 
-Congratulations on building your Mastra agent with Next.js! 🎉 
+Congratulations on building your Mastra agent with Next.js! 🎉
 
 From here, you can extend the project with your own tools and logic:
 
@@ -268,8 +269,8 @@ From here, you can extend the project with your own tools and logic:
 - Give your agent its own [tools](/docs/v1/agents/using-tools)
 - Add human-like [memory](/docs/v1/agents/agent-memory) to your agent
 
-When you're ready, read more about how Mastra integrates with AI SDK and Next.js, and how to deploy to Vercel:
+When you're ready, read more about how Mastra integrates with AI SDK and Next.js, and how to deploy your agent anywhere, including Vercel:
 
 - Integrate Mastra with [AI SDK](/docs/v1/frameworks/agentic-uis/ai-sdk)
-- Use Mastra in your [Next.js app](/docs/v1/frameworks/web-frameworks/next-js)
-- Deploy your agent to [Vercel](/docs/v1/deployment/serverless-platforms/vercel-deployer)
+- Deploy your agent to [Vercel](/docs/v1/deployment/cloud-providers/vercel-deployer)
+- Deploy your agent [anywhere](/docs/v1/deployment/overview)