@mastra/mcp-docs-server 1.1.8 → 1.1.9-alpha.1

package/.docs/guides/guide/research-assistant.md

@@ -1,4 +1,4 @@
-# Building a Research Paper Assistant with RAG
+# Building a research paper assistant with RAG
 
 In this guide, you'll create an AI research assistant that can analyze academic papers and answer specific questions about their content using Retrieval Augmented Generation (RAG).
 
@@ -39,7 +39,7 @@ Your implementation will:
 3. Use similarity search to find relevant sections
 4. Generate accurate responses using retrieved context
 
-## Creating the Agent
+## Creating the agent
 
 Let's define the agent's behavior, connect it to your Mastra project, and create the vector store.
 
@@ -256,7 +256,7 @@ In the following steps you'll fetch the research paper, split it into smaller ch
 
    If the operation was successful you should see no output/errors in your terminal.
 
-## Test the Assistant
+## Test the assistant
 
 Now that the vector database has all embeddings, you can test the research assistant with different types of queries.
 
@@ -338,7 +338,7 @@ curl -X POST http://localhost:4111/api/agents/researchAgent/generate \
   }'
 ```
 
-## Advanced RAG Examples
+## Advanced RAG examples
 
 Explore these examples for more advanced RAG techniques:
 

package/.docs/guides/guide/research-coordinator.md

@@ -1,4 +1,4 @@
-# Building a Research Coordinator with Supervisor Pattern
+# Building a research coordinator with supervisor pattern
 
 In this guide, you'll build a research coordinator that orchestrates multiple specialized agents using the supervisor pattern. The coordinator will delegate research tasks to a research agent and writing tasks to a writing agent, then synthesize the results into a comprehensive report.
 

package/.docs/guides/guide/stock-agent.md

@@ -1,6 +1,6 @@
-# Building an AI Stock Agent
+# Building an AI stock agent
 
-In this guide, you're going to create a simple agent that fetches the last day's closing stock price for a given symbol. You'll learn how to create a tool, add it to an agent, and use the agent to fetch stock prices.
+In this guide, you're going to create an agent that fetches the last day's closing stock price for a given symbol. You'll learn how to create a tool, add it to an agent, and use the agent to fetch stock prices.
 
 [YouTube video player](https://www.youtube-nocookie.com/embed/rIaZ4l7y9wo)
 
@@ -10,7 +10,7 @@ In this guide, you're going to create a simple agent that fetches the last day's
 - An API key from a supported [Model Provider](https://mastra.ai/models)
 - An existing Mastra project (Follow the [installation guide](https://mastra.ai/guides/getting-started/quickstart) to set up a new project)
 
-## Creating the Agent
+## Creating the agent
 
 To create an agent in Mastra use the `Agent` class to define it and then register it with Mastra.
 
@@ -39,9 +39,9 @@ To create an agent in Mastra use the `Agent` class to define it and then registe
    })
    ```
 
-## Creating the Stock Price Tool
+## Creating the stock price tool
 
-So far the Stock Agent doesn't know anything about the current stock prices. To change this, create a tool and add it to the agent.
+The Stock Agent doesn't yet know anything about current stock prices. To change this, create a tool and add it to the agent.
 
 1. Create a new file `src/mastra/tools/stockPrices.ts`. Inside, add a `stockPrices` tool that will fetch the last day's closing stock price for a given symbol:
 
