@mastra/mcp-docs-server 1.0.0-beta.11 → 1.0.0-beta.14

package/.docs/raw/deployment/monorepo.mdx

@@ -1,11 +1,25 @@
 ---
-title: "Monorepo Deployment | Deployment"
+title: "Deploy in a Monorepo | Deployment"
 description: Learn how to deploy Mastra applications that are part of a monorepo setup
 ---
 
-# Monorepo Deployment
+# Deploy in a Monorepo
 
-Deploying Mastra in a monorepo follows the same approach as deploying a standalone application. While some [Cloud](./cloud-providers/) or [Serverless Platform](./cloud-providers/) providers may introduce extra requirements, the core setup is the same.
+Deploying Mastra in a monorepo follows the same approach as deploying a standalone application. While some [Cloud](/guides/v1/deployment) or [Serverless Platform](/guides/v1/deployment) providers may introduce extra requirements, the core setup is the same.
+
+## Supported monorepos
+
+Mastra works with:
+
+- npm workspaces
+- pnpm workspaces
+- Yarn workspaces
+- Turborepo
+
+Known limitations:
+
+- Bun workspaces - partial support; known issues
+- Nx - You can use Nx's [supported dependency strategies](https://nx.dev/concepts/decisions/dependency-management) but you need to have `package.json` files inside your workspace packages
 
 ## Example monorepo
 
@@ -44,10 +58,15 @@ api/
 
 ## Deployment configuration
 
-The image below shows how to select `apps/api` as the project root when deploying to [Mastra Cloud](./mastra-cloud/overview). While the interface may differ between providers, the configuration remains the same.
+The image below shows how to select `apps/api` as the project root when deploying to [Mastra Cloud](/docs/v1/mastra-cloud/overview). While the interface may differ between providers, the configuration remains the same.
 
 ![Deployment configuration](/img/monorepo/monorepo-mastra-cloud.jpg)
 
+
+:::info
+Make sure the correct package (e.g. `apps/api`) is selected as the deploy target. Selecting the wrong project root is a common deployment issue in monorepos.
+:::
+
 ## Dependency management
 
 In a monorepo, keep dependencies consistent to avoid version conflicts and build errors.
@@ -55,43 +74,3 @@ In a monorepo, keep dependencies consistent to avoid version conflicts and build
 - Use a **single lockfile** at the project root so all packages resolve the same versions.
 - Align versions of **shared libraries** (like Mastra or frameworks) to prevent duplicates.
 
