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

package/.docs/raw/reference/server/hono-adapter.mdx

@@ -25,7 +25,7 @@ For general adapter concepts (constructor options, initialization flow, etc.), s
 
 Install the Hono adapter and Hono framework:
 
-```bash copy
+```bash
 npm install @mastra/hono@beta hono
 ```
 
@@ -35,7 +35,7 @@ npm install @mastra/hono@beta hono
 
 Create your server file:
 
-```typescript title="server.ts" copy
+```typescript title="server.ts"
 import { Hono } from 'hono';
 import { HonoBindings, HonoVariables, MastraServer } from '@mastra/hono';
 import { mastra } from './mastra';
@@ -54,7 +54,7 @@ export default app;
 
 ## Full example
 
-```typescript title="server.ts" copy
+```typescript title="server.ts"
 import { Hono } from 'hono';
 import { HonoBindings, HonoVariables, MastraServer } from '@mastra/hono';
 import { mastra } from './mastra';
@@ -147,7 +147,7 @@ export default app;
 
 Add routes directly to the Hono app:
 
-```typescript title="server.ts" copy
+```typescript title="server.ts"
 import { Hono } from 'hono';
 import { HonoBindings, HonoVariables, MastraServer } from '@mastra/hono';
 
@@ -176,7 +176,7 @@ Routes added before `init()` run without Mastra context. Add routes after `init(
 
 In Hono middleware and route handlers, access Mastra context via `c.get()`:
 
-```typescript copy
+```typescript
 app.get('/custom', async (c) => {
   const mastra = c.get('mastra');
   const requestContext = c.get('requestContext');
@@ -203,7 +203,7 @@ Available context keys:
 
 Add Hono middleware before or after `init()`:
 
-```typescript title="server.ts" copy
+```typescript title="server.ts"
 import { Hono } from 'hono';
 import { HonoBindings, HonoVariables, MastraServer } from '@mastra/hono';
 
@@ -221,7 +221,6 @@ await server.init();
 // Middleware after init has access to Mastra context
 app.use('*', async (c, next) => {
   const mastra = c.get('mastra');
-  // ...
   await next();
 });
 ```

package/.docs/raw/reference/server/mastra-server.mdx

@@ -11,13 +11,13 @@ The `MastraServer` abstract class is the base for all server adapters. Extend th
 
 ## Import
 
-```typescript copy
+```typescript
 import { MastraServer } from '@mastra/server/server-adapter';
 ```
 
 ## Type parameters
 
-```typescript copy
+```typescript
 MastraServer<TApp, TRequest, TResponse>
 ```
 
@@ -29,7 +29,7 @@ MastraServer<TApp, TRequest, TResponse>
 
 ## Constructor
 
-```typescript copy
+```typescript
 constructor(options: MastraServerOptions<TApp>)
 ```
 
@@ -119,7 +119,7 @@ These methods must be implemented by adapters:
 
 Attach Mastra context to every request.
 
-```typescript copy
+```typescript
 abstract registerContextMiddleware(): void
 ```
 
@@ -133,7 +133,7 @@ abstract registerContextMiddleware(): void
 
 Register authentication and authorization middleware.
 
-```typescript copy
+```typescript
 abstract registerAuthMiddleware(): void
 ```
 
@@ -141,7 +141,7 @@ abstract registerAuthMiddleware(): void
 
 Register a single route with the framework.
 
-```typescript copy
+```typescript
 abstract registerRoute(
   app: TApp,
   route: ServerRoute,
@@ -153,7 +153,7 @@ abstract registerRoute(
 
 Extract parameters from the request.
 
-```typescript copy
+```typescript
 abstract getParams(
   route: ServerRoute,
   request: TRequest
@@ -168,7 +168,7 @@ abstract getParams(
 
 Send response based on route type.
 
-```typescript copy
+```typescript
 abstract sendResponse(
   route: ServerRoute,
   response: TResponse,
@@ -180,7 +180,7 @@ abstract sendResponse(
 
 Handle streaming responses.
 
-```typescript copy
+```typescript
 abstract stream(
   route: ServerRoute,
   response: TResponse,
@@ -194,7 +194,7 @@ abstract stream(
 
 Initialize the server by registering all middleware and routes.
 
-```typescript copy
+```typescript
 async init(): Promise<void>
 ```
 
@@ -207,7 +207,7 @@ Calls in order:
 
 Register all Mastra routes.
 
-```typescript copy
+```typescript
 async registerRoutes(): Promise<void>
 ```
 
@@ -215,7 +215,7 @@ async registerRoutes(): Promise<void>
 
 Get the framework app instance.
 
-```typescript copy
+```typescript
 getApp<T = TApp>(): T
 ```
 
@@ -223,7 +223,7 @@ getApp<T = TApp>(): T
 
 Validate path parameters with the route's Zod schema.
 
-```typescript copy
+```typescript
 async parsePathParams(
   route: ServerRoute,
   params: Record<string, string>
@@ -234,7 +234,7 @@ async parsePathParams(
 
 Validate query parameters with the route's Zod schema.
 
-```typescript copy
+```typescript
 async parseQueryParams(
   route: ServerRoute,
   params: Record<string, string>
@@ -245,7 +245,7 @@ async parseQueryParams(
 
 Validate request body with the route's Zod schema.
 
-```typescript copy
+```typescript
 async parseBody(
   route: ServerRoute,
   body: unknown
@@ -256,7 +256,7 @@ async parseBody(
 
 Register an endpoint that serves the OpenAPI specification.
 
-```typescript copy
+```typescript
 async registerOpenAPIRoute(
   app: TApp,
   config: OpenAPIConfig,
@@ -270,7 +270,7 @@ async registerOpenAPIRoute(
 
 Merge request context from multiple sources (query params and body).
 
-```typescript copy
+```typescript
 protected mergeRequestContext(options: {
   paramsRequestContext?: Record<string, any>;
   bodyRequestContext?: Record<string, any>;
@@ -281,7 +281,7 @@ protected mergeRequestContext(options: {
 
 ### BodyLimitOptions
 
-```typescript copy
+```typescript
 interface BodyLimitOptions {
   maxSize: number;
   onError: (error: unknown) => unknown;
@@ -290,7 +290,7 @@ interface BodyLimitOptions {
 
 ### StreamOptions
 
-```typescript copy
+```typescript
 interface StreamOptions {
   redact?: boolean;
 }
@@ -298,7 +298,7 @@ interface StreamOptions {
 
 ## Example
 
-```typescript copy
+```typescript
 import { MastraServer, ServerRoute } from '@mastra/server/server-adapter';
 import type { Mastra } from '@mastra/core';
 

package/.docs/raw/reference/storage/cloudflare-d1.mdx

@@ -15,7 +15,7 @@ npm install @mastra/cloudflare-d1@beta
 
 ## Usage
 
-```typescript copy showLineNumbers
+```typescript
 import { D1Store } from "@mastra/cloudflare-d1";
 
 type Env = {
@@ -99,7 +99,7 @@ The storage implementation handles schema creation and updates automatically. It
 
 When you pass storage to the Mastra class, `init()` is called automatically before any storage operation:
 
-```typescript copy
+```typescript
 import { Mastra } from "@mastra/core";
 import { D1Store } from "@mastra/cloudflare-d1";
 
@@ -114,7 +114,7 @@ const mastra = new Mastra({
 
 If you're using storage directly without Mastra, you must call `init()` explicitly to create the tables:
 
-```typescript copy
+```typescript
 import { D1Store } from "@mastra/cloudflare-d1";
 
 const storage = new D1Store({

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

@@ -9,13 +9,13 @@ The Cloudflare KV storage implementation provides a globally distributed, server
 
 ## Installation
 
-```bash copy
+```bash
 npm install @mastra/cloudflare@beta
 ```
 
 ## Usage
 
-```typescript copy showLineNumbers
+```typescript
 import { CloudflareStore } from "@mastra/cloudflare";
 
 // --- Example 1: Using Workers Binding ---

package/.docs/raw/reference/storage/convex.mdx

@@ -9,7 +9,7 @@ The Convex storage implementation provides a serverless storage solution using [
 
 ## Installation
 
-```bash copy
+```bash
 npm install @mastra/convex@beta
 ```
 
@@ -21,7 +21,7 @@ Before using `ConvexStore`, you need to set up the Convex schema and storage han
 
 In `convex/schema.ts`:
 
-```typescript copy
+```typescript
 import { defineSchema } from 'convex/server';
 import {
   mastraThreadsTable,
@@ -32,7 +32,7 @@ import {
   mastraVectorIndexesTable,
   mastraVectorsTable,
   mastraDocumentsTable,
-} from '@mastra/convex/server';
+} from '@mastra/convex/schema';
 
 export default defineSchema({
   mastra_threads: mastraThreadsTable,
@@ -50,7 +50,7 @@ export default defineSchema({
 
 In `convex/mastra/storage.ts`:
 
-```typescript copy
+```typescript
 import { mastraStorage } from '@mastra/convex/server';
 
 export const handle = mastraStorage;
@@ -58,7 +58,7 @@ export const handle = mastraStorage;
 
 ### 3. Deploy to Convex
 
-```bash copy
+```bash
 npx convex dev
 # or for production
 npx convex deploy
@@ -66,7 +66,7 @@ npx convex deploy
 
 ## Usage
 
-```typescript copy showLineNumbers
+```typescript
 import { ConvexStore } from "@mastra/convex";
 
 const storage = new ConvexStore({

package/.docs/raw/reference/storage/dynamodb.mdx

@@ -18,7 +18,7 @@ The DynamoDB storage implementation provides a scalable and performant NoSQL dat
 
 ## Installation
 
-```bash copy
+```bash
 npm install @mastra/dynamodb@beta
 # or
 pnpm add @mastra/dynamodb@beta
@@ -36,7 +36,7 @@ Detailed instructions for setting up the table using AWS CloudFormation or AWS C
 
 ### Basic Usage
 
-```typescript copy showLineNumbers
+```typescript
 import { Memory } from "@mastra/memory";
 import { DynamoDBStore } from "@mastra/dynamodb";
 
@@ -72,7 +72,7 @@ For local development, you can use [DynamoDB Local](https://docs.aws.amazon.com/
 
 2.  **Configure `DynamoDBStore` to use the local endpoint:**
 
-    ```typescript copy showLineNumbers
+    ```typescript copy
     import { DynamoDBStore } from "@mastra/dynamodb";
 
     const storage = new DynamoDBStore({
@@ -134,7 +134,7 @@ For local development, you can use [DynamoDB Local](https://docs.aws.amazon.com/
 
 The IAM role or user executing the code needs appropriate permissions to interact with the specified DynamoDB table and its indexes. Below is a sample policy. Replace `${YOUR_TABLE_NAME}` with your actual table name and `${YOUR_AWS_REGION}` and `${YOUR_AWS_ACCOUNT_ID}` with appropriate values.
 
-```json copy
+```json
 {
   "Version": "2012-10-17",
   "Statement": [

package/.docs/raw/reference/storage/lance.mdx

@@ -17,7 +17,7 @@ npm install @mastra/lance@beta
 
 ### Basic Storage Usage
 
-```typescript copy showLineNumbers
+```typescript
 import { LanceStorage } from "@mastra/lance";
 
 // Connect to a local database
@@ -77,7 +77,7 @@ The LanceStorage implementation automatically handles schema creation and update
 
 When you pass storage to the Mastra class, `init()` is called automatically before any storage operation:
 
-```typescript copy
+```typescript
 import { Mastra } from "@mastra/core";
 import { LanceStorage } from "@mastra/lance";
 
@@ -90,7 +90,7 @@ const mastra = new Mastra({
 
 If you're using storage directly without Mastra, you must call `init()` explicitly to create the tables:
 
-```typescript copy
+```typescript
 import { LanceStorage } from "@mastra/lance";
 
 const storage = await LanceStorage.create("my-storage", "/path/to/db");

package/.docs/raw/reference/storage/libsql.mdx

@@ -1,37 +1,81 @@
 ---
-title: "Reference: LibSQL Storage | Storage"
-description: Documentation for the LibSQL storage implementation in Mastra.
+title: "Reference: libSQL Storage | Storage"
+description: Documentation for the libSQL storage implementation in Mastra.
 ---
 
-# LibSQL Storage
+# libSQL Storage
 
-The LibSQL storage implementation provides a SQLite-compatible storage solution that can run both in-memory and as a persistent database.
+[libSQL](https://docs.turso.tech/libsql) is an open-source, SQLite-compatible database that supports both local and remote deployments. It can be used to store message history, workflow snapshots, traces, and eval scores.
+
+For vectors like semantic recall or traditional RAG, use [libSQL Vector](/reference/v1/vectors/libsql) which covers embeddings and vector search.
 
 ## Installation
 
-```bash copy
+Storage providers must be installed as separate packages:
+
+```bash
 npm install @mastra/libsql@beta
 ```
 
 ## Usage
 
-```typescript copy showLineNumbers
+```typescript
 import { LibSQLStore } from "@mastra/libsql";
+import { Mastra } from "@mastra/core";
 
-// File database (development)
-const storage = new LibSQLStore({
-  id: 'libsql-storage',
-  url: "file:./storage.db",
+const mastra = new Mastra({
+  storage: new LibSQLStore({
+    id: 'libsql-storage',
+    url: "file:./storage.db",
+  }),
 });
+```
 
-// Persistent database (production)
-const storage = new LibSQLStore({
-  id: 'libsql-storage',
-  url: process.env.DATABASE_URL,
+Agent-level file storage:
+
+```typescript
+import { Memory } from "@mastra/memory";
+import { Agent } from "@mastra/core/agent";
+import { LibSQLStore } from "@mastra/libsql";
+
+export const agent = new Agent({
+  id: "example-agent",
+  memory: new Memory({
+    storage: new LibSQLStore({
+      id: 'libsql-storage',
+      url: "file:./agent.db",
+    }),
+  }),
 });
 ```
 
-## Parameters
+:::warning
+File storage doesn't work with serverless platforms that have ephemeral file systems. For serverless deployments, use [Turso](https://turso.tech) or a different database engine.
+:::
+
+Production with remote database:
+
+```typescript 
+storage: new LibSQLStore({
+  id: 'libsql-storage',
+  url: "libsql://your-db-name.aws-ap-northeast-1.turso.io",
+  authToken: process.env.TURSO_AUTH_TOKEN,
+})
+```
+
+For local development and testing, you can store data in memory:
+
+```typescript 
+storage: new LibSQLStore({
+  id: 'libsql-storage',
+  url: ":memory:",
+})
+```
+:::warning
+In-memory storage resets when the process changes. Only suitable for development.
+:::
+
+## Options
 
 <PropertiesTable
   content={[
@@ -39,75 +83,46 @@ const storage = new LibSQLStore({
       name: "url",
       type: "string",
       description:
-        "Database URL. Use ':memory:' for in-memory database, 'file:filename.db' for a file database, or any LibSQL-compatible connection string for persistent storage.",
+        "Database URL. Use `:memory:` for in-memory database, `file:filename.db` for a file database, or a libSQL connection string (e.g., `libsql://your-database.turso.io`) for remote storage.",
       isOptional: false,
     },
     {
       name: "authToken",
       type: "string",
-      description: "Authentication token for remote LibSQL databases.",
+      description: "Authentication token for remote libSQL databases.",
       isOptional: true,
     },
   ]}
 />
 
-## Additional Notes
-
-### In-Memory vs Persistent Storage
-
-The file configuration (`file:storage.db`) is useful for:
-
-- Development and testing
-- Temporary storage
-- Quick prototyping
-
-For production use cases, use a persistent database URL: `libsql://your-database.turso.io`
+## Initialization
 
-### Schema Management
+When you pass storage to the Mastra class, `init()` is called automatically to create the [core schema](/reference/v1/storage/overview#core-schema):
 
-The storage implementation handles schema creation and updates automatically. It creates the following tables:
-
-- `mastra_workflow_snapshot`: Stores workflow state and execution data
-- `mastra_evals`: Stores evaluation results and metadata
-- `mastra_threads`: Stores conversation threads
-- `mastra_messages`: Stores individual messages
-- `mastra_traces`: Stores telemetry and tracing data
-- `mastra_scorers`: Stores scoring and evaluation data
-- `mastra_resources`: Stores resource working memory data
-
-### Initialization
-
-When you pass storage to the Mastra class, `init()` is called automatically before any storage operation:
-
-```typescript copy
+```typescript 
 import { Mastra } from "@mastra/core";
 import { LibSQLStore } from "@mastra/libsql";
 
 const storage = new LibSQLStore({
+  id: 'libsql-storage',
   url: "file:./storage.db",
 });
 
 const mastra = new Mastra({
-  storage, // init() is called automatically
+  storage, // init() called automatically
 });
 ```
 
-If you're using storage directly without Mastra, you must call `init()` explicitly to create the tables:
+If using storage directly without Mastra, call `init()` explicitly:
 
-```typescript copy
+```typescript 
 import { LibSQLStore } from "@mastra/libsql";
 
 const storage = new LibSQLStore({
+  id: 'libsql-storage',
   url: "file:./storage.db",
 });
 
-// Required when using storage directly
 await storage.init();
-
-// Now you can use the storage
 await storage.getThread({ threadId: "..." });
 ```
-
-:::warning
-If `init()` is not called, tables won't be created and storage operations will fail silently or throw errors.
-:::