@@ -90,7 +90,7 @@ So far the Stock Agent doesn't know anything about the current stock prices. To
    })
    ```
 
-## Running the Agent Server
+## Running the agent server
 
 Learn how to interact with your agent through Mastra's API.
 

package/.docs/guides/guide/web-search.md

@@ -1,4 +1,4 @@
-# Building an Agent that can search the web
+# Building an agent that can search the web
 
 When building a web search agent, you have two main strategies to consider:
 
@@ -202,7 +202,7 @@ Some LLM providers include built-in web search capabilities that can be used dir
 
    Inside Studio navigate to the **"Search Agent"** and ask it: "What happened last week in AI news?"
 
-## Using Search APIs
+## Using search APIs
 
 For more control over search behavior, you can integrate external search APIs as custom tools. [Exa](https://exa.ai/) is a search engine built specifically for AI applications, offering semantic search, configurable filters (category, domain, date range), and the ability to retrieve full page contents. The search API is wrapped in a Mastra tool that defines the input schema, output format, and execution logic.
 

package/.docs/guides/guide/whatsapp-chat-bot.md

@@ -1,4 +1,4 @@
-# WhatsApp Chat Bot
+# WhatsApp chat bot
 
 This guide demonstrates how to create a WhatsApp chat bot using Mastra agents and workflows. The bot receives incoming WhatsApp messages via webhook, processes them through an AI agent, breaks responses into natural text messages, and sends them back via the WhatsApp Business API.
 

package/.docs/guides/migrations/agentnetwork.md

@@ -6,7 +6,7 @@ As of `v0.20.0` for `@mastra/core`, the following changes apply.
 
 - Bump all your model provider packages by a major version.
 
-> **Note:** This will ensure that they are all v5 models now.
+> **Note:** This will ensure that they're all v5 models now.
 
 ## Memory is required
 

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

@@ -9,11 +9,11 @@ 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
+## 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
+## Message format conversion
 
 For cases where you need to manually convert messages between AI SDK and Mastra formats, use the `convertMessages()` utility:
 
@@ -32,7 +32,7 @@ const aiv5Messages = convertMessages(mastraMessages).to('AIV5.Core')
 
 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
+## 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.
 

package/.docs/guides/migrations/network-to-supervisor.md

@@ -1,4 +1,4 @@
-# Migrate from `.network()` to Supervisor Pattern
+# Migrate from `.network()` to supervisor pattern
 
 The supervisor pattern using `Agent.stream()` and `Agent.generate()` is the recommended approach for coordinating multiple agents, replacing the older `.network()` API. This guide walks you through each step of the migration.
 

package/.docs/guides/migrations/upgrade-to-v1/agent.md

@@ -1,4 +1,4 @@
-# Agent Class
+# Agent class
 
 The Agent class has been updated with reorganized voice methods, updated property access patterns, and streamlined streaming APIs.
 

package/.docs/guides/migrations/upgrade-to-v1/client.md

@@ -271,9 +271,9 @@ To migrate, use workflow streaming APIs instead of watch.
 + }
 ```
 
-### Run-related methods cannot be called directly on workflow instance
+### Run-related methods can't be called directly on workflow instance
 
-Run-related methods cannot be called directly on workflow instance. You need to create a run instance first using `createRun()` method.
+Run-related methods can't be called directly on workflow instance. You need to create a run instance first using `createRun()` method.
 
 ```diff
 - const result = await workflow.start({ runId: '123', inputData: { ... } });

package/.docs/guides/migrations/upgrade-to-v1/deployment.md

@@ -4,7 +4,7 @@ The `CloudflareDeployer` configuration has been updated to use standard `wrangle
 
 ## Changed
 
-### CloudflareDeployer uses standard wrangler.json property names
+### `CloudflareDeployer` uses standard `wrangler.json` property names
 
 The `CloudflareDeployer` constructor now accepts standard `wrangler.json` property names instead of custom camelCase variants. This change aligns the deployer with Cloudflare's official configuration format and provides access to all wrangler configuration options.
 