-## Deployment pitfalls
-
-Common issues to watch for when deploying Mastra in a monorepo:
-
-- **Wrong project root**: make sure the correct package (e.g. `apps/api`) is selected as the deploy target.
-
-## Bundler options
-
-Use `transpilePackages` to compile TypeScript workspace packages or libraries. List package names exactly as they appear in each `package.json`. Use `externals` to exclude dependencies resolved at runtime, and `sourcemap` to emit readable stack traces.
-
-```typescript title="src/mastra/index.ts" showLineNumbers copy
-import { Mastra } from "@mastra/core";
-
-export const mastra = new Mastra({
-  // ...
-  bundler: {
-    transpilePackages: ["utils"],
-    externals: ["ui"],
-    sourcemap: true,
-  },
-});
-```
-
-> See [Mastra Class](/reference/v1/core/mastra-class) for more configuration options.
-
-## Supported monorepos
-
-Mastra works with:
-
-- npm workspaces
-- pnpm workspaces
-- Yarn workspaces
-- Turborepo
-
-Known limitations:
-
-- Bun workspaces — partial support; known issues
-- Nx — You can use Nx's [supported dependency strategies](https://nx.dev/concepts/decisions/dependency-management) but you need to have `package.json` files inside your workspace packages
-
-> If you are experiencing issues with monorepos see our: [Monorepos Support mega issue](https://github.com/mastra-ai/mastra/issues/6852).

package/.docs/raw/deployment/overview.mdx

@@ -5,78 +5,60 @@ description: Learn about different deployment options for your Mastra applicatio
 
 # Deployment Overview
 
-Mastra offers multiple deployment options to suit your application's needs, from fully-managed solutions to self-hosted options, and web framework integrations. This guide will help you understand the available deployment paths and choose the right one for your project.
+Mastra applications can be deployed to any Node.js-compatible environment. You can deploy a Mastra server, integrate with an existing web framework, deploy to cloud providers, or use Mastra Cloud for managed hosting.
 
-## Choosing a Deployment Option
+## Runtime support
 
-| Option                   | Best For                                                      | Key Benefits                                                         |
-| ------------------------ | ------------------------------------------------------------- | -------------------------------------------------------------------- |
-| **Mastra Cloud**         | Teams wanting to ship quickly without infrastructure concerns | Fully-managed, automatic scaling, built-in observability             |
-| **Framework Deployment** | Teams already using Next.js, Astro etc                        | Simplify deployment with a unified codebase for frontend and backend |
-| **Server Deployment**    | Teams needing maximum control and customization               | Full control, custom middleware, integrate with existing apps        |
-| **Serverless Platforms** | Teams already using Vercel, Netlify, or Cloudflare            | Platform integration, simplified deployment, automatic scaling       |
-
-## Deployment Options
-
-### Runtime support
+Mastra can run against any of these runtime environments:
 
 - Node.js `v22.13.0` or later
 - Bun
 - Deno
-- [Cloudflare](../deployment/cloud-providers/cloudflare-deployer)
-
-### Mastra Cloud
-
-Mastra Cloud is a deployment platform that connects to your GitHub repository, automatically deploys on code changes, and provides monitoring tools. It includes:
+- Cloudflare
 
-- GitHub repository integration
-- Deployment on git push
-- Agent testing interface
-- Comprehensive logs and traces
-- Custom domains for each project
+## Deployment Options
 
-[View Mastra Cloud documentation →](./mastra-cloud/overview)
+### Mastra Server
 
-### With a Web Framework
+Mastra provides a [server](/docs/v1/server/mastra-server) powered by Hono that can be deployed independently. Use the `mastra build` command to build your application and deploy the output to your preferred VM, container, or PaaS platform.
 
-Mastra can be integrated with a variety of web frameworks. For example, see one of the following for a detailed guide.
+See the [Mastra server deployment guide](/docs/v1/deployment/mastra-server).
 
-- [With Next.js](/guides/v1/getting-started/next-js)
-- [With Astro](/guides/v1/getting-started/astro)
+### Monorepo
 
-When integrated with a framework, Mastra typically requires no additional configuration for deployment.
+Deploy a Mastra server as part of a monorepo setup, following the same approach as standalone deployment.
 
-[View Web Framework Integration →](./web-framework)
+Read about [monorepo deployment](/docs/v1/deployment/monorepo).
 
-### With a Server
+### Cloud Providers
 
-You can deploy Mastra as a standard Node.js HTTP server, which gives you full control over your infrastructure and deployment environment.
+Mastra applications can be deployed to cloud providers and serverless platforms. Mastra includes optional built-in deployers for Vercel, Netlify, and Cloudflare to automate the build and deployment process.
 
-- Custom API routes and middleware
-- Configurable CORS and authentication
-- Deploy to VMs, containers, or PaaS platforms
-- Ideal for integrating with existing Node.js applications
+- [Amazon EC2](/guides/v1/deployment/amazon-ec2)
+- [AWS Lambda](/guides/v1/deployment/aws-lambda)
+- [Azure App Services](/guides/v1/deployment/azure-app-services)
+- [Cloudflare](/guides/v1/deployment/cloudflare-deployer)
+- [Digital Ocean](/guides/v1/deployment/digital-ocean)
+- [Netlify](/guides/v1/deployment/netlify-deployer)
+- [Vercel](/guides/v1/deployment/vercel-deployer)
 
-[Building Mastra →](./building-mastra)
+### Web Framework
 
-### Serverless Platforms
+When Mastra is integrated with a web framework, it deploys alongside your application using the framework's standard deployment process. The guides below cover framework-specific configuration requirements for deployment:
 
-Mastra provides platform-specific deployers for popular serverless platforms, enabling you to deploy your application with minimal configuration.
+- [With Next.js on Vercel](/docs/v1/deployment/web-framework#with-nextjs-on-vercel)
+- [With Astro on Vercel](/docs/v1/deployment/web-framework#with-astro-on-vercel)
+- [With Astro on Netlify](/docs/v1/deployment/web-framework#with-astro-on-netlify)
 
-- Deploy to Cloudflare Workers, Vercel, or Netlify
-- Platform-specific optimizations
-- Simplified deployment process
-- Automatic scaling through the platform
+### Mastra Cloud
 
-[Building Mastra →](./building-mastra)
+We're building Mastra Cloud to be the easiest place to deploy and observe your Mastra agents. It's currently in beta.
 
-## Client Configuration
+Learn more in the [Mastra Cloud docs](/docs/v1/mastra-cloud/overview).
 
-Once your Mastra application is deployed, you'll need to configure your client to communicate with it. The Mastra Client SDK provides a simple and type-safe interface for interacting with your Mastra server.
+## Workflow Runners
 
-- Type-safe API interactions
-- Authentication and request handling
-- Retries and error handling
-- Support for streaming responses
+Mastra supports deploying workflows to specialized workflow execution platforms that handle orchestration, monitoring, and reliability. [Inngest](https://www.inngest.com) is a developer platform for running background workflows without managing infrastructure. Mastra workflows can be deployed to Inngest, which provides step memoization, automatic retries, real-time monitoring, and suspend/resume capabilities.
 
-[Client configuration guide →](/docs/v1/server-db/mastra-client)
+- [Inngest deployment guide](/guides/v1/deployment/inngest)
+- [Inngest workflow example](https://github.com/mastra-ai/mastra/tree/main/examples/inngest)

package/.docs/raw/deployment/web-framework.mdx

@@ -1,24 +1,26 @@
 ---
-title: "Web Framework Integration | Deployment"
+title: "Deploy with a Web Framework | Deployment"
 description: "Learn how Mastra can be deployed when integrated with a Web Framework"
 ---
 
-# Web Framework Integration
+# Deploy with a Web Framework
 
-This guide covers deploying integrated Mastra applications. Mastra can be integrated with a variety of web frameworks, see one of the following for a detailed guide.
+When Mastra is integrated with a web framework, it deploys alongside your application using the framework's standard deployment process. Follow the instructions below to ensure your Mastra integration deploys correctly.
+
+:::warning
+If you're deploying to a cloud provider, remove any usage of [LibSQLStore](/reference/v1/storage/libsql) from your Mastra configuration. LibSQLStore requires filesystem access and is not compatible with serverless platforms.
+:::
+
+Integration guides:
 
 - [With Next.js](/guides/v1/getting-started/next-js)
 - [With Astro](/guides/v1/getting-started/astro)
 
-When integrated with a framework, Mastra typically requires no additional configuration for deployment.
-
 ## With Next.js on Vercel
 
-If you've integrated Mastra with Next.js [by following our guide](/guides/v1/getting-started/next-js) and plan to deploy to Vercel, no additional setup is required.
+If you've integrated Mastra with Next.js [by following our guide](/guides/v1/getting-started/next-js) and plan to deploy to Vercel, add `serverExternalPackages: ["@mastra/*"]` to your `next.config.ts`:
 
-The only thing to verify is that you've added the following to your `next.config.ts` and removed any usage of [LibSQLStore](/docs/v1/deployment/overview), which is not supported in serverless environments:
-
-```typescript {4} title="next.config.ts" showLineNumbers copy
+```typescript {4} title="next.config.ts"
 import type { NextConfig } from "next";
 
 const nextConfig: NextConfig = {
@@ -30,16 +32,13 @@ export default nextConfig;
 
 ## With Astro on Vercel
 
-If you've integrated Mastra with Astro [by following our guide](/guides/v1/getting-started/astro) and plan to deploy to Vercel, no additional setup is required.
-
-The only thing to verify is that you've added the following to your `astro.config.mjs` and removed any usage of [LibSQLStore](/docs/v1/deployment/overview), which is not supported in serverless environments:
+If you've integrated Mastra with Astro [by following our guide](/guides/v1/getting-started/astro) and plan to deploy to Vercel, add the Vercel adapter and server output to your `astro.config.mjs`:
 
-```javascript {2,6,7} title="astro.config.mjs" showLineNumbers copy
+```javascript {2,5-6} title="astro.config.mjs"
 import { defineConfig } from "astro/config";
 import vercel from "@astrojs/vercel";
 
 export default defineConfig({
-  // ...
   adapter: vercel(),
   output: "server",
 });
@@ -47,16 +46,13 @@ export default defineConfig({
 
 ## With Astro on Netlify
 
-If you've integrated Mastra with Astro [by following our guide](/guides/v1/getting-started/astro) and plan to deploy to Netlify, no additional setup is required.
-
-The only thing to verify is that you've added the following to your `astro.config.mjs` and removed any usage of [LibSQLStore](/docs/v1/deployment/overview), which is not supported in serverless environments:
+If you've integrated Mastra with Astro [by following our guide](/guides/v1/getting-started/astro) and plan to deploy to Netlify, add the Netlify adapter and server output to your `astro.config.mjs`:
 
-```javascript {2,6,7} title="astro.config.mjs" showLineNumbers copy
+```javascript {2,5-6} title="astro.config.mjs"
 import { defineConfig } from "astro/config";
 import netlify from "@astrojs/netlify";
 
 export default defineConfig({
-  // ...
   adapter: netlify(),
   output: "server",
 });

package/.docs/raw/evals/custom-scorers.mdx

@@ -65,7 +65,6 @@ For type safety and compatibility with both live agent scoring and trace scoring
 
 ```typescript
 const myScorer = createScorer({
-  // ...
   type: "agent", // Automatically handles agent input/output types
 }).generateScore(({ run, results }) => {
   // run.output is automatically typed as ScorerRunOutputForAgent
@@ -241,9 +240,13 @@ A custom scorer in Mastra uses `createScorer` with four core components:
 
 Together, these components allow you to define custom evaluation logic using LLMs as judges.
 
-> See [createScorer](/reference/v1/evals/create-scorer) for the full API and configuration options.
+:::info
 
-```typescript title="src/mastra/scorers/gluten-checker.ts" showLineNumbers copy
+Visit [createScorer](/reference/v1/evals/create-scorer) for the full API and configuration options.
+
+:::
+
+```typescript title="src/mastra/scorers/gluten-checker.ts"
 import { createScorer } from "@mastra/core/evals";
 import { z } from "zod";
 
@@ -399,7 +402,7 @@ The reason generation step creates explanations that help users understand why a
 
 ## High gluten-free example
 
-```typescript title="src/example-high-gluten-free.ts" showLineNumbers copy
+```typescript title="src/example-high-gluten-free.ts"
 const result = await glutenCheckerScorer.run({
   input: [{ role: 'user', content: 'Mix rice, beans, and vegetables' }],
   output: { text: 'Mix rice, beans, and vegetables' },
@@ -425,7 +428,7 @@ console.log('Reason:', result.reason);
 
 ## Partial gluten example
 
-```typescript title="src/example-partial-gluten.ts" showLineNumbers copy
+```typescript title="src/example-partial-gluten.ts"
 const result = await glutenCheckerScorer.run({
   input: [{ role: "user", content: "Mix flour and water to make dough" }],
   output: { text: "Mix flour and water to make dough" },
@@ -451,7 +454,7 @@ console.log("Reason:", result.reason);
 
 ## Low gluten-free example
 
-```typescript title="src/example-low-gluten-free.ts" showLineNumbers copy
+```typescript title="src/example-low-gluten-free.ts"
 const result = await glutenCheckerScorer.run({
   input: [{ role: "user", content: "Add soy sauce and noodles" }],
   output: { text: "Add soy sauce and noodles" },

package/.docs/raw/evals/overview.mdx

@@ -23,7 +23,7 @@ There are different kinds of scorers, each serving a specific purpose. Here are
 
 To access Mastra's scorers feature install the `@mastra/evals` package.
 
-```bash copy
+```bash
 npm install @mastra/evals@beta
 ```
 
@@ -35,7 +35,7 @@ npm install @mastra/evals@beta
 
 You can add built-in scorers to your agents to automatically evaluate their outputs. See the [full list of built-in scorers](/docs/v1/evals/built-in-scorers) for all available options.
 
-```typescript title="src/mastra/agents/evaluated-agent.ts" showLineNumbers copy
+```typescript title="src/mastra/agents/evaluated-agent.ts"
 import { Agent } from "@mastra/core/agent";
 import {
   createAnswerRelevancyScorer,
@@ -43,7 +43,6 @@ import {
 } from "@mastra/evals/scorers/prebuilt";
 
 export const evaluatedAgent = new Agent({
-  // ...
   scorers: {
     relevancy: {
       scorer: createAnswerRelevancyScorer({ model: "openai/gpt-4.1-nano" }),
@@ -61,13 +60,12 @@ export const evaluatedAgent = new Agent({
 
 You can also add scorers to individual workflow steps to evaluate outputs at specific points in your process:
 
-```typescript title="src/mastra/workflows/content-generation.ts" showLineNumbers copy
+```typescript title="src/mastra/workflows/content-generation.ts"
 import { createWorkflow, createStep } from "@mastra/core/workflows";
 import { z } from "zod";
 import { customStepScorer } from "../scorers/custom-step-scorer";
 
 const contentStep = createStep({
-  // ...
   scorers: {
     customStepScorer: {
       scorer: customStepScorer(),
@@ -115,7 +113,6 @@ To score traces, you first need to register your scorers with your Mastra instan
 
 ```typescript
 const mastra = new Mastra({
-  // ...
   scorers: {
     answerRelevancy: myAnswerRelevancyScorer,
     responseQuality: myResponseQualityScorer,

package/.docs/raw/evals/running-in-ci.mdx

@@ -15,7 +15,7 @@ You can use any testing framework that supports ESM modules, such as [Vitest](ht
 
 Use `runEvals` to evaluate your agent against multiple test cases. The function accepts an array of data items, each containing an `input` and optional `groundTruth` for scorer validation.
 
-```typescript copy showLineNumbers title="src/mastra/agents/weather-agent.test.ts"
+```typescript title="src/mastra/agents/weather-agent.test.ts"
 import { describe, it, expect } from 'vitest';
 import { createScorer, runEvals } from "@mastra/core/evals";
 import { weatherAgent } from "./weather-agent";
@@ -72,7 +72,7 @@ The `runEvals` function returns an object with:
 
 Create separate test cases for different evaluation scenarios:
 
-```typescript copy showLineNumbers title="src/mastra/agents/weather-agent.test.ts"
+```typescript title="src/mastra/agents/weather-agent.test.ts"
 describe('Weather Agent Tests', () => {
   const locationScorer = createScorer({ /* ... */ });
 

package/.docs/raw/getting-started/manual-install.mdx

@@ -22,7 +22,7 @@ If you prefer not to use our automatic CLI tool, you can set up your project you
 
 Create a new project and change directory:
 
-```bash copy
+```bash
 mkdir my-first-agent && cd my-first-agent
 ```
 
@@ -31,7 +31,7 @@ Initialize a TypeScript project and install the following dependencies:
 <Tabs>
 <TabItem value="npm" label="npm">
 
-```bash copy
+```bash
 npm init -y
 npm install -D typescript @types/node mastra@beta
 npm install @mastra/core@beta zod@^4
@@ -40,7 +40,7 @@ npm install @mastra/core@beta zod@^4
 </TabItem>
 <TabItem value="pnpm" label="pnpm">
 
-```bash copy
+```bash
 pnpm init
 pnpm add -D typescript @types/node mastra@beta
 pnpm add @mastra/core@beta zod@^4
@@ -49,7 +49,7 @@ pnpm add @mastra/core@beta zod@^4
 </TabItem>
 <TabItem value="yarn" label="yarn">
 
-```bash copy
+```bash
 yarn init -y
 yarn add -D typescript @types/node mastra@beta
 yarn add @mastra/core@beta zod@^4
@@ -58,7 +58,7 @@ yarn add @mastra/core@beta zod@^4
 </TabItem>
 <TabItem value="bun" label="bun">
 
-```bash copy
+```bash
 bun init -y
 bun add -d typescript @types/node mastra@beta
 bun add @mastra/core@beta zod@^4
@@ -69,7 +69,7 @@ bun add @mastra/core@beta zod@^4
 
 Add `dev` and `build` scripts to your `package.json` file:
 
-```json title="package.json" copy /,/ /"dev": "mastra dev",/ /"build": "mastra build"/
+```json title="package.json" /,/ /"dev": "mastra dev",/ /"build": "mastra build"/
 {
   "scripts": {
     "test": "echo \"Error: no test specified\" && exit 1",
@@ -85,13 +85,13 @@ Add `dev` and `build` scripts to your `package.json` file:
 
 Create a `tsconfig.json` file:
 
-```bash copy
+```bash
 touch tsconfig.json
 ```
 
 Add the following configuration:
 
-```json title="tsconfig.json" copy
+```json title="tsconfig.json"
 {
   "compilerOptions": {
     "target": "ES2022",
@@ -120,13 +120,13 @@ Mastra requires modern `module` and `moduleResolution` settings. Using `CommonJS
 
 Create an `.env` file:
 
-```bash copy
+```bash
 touch .env
 ```
 
 Add your API key:
 
-```bash title=".env" copy
+```bash title=".env"
 GOOGLE_GENERATIVE_AI_API_KEY=<your-api-key>
 ```
 
@@ -142,13 +142,13 @@ This guide uses Google Gemini, but you can use any supported [model provider](/m
 
 Create a `weather-tool.ts` file:
 
-```bash copy
+```bash
 mkdir -p src/mastra/tools && touch src/mastra/tools/weather-tool.ts
 ```
 
 Add the following code:
 
-```ts title="src/mastra/tools/weather-tool.ts" showLineNumbers copy
+```ts title="src/mastra/tools/weather-tool.ts"
 import { createTool } from "@mastra/core/tools";
 import { z } from "zod";
 
@@ -181,13 +181,13 @@ We've shortened and simplified the `weatherTool` example here. You can see the c
 
 Create a `weather-agent.ts` file:
 
-```bash copy
+```bash
 mkdir -p src/mastra/agents && touch src/mastra/agents/weather-agent.ts
 ```
 
 Add the following code:
 
-```ts title="src/mastra/agents/weather-agent.ts" showLineNumbers copy
+```ts title="src/mastra/agents/weather-agent.ts"
 import { Agent } from "@mastra/core/agent";
 import { weatherTool } from "../tools/weather-tool";
 
@@ -217,13 +217,13 @@ export const weatherAgent = new Agent({
 
 Create the Mastra entry point and register your agent:
 
-```bash copy
+```bash
 touch src/mastra/index.ts
 ```
 
 Add the following code:
 
-```ts title="src/mastra/index.ts" showLineNumbers copy
+```ts title="src/mastra/index.ts"
 import { Mastra } from "@mastra/core";
 import { weatherAgent } from "./agents/weather-agent";
 
@@ -241,28 +241,28 @@ You can now launch [Studio](/docs/v1/getting-started/studio) and test your agent
 <Tabs>
 <TabItem value="npm" label="npm">
 
-```bash copy
+```bash
 npm run dev
 ```
 
 </TabItem>
 <TabItem value="pnpm" label="pnpm">
 
-```bash copy
+```bash
 pnpm run dev
 ```
 
 </TabItem>
 <TabItem value="yarn" label="yarn">
 
-```bash copy
+```bash
 yarn run dev
 ```
 
 </TabItem>
 <TabItem value="bun" label="bun">
 
-```bash copy
+```bash
 bun run dev
 ```
 

package/.docs/raw/getting-started/mcp-docs-server.mdx

@@ -25,7 +25,7 @@ During the interactive [create-mastra](/reference/v1/cli/create-mastra) wizard,
 
 If there are no specific instructions for your tool below, you may be able to add the MCP server with this common JSON configuration anyways.
 
-```json copy
+```json
 {
   "mcpServers": {
     "mastra": {
@@ -41,7 +41,7 @@ If there are no specific instructions for your tool below, you may be able to ad
 
 Install using the terminal command:
 
-```bash copy
+```bash
 claude mcp add mastra -- npx -y @mastra/mcp-docs-server@beta
 ```
 

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

@@ -6,6 +6,7 @@ description: Choose how to get started with Mastra - quickstart, framework integ
 import { CardGrid, CardGridItem } from "@site/src/components/cards/card-grid";
  
 # Start
+
 Create a new Mastra project, or integrate Mastra with your preferred framework to start building.
 
 ## New project
@@ -62,11 +63,19 @@ Integrate Mastra with SvelteKit
     href="/guides/v1/getting-started/express"
     logo={<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 861.6297 500" width="32" height="32"><path d="M822.05434 464.78529c-23.57102 8.91305-50.08664-1.16881-61.78139-23.49073l-112.4692-155.53981-16.30803-21.72701-130.51543 177.49688c-11.00437 21.35391-36.14786 31.22309-58.7396 23.05618l168.14149-225.57746L453.94772 35.178469c23.20955-8.38407 49.07747.715704 61.98587 21.727011l116.55901 157.4569L749.74175 57.518928c11.0937-21.002063 36.16603-30.356097 58.30506-21.752557l-60.70782 80.543289-82.23033 107.02469c-9.6735 8.63851-9.6735 23.77308 0 32.41158l156.61338 209.03936ZM39.626477 236.19163l13.700796-67.66046C90.953337 34.743916 244.32044-20.928337 349.83703 61.941017 411.61839 110.45615 427.0318 179.1902 424.01558 256.64057H75.94892C70.325459 394.9777 170.14188 478.51165 297.82 435.87559c42.0737-15.33669 73.74401-50.3044 84.17297-93.75842 6.74816-21.72701 17.89283-25.45896 38.29067-19.1709-6.89256 53.65922-37.9963 101.20027-84.40304 129.00732-77.62638 42.45286-173.75024 30.1679-238.204672-30.44338-31.082401-34.94215-49.844311-79.11186-53.49956-125.76104 0-7.66837-2.556118-14.82549-4.345401-21.727-.170408-12.89987-.255612-25.51006-.255612-37.83054zm36.756986-9.35539H391.14389c-1.96821-100.27654-65.2577-171.413323-149.66074-172.077907C147.52023 53.480264 80.294322 123.05782 76.153409 226.40169Z" fill="currentColor"/></svg>}
   >
-    Create endpoints that call agents and stream responses
+    Integrate Mastra with the Express server adapter
+  </CardGridItem>
+  <CardGridItem
+    title="Hono"
+    href="/guides/v1/getting-started/hono"
+    logo={<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 76 98" width="32" height="32"><path fill="url(#a)" d="m11 25 7 9s9-18 22-34c17 20 36 48 36 64 0 20-19 34-37 34C17 98 0 81 0 61c0-6 3-24 11-36Z"/><path fill="#F95" d="M39 21c47 51 14 66 0 66-11 0-51-11 0-66Z"/><defs><linearGradient id="a" x2="0%" y2="100%"><stop stop-color="#F84"/><stop offset="100%" stop-color="#F30"/></linearGradient></defs></svg>}
+  >
+    Integrate Mastra with the Hono server adapter
   </CardGridItem>
 </CardGrid>
 
 Mastra works great with agentic UI frameworks like [AI SDK UI](/guides/v1/build-your-ui/ai-sdk-ui), [CopilotKit](/guides/v1/build-your-ui/copilotkit), and [Assistant UI](/guides/v1/build-your-ui/assistant-ui). Use them with any of the frontend frameworks above to stream agent responses, render tools, and build chat interfaces.
 
 ## Start from a template
+
 Have a use case in mind? Start with a pre-built [template](https://mastra.ai/templates) from Mastra or our community.

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

@@ -101,7 +101,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 [Mastra Server](/docs/v1/server-db/mastra-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/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/guides/agent-frameworks/ai-sdk.mdx

@@ -49,7 +49,7 @@ Install `@mastra/ai-sdk` to begin using the `withMastra()` function.
 
 Processors let you transform messages before they're sent to the model (`processInput`) and after responses are received (`processOutputResult`). This example creates a logging processor that logs message counts at each stage, then wraps an OpenAI model with it.
 
-```typescript title="src/example.ts" copy
+```typescript title="src/example.ts"
 import { openai } from '@ai-sdk/openai';
 import { generateText } from 'ai';
 import { withMastra } from '@mastra/ai-sdk';
@@ -80,9 +80,9 @@ const { text } = await generateText({
 
 ### With Memory
 
-Memory automatically loads previous messages from storage before the LLM call and saves new messages after. This example configures a LibSQL storage backend to persist conversation history, loading the last 10 messages for context.
+Memory automatically loads previous messages from storage before the LLM call and saves new messages after. This example configures a libSQL storage backend to persist conversation history, loading the last 10 messages for context.
 
-```typescript title="src/memory-example.ts" copy
+```typescript title="src/memory-example.ts"
 import { openai } from '@ai-sdk/openai';
 import { generateText } from 'ai';
 import { withMastra } from '@mastra/ai-sdk';
@@ -113,7 +113,7 @@ const { text } = await generateText({
 
 You can combine processors and memory together. Input processors run after memory loads historical messages, and output processors run before memory saves the response.
 
-```typescript title="src/combined-example.ts" copy
+```typescript title="src/combined-example.ts"
 import { openai } from '@ai-sdk/openai';
 import { generateText } from 'ai';
 import { withMastra } from '@mastra/ai-sdk';