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

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

@@ -84,7 +84,7 @@ For tools that are executed inside a workflow, access workflow-specific properti
 ```
 
 :::note
-For MCP-specific tool context changes, see the [MCP migration guide]/guides/v1/migrations/upgrade-to-v1/mcp).
+For MCP-specific tool context changes, see the [MCP migration guide](/guides/v1/migrations/upgrade-to-v1/mcp).
 :::
 
 ### `RuntimeContext` to `RequestContext`
@@ -109,7 +109,7 @@ To migrate, update references from `runtimeContext` to `requestContext` in tool
 You can use Mastra's codemod CLI to update your imports automatically:
 
 ```shell
-npx @mastra/codemod v1/runtime-context .
+npx @mastra/codemod@beta v1/runtime-context .
 ```
 
 :::

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

@@ -46,14 +46,14 @@ export const mastra = new Mastra({
 });
 ```
 
-This minimal configuration automatically includes the `DefaultExporter`, `CloudExporter`, and `SensitiveDataFilter` processor. See the [observability tracing documentation]/docs/v1/observability/tracing/overview) for full configuration options.
+This minimal configuration automatically includes the `DefaultExporter`, `CloudExporter`, and `SensitiveDataFilter` processor. See the [observability tracing documentation](/docs/v1/observability/tracing/overview) for full configuration options.
 
 **After (v1 with custom configuration):**
 
 If you need to configure specific exporters (like OTLP), install the exporter package and configure it:
 
 ```bash
-npm install @mastra/otel-exporter @opentelemetry/exporter-trace-otlp-proto
+npm install @mastra/otel-exporter@beta @opentelemetry/exporter-trace-otlp-proto
 ```
 
 ```typescript
@@ -89,7 +89,7 @@ Key changes:
 3. Use `default: { enabled: true }` for quick setup, or `configs:` for custom configuration
 4. Export types change from string literals (`'otlp'`) to exporter class instances (`new OtelExporter()`)
 
-See the [exporters documentation]/docs/v1/observability/tracing/overview#exporters) for all available exporters.
+See the [exporters documentation](/docs/v1/observability/tracing/overview#exporters) for all available exporters.
 
 ### From AI Tracing
 
@@ -134,7 +134,7 @@ The observability functionality has moved to a dedicated `@mastra/observability`
 To migrate, install the package and update your import statements:
 
 ```bash
-npm install @mastra/observability
+npm install @mastra/observability@beta
 ```
 
 ```diff
@@ -204,13 +204,13 @@ To migrate, update method implementations in custom exporters.
 
 The OTEL-based `telemetry` configuration from 0.x has been removed. The old system with `serviceName`, `sampling.type`, and `export.type` properties is no longer supported.
 
-To migrate, follow the "From OTEL-based Telemetry" section above. For detailed configuration options, see the [observability tracing documentation]/docs/v1/observability/tracing/overview).
+To migrate, follow the "From OTEL-based Telemetry" section above. For detailed configuration options, see the [observability tracing documentation](/docs/v1/observability/tracing/overview).
 
 ### Custom instrumentation files
 
 The automatic detection of instrumentation files in `/mastra` (with `.ts`, `.js`, or `.mjs` extensions) has been removed. Custom instrumentation is no longer supported through separate files.
 
-To migrate, use the built-in exporter system or implement custom exporters using the `ObservabilityExporter` interface. See the [exporters documentation]/docs/v1/observability/tracing/overview#exporters) for details.
+To migrate, use the built-in exporter system or implement custom exporters using the `ObservabilityExporter` interface. See the [exporters documentation](/docs/v1/observability/tracing/overview#exporters) for details.
 
 ### `instrumentation.mjs` files
 
@@ -258,11 +258,11 @@ If you were using OTEL-based telemetry with specific providers in 0.x, here's ho
 
 | Provider | Exporter | Guide | Reference |
 |----------|----------|-------|-----------|
-| Arize AX, Arize Phoenix | **Arize** | [Guide]/docs/v1/observability/tracing/exporters/arize) | [Reference]/reference/v1/observability/tracing/exporters/arize) |
-| Braintrust | **Braintrust** | [Guide]/docs/v1/observability/tracing/exporters/braintrust) | [Reference]/reference/v1/observability/tracing/exporters/braintrust) |
-| Langfuse | **Langfuse** | [Guide]/docs/v1/observability/tracing/exporters/langfuse) | [Reference]/reference/v1/observability/tracing/exporters/langfuse) |
-| LangSmith | **LangSmith** | [Guide]/docs/v1/observability/tracing/exporters/langsmith) | [Reference]/reference/v1/observability/tracing/exporters/langsmith) |
-| Dash0, Laminar, New Relic, SigNoz, Traceloop, Custom OTEL | **OpenTelemetry** | [Guide]/docs/v1/observability/tracing/exporters/otel) | [Reference]/reference/v1/observability/tracing/exporters/otel) |
+| Arize AX, Arize Phoenix | **Arize** | [Guide](/docs/v1/observability/tracing/exporters/arize) | [Reference](/reference/v1/observability/tracing/exporters/arize) |
+| Braintrust | **Braintrust** | [Guide](/docs/v1/observability/tracing/exporters/braintrust) | [Reference](/reference/v1/observability/tracing/exporters/braintrust) |
+| Langfuse | **Langfuse** | [Guide](/docs/v1/observability/tracing/exporters/langfuse) | [Reference](/reference/v1/observability/tracing/exporters/langfuse) |
+| LangSmith | **LangSmith** | [Guide](/docs/v1/observability/tracing/exporters/langsmith) | [Reference](/reference/v1/observability/tracing/exporters/langsmith) |
+| Dash0, Laminar, New Relic, SigNoz, Traceloop, Custom OTEL | **OpenTelemetry** | [Guide](/docs/v1/observability/tracing/exporters/otel) | [Reference](/reference/v1/observability/tracing/exporters/otel) |
 | LangWatch | \<coming soon\> | - | - |
 
 ### Installation
@@ -274,7 +274,7 @@ npm install @mastra/[exporter-name]-exporter
 
 **OpenTelemetry exporter** (Dash0, Laminar, New Relic, SigNoz, Traceloop):
 ```bash
-npm install @mastra/otel-exporter
+npm install @mastra/otel-exporter@beta
 ```
 
-Plus the required protocol package for your provider (see [OTEL guide]/docs/v1/observability/tracing/exporters/otel#installation)).
+Plus the required protocol package for your provider (see [OTEL guide](/docs/v1/observability/tracing/exporters/otel#installation)).

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

@@ -5,10 +5,34 @@ description: "Learn how to migrate vector-related changes when upgrading to v1."
 
 # Vectors
 
-Vector store methods have been renamed to follow consistent naming conventions.
+Vector store constructors now require an `id` property, and vector store methods have been renamed to follow consistent naming conventions.
 
 ## Changed
 
+### Required `id` property for vector store instances
+
+Vector store instances now require an `id` property. This unique identifier is used for tracking and managing vector store instances within Mastra. The `id` should be a descriptive, unique string for each vector store in your application.
+
+To migrate, add an `id` field to your vector store constructor.
+
+```diff
+  const vectorStore = new PgVector({
++   id: 'main-vector-store',
+    connectionString: process.env.POSTGRES_CONNECTION_STRING,
+  });
+
+  const chromaStore = new ChromaVector({
++   id: 'chroma-embeddings',
+    url: process.env.CHROMA_URL,
+  });
+
+  const pineconeStore = new PineconeVector({
++   id: 'pinecone-production',
+    apiKey: process.env.PINECONE_API_KEY,
+    environment: process.env.PINECONE_ENVIRONMENT,
+  });
+```
+
 ### `getVectors` to `listVectors`
 
 The `getVectors()` method has been renamed to `listVectors()`. This change aligns with the naming convention used across the API where plural getter methods use the `list` prefix.

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

@@ -33,7 +33,7 @@ To migrate, update configuration property names when configuring agents with voi
 You can use Mastra's codemod CLI to update your code automatically:
 
 ```shell
-npx @mastra/codemod v1/voice-property-names .
+npx @mastra/codemod@beta v1/voice-property-names .
 ```
 
 :::

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

@@ -25,7 +25,7 @@ To migrate, replace all calls to `mastra.getWorkflows()` with `mastra.listWorkfl
 You can use Mastra's codemod CLI to update your imports automatically:
 
 ```shell
-npx @mastra/codemod v1/workflows-get-workflows .
+npx @mastra/codemod@beta v1/mastra-plural-apis .
 ```
 
 :::
@@ -52,7 +52,7 @@ To migrate, update references from `runtimeContext` to `requestContext` in step
 You can use Mastra's codemod CLI to update your imports automatically:
 
 ```shell
-npx @mastra/codemod v1/runtime-context .
+npx @mastra/codemod@beta v1/runtime-context .
 ```
 
 :::
@@ -68,6 +68,16 @@ To migrate, rename method calls from `createRunAsync` to `createRun`.
 + await workflow.createRun({ input: { ... } });
 ```
 
+:::tip[Codemod]
+
+You can use Mastra's codemod CLI to update your code automatically:
+
+```shell
+npx @mastra/codemod@beta v1/workflow-create-run-async .
+```
+
+:::
+
 ### `runCount` to `retryCount` (deprecated)
 
 The `runCount` parameter has been deprecated in favor of `retryCount` in workflow step execution. This change provides clearer naming that better describes retry behavior. The old `runCount` still works but shows deprecation warnings.
@@ -83,6 +93,16 @@ To migrate, rename `runCount` to `retryCount` in step execution functions.
   });
 ```
 
+:::tip[Codemod]
+
+You can use Mastra's codemod CLI to update your code automatically:
+
+```shell
+npx @mastra/codemod@beta v1/workflow-run-count .
+```
+
+:::
+
 ### `getWorkflowRuns` to `listWorkflowRuns`
 
 The `getWorkflowRuns()` method has been renamed to `listWorkflowRuns()`. This change aligns with the convention that `list*` methods return collections.
@@ -94,6 +114,16 @@ To migrate, rename method calls from `getWorkflowRuns` to `listWorkflowRuns`.
 + const runs = await workflow.listWorkflowRuns({ fromDate, toDate });
 ```
 
+:::tip[Codemod]
+
+You can use Mastra's codemod CLI to update your code automatically:
+
+```shell
+npx @mastra/codemod@beta v1/workflow-list-runs .
+```
+
+:::
+
 ## Removed
 
 ### Legacy workflows export

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

@@ -0,0 +1,275 @@
+---
+title: "Next.js Quickstart"
+description: "Get started with Mastra, Next.js, and AS SDK UI. Quickly."
+---
+
+# Next.js Quickstart
+
+In this quickstart, you'll build an AI agent with tool-calling capabilities using [Mastra](/docs/v1), then connect it to Next.js by importing and calling the agent directly within your routes. 
+
+You'll use [AI SDK UI](https://ai-sdk.dev/docs/ai-sdk-ui/overview) and [AI Elements](https://ai-sdk.dev/elements) to create a beautiful, interactive chat experience. 
+
+In ~5 minutes, you'll have a functional AI-powered app ready to extend with your own tools and logic.
+
+<figure>
+![Screenshot of a chat-style web app displaying a completed "weatherTool" tool call, answering "What is the weather in London?" with a JSON result. A message suggests offering activity ideas, and a text input field is at the bottom.](/img/nextjs-quickstart.png)
+<figcaption class="text-sm text-center">What you'll build: an agent that can call a weather tool, display the JSON result, stream a weather summary in the chat UI, and persist conversation history across reloads.</figcaption>
+</figure>
+
+## Before you begin
+
+* You'll need an API key from a supported [model provider](/models/v1). If you don't have a preference, use [OpenAI](https://platform.openai.com/api-keys).
+
+## Create a new Next.js app
+
+Run the following command to [create a new Next.js app](https://nextjs.org/docs/app/getting-started/installation):
+
+```bash
+npx create-next-app \
+    my-nextjs-agent \
+    --yes \
+    --ts \
+    --eslint \
+    --tailwind \
+    --src-dir \
+    --app \
+    --turbopack \
+    --no-react-compiler \
+    --no-import-alias
+```
+
+This creates a project called `my-nextjs-agent`, but you can replace it with any name you want.
+
+## Initialize Mastra
+`cd` and run [`mastra init`](/reference/v1/cli/create-mastra). 
+
+When prompted, choose a provider (e.g. OpenAI) and enter your key:
+
+```bash
+cd my-nextjs-agent
+npx --force mastra@beta init
+```
+This creates a `src/mastra` folder with an example weather agent and the following files:
+
+-	`index.ts` - Mastra config, including memory
+- `tools/weather-tool.ts` - a tool to fetch weather for a given location
+-	`agents/weather-agent.ts`- a weather agent with a prompt that uses the tool
+
+You'll call `weather-agent.ts` from your Next.js routes in the next steps.
+
+
+## Install AI SDK UI and AI Elements
+
+Install AI SDK UI along with the Mastra adapter:
+
+```bash
+npm install \
+    @mastra/ai-sdk \
+    @ai-sdk/react 
+```
+
+Next, initialize AI Elements. When prompted, choose the default options:
+
+```bash
+npx ai-elements@latest
+```
+
+This downloads the entire AI Elements UI component library into a `@/components/ai-elements` folder.
+
+
+## Create a chat route
+
+Create `src/app/api/chat/route.ts`:
+
+```ts title="src/app/api/chat/route.ts"
+import { mastra } from "@/mastra";
+import { NextResponse } from "next/server";
+import { toAISdkFormat } from "@mastra/ai-sdk";
+import { convertMessages } from "@mastra/core/agent";
+import { createUIMessageStreamResponse } from "ai";
+
+const weatherAgent = mastra.getAgent("weatherAgent");
+
+export async function POST(req: Request) {
+  const { messages } = await req.json();
+
+  const stream = await weatherAgent.stream(messages, {
+    memory: {
+      thread: "example-user-id",
+      resource: "weather-chat",
+    },
+  });
+
+  return createUIMessageStreamResponse({
+    stream: toAISdkFormat(stream, { from: "agent" }),
+  })
+}
+
+export async function GET() {
+  const memory = await weatherAgent.getMemory();
+  const response = await memory?.query({
+    threadId: "example-user-id",
+    resourceId: "weather-chat",
+  });
+
+  const uiMessages = 
+    convertMessages(response?.uiMessages ?? []).to("AIV5.UI");
+  return NextResponse.json(uiMessages);
+}
+```
+
+The POST route accepts a prompt and streams the agent's response back in AI SDK format, while the GET route fetches message history from memory so the UI can be hydrated when the client reloads.
+
+## Create a chat page
+
+Create `src/app/chat/page.tsx`:
+
+```tsx title="src/app/chat/page.tsx"
+'use client';
+
+import '@/app/globals.css';
+import { useEffect, useState } from 'react';
+import { DefaultChatTransport } from 'ai';
+import { useChat } from '@ai-sdk/react';
+
+import {
+  PromptInput,
+  PromptInputBody,
+  PromptInputTextarea,
+} from '@/components/ai-elements/prompt-input';
+
+import {
+  Conversation,
+  ConversationContent,
+  ConversationScrollButton,
+} from '@/components/ai-elements/conversation';
+
+import { Message, MessageContent, MessageResponse } from '@/components/ai-elements/message';
+
+import {
+  Tool,
+  ToolHeader,
+  ToolContent,
+  ToolInput,
+  ToolOutput,
+} from '@/components/ai-elements/tool';
+
+
+function Chat() {
+  const [input, setInput] = useState<string>('');
+
+  const { messages, setMessages, sendMessage, status } = useChat({
+    transport: new DefaultChatTransport({
+      api: '/api/chat',
+    }),
+  });
+
+  useEffect(() => {
+    const fetchMessages = async () => {
+      const res = await fetch('/api/chat');
+      const data = await res.json();
+      setMessages([...data]);
+    };
+    fetchMessages();
+  }, [setMessages]);
+
+  const handleSubmit = async () => {
+    if (!input.trim()) return;
+
+    sendMessage({ text: input });
+    setInput('');
+  };
+
+  return (
+    <div className="w-full p-6 relative size-full h-screen">
+      <div className="flex flex-col h-full">
+        <Conversation className="h-full">
+          <ConversationContent>
+            {messages.map((message: any) => (
+              <div key={message.id}>
+                {message.parts?.map((part: any, i: number) => {
+                  if (part.type === 'text') {
+                    return (
+                      <Message 
+                        key={`${message.id}-${i}`} 
+                        from={message.role}>
+                          <MessageContent>
+                            <MessageResponse>{part.text}</MessageResponse>
+                          </MessageContent>
+                      </Message>
+                    );
+                  }
+
+                  if (part.type?.startsWith('tool-')) {
+                    return (
+                      <Tool key={`${message.id}-${i}`}>
+                        <ToolHeader
+                          type={part.type}
+                          state={part.state || 'output-available'}
+                          className="cursor-pointer"
+                        />
+                        <ToolContent>
+                          <ToolInput input={part.input || part.args || {}} />
+                          <ToolOutput
+                            output={part.output || part.result}
+                            errorText={part.errorText || part.error}
+                          />
+                        </ToolContent>
+                      </Tool>
+                    );
+                  }
+
+                  return null;
+                })}
+              </div>
+            ))}
+            <ConversationScrollButton />
+          </ConversationContent>
+        </Conversation>
+
+        <PromptInput onSubmit={handleSubmit} className="mt-20">
+          <PromptInputBody>
+            <PromptInputTextarea
+              onChange={(e: any) => setInput(e.target.value)}
+              className="md:leading-10"
+              value={input}
+              placeholder="Type your message..."
+              disabled={status !== 'ready'}
+            />
+          </PromptInputBody>
+        </PromptInput>
+      </div>
+    </div>
+  );
+}
+
+export default Chat;
+```
+
+This component connects [`useChat()`](https://ai-sdk.dev/docs/reference/ai-sdk-ui/use-chat) to the `api/chat` endpoint, sending prompts there and streaming the response back in chunks.
+
+It renders the response text using the [`<MessageResponse>`](https://ai-sdk.dev/elements/components/message#messageresponse-) component, and shows any tool invocations with the [`<Tool>`](https://ai-sdk.dev/elements/components/tool) component.
+
+
+## Test your agent 
+1. Run your Next.js app with `npm run dev`
+
+2. Open the chat at http://localhost:3000/chat
+
+3. Try asking about the weather. If your API key is set up correctly, you'll get a response.
+
+## Next steps
+
+Congratulations on building your Mastra agent with Next.js! 🎉 
+
+From here, you can extend the project with your own tools and logic:
+
+- Learn more about [agents](/docs/v1/agents/overview)
+- Give your agent its own [tools](/docs/v1/agents/using-tools)
+- Add human-like [memory](/docs/v1/agents/agent-memory) to your agent
+
+When you're ready, read more about how Mastra integrates with AI SDK and Next.js, and how to deploy to Vercel:
+
+- Integrate Mastra with [AI SDK](/docs/v1/frameworks/agentic-uis/ai-sdk)
+- Use Mastra in your [Next.js app](/docs/v1/frameworks/web-frameworks/next-js)
+- Deploy your agent to [Vercel](/docs/v1/deployment/serverless-platforms/vercel-deployer)

package/.docs/raw/index.mdx

@@ -27,7 +27,7 @@ Some highlights include:
 
 - [**Workflows**](/docs/v1/workflows/overview) - When you need explicit control over execution, use Mastra's graph-based workflow engine to orchestrate complex multi-step processes. Mastra workflows use an intuitive syntax for control flow (`.then()`, `.branch()`, `.parallel()`).
 
-- [**Human-in-the-loop**]/docs/v1/workflows/suspend-and-resume) - Suspend an agent or workflow and await user input or approval before resuming. Mastra uses [storage](/docs/v1/server-db/storage) to remember execution state, so you can pause indefinitely and resume where you left off.
+- [**Human-in-the-loop**](/docs/v1/workflows/suspend-and-resume) - Suspend an agent or workflow and await user input or approval before resuming. Mastra uses [storage](/docs/v1/server-db/storage) to remember execution state, so you can pause indefinitely and resume where you left off.
 
 - **Context management** - Give your agents the right context at the right time. Provide [conversation history](/docs/v1/memory/conversation-history), [retrieve](/docs/v1/rag/overview) data from your sources (APIs, databases, files), and add human-like [working](/docs/v1/memory/working-memory) and [semantic](/docs/v1/memory/semantic-recall) memory so your agents behave coherently.
 

package/.docs/raw/logging.mdx

@@ -7,11 +7,11 @@ description: Learn how to use logging in Mastra to monitor execution, capture ap
 
 Mastra's logging system captures function execution, input data, and output responses in a structured format.
 
-When deploying to Mastra Cloud, logs are shown on the [Logs]/docs/v1/mastra-cloud/observability) page. In self-hosted or custom environments, logs can be directed to files or external services depending on the configured transports.
+When deploying to Mastra Cloud, logs are shown on the [Logs](/docs/v1/mastra-cloud/observability) page. In self-hosted or custom environments, logs can be directed to files or external services depending on the configured transports.
 
 ## PinoLogger
 
-When [initializing a new Mastra project]/docs/v1/getting-started/installation) using the CLI, `PinoLogger` is included by default.
+When [initializing a new Mastra project](/docs/v1/getting-started/installation) using the CLI, `PinoLogger` is included by default.
 
 ```typescript title="src/mastra/index.ts" showLineNumbers copy
 import { Mastra } from "@mastra/core";
@@ -26,7 +26,7 @@ export const mastra = new Mastra({
 });
 ```
 
-> See the [PinoLogger]/reference/v1/logging/pino-logger) API reference for all available configuration options.
+> See the [PinoLogger](/reference/v1/logging/pino-logger) API reference for all available configuration options.
 
 ## Logging from workflows and tools
 

package/.docs/raw/mastra-cloud/observability.mdx

@@ -13,7 +13,7 @@ Mastra Cloud captures execution data to help you monitor your application's beha
 
 ## Logs
 
-You can view detailed logs for debugging and monitoring your application's behavior on the [Logs]/docs/v1/mastra-cloud/dashboard#logs) page of the Dashboard.
+You can view detailed logs for debugging and monitoring your application's behavior on the [Logs](/docs/v1/mastra-cloud/dashboard#logs) page of the Dashboard.
 
 ![Dashboard logs](/img/mastra-cloud/mastra-cloud-dashboard-logs.jpg)
 
@@ -23,11 +23,11 @@ Each log entry includes its severity level and a detailed message showing agent,
 
 ## Traces
 
-More detailed traces are available for both agents and workflows by using a [logger]/docs/v1/logging) or enabling [observability]/docs/v1/observability/tracing/overview) using one of our [supported providers]/docs/v1/observability/tracing/overview#exporters).
+More detailed traces are available for both agents and workflows by using a [logger](/docs/v1/logging) or enabling [observability](/docs/v1/observability/tracing/overview) using one of our [supported providers](/docs/v1/observability/tracing/overview#exporters).
 
 ### Agents
 
-With a [logger]/docs/v1/logging) enabled, you can view detailed outputs from your agents in the **Traces** section in Studio.
+With a [logger](/docs/v1/logging) enabled, you can view detailed outputs from your agents in the **Traces** section in Studio.
 
 ![observability agents](/img/mastra-cloud/mastra-cloud-observability-agents.jpg)
 
@@ -37,7 +37,7 @@ Tools passed to the agent during generation are standardized using `convertTools
 
 ### Workflows
 
-With a [logger]/docs/v1/logging) enabled, you can view detailed outputs from your workflows in the **Traces** section in Studio.
+With a [logger](/docs/v1/logging) enabled, you can view detailed outputs from your workflows in the **Traces** section in Studio.
 
 ![observability workflows](/img/mastra-cloud/mastra-cloud-observability-workflows.jpg)
 
@@ -47,5 +47,5 @@ Workflows are created using `createWorkflow`, which sets up steps, metadata, and
 
 ## Next steps
 
-- [Logging]/docs/v1/logging)
-- [Tracing]/docs/v1/observability/tracing/overview)
+- [Logging](/docs/v1/logging)
+- [Tracing](/docs/v1/observability/tracing/overview)

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

@@ -16,7 +16,7 @@ Mastra's memory system uses [storage providers](#memory-storage-adapters) to per
 First install the required dependencies:
 
 ```bash copy
-npm install @mastra/core @mastra/memory @mastra/libsql
+npm install @mastra/core@beta @mastra/memory@beta @mastra/libsql@beta
 ```
 
 Then add a storage adapter to the main Mastra instance. Any agent with memory enabled will use this shared storage to store and recall interactions.
@@ -69,7 +69,7 @@ All memory types are [resource-scoped](./working-memory#resource-scoped-memory-d
 
 To persist and recall information between conversations, memory requires a storage adapter.
 
-Supported options include [LibSQL](/docs/v1/memory/storage/memory-with-libsql), [MongoDB](/examples/v1/memory/memory-with-mongodb), [Postgres](/docs/v1/memory/storage/memory-with-pg), and [Upstash](/docs/v1/memory/storage/memory-with-upstash)
+Supported options include [LibSQL](/docs/v1/memory/storage/memory-with-libsql), [MongoDB](/docs/v1/memory/storage/memory-with-mongodb), [Postgres](/docs/v1/memory/storage/memory-with-pg), and [Upstash](/docs/v1/memory/storage/memory-with-upstash)
 
 We use LibSQL out of the box because it is file-based or in-memory, so it is easy to install and works well with Studio.
 

package/.docs/raw/memory/semantic-recall.mdx

@@ -94,7 +94,7 @@ const agent = new Agent({
 **Storage/vector code Examples**:
 
 - [LibSQL](/docs/v1/memory/storage/memory-with-libsql)
-- [MongoDB](/examples/v1/memory/memory-with-mongodb)
+- [MongoDB](/docs/v1/memory/storage/memory-with-mongodb)
 - [Postgres](/docs/v1/memory/storage/memory-with-pg)
 - [Upstash](/docs/v1/memory/storage/memory-with-upstash)
 
@@ -147,7 +147,7 @@ const agent = new Agent({
 To use FastEmbed (a local embedding model), install `@mastra/fastembed`:
 
 ```bash npm2yarn copy
-npm install @mastra/fastembed
+npm install @mastra/fastembed@beta
 ```
 
 Then configure it in your memory:

package/.docs/raw/memory/storage/memory-with-libsql.mdx

@@ -18,7 +18,7 @@ OPENAI_API_KEY=<your-api-key>
 And install the following package:
 
 ```bash copy
-npm install @mastra/libsql
+npm install @mastra/libsql@beta
 ```
 
 ## Adding memory to an agent
@@ -56,7 +56,7 @@ Embeddings are numeric vectors used by memory’s `semanticRecall` to retrieve r
 Install `fastembed` to get started:
 
 ```bash copy
-npm install @mastra/fastembed
+npm install @mastra/fastembed@beta
 ```
 
 Add the following to your agent: