@mastra/mcp-docs-server 1.2.8-alpha.0 → 1.2.8-alpha.2

package/.docs/docs/agent-builder/deploying.md

@@ -29,6 +29,7 @@ import { LibSQLStore } from '@mastra/libsql'
 
 new Mastra({
   storage: new LibSQLStore({
+    id: 'mastra-storage',
     url: process.env.DATABASE_URL!,
     authToken: process.env.DATABASE_AUTH_TOKEN,
   }),

package/.docs/docs/agent-builder/overview.md

@@ -67,7 +67,7 @@ import { createBuilderAgent } from '@mastra/editor/ee'
 import { LibSQLStore } from '@mastra/libsql'
 
 export const mastra = new Mastra({
-  storage: new LibSQLStore({ url: 'file:./mastra.db' }),
+  storage: new LibSQLStore({ id: 'mastra-storage', url: 'file:./mastra.db' }),
   agents: { builderAgent: createBuilderAgent() },
   editor: new MastraEditor({
     builder: {

package/.docs/docs/agent-controller/overview.md

@@ -65,7 +65,7 @@ const agent = new Agent({
 const agentController = new AgentController({
   id: 'my-agent',
   agent,
-  storage: new LibSQLStore({ url: 'file:./data.db' }),
+  storage: new LibSQLStore({ id: 'agent-storage', url: 'file:./data.db' }),
   modes: [
     {
       id: 'plan',

package/.docs/docs/agents/using-tools.md

@@ -193,6 +193,43 @@ export const researchAgent = new Agent({
 })
 ```
 
+## Share tools across agents
+
+Direct imports are the simplest choice when one tool is used by one or a small number of agents. Each agent imports the tool and adds it to its `tools` record, as shown in the quickstart above.
+
+For tools shared across agents or retrieved elsewhere from the Mastra instance, register them once with `new Mastra({ tools })`. A function-based Agent `tools` callback can then resolve entries from that registry.
+
+```typescript
+import { Agent } from '@mastra/core/agent'
+import { Mastra } from '@mastra/core/mastra'
+import { weatherTool } from './tools/weather-tool'
+
+export const sharedWeatherAgent = new Agent({
+  id: 'shared-weather-agent',
+  name: 'Shared Weather Agent',
+  instructions: `
+    You are a helpful weather assistant.
+    Use the weatherTool to fetch current weather data.`,
+  model: 'openai/gpt-5.5',
+  tools: ({ mastra }) => {
+    if (!mastra) {
+      throw new Error('Mastra instance is required to resolve shared tools')
+    }
+
+    return { weatherTool: mastra.getTool('weather') }
+  },
+})
+
+export const mastra = new Mastra({
+  tools: { weather: weatherTool },
+  agents: { sharedWeatherAgent },
+})
+```
+
+Register the tool and Agent on the same Mastra instance. The Agent can then retrieve the shared tool by its registration key in the `tools` callback and return it under the name the model should use. Keep the `mastra` guard because it's optional in the callback type.
+
+For API details, see [`Mastra.getTool()`](https://mastra.ai/reference/core/getTool), [`Mastra.getToolById()`](https://mastra.ai/reference/core/getToolById), [`Mastra.listTools()`](https://mastra.ai/reference/core/listTools), and the [`Agent` reference](https://mastra.ai/reference/agents/agent).
+
 ## Shape output for the model
 
 Use `toModelOutput` when your tool returns rich structured data for your application, but you want the model to receive a smaller or multimodal representation. This keeps model context focused while preserving the full tool result in your app.

package/.docs/docs/capabilities/channels/other-adapters.md

@@ -2,7 +2,7 @@
 
 # More
 
-Mastra channels use Chat SDK adapters, so the pages in this section are not the full list of supported platforms. Use any Chat SDK platform adapter that exports an adapter factory compatible with `channels.adapters`.
+Mastra channels use Chat SDK adapters, so the pages in this section aren't the full list of supported platforms. Use any Chat SDK platform adapter that exports an adapter factory compatible with `channels.adapters`.
 
 ## Adapter catalog
 

package/.docs/docs/capabilities/channels/overview.md

@@ -58,6 +58,7 @@ import { yourAgent } from './agents/your-agent'
 export const mastra = new Mastra({
   agents: { yourAgent },
   storage: new LibSQLStore({
+    id: 'mastra-storage',
     url: process.env.DATABASE_URL,
   }),
 })

package/.docs/docs/capabilities/channels/slack.md

@@ -53,7 +53,7 @@ export const yourAgent = new Agent({
 
 ## Create a Slack app
 
-To connect your agent, create a Slack app in the workspace where you want it to run. The Slack app controls how your agent appears in Slack, what it can do, and which events it receives.
+To connect your agent, create a Slack app in the workspace where you want it to run. The Slack app controls your agent's display in Slack, its capabilities, and the events it receives.
 
 This guide uses a [manifest](https://docs.slack.dev/app-manifests/configuring-apps-with-app-manifests/#creating_manifests): a configuration file that creates the Slack app settings for you. This is the fastest path when you are adding your agent to your own workspace. It doesn't cover the platform OAuth flow where other workspaces install your agent.
 
@@ -109,7 +109,7 @@ This manifest configures:
 - `display_information.name` and `features.bot_user.display_name`: Set your agent's name in Slack. You can update it at any time; remember to reinstall the app after changing names or permissions.
 - `app_home.messages_tab_enabled` and `app_home.messages_tab_read_only_enabled`: Enable direct messages from the Slack app's **Messages** tab.
 - `always_online`: Shows the Slack bot user as always available.
-- `oauth_config.scopes.bot`: Grants the bot permission to post messages, read channel messages where it is present, read mentions, read and write direct messages, and look up users.
+- `oauth_config.scopes.bot`: Grants the bot permission to post messages, read channel messages where it's present, read mentions, read and write direct messages, and look up users.
 - `event_subscriptions`: Tells Slack which message events to send to the webhook.
 - `interactivity`: Enables interactive cards and tells Slack where to send card actions.
 

package/.docs/docs/getting-started/file-based-agents.md

@@ -10,9 +10,9 @@ File-based agents are an experimental, convention-based way to define [Mastra ag
 
 This approach reduces glue code and makes the file system itself a direct representation of your [project structure](https://mastra.ai/reference/project-structure), so both you and your coding agent can understand it at a glance.
 
-You can build your entire project with file-based agents or combine this approach with agents and other primitives defined directly in code, making it easy to adopt incrementally.
+You can build your entire project with file-based agents or combine this approach with agents and other primitives defined directly in code for incremental adoption.
 
-File-based agents have some limitations while in beta. Not every Mastra feature can be defined in a file yet, and they are not the best fit for dynamic configuration or runtime wiring. When needed, you can define agents and related primitives directly in code.
+File-based agents have some limitations while in beta. Not every Mastra feature can be defined in a file yet, and they're not the best fit for dynamic configuration or runtime wiring. When needed, you can define agents and related primitives directly in code.
 
 > **Note:** All Mastra documentation currently shows agents and primitives defined directly in code. File-based agents use the same underlying concepts and APIs, so the guidance elsewhere in the docs still applies. As file-based agents mature, more examples may use this structure where appropriate.
 

package/.docs/docs/long-running-agents/schedules.md

@@ -30,7 +30,7 @@ const pinger = new Agent({
 
 const mastra = new Mastra({
   agents: { pinger },
-  storage: new LibSQLStore({ url: 'file:./mastra.db' }),
+  storage: new LibSQLStore({ id: 'mastra-storage', url: 'file:./mastra.db' }),
 })
 
 await mastra.schedules.create({
@@ -164,7 +164,7 @@ Hooks let you run code at key points in an agent schedule's lifecycle, for examp
 ```typescript
 const mastra = new Mastra({
   agents: { pinger },
-  storage: new LibSQLStore({ url: 'file:./mastra.db' }),
+  storage: new LibSQLStore({ id: 'mastra-storage', url: 'file:./mastra.db' }),
   schedules: {
     prepare: async ({ agentId, schedule, trigger }) => {
       // Return overrides, null to skip this fire, or undefined for defaults

package/.docs/docs/mastra-platform/database.md

@@ -99,6 +99,7 @@ Turso exposes two environment variables: `TURSO_DATABASE_URL` and `TURSO_AUTH_TO
 import { LibSQLStore } from '@mastra/libsql'
 
 export const storage = new LibSQLStore({
+  id: 'mastra-storage',
   url: process.env.TURSO_DATABASE_URL!,
   authToken: process.env.TURSO_AUTH_TOKEN!,
 })

package/.docs/docs/mastra-platform/deploy.md

@@ -44,6 +44,7 @@ A local `.env` file is optional. Environment variables stored on the platform ar
    >
    > ```ts
    > new LibSQLStore({
+   >   id: 'mastra-storage',
    >   // Uses the hosted database when deployed, a local file during development
    >   url: process.env.TURSO_DATABASE_URL ?? 'file:./mastra.db',
    >   authToken: process.env.TURSO_AUTH_TOKEN,
@@ -82,12 +83,13 @@ The region is fixed when the environment is created. Databases attached to an en
 
 Preflight validates the built output before anything ships, and only flags issues in your own code:
 
-- **Local storage paths**: A hard block. File-backed storage (for example `file:./mastra.db`) is lost on every deploy. Preflight passes when the path is guarded by an environment variable that is set locally, stored on the platform, or provided by a managed database:
+- **Local storage paths**: A hard block. File-backed storage (for example `file:./mastra.db`) is lost on every deploy. Preflight passes when the path is guarded by an environment variable that's set locally, stored on the platform, or provided by a managed database:
 
   ```ts
   import { LibSQLStore } from '@mastra/libsql'
 
   export const storage = new LibSQLStore({
+    id: 'mastra-storage',
     // Uses the hosted database when deployed, a local file during development
     url: process.env.TURSO_DATABASE_URL ?? 'file:./mastra.db',
     authToken: process.env.TURSO_AUTH_TOKEN,

package/.docs/docs/memory/multi-user-threads.md

@@ -58,7 +58,7 @@ import { Memory } from '@mastra/memory'
 import { LibSQLStore } from '@mastra/libsql'
 
 const memory = new Memory({
-  storage: new LibSQLStore({ url: 'file:./collab.db' }),
+  storage: new LibSQLStore({ id: 'collab-storage', url: 'file:./collab.db' }),
   options: {
     lastMessages: 20,
   },
@@ -128,7 +128,7 @@ import { Memory } from '@mastra/memory'
 import { LibSQLStore } from '@mastra/libsql'
 
 const memory = new Memory({
-  storage: new LibSQLStore({ url: 'file:./collab.db' }),
+  storage: new LibSQLStore({ id: 'collab-storage', url: 'file:./collab.db' }),
   options: {
     lastMessages: 20,
   },
@@ -148,7 +148,7 @@ import { Memory } from '@mastra/memory'
 import { LibSQLStore } from '@mastra/libsql'
 
 const memory = new Memory({
-  storage: new LibSQLStore({ url: 'file:./collab.db' }),
+  storage: new LibSQLStore({ id: 'collab-storage', url: 'file:./collab.db' }),
   options: {
     lastMessages: 20,
     observationalMemory: true,
@@ -171,7 +171,7 @@ import { Memory } from '@mastra/memory'
 import { LibSQLStore } from '@mastra/libsql'
 
 const memory = new Memory({
-  storage: new LibSQLStore({ url: 'file:./collab.db' }),
+  storage: new LibSQLStore({ id: 'collab-storage', url: 'file:./collab.db' }),
   options: {
     lastMessages: 20,
     workingMemory: {

package/.docs/docs/memory/observational-memory.md

@@ -47,7 +47,7 @@ See [configuration options](https://mastra.ai/reference/memory/observational-mem
 >
 > For an AI SDK example, see [Using Mastra Memory](https://mastra.ai/guides/build-your-ui/ai-sdk-ui).
 
-> **Note:** OM currently only supports `@mastra/pg`, `@mastra/libsql`, and `@mastra/mongodb` storage adapters. It uses background agents for managing memory. When no model is set, the default model is `google/gemini-2.5-flash`.
+> **Note:** OM currently only supports `@mastra/pg`, `@mastra/libsql`, `@mastra/mongodb`, and `@mastra/convex` storage adapters. It uses background agents for managing memory. When no model is set, the default model is `google/gemini-2.5-flash`.
 
 ## Temporal gap markers
 

package/.docs/docs/memory/working-memory.md

@@ -403,7 +403,7 @@ By default, working memory reaches the model as part of the system message. You
 
 ```typescript
 const memory = new Memory({
-  storage: new LibSQLStore({ url: 'file:./mastra.db' }),
+  storage: new LibSQLStore({ id: 'mastra-storage', url: 'file:./mastra.db' }),
   options: {
     workingMemory: {
       enabled: true,

package/.docs/docs/observability/integrations/exporters/braintrust.md

@@ -109,10 +109,38 @@ new BraintrustExporter({
 
 ## Attach traces to Braintrust evals
 
+Install the Braintrust SDK directly when your application uses `Eval()`, `logger.traced()`, or `currentSpan`:
+
+**npm**:
+
+```bash
+npm install braintrust@latest
+```
+
+**pnpm**:
+
+```bash
+pnpm add braintrust@latest
+```
+
+**Yarn**:
+
+```bash
+yarn add braintrust@latest
+```
+
+**Bun**:
+
+```bash
+bun add braintrust@latest
+```
+
 When you run Mastra inside Braintrust `Eval()` or `logger.traced()`, pass the Braintrust logger and `currentSpan` resolver to the exporter. Import `currentSpan` from the same `braintrust` package instance that creates the eval or traced span.
 
 This helps Mastra attach its spans under the active Braintrust span when your app and `@mastra/braintrust` resolve different installed copies of the Braintrust SDK.
 
+The exporter accepts compatible logger and span objects from Braintrust SDK v2 and v3. Your application's Braintrust SDK version doesn't need to match the version installed by `@mastra/braintrust`.
+
 ```typescript
 import { currentSpan, initLogger } from 'braintrust'
 import { BraintrustExporter } from '@mastra/braintrust'
@@ -144,15 +172,19 @@ await Eval('my-project', {
 })
 ```
 
+If your application upgrades its direct Braintrust dependency from v2 to v3 and uses Nunjucks prompt templates, follow the [Braintrust v2 to v3 migration guide](https://www.braintrust.dev/docs/sdks/typescript/migrations/v2-to-v3).
+
 ## Querying Braintrust with returned `spanId`
 
-For Braintrust, use `spanId` as the root span identifier when searching for traces because Braintrust root-span queries are typically faster than trace-id queries.
+Mastra uses its returned `spanId` as both the Braintrust row ID and span ID. Use it to find the corresponding Braintrust span by `id` or `span_id`.
+
+Braintrust v3 stores a separate W3C trace ID in `root_span_id`, so the returned Mastra `spanId` isn't the Braintrust `root_span_id`.
 
 ```typescript
 const result = await agent.stream('Summarize this ticket')
 
 console.log('Mastra trace ID:', result.traceId)
-console.log('Braintrust root span ID:', result.spanId)
+console.log('Braintrust row and span ID:', result.spanId)
 
 // Use result.spanId in your Braintrust lookup/query path
 ```

package/.docs/docs/voice/livekit.md

@@ -360,7 +360,7 @@ import { LibSQLStore } from '@mastra/libsql'
 import { Observability, MastraStorageExporter } from '@mastra/observability'
 
 export const mastra = new Mastra({
-  storage: new LibSQLStore({ url: 'file:./voice-agent.db' }),
+  storage: new LibSQLStore({ id: 'voice-agent-storage', url: 'file:./voice-agent.db' }),
   observability: new Observability({
     configs: {
       default: {

package/.docs/guides/build-your-ui/ai-sdk-ui.md

@@ -1134,6 +1134,7 @@ import { LibSQLStore } from '@mastra/libsql'
 export const mastra = new Mastra({
   workflows: { approvalWorkflow },
   storage: new LibSQLStore({
+    id: 'mastra-storage',
     url: 'file:../mastra.db',
   }),
   server: {

package/.docs/guides/guide/signal-provider.md

@@ -26,6 +26,7 @@ import { LibSQLStore } from '@mastra/libsql'
 
 export const mastra = new Mastra({
   storage: new LibSQLStore({
+    id: 'mastra-storage',
     url: 'file:./mastra.db',
   }),
 })
@@ -133,6 +134,7 @@ import { devAgent } from './agents/dev-agent'
 export const mastra = new Mastra({
   agents: { devAgent },
   storage: new LibSQLStore({
+    id: 'mastra-storage',
     url: 'file:./mastra.db',
   }),
 })

package/.docs/reference/agent-controller/agent-controller-class.md

@@ -22,7 +22,7 @@ import { z } from 'zod'
 const agentController = new AgentController({
   id: 'my-coding-agent',
   agent: myAgent,
-  storage: new LibSQLStore({ url: 'file:./data.db' }),
+  storage: new LibSQLStore({ id: 'agent-storage', url: 'file:./data.db' }),
   stateSchema: z.object({
     currentModelId: z.string().optional(),
   }),

package/.docs/reference/agents/agent.md

@@ -439,7 +439,7 @@ Returns an `AgentThreadSubscription` object with these members:
 
 **agents** (`Record<string, Agent> | ({ requestContext: RequestContext }) => Record<string, Agent> | Promise<Record<string, Agent>>`): Subagents that the agent can access. Can be provided statically or resolved dynamically.
 
-**tools** (`ToolsInput | ({ requestContext: RequestContext }) => ToolsInput | Promise<ToolsInput>`): Tools that the agent can access. Can be provided statically or resolved dynamically.
+**tools** (`ToolsInput | ({ requestContext: RequestContext, mastra?: Mastra }) => ToolsInput | Promise<ToolsInput>`): Tools that the agent can access. Can be provided statically or resolved dynamically from the request context and associated Mastra instance when available.
 
 **hooks** (`ToolHooks`): Hooks that run before and after every tool call made by this agent. Per-execution hooks passed to generate() or stream() override matching hooks set here. See Tool hooks below.
 

package/.docs/reference/cli/mastra.md

@@ -429,7 +429,7 @@ Emit machine-readable JSON. Secret values are masked unless `--show-secrets` is
 
 ### `mastra env db delete`
 
-Permanently deletes a database with the provider, including all of its data. This cannot be undone. The CLI prompts for confirmation unless `--yes` is passed. After deletion, deploys no longer receive the database's env vars.
+Permanently deletes a database with the provider, including all of its data. This can't be undone. The CLI prompts for confirmation unless `--yes` is passed. After deletion, deploys no longer receive the database's env vars.
 
 ```bash
 mastra env db delete <database>

package/.docs/reference/core/getTool.md

@@ -0,0 +1,33 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
+# Mastra.getTool()
+
+The `.getTool()` method retrieves a tool from the Mastra-level registry by its registration key.
+
+## Usage example
+
+Register a tool under the `weather` key, then use that key to retrieve it.
+
+```typescript
+import { Mastra } from '@mastra/core/mastra'
+import { weatherTool } from './tools/weather-tool'
+
+export const mastra = new Mastra({
+  tools: {
+    weather: weatherTool,
+  },
+})
+
+const tool = mastra.getTool('weather')
+```
+
+## Parameters
+
+**name** (`TToolName extends keyof TTools`): The registration key of the tool in the Mastra tools registry.
+
+## Related
+
+- [Share tools across agents](https://mastra.ai/docs/agents/using-tools)
+- [Mastra class](https://mastra.ai/reference/core/mastra-class)
+- [Mastra.getToolById()](https://mastra.ai/reference/core/getToolById)
+- [Mastra.listTools()](https://mastra.ai/reference/core/listTools)

package/.docs/reference/core/getToolById.md

@@ -0,0 +1,48 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
+# Mastra.getToolById()
+
+The `.getToolById()` method first searches the Mastra-level registry for a tool with a matching intrinsic `id`. If no intrinsic ID matches, it treats the value as a registration key.
+
+## Usage example
+
+This example uses `weather` as the registration key and `weather-tool` as the tool's intrinsic ID.
+
+```typescript
+import { Mastra } from '@mastra/core/mastra'
+import { createTool } from '@mastra/core/tools'
+import { z } from 'zod'
+
+const weatherTool = createTool({
+  id: 'weather-tool',
+  description: 'Fetches weather for a location',
+  inputSchema: z.object({
+    location: z.string(),
+  }),
+  outputSchema: z.object({
+    weather: z.string(),
+  }),
+  execute: async ({ location }) => ({
+    weather: `Weather for ${location}`,
+  }),
+})
+
+export const mastra = new Mastra({
+  tools: {
+    weather: weatherTool,
+  },
+})
+
+const toolById = mastra.getToolById('weather-tool')
+```
+
+## Parameters
+
+**id** (`TTools[TToolName]['id']`): The intrinsic tool ID to find. When no tool has that ID, Mastra uses the value as a registration key.
+
+## Related
+
+- [Share tools across agents](https://mastra.ai/docs/agents/using-tools)
+- [Mastra class](https://mastra.ai/reference/core/mastra-class)
+- [Mastra.getTool()](https://mastra.ai/reference/core/getTool)
+- [Mastra.listTools()](https://mastra.ai/reference/core/listTools)

package/.docs/reference/core/listTools.md

@@ -0,0 +1,38 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
+# Mastra.listTools()
+
+The `.listTools()` method returns the tools configured on a Mastra instance. The returned record uses Mastra registration keys and tool instances as values.
+
+## Usage example
+
+```typescript
+import { Mastra } from '@mastra/core/mastra'
+import { weatherTool } from './tools/weather-tool'
+
+export const mastra = new Mastra({
+  tools: {
+    weather: weatherTool,
+  },
+})
+
+const tools = mastra.listTools()
+const weather = tools?.weather
+```
+
+## Parameters
+
+This method doesn't accept any parameters.
+
+## Returns
+
+**tools** (`TTools | undefined`): The Mastra-level tool registry, where each key is a registration key and each value is a tool instance. Returns undefined when no registry is available.
+
+This method lists the Mastra-level registry. It doesn't include tools that exist only in a function-based Agent `tools` callback.
+
+## Related
+
+- [Share tools across agents](https://mastra.ai/docs/agents/using-tools)
+- [Mastra class](https://mastra.ai/reference/core/mastra-class)
+- [Mastra.getTool()](https://mastra.ai/reference/core/getTool)
+- [Mastra.getToolById()](https://mastra.ai/reference/core/getToolById)

package/.docs/reference/core/mastra-class.md

@@ -53,7 +53,7 @@ Visit the [Configuration reference](https://mastra.ai/reference/configuration) f
 
 **agents** (`Record<string, Agent>`): Agent instances to register, keyed by name (Default: `{}`)
 
-**tools** (`Record<string, ToolApi>`): Custom tools to register. Structured as a key-value pair, with keys being the tool name and values being the tool function. (Default: `{}`)
+**tools** (`Record<string, ToolApi>`): Tool instances to register. Keys are registration keys used by \`getTool()\`, and values are tool instances. Use \`getToolById()\` for intrinsic ID lookup and \`listTools()\` to read the registry. (Default: `{}`)
 
 **storage** (`MastraCompositeStore`): Storage engine instance for persisting data
 

package/.docs/reference/file-based-agents/logger.md

@@ -19,7 +19,7 @@ export default new PinoLogger({
 })
 ```
 
-Mastra registers the logger before storage, observability, and file-based agents, so those primitives log through this logger as they are wired up.
+Mastra registers the logger before storage, observability, and file-based agents, so those primitives log through this logger as they're wired up.
 
 ## Precedence with code
 

package/.docs/reference/index.md

@@ -97,6 +97,8 @@ The Reference section provides documentation of Mastra's API, including paramete
 - [.getServer()](https://mastra.ai/reference/core/getServer)
 - [.getStorage()](https://mastra.ai/reference/core/getStorage)
 - [.getTelemetry()](https://mastra.ai/reference/core/getTelemetry)
+- [.getTool()](https://mastra.ai/reference/core/getTool)
+- [.getToolById()](https://mastra.ai/reference/core/getToolById)
 - [.getVector()](https://mastra.ai/reference/core/getVector)
 - [.getWorkflow()](https://mastra.ai/reference/core/getWorkflow)
 - [.listAgents()](https://mastra.ai/reference/core/listAgents)
@@ -106,6 +108,7 @@ The Reference section provides documentation of Mastra's API, including paramete
 - [.listMCPServers()](https://mastra.ai/reference/core/listMCPServers)
 - [.listMemory()](https://mastra.ai/reference/core/listMemory)
 - [.listScorers()](https://mastra.ai/reference/core/listScorers)
+- [.listTools()](https://mastra.ai/reference/core/listTools)
 - [.listVectors()](https://mastra.ai/reference/core/listVectors)
 - [.listWorkflows()](https://mastra.ai/reference/core/listWorkflows)
 - [.removeWorkspace()](https://mastra.ai/reference/core/removeWorkspace)

package/.docs/reference/storage/clickhouse.md

@@ -131,7 +131,7 @@ bun x mastra migrate
 
 The migration copies span data from `mastra_ai_spans` into `mastra_span_events` in day-sized batches. It handles column mapping, deduplicates legacy rows, and preserves the original table as a backup. After migration, traces appear in Studio through the vNext adapter.
 
-> **Note:** The legacy table is not deleted. Drop it manually after verifying the migration.
+> **Note:** The legacy table isn't deleted. Drop it manually after verifying the migration.
 
 ### ClickHouse for every domain
 

package/.docs/reference/storage/convex.md

@@ -50,6 +50,7 @@ import {
   mastraResourcesTable,
   mastraWorkflowSnapshotsTable,
   mastraScoresTable,
+  mastraObservationalMemoryTable,
   mastraVectorIndexesTable,
   mastraVectorsTable,
   mastraCacheTable,
@@ -63,6 +64,7 @@ export default defineSchema({
   mastra_resources: mastraResourcesTable,
   mastra_workflow_snapshots: mastraWorkflowSnapshotsTable,
   mastra_scorers: mastraScoresTable,
+  mastra_observational_memory: mastraObservationalMemoryTable,
   mastra_vector_indexes: mastraVectorIndexesTable,
   mastra_vectors: mastraVectorsTable,
   mastra_cache: mastraCacheTable,
@@ -192,16 +194,21 @@ Use a non-empty `keyPrefix` unless you intentionally want `clear()` to remove ev
 
 The storage implementation uses typed Convex tables for each Mastra domain:
 
-| Domain      | Convex Table                | Purpose                                   |
-| ----------- | --------------------------- | ----------------------------------------- |
-| Threads     | `mastra_threads`            | Conversation threads                      |
-| Messages    | `mastra_messages`           | Chat messages                             |
-| Resources   | `mastra_resources`          | User working memory                       |
-| Workflows   | `mastra_workflow_snapshots` | Workflow state                            |
-| Scorers     | `mastra_scorers`            | Evaluation data                           |
-| Cache       | `mastra_cache`              | Cache values, counters, and list metadata |
-| Cache Items | `mastra_cache_list_items`   | Cache list entries                        |
-| Fallback    | `mastra_documents`          | Unknown tables                            |
+| Domain               | Convex Table                  | Purpose                                   |
+| -------------------- | ----------------------------- | ----------------------------------------- |
+| Threads              | `mastra_threads`              | Conversation threads                      |
+| Messages             | `mastra_messages`             | Chat messages                             |
+| Resources            | `mastra_resources`            | User working memory                       |
+| Observational Memory | `mastra_observational_memory` | Observational memory generations          |
+| Workflows            | `mastra_workflow_snapshots`   | Workflow state                            |
+| Scorers              | `mastra_scorers`              | Evaluation data                           |
+| Cache                | `mastra_cache`                | Cache values, counters, and list metadata |
+| Cache Items          | `mastra_cache_list_items`     | Cache list entries                        |
+| Fallback             | `mastra_documents`            | Unknown tables                            |
+
+### Observational memory
+
+`ConvexStore` supports [observational memory](https://mastra.ai/docs/memory/observational-memory). Add `mastraObservationalMemoryTable` to your Convex schema and redeploy with `npx convex deploy` to enable it. Existing deployments created before this table was added need the same schema update.
 
 ### Architecture
 

package/.docs/reference/storage/retention.md

@@ -228,7 +228,7 @@ const storage = new MongoDBStore({
 })
 ```
 
-> **Tip:** TTL indexes delete documents shortly after they expire (background thread runs every \~60 seconds), but the exact timing is not guaranteed. For precise, immediate cleanup, use `prune()` instead.
+> **Tip:** TTL indexes delete documents shortly after they expire (background thread runs every \~60 seconds), but the exact timing isn't guaranteed. For precise, immediate cleanup, use `prune()` instead.
 
 ## Reclaiming disk
 

package/.docs/reference/tools/task-tools.md

@@ -85,7 +85,7 @@ At least one of `content`, `status`, or `activeForm` is required.
 ### Behavior
 
 - When the update sets a task to `in_progress`, any other `in_progress` task is automatically demoted to `pending`.
-- Returns an error with available task IDs when the ID is not found.
+- Returns an error with available task IDs when the ID isn't found.
 
 ## `task_complete`
 
@@ -97,7 +97,7 @@ Mark one task completed by its stable ID.
 
 ### Behavior
 
-Returns an error with available task IDs when the ID is not found.
+Returns an error with available task IDs when the ID isn't found.
 
 ## `task_check`
 

package/CHANGELOG.md

@@ -1,5 +1,12 @@
 # @mastra/mcp-docs-server
 
+## 1.2.8-alpha.1
+
+### Patch Changes
+
+- Updated dependencies [[`8a0d145`](https://github.com/mastra-ai/mastra/commit/8a0d145aadbdf7278665aceaaec364b35dd9bd94), [`bd2f1d2`](https://github.com/mastra-ai/mastra/commit/bd2f1d274d05e60e2366f005ea0d94d5cea0d5ff), [`21a0eb8`](https://github.com/mastra-ai/mastra/commit/21a0eb86746ba0b703acea360d4f84c6a5a493f2), [`de86fd7`](https://github.com/mastra-ai/mastra/commit/de86fd7119f0438381d1a642e3d258143c0b9c29), [`2745031`](https://github.com/mastra-ai/mastra/commit/2745031d1d4a4978f037092da371428c32e2842a), [`db650ce`](https://github.com/mastra-ai/mastra/commit/db650ce490348914e85b93651d83acdf8f2a4c31), [`6354eeb`](https://github.com/mastra-ai/mastra/commit/6354eeb32efa9f5f68f51dda394e90e2ee76f1fb)]:
+  - @mastra/core@1.51.1-alpha.0
+
 ## 1.2.7
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mastra/mcp-docs-server",
-  "version": "1.2.8-alpha.0",
+  "version": "1.2.8-alpha.2",
   "description": "MCP server for accessing Mastra.ai documentation, changelogs, and news.",
   "type": "module",
   "main": "dist/index.js",
@@ -28,8 +28,8 @@
     "jsdom": "^26.1.0",
     "local-pkg": "^1.1.2",
     "zod": "^4.4.3",
-    "@mastra/mcp": "^1.14.0",
-    "@mastra/core": "1.51.0"
+    "@mastra/core": "1.51.1-alpha.0",
+    "@mastra/mcp": "^1.14.0"
   },
   "devDependencies": {
     "@hono/node-server": "^1.19.11",
@@ -45,9 +45,9 @@
     "tsx": "^4.22.4",
     "typescript": "^6.0.3",
     "vitest": "4.1.10",
-    "@internal/types-builder": "0.0.89",
     "@internal/lint": "0.0.114",
-    "@mastra/core": "1.51.0"
+    "@internal/types-builder": "0.0.89",
+    "@mastra/core": "1.51.1-alpha.0"
   },
   "homepage": "https://mastra.ai",
   "repository": {