@@ -32,6 +32,6 @@ const deployer = new CloudflareDeployer({
   });
 ```
 
-The `workerNamespace` field has been removed as it is no longer used.
+The `workerNamespace` field has been removed as it's no longer used.
 
 For all available configuration options, see the [Wrangler configuration documentation](https://developers.cloudflare.com/workers/wrangler/configuration/).

package/.docs/guides/migrations/upgrade-to-v1/evals.md

@@ -1,4 +1,4 @@
-# Evals & Scorers
+# Evals and scorers
 
 The evaluation API has been consolidated on the new scorers system with updated naming conventions and configuration requirements.
 

package/.docs/guides/migrations/upgrade-to-v1/mastra.md

@@ -1,4 +1,4 @@
-# Mastra Class
+# Mastra class
 
 The Mastra class has been restructured to restrict top-level imports and replace direct property access with getter methods.
 

package/.docs/guides/migrations/upgrade-to-v1/memory.md

@@ -29,7 +29,7 @@ const memory = new Memory({
 
 ### Default memory scope from `thread` to `resource`
 
-The default scope for both working memory and semantic recall has changed from `'thread'` to `'resource'`. This change aligns with common use cases where applications want to remember user information across conversations. When semantic recall is enabled, it now defaults to searching across all user conversations rather than just the current thread.
+The default scope for both working memory and semantic recall has changed from `'thread'` to `'resource'`. This change aligns with common use cases where applications want to remember user information across conversations. When semantic recall is enabled, it now defaults to searching across all user conversations rather than the current thread.
 
 To migrate, if you want to maintain the old behavior where memory is isolated per conversation thread, explicitly set `scope: 'thread'`.
 
@@ -119,7 +119,7 @@ agent.stream('Hello', {
 
 ### `Memory.query()` renamed to `Memory.recall()`
 
-The `Memory.query()` method has been renamed to `Memory.recall()`. The new method returns a simpler format with just `{ messages: MastraDBMessage[] }` instead of multiple format variations. This change better describes the action of retrieving messages from memory and simplifies the API.
+The `Memory.query()` method has been renamed to `Memory.recall()`. The new method returns a simpler format with `{ messages: MastraDBMessage[] }` instead of multiple format variations. This change better describes the action of retrieving messages from memory and simplifies the API.
 
 To migrate, rename `query()` to `recall()` and update code that expects the old return format.
 

package/.docs/guides/migrations/upgrade-to-v1/overview.md

@@ -8,7 +8,7 @@ This guide provides a comprehensive overview of breaking changes when upgrading
 
 > **Need help?:** Need help with the migration? Join our [Discord community](https://discord.gg/BTYqqHKUrf) to ask questions.
 
-## Migration Strategy
+## Migration strategy
 
 ### Update all Mastra packages to `latest` tag
 
@@ -58,7 +58,7 @@ Work through the [migration checklist](#migration-checklist) below to update you
 
 > **Database Migration Required:** If you're using PostgreSQL or LibSQL storage, you'll need to run a database migration. See the [Storage migration guide](https://mastra.ai/guides/migrations/upgrade-to-v1/storage) for details.
 
-## Breaking Changes by Area
+## Breaking changes by area
 
 - **[Mastra Class](https://mastra.ai/guides/migrations/upgrade-to-v1/mastra)** - Import restructuring and property access changes.
 - **[Agent Class](https://mastra.ai/guides/migrations/upgrade-to-v1/agent)** - Voice methods moved to namespace and streaming API updates.
@@ -76,7 +76,7 @@ Work through the [migration checklist](#migration-checklist) below to update you
 - **[Client SDKs](https://mastra.ai/guides/migrations/upgrade-to-v1/client)** - Types and utilities renamed for consistency.
 - **[Voice Packages](https://mastra.ai/guides/migrations/upgrade-to-v1/voice)** - Packages renamed from speech to voice.
 
-## Migration Checklist
+## Migration checklist
 
 Work through this checklist in order, starting with high-impact changes that affect most applications.
 

package/.docs/guides/migrations/upgrade-to-v1/storage.md

@@ -2,7 +2,7 @@
 
 Storage APIs have been standardized with consistent pagination and naming patterns across all methods.
 
-## Database Migration
+## Database migration
 
 Run these SQL migrations through your normal migration process (e.g., Prisma Migrate, Drizzle Kit, or your DBA review process).
 
@@ -23,7 +23,7 @@ ALTER TABLE mastra_scorers DROP COLUMN "runtimeContext";
 
 ### Duplicate spans migration
 
-If you're upgrading from an older version of Mastra, you may have duplicate `(traceId, spanId)` entries in your `mastra_spans` table. V1 adds a unique constraint on these columns to ensure data integrity, but this constraint cannot be added if duplicates exist.
+If you're upgrading from an older version of Mastra, you may have duplicate `(traceId, spanId)` entries in your `mastra_spans` table. V1 adds a unique constraint on these columns to ensure data integrity, but this constraint can't be added if duplicates exist.
 
 > **Who needs this migration:** Only if you have existing spans data from Mastra versions prior to v1 and encounter errors about duplicate key violations or constraint creation failures.
 
@@ -89,7 +89,7 @@ USING snapshot::jsonb;
 
 ## Added
 
-### Storage composition in MastraCompositeStore
+### Storage composition in `MastraCompositeStore`
 
 `MastraCompositeStore` can now compose storage domains from different adapters. Use it when you need different databases for different purposes - for example, PostgreSQL for memory and workflows, but a specialized database for observability.
 
@@ -460,7 +460,7 @@ To migrate, rename the method and use named arguments.
 + });
 ```
 
-### PostgresStore `schema` to `schemaName`
+### `PostgresStore`: `schema` to `schemaName`
 
 The `schema` parameter has been renamed to `schemaName` in the PostgresStore constructor. This change provides clearer naming to avoid confusion with database schema concepts.
 

package/.docs/guides/migrations/upgrade-to-v1/tools.md

@@ -8,7 +8,7 @@ Tool execution signatures have been updated to use separate input and context pa
 
 All `createTool` execute functions now use a new signature with separate `inputData` and `context` parameters instead of a single destructured object. This change provides clearer separation between tool inputs and execution context.
 
-**Note:** This change only applies to `createTool`. If you're using `createStep` for workflows, the signature remains `async (inputData, context)` and does not need to be changed.
+**Note:** This change only applies to `createTool`. If you're using `createStep` for workflows, the signature remains `async (inputData, context)` and doesn't need to be changed.
 
 To migrate, update `createTool` signatures to use `inputData` as the first parameter (typed from `inputSchema`) and `context` as the second parameter.
 
@@ -80,7 +80,7 @@ createTool({
 
 The `suspendPayload` gets validated against the `suspendSchema` when the tool is executed. If the suspendPayload doesn't match the `suspendSchema`, a warning is logged and the error is returned as tool output, but suspension continues. Also, when the tool is resumed, the `resumeData` gets validated against the `resumeSchema`. If the resumeData doesn't match the `resumeSchema`, the tool will return a `ValidationError`, preventing the tool resumption.
 
-To skip the `suspendSchema` or `resumeSchema` validation, do not define `suspendSchema` or `resumeSchema` in the tool creation.
+To skip the `suspendSchema` or `resumeSchema` validation, don't define `suspendSchema` or `resumeSchema` in the tool creation.
 
 > **Note:** For MCP-specific tool context changes, see the [MCP migration guide](https://mastra.ai/guides/migrations/upgrade-to-v1/mcp).
 

package/.docs/guides/migrations/upgrade-to-v1/tracing.md

@@ -2,7 +2,7 @@
 
 The observability system has been restructured in v1 with a dedicated `@mastra/observability` package. This guide covers two migration paths depending on which version you're upgrading from.
 
-## Migration Paths
+## Migration paths
 
 ### From OTEL-based Telemetry (0.x)
 
@@ -342,7 +342,7 @@ node --env-file=".env" .mastra/output/index.mjs
 
 No separate instrumentation files or special startup flags required.
 
-## Provider Migration Reference
+## Provider migration reference
 
 If you were using OTEL-based telemetry with specific providers in 0.x, here's how to configure them in v1:
 

package/.docs/guides/migrations/upgrade-to-v1/vectors.md

@@ -40,7 +40,7 @@ const vectorStore = new VectorStore({ ... });
 + const vectors = await vectorStore.listVectors({ ... });
 ```
 
-### LibSQLVector: `connectionUrl` to `url`
+### `LibSQLVector`: `connectionUrl` to `url`
 
 The `connectionUrl` parameter has been renamed to `url` to align with the `@libsql/client` API and match LibSQLStorage.
 
@@ -52,7 +52,7 @@ const vectorStore = new LibSQLVector({
   });
 ```
 
-### OpenSearchVector: `url` to `node`
+### `OpenSearchVector`: `url` to `node`
 
 The `url` parameter has been renamed to `node` to match the OpenSearch `ClientOptions` API. The constructor now accepts all OpenSearch client options including authentication, SSL, and compression.
 
@@ -64,7 +64,7 @@ const vectorStore = new OpenSearchVector({
   });
 ```
 
-### PineconeVector: `environment` removed
+### `PineconeVector`: `environment` removed
 
 The `environment` parameter has been removed. Use `controllerHostUrl` instead if you need to specify a custom controller host. The constructor now accepts all Pinecone configuration options.
 

package/.docs/guides/migrations/upgrade-to-v1/voice.md

@@ -1,4 +1,4 @@
-# Voice Packages
+# Voice
 
 Voice packages have been renamed from speech to voice with updated class names and API methods.
 

package/.docs/guides/migrations/upgrade-to-v1/workflows.md

@@ -84,7 +84,7 @@ createStep({
 
 ### `getInitData` returns unknown
 
-The `getInitData` function in the execute function now returns unknown instead of any. You'll need to type it yourself. To simply migrate, change `getInitData()` into `getInitData<any>()`
+The `getInitData` function in the execute function now returns unknown instead of any. You'll need to type it yourself. To migrate, change `getInitData()` into `getInitData<any>()`
 
 ```diff
 createStep({
@@ -198,7 +198,7 @@ const run = await workflow.createRun();
 + });
 ```
 
-> **Note:** The `writer` parameter passed to step `execute` functions is not affected by this change. It remains a `ToolStream` that extends `WritableStream<unknown>` and provides `.write()` and `.custom()` methods:
+> **Note:** The `writer` parameter passed to step `execute` functions isn't affected by this change. It remains a `ToolStream` that extends `WritableStream<unknown>` and provides `.write()` and `.custom()` methods:
 >
 > ```ts
 > createStep({
@@ -240,9 +240,9 @@ See [`Run.stream()`](https://mastra.ai/reference/streaming/workflows/stream), [`
 > npx @mastra/codemod@latest v1/workflow-stream-vnext .
 > ```
 
-### `suspend` and `setState` are not available in step condition functions parameters
+### `suspend` and `setState` aren't available in step condition functions parameters
 
-The `suspend` and `setState` functions are not available in step condition functions parameters.
+The `suspend` and `setState` functions aren't available in step condition functions parameters.
 
 To migrate, use the `suspend` function in the step execute function instead.
 
@@ -260,7 +260,7 @@ This is the same for `dountil` and `branch` condition functions parameters.
 
 The `./workflows/legacy` export path has been removed from `@mastra/core`. Legacy workflows are no longer supported.
 
-To migrate, use the new workflow API. There is no direct migration path from legacy workflows.
+To migrate, use the new workflow API. No direct migration path exists from legacy workflows.
 
 ```diff
 - import { LegacyWorkflow } from '@mastra/core/workflows/legacy';
@@ -268,7 +268,7 @@ To migrate, use the new workflow API. There is no direct migration path from leg
 + // Migrate to the new workflow API
 ```
 
-### `pipeThrough` and `pipeTo` methods from WorkflowRunOutput
+### `pipeThrough` and `pipeTo` methods from `WorkflowRunOutput`
 
 The `pipeThrough()` and `pipeTo()` methods on `WorkflowRunOutput` are deprecated. These methods still work but show console warnings.
 

package/.docs/guides/migrations/vnext-to-standard-apis.md

@@ -1,4 +1,4 @@
-# Migrate from VNext to Standard APIs
+# Migrate from VNext to standard APIs
 
 As of `v0.20.0` for `@mastra/core`, the following changes apply.
 
@@ -40,7 +40,7 @@ Choose the migration path that fits your needs:
 
 - Bump all your model provider packages by a major version.
 
-> This will ensure that they are all v5 models now. Follow the guide below to understand the key differences and update your code accordingly.
+> This will ensure that they're all v5 models now. Follow the guide below to understand the key differences and update your code accordingly.
 
 ## Key differences
 
@@ -306,7 +306,7 @@ The following options are available in the standard `.stream()` and `generate()`
 
 - `output`
 
-  The `output` property is deprecated in favor of `structuredOutput`, to achieve the same results, omit the model and only pass `structuredOutput.schema`, optionally add `jsonPromptInjection: true` if your model does not natively support `response_format`.
+  The `output` property is deprecated in favor of `structuredOutput`, to achieve the same results, omit the model and only pass `structuredOutput.schema`, optionally add `jsonPromptInjection: true` if your model doesn't natively support `response_format`.
 
   ```typescript
   const result = await agent.generate(messages, {

package/.docs/models/embeddings.md

@@ -1,8 +1,8 @@
-# Embedding Models
+# Embedding models
 
 Mastra's model router supports embedding models using the same `provider/model` string format as language models. This provides a unified interface for both chat and embedding models with TypeScript autocomplete support.
 
-## Quick Start
+## Quick start
 
 ```typescript
 import { ModelRouterEmbeddingModel } from "@mastra/core/llm";
@@ -15,7 +15,7 @@ const { embeddings } = await embedMany({
 });
 ```
 
-## Supported Models
+## Supported models
 
 ### OpenAI
 
@@ -127,7 +127,7 @@ const modelId: EmbeddingModelId = "openai/text-embedding-3-small";
 const embedder = new ModelRouterEmbeddingModel(modelId);
 ```
 
-## Error Handling
+## Error handling
 
 The model router validates provider and model IDs at construction time:
 

package/.docs/models/gateways/custom-gateways.md

@@ -1,4 +1,4 @@
-# Custom Model Gateways
+# Custom model gateways
 
 Custom model gateways allow you to implement private or specialized LLM provider integrations by extending the `MastraModelGateway` base class.
 
@@ -357,7 +357,7 @@ Examples:
 
 - `private/my-provider/model-1`
 
-## Advanced Example
+## Advanced example
 
 Token-based gateway with caching:
 
@@ -432,7 +432,7 @@ class TokenGateway extends MastraModelGateway {
 }
 ```
 
-## Error Handling
+## Error handling
 
 Provide descriptive errors for common failure scenarios:
 
@@ -513,7 +513,7 @@ describe('MyPrivateGateway', () => {
 });
 ```
 
-## Best Practices
+## Best practices
 
 1. **Use descriptive IDs for versioning**: Set explicit `id` values when you need to version your gateways
 

package/.docs/models/gateways/netlify.md

@@ -1,6 +1,6 @@
 # Netlify
 
-Netlify AI Gateway provides unified access to multiple providers with built-in caching and observability. Access 60 models through Mastra's model router.
+Netlify AI Gateway provides unified access to multiple providers with built-in caching and observability. Access 59 models through Mastra's model router.
 
 Learn more in the [Netlify documentation](https://docs.netlify.com/build/ai-gateway/overview/).
 
@@ -31,7 +31,7 @@ OPENAI_API_KEY=sk-...
 ANTHROPIC_API_KEY=ant-...
 ```
 
-## Available Models
+## Available models
 
 | Model                                          |
 | ---------------------------------------------- |
@@ -57,7 +57,6 @@ ANTHROPIC_API_KEY=ant-...
 | `gemini/gemini-2.5-pro`                        |
 | `gemini/gemini-3-flash-preview`                |
 | `gemini/gemini-3-pro-image-preview`            |
-| `gemini/gemini-3-pro-preview`                  |
 | `gemini/gemini-3.1-flash-image-preview`        |
 | `gemini/gemini-3.1-flash-lite-preview`         |
 | `gemini/gemini-3.1-pro-preview`                |

package/.docs/models/gateways/openrouter.md

@@ -1,6 +1,6 @@
 # ![OpenRouter logo](https://models.dev/logos/openrouter.svg)OpenRouter
 
-OpenRouter aggregates models from multiple providers with enhanced features like rate limiting and failover. Access 186 models through Mastra's model router.
+OpenRouter aggregates models from multiple providers with enhanced features like rate limiting and failover. Access 193 models through Mastra's model router.
 
 Learn more in the [OpenRouter documentation](https://openrouter.ai/models).
 
@@ -30,7 +30,7 @@ OPENAI_API_KEY=sk-...
 ANTHROPIC_API_KEY=ant-...
 ```
 
-## Available Models
+## Available models
 
 | Model                                                           |
 | --------------------------------------------------------------- |
@@ -91,6 +91,9 @@ ANTHROPIC_API_KEY=ant-...
 | `google/gemma-3n-e2b-it:free`                                   |
 | `google/gemma-3n-e4b-it`                                        |
 | `google/gemma-3n-e4b-it:free`                                   |
+| `inception/mercury`                                             |
+| `inception/mercury-2`                                           |
+| `inception/mercury-coder`                                       |
 | `kwaipilot/kat-coder-pro:free`                                  |
 | `liquid/lfm-2.5-1.2b-instruct:free`                             |
 | `liquid/lfm-2.5-1.2b-thinking:free`                             |
@@ -153,6 +156,9 @@ ANTHROPIC_API_KEY=ant-...
 | `openai/gpt-5.2-chat`                                           |
 | `openai/gpt-5.2-codex`                                          |
 | `openai/gpt-5.2-pro`                                            |
+| `openai/gpt-5.3-codex`                                          |
+| `openai/gpt-5.4`                                                |
+| `openai/gpt-5.4-pro`                                            |
 | `openai/gpt-oss-120b`                                           |
 | `openai/gpt-oss-120b:exacto`                                    |
 | `openai/gpt-oss-120b:free`                                      |
@@ -161,6 +167,7 @@ ANTHROPIC_API_KEY=ant-...
 | `openai/gpt-oss-safeguard-20b`                                  |
 | `openai/o4-mini`                                                |
 | `openrouter/aurora-alpha`                                       |
+| `openrouter/free`                                               |
 | `openrouter/sherlock-dash-alpha`                                |
 | `openrouter/sherlock-think-alpha`                               |
 | `prime-intellect/intellect-3`                                   |

package/.docs/models/gateways/vercel.md

@@ -1,6 +1,6 @@
 # ![Vercel logo](https://models.dev/logos/vercel.svg)Vercel
 
-Vercel aggregates models from multiple providers with enhanced features like rate limiting and failover. Access 199 models through Mastra's model router.
+Vercel aggregates models from multiple providers with enhanced features like rate limiting and failover. Access 208 models through Mastra's model router.
 
 Learn more in the [Vercel documentation](https://ai-sdk.dev/providers/ai-sdk-providers).
 
@@ -30,7 +30,7 @@ OPENAI_API_KEY=sk-...
 ANTHROPIC_API_KEY=ant-...
 ```
 
-## Available Models
+## Available models
 
 | Model                                          |
 | ---------------------------------------------- |
@@ -104,6 +104,8 @@ ANTHROPIC_API_KEY=ant-...
 | `google/gemini-3-flash`                        |
 | `google/gemini-3-pro-image`                    |
 | `google/gemini-3-pro-preview`                  |
+| `google/gemini-3.1-flash-image-preview`        |
+| `google/gemini-3.1-flash-lite-preview`         |
 | `google/gemini-3.1-pro-preview`                |
 | `google/gemini-embedding-001`                  |
 | `google/imagen-4.0-fast-generate-001`          |
@@ -111,6 +113,7 @@ ANTHROPIC_API_KEY=ant-...
 | `google/imagen-4.0-ultra-generate-001`         |
 | `google/text-embedding-005`                    |
 | `google/text-multilingual-embedding-002`       |
+| `inception/mercury-2`                          |
 | `inception/mercury-coder-small`                |
 | `kwaipilot/kat-coder-pro-v1`                   |
 | `meituan/longcat-flash-chat`                   |
@@ -181,7 +184,10 @@ ANTHROPIC_API_KEY=ant-...
 | `openai/gpt-5.2-chat`                          |
 | `openai/gpt-5.2-codex`                         |
 | `openai/gpt-5.2-pro`                           |
+| `openai/gpt-5.3-chat`                          |
 | `openai/gpt-5.3-codex`                         |
+| `openai/gpt-5.4`                               |
+| `openai/gpt-5.4-pro`                           |
 | `openai/gpt-oss-120b`                          |
 | `openai/gpt-oss-20b`                           |
 | `openai/gpt-oss-safeguard-20b`                 |
@@ -206,6 +212,9 @@ ANTHROPIC_API_KEY=ant-...
 | `voyage/voyage-3-large`                        |
 | `voyage/voyage-3.5`                            |
 | `voyage/voyage-3.5-lite`                       |
+| `voyage/voyage-4`                              |
+| `voyage/voyage-4-large`                        |
+| `voyage/voyage-4-lite`                         |
 | `voyage/voyage-code-2`                         |
 | `voyage/voyage-code-3`                         |
 | `voyage/voyage-finance-2`                      |

package/.docs/models/gateways.md

@@ -2,11 +2,11 @@
 
 Gateway providers aggregate multiple model providers and add features like caching, rate limiting, analytics, and automatic failover. Use gateways when you need observability, cost management, or simplified multi-provider access.
 
-## Custom Gateways
+## Custom gateways
 
 Create custom gateways for private LLM deployments or specialized provider integrations. See [Custom Gateways](https://mastra.ai/models/gateways/custom-gateways) for implementation details.
 
-## Built-in Gateways
+## Built-in gateways
 
 - [Azure OpenAI](https://mastra.ai/models/gateways/azure-openai)
 - [Netlify](https://mastra.ai/models/gateways/netlify)

package/.docs/models/index.md

@@ -1,6 +1,6 @@
 # Model Providers
 
-Mastra provides a unified interface for working with LLMs across multiple providers, giving you access to 2613 models from 88 providers through a single API.
+Mastra provides a unified interface for working with LLMs across multiple providers, giving you access to 3239 models from 92 providers through a single API.
 
 ## Features