@mastra/mcp-docs-server 0.13.2 → 0.13.3-alpha.0

package/.docs/raw/getting-started/model-providers.mdx

@@ -3,7 +3,7 @@ title: "Model Providers | Getting Started | Mastra Docs"
 description: "Learn how to configure and use different model providers with Mastra."
 ---
 
-import { Callout, Tabs } from 'nextra/components'
+import { Callout } from 'nextra/components'
 
 # Model Providers
 
@@ -26,11 +26,11 @@ const result = await agent.generate("What is the weather like?");
 
 Model providers from the AI SDK can be grouped into three main categories:
 
-- Official providers maintained by the AI SDK team
-- OpenAI-compatible providers
-- Community providers
+- [Official providers maintained by the AI SDK team](/docs/getting-started/model-providers#official-providers)
+- [OpenAI-compatible providers](/docs/getting-started/model-providers#openai-compatible-providers)
+- [Community providers](/docs/getting-started/model-providers#community-providers)
 
-You can find a list of all available model providers in the [AI SDK documentation](https://ai-sdk.dev/providers/ai-sdk-providers).
+> You can find a list of all available model providers in the [AI SDK documentation](https://ai-sdk.dev/providers/ai-sdk-providers).
 
 <Callout>
 AI SDK model providers are packages that need to be installed in your Mastra project.
@@ -41,125 +41,116 @@ If you want to use a different model provider, you need to install it in your pr
 
 Here are some examples of how Mastra agents can be configured to use the different types of model providers:
 
-<Tabs items={["Official providers", "OpenAI compatible providers", "Community providers"]}>
-  <Tabs.Tab>
-    ### Official providers
-
-    Official model providers are maintained by the AI SDK team.
-    Their packages are usually prefixed with `@ai-sdk/`, e.g. `@ai-sdk/anthropic`, `@ai-sdk/openai`, etc.
-
-    ```typescript showLineNumbers copy {1,7} filename="src/mastra/agents/weather-agent.ts"
-    import { openai } from "@ai-sdk/openai";
-    import { Agent } from "@mastra/core/agent";
-
-    const agent = new Agent({
-      name: "WeatherAgent",
-      instructions: "Instructions for the agent...",
-      model: openai("gpt-4-turbo"),
-    });
-    ```
-
-    Additional configuration may be done by importing a helper function from the AI SDK provider.
-    Here's an example using the OpenAI provider:
-
-    ```typescript showLineNumbers copy filename="src/mastra/agents/weather-agent.ts" {1,4-8,13}
-    import { createOpenAI } from "@ai-sdk/openai";
-    import { Agent } from "@mastra/core/agent"
-
-    const openai = createOpenAI({
-        baseUrl: "<your-custom-base-url>",
-        apiKey: "<your-custom-api-key>",
-        ...otherOptions
-    });
-
-    const agent = new Agent({
-        name: "WeatherAgent",
-        instructions: "Instructions for the agent...",
-        model: openai("<model-name>"),
-    });
-    ```
-
-    Different AI providers may have different options for configuration. Please refer to the [AI SDK documentation](https://ai-sdk.dev/providers/ai-sdk-providers) for more information.
-  </Tabs.Tab>
-
-  <Tabs.Tab>
-    ### OpenAI-compatible providers
-
-    Some language model providers implement the OpenAI API. For these providers, you can use the [`@ai-sdk/openai-compatible`](https://www.npmjs.com/package/@ai-sdk/openai-compatible) provider.
-
-    Here's the general setup and provider instance creation:
-
-    ```typescript showLineNumbers copy filename="src/mastra/agents/weather-agent.ts" {1,4-14,19}
-    import { createOpenAICompatible } from "@ai-sdk/openai-compatible";
-    import { Agent } from "@mastra/core/agent";
-
-    const openaiCompatible = createOpenAICompatible({
-        name: "<model-name>",
-        baseUrl: "<base-url>",
-        apiKey: "<api-key>",
-        headers: {},
-        queryParams: {},
-        fetch: async (url, options) => {
-            // custom fetch logic
-            return fetch(url, options);
-        }
-    });
-
-    const agent = new Agent({
-        name: "WeatherAgent",
-        instructions: "Instructions for the agent...",
-        model: openaiCompatible("<model-name>"),
-    });
-    ```
-
-    For more information on the OpenAI-compatible provider, please refer to the [AI SDK documentation](https://ai-sdk.dev/providers/openai-compatible-providers).
-    
-  </Tabs.Tab>
-
-  <Tabs.Tab>
-    ### Community providers
-
-    The AI SDK provides a [Language Model Specification](https://github.com/vercel/ai/tree/main/packages/provider/src/language-model/v1).
-    Following this specification, you can create your own model provider compatible with the AI SDK.
-
-    Some community providers have implemented this specification and are compatible with the AI SDK.
-    We will look at one such provider, the Ollama provider available in the [`ollama-ai-provider`](https://github.com/sgomez/ollama-ai-provider) package.
-
-    Here's an example:
-
-    ```typescript showLineNumbers copy filename="src/mastra/agents/weather-agent.ts" {1,7}
-    import { ollama } from "ollama-ai-provider";
-    import { Agent } from "@mastra/core/agent";
-
-    const agent = new Agent({
-        name: "WeatherAgent",
-        instructions: "Instructions for the agent...",
-        model: ollama("llama3.2:latest"),
-    });
-    ```
-
-    You can also configure the Ollama provider like so:
-
-    ```typescript showLineNumbers copy filename="src/mastra/agents/weather-agent.ts" {1,4-7,12}
-    import { createOllama } from "ollama-ai-provider";
-    import { Agent } from "@mastra/core/agent";
-
-    const ollama = createOllama({
-        baseUrl: "<your-custom-base-url>",
-        ...otherOptions,
-    });
-
-    const agent = new Agent({
-        name: "WeatherAgent",
-        instructions: "Instructions for the agent...",
-        model: ollama("llama3.2:latest"),
-    });
-    ```
-
-    For more information on the Ollama provider and other available community providers, please refer to the [AI SDK documentation](https://ai-sdk.dev/providers/community-providers).
-
-    <Callout>
-    While this example shows how to use the Ollama provider, other providers like `openrouter`, `azure`, etc. may also be used.
-    </Callout>
-  </Tabs.Tab>
-</Tabs>
+### Official providers
+
+Official model providers are maintained by the AI SDK team.
+Their packages are usually prefixed with `@ai-sdk/`, e.g. `@ai-sdk/anthropic`, `@ai-sdk/openai`, etc.
+
+```typescript showLineNumbers copy {1,7} filename="src/mastra/agents/weather-agent.ts"
+import { openai } from "@ai-sdk/openai";
+import { Agent } from "@mastra/core/agent";
+
+const agent = new Agent({
+  name: "WeatherAgent",
+  instructions: "Instructions for the agent...",
+  model: openai("gpt-4-turbo"),
+});
+```
+
+Additional configuration may be done by importing a helper function from the AI SDK provider.
+Here's an example using the OpenAI provider:
+
+```typescript showLineNumbers copy filename="src/mastra/agents/weather-agent.ts" {1,4-8,13}
+import { createOpenAI } from "@ai-sdk/openai";
+import { Agent } from "@mastra/core/agent"
+
+const openai = createOpenAI({
+    baseUrl: "<your-custom-base-url>",
+    apiKey: "<your-custom-api-key>",
+    ...otherOptions
+});
+
+const agent = new Agent({
+    name: "WeatherAgent",
+    instructions: "Instructions for the agent...",
+    model: openai("<model-name>"),
+});
+```
+
+### OpenAI-compatible providers
+
+Some language model providers implement the OpenAI API. For these providers, you can use the [`@ai-sdk/openai-compatible`](https://www.npmjs.com/package/@ai-sdk/openai-compatible) provider.
+
+Here's the general setup and provider instance creation:
+
+```typescript showLineNumbers copy filename="src/mastra/agents/weather-agent.ts" {1,4-14,19}
+import { createOpenAICompatible } from "@ai-sdk/openai-compatible";
+import { Agent } from "@mastra/core/agent";
+
+const openaiCompatible = createOpenAICompatible({
+    name: "<model-name>",
+    baseUrl: "<base-url>",
+    apiKey: "<api-key>",
+    headers: {},
+    queryParams: {},
+    fetch: async (url, options) => {
+        // custom fetch logic
+        return fetch(url, options);
+    }
+});
+
+const agent = new Agent({
+    name: "WeatherAgent",
+    instructions: "Instructions for the agent...",
+    model: openaiCompatible("<model-name>"),
+});
+```
+
+For more information on the OpenAI-compatible provider, please refer to the [AI SDK documentation](https://ai-sdk.dev/providers/openai-compatible-providers).
+
+### Community providers
+
+The AI SDK provides a [Language Model Specification](https://github.com/vercel/ai/tree/main/packages/provider/src/language-model/v1).
+Following this specification, you can create your own model provider compatible with the AI SDK.
+
+Some community providers have implemented this specification and are compatible with the AI SDK.
+We will look at one such provider, the Ollama provider available in the [`ollama-ai-provider`](https://github.com/sgomez/ollama-ai-provider) package.
+
+Here's an example:
+
+```typescript showLineNumbers copy filename="src/mastra/agents/weather-agent.ts" {1,7}
+import { ollama } from "ollama-ai-provider";
+import { Agent } from "@mastra/core/agent";
+
+const agent = new Agent({
+    name: "WeatherAgent",
+    instructions: "Instructions for the agent...",
+    model: ollama("llama3.2:latest"),
+});
+```
+
+You can also configure the Ollama provider like so:
+
+```typescript showLineNumbers copy filename="src/mastra/agents/weather-agent.ts" {1,4-7,12}
+import { createOllama } from "ollama-ai-provider";
+import { Agent } from "@mastra/core/agent";
+
+const ollama = createOllama({
+    baseUrl: "<your-custom-base-url>",
+    ...otherOptions,
+});
+
+const agent = new Agent({
+    name: "WeatherAgent",
+    instructions: "Instructions for the agent...",
+    model: ollama("llama3.2:latest"),
+});
+```
+
+For more information on the Ollama provider and other available community providers, please refer to the [AI SDK documentation](https://ai-sdk.dev/providers/community-providers).
+
+<Callout>
+While this example shows how to use the Ollama provider, other providers like `openrouter`, `azure`, etc. may also be used.
+</Callout>
+
+Different AI providers may have different options for configuration. Please refer to the [AI SDK documentation](https://ai-sdk.dev/providers/ai-sdk-providers) for more information.

package/.docs/raw/memory/overview.mdx

@@ -82,6 +82,36 @@ const response = await myMemoryAgent.stream("Hello, my name is Alice.", {
 
 **Important:** without these ID's your agent will not use memory, even if memory is properly configured. The playground handles this for you, but you need to add ID's yourself when using memory in your application.
 
+### Thread Title Generation
+
+Mastra can automatically generate meaningful titles for conversation threads based on the user's first message. This helps organize and identify conversations in your application UI.
+
+```typescript {3-7}
+const memory = new Memory({
+  options: {
+    threads: {
+      generateTitle: true, // Enable automatic title generation
+    },
+  },
+});
+```
+
+By default, title generation uses the same model as your agent. For cost optimization, you can specify a cheaper model specifically for title generation:
+
+```typescript {5-7}
+const memory = new Memory({
+  options: {
+    threads: {
+      generateTitle: {
+        model: openai("gpt-4.1-nano"), // Use cheaper model for titles
+      },
+    },
+  },
+});
+```
+
+Title generation happens asynchronously after the agent responds, so it doesn't impact response time. See the [full configuration reference](../../reference/memory/Memory.mdx#thread-title-generation) for more details and examples.
+
 ## Conversation History
 
 By default, the `Memory` instance includes the [last 10 messages](../../reference/memory/Memory.mdx) from the current Memory thread in each new request. This provides the agent with immediate conversational context.

package/.docs/raw/reference/agents/generate.mdx

@@ -261,14 +261,14 @@ Configuration options for memory management:
       description: "Thread-specific memory configuration.",
       properties: [
         {
-          type: "boolean",
+          type: "boolean | object",
           parameters: [
             {
               name: "generateTitle",
-              type: "boolean",
+              type: "boolean | { model: LanguageModelV1 | ((ctx: RuntimeContext) => LanguageModelV1 | Promise<LanguageModelV1>) }",
               isOptional: true,
               description:
-                "Whether to automatically generate titles for new threads.",
+                "Controls automatic thread title generation from the user's first message. Can be a boolean to enable/disable using the agent's model, or an object with a custom model for title generation (useful for cost optimization). Example: { model: openai('gpt-4.1-nano') }",
             },
           ],
         },

package/.docs/raw/reference/agents/getModel.mdx

@@ -86,7 +86,7 @@ const agent = new Agent({
     }
 
     // Default to OpenAI
-    return highQuality ? openai("gpt-4o") : openai("gpt-3.5-turbo");
+    return highQuality ? openai("gpt-4o") : openai("gpt-4.1-nano");
   },
 });
 

package/.docs/raw/reference/agents/stream.mdx

@@ -267,14 +267,14 @@ Configuration options for memory management:
       description: "Thread-specific memory configuration.",
       properties: [
         {
-          type: "boolean",
+          type: "boolean | object",
           parameters: [
             {
               name: "generateTitle",
-              type: "boolean",
+              type: "boolean | { model: LanguageModelV1 | ((ctx: RuntimeContext) => LanguageModelV1 | Promise<LanguageModelV1>) }",
               isOptional: true,
               description:
-                "Whether to automatically generate titles for new threads.",
+                "Controls automatic thread title generation from the user's first message. Can be a boolean to enable/disable using the agent's model, or an object with a custom model for title generation (useful for cost optimization). Example: { model: openai('gpt-4.1-nano') }",
             },
           ],
         },

package/.docs/raw/reference/deployer/cloudflare.mdx

@@ -5,21 +5,15 @@ description: "Documentation for the CloudflareDeployer class, which deploys Mast
 
 # CloudflareDeployer
 
-The CloudflareDeployer deploys standalone Mastra applications to Cloudflare Workers, handling configuration, environment variables, and route management. It extends the abstract Deployer class to provide Cloudflare-specific deployment functionality.
+The `CloudflareDeployer` class handles deployment of standalone Mastra applications to Cloudflare Workers. It manages configuration, deployment, and extends the base [Deployer](/reference/deployer/deployer) class with Cloudflare specific functionality.
 
-## Installation
-
-```bash copy
-npm install @mastra/deployer-cloudflare@latest
-```
-
-## Usage Example
+## Usage example
 
 ```typescript filename="src/mastra/index.ts" showLineNumbers copy
-import { Mastra } from "@mastra/core";
+import { Mastra } from "@mastra/core/mastra";
 import { CloudflareDeployer } from "@mastra/deployer-cloudflare";
 
-const mastra = new Mastra({
+export const mastra = new Mastra({
   // ...
   deployer: new CloudflareDeployer({
     scope: "your-account-id",
@@ -206,112 +200,3 @@ const mastra = new Mastra({
     },
   ]}
 />
-
-### Environment Variables
-
-The CloudflareDeployer handles environment variables from multiple sources:
-
-1. **Environment Files**: Variables from `.env.production` and `.env` files.
-2. **Configuration**: Variables passed through the `env` parameter.
-
-## Lint Mastra Project
-
-Lint your Mastra project to make sure it's fine to build
-
-```bash
-npx mastra lint
-```
-
-## Build Mastra Project
-
-To build your Mastra project for cloudflare deployment:
-
-```bash
-npx mastra build
-```
-
-The build process generates the following output structure in the `.mastra/output` directory:
-
-```
-.mastra/output/
-├── index.mjs # Main worker entry point
-├── wrangler.json # Cloudflare Worker configuration
-└── assets/ # Static assets and dependencies
-
-```
-
-### Wrangler Configuration
-
-The CloudflareDeployer automatically generates a `wrangler.json` configuration file with the following settings:
-
-```json
-{
-  "name": "your-project-name",
-  "main": "./output/index.mjs",
-  "compatibility_date": "2024-12-02",
-  "compatibility_flags": [
-    "nodejs_compat",
-    "nodejs_compat_populate_process_env"
-  ],
-  "observability": {
-    "logs": {
-      "enabled": true
-    }
-  },
-  "vars": {
-    // Environment variables from .env files and configuration
-  },
-  "routes": [
-    // Route configurations if specified
-  ],
-  "d1_databases": [
-    // D1 database bindings if specified
-  ],
-  "kv_namespaces": [
-    // KV namespace bindings if specified
-  ]
-}
-```
-
-Compatibility flags:
-
-- `nodejs_compat`: Enables Node.js compatibility in Workers.
-- `nodejs_compat_populate_process_env`: Populates `process.env` with variables from `vars`.
-
-### Route Configuration
-
-Routes can be configured to direct traffic to your worker based on URL patterns and domains:
-
-```typescript
-const routes = [
-  {
-    pattern: "api.example.com/*",
-    zone_name: "example.com",
-    custom_domain: true,
-  },
-  {
-    pattern: "example.com/api/*",
-    zone_name: "example.com",
-  },
-];
-```
-
-## Deployment Options
-
-After building, you can deploy your Mastra application `.mastra/output` to Cloudflare Workers using any of these methods:
-
-1. **Wrangler CLI**: Deploy directly using Cloudflare's official CLI tool
-
-   - Install the CLI: `npm install -g wrangler`
-   - Navigate to the output directory: `cd .mastra/output`
-   - Login to your Cloudflare account: `wrangler login`
-   - Deploy to preview environment: `wrangler deploy`
-   - For production deployment: `wrangler deploy --env production`
-
-2. **Cloudflare Dashboard**: Upload the build output manually through the Cloudflare dashboard
-
-> You can also run `wrangler dev` in your output directory `.mastra/output` to test your Mastra application locally.
-
-## Platform Documentation
-
-- [Cloudflare Workers](https://developers.cloudflare.com/workers/)

package/.docs/raw/reference/deployer/netlify.mdx

@@ -5,95 +5,16 @@ description: "Documentation for the NetlifyDeployer class, which deploys Mastra
 
 # NetlifyDeployer
 
-The NetlifyDeployer deploys standalone Mastra applications to Netlify Functions, handling site creation, configuration, and deployment processes. It extends the abstract Deployer class to provide Netlify-specific deployment functionality.
+The `NetlifyDeployer` class handles deployment of standalone Mastra applications to Netlify. It manages configuration, deployment, and extends the base [Deployer](/reference/deployer/deployer) class with Netlify specific functionality.
 
-## Installation
-
-```bash copy
-npm install @mastra/deployer-netlify@latest
-```
-
-## Usage Example
+## Usage example
 
 ```typescript filename="src/mastra/index.ts" showLineNumbers copy
-import { Mastra } from "@mastra/core";
+import { Mastra } from "@mastra/core/mastra";
 import { NetlifyDeployer } from "@mastra/deployer-netlify";
 
-const mastra = new Mastra({
+export const mastra = new Mastra({
   // ...
   deployer: new NetlifyDeployer()
 });
 ```
-
-## Lint Mastra Project
-
-Lint your Mastra project to make sure it's fine to build
-
-```bash
-npx mastra lint
-```
-
-## Build Mastra Project
-
-To build your Mastra project for Netlify deployment:
-
-```bash
-npx mastra build
-```
-
-The build process generates the following output structure in the `.mastra/output` directory:
-
-```
-.netlify/
-├── v1/
-    └── functions/
-    │   └── api/
-    │       └── index.mjs    # Application entry point
-    │ config.json            # Netlify configuration
-```
-
-### Netlify Configuration
-
-The NetlifyDeployer automatically generates a `config.json` configuration file in `.netlify/v1` with the following settings:
-
-```json
-{
-  "redirects": [
-    {
-      "force": true,
-      "from": "/*",
-      "to": "/.netlify/functions/api/:splat",
-      "status": 200
-    }
-  ]
-}
-```
-
-## Deployment Options
-
-After building, you can deploy your Mastra application `.mastra/output` to Netlify using any of these methods:
-
-1. **Netlify CLI**: Deploy directly using Netlify's official CLI tool
-
-   - Install the CLI: `npm install -g netlify-cli`
-   - Deploy with functions directory specified: `netlify deploy`
-   - For production deployment add `--prod` flag: `netlify deploy --prod`
-
-2. **Netlify Dashboard**: Connect your Git repository or drag-and-drop the build output through the Netlify dashboard
-
-  When connecting a Mastra project Git repository to Netlify, use these recommended build settings since Netlify resolves paths relative to the project root:
-
-   ```bash
-   # Build command
-   npm run build
-   ```
-
-
-
-3. **Netlify Dev**: Run your Mastra application locally with Netlify's development environment
-
-> You can also run `netlify dev` in your project root to test your Mastra application locally.
-
-## Platform Documentation
-
-- [Netlify](https://docs.netlify.com/)

package/.docs/raw/reference/deployer/vercel.mdx

@@ -5,63 +5,16 @@ description: "Documentation for the VercelDeployer class, which deploys Mastra a
 
 # VercelDeployer
 
-The VercelDeployer deploys standalone Mastra applications to Vercel, handling configuration, environment variable synchronization, and deployment processes. It extends the abstract Deployer class to provide Vercel-specific deployment functionality.
+The `VercelDeployer` class handles deployment of standalone Mastra applications to Vercel. It manages configuration, deployment, and extends the base [Deployer](/reference/deployer/deployer) class with Vercel specific functionality.
 
-## Installation
-
-```bash copy
-npm install @mastra/deployer-vercel@latest
-```
-
-## Usage Example
+## Usage example
 
 ```typescript filename="src/mastra/index.ts" showLineNumbers copy
-import { Mastra } from "@mastra/core";
+import { Mastra } from "@mastra/core/mastra";
 import { VercelDeployer } from "@mastra/deployer-vercel";
 
-const mastra = new Mastra({
+export const mastra = new Mastra({
   // ...
   deployer: new VercelDeployer()
 });
 ```
-
-## Lint Mastra Project
-
-Lint your Mastra project to make sure it's fine to build
-
-```bash
-npx mastra lint
-```
-
-## Build Mastra Project
-
-To build your Mastra project for Vercel deployment:
-
-```bash
-npx mastra build
-```
-
-The build process generates the following output structure in the `.vercel/output` directory:
-
-```
-.vercel/output/functions/index.func
-└── index.mjs       # Application entry point
-```
-
-## Deployment Options
-
-After building, you can deploy your Mastra application to Vercel using any of these methods:
-
-1. **Vercel CLI**: Deploy directly using Vercel's official CLI tool
-
-   - Install the CLI: `npm install -g vercel`
-   - Deploy to preview environment: `vercel --prebuilt`
-   - For production deployment: `vercel --prod --prebuilt`
-
-2. **Vercel Dashboard**: Connect your Git repository or drag-and-drop the build output through the Vercel dashboard
-
-> You can also run `vercel dev` in your project directory to test your Mastra application locally. (Make sure you configured your dev command to `mastra dev`)
-
-## Platform Documentation
-
-- [Vercel](https://vercel.com/docs)