@mastra/mcp-docs-server 0.0.0-error-handler-fix-20251020202607 → 0.0.0-execa-dynamic-import-20260304221256

package/.docs/raw/reference/core/mastra-class.mdx

@@ -1,143 +0,0 @@
----
-title: "Reference: Mastra Class | Core | Mastra Docs"
-description: "Documentation for the `Mastra` class in Mastra, the core entry point for managing agents, workflows, MCP servers, and server endpoints."
----
-
-# Mastra Class
-
-The `Mastra` class is the central orchestrator in any Mastra application, managing agents, workflows, storage, logging, telemetry, and more. Typically, you create a single instance of `Mastra` to coordinate your application.
-
-Think of `Mastra` as a top-level registry:
-
-- Registering **integrations** makes them accessible to **agents**, **workflows**, and **tools** alike.
-- **tools** aren’t registered on `Mastra` directly but are associated with agents and discovered automatically.
-
-
-## Usage example
-
-```typescript filename="src/mastra/index.ts"
-import { Mastra } from '@mastra/core/mastra';
-import { PinoLogger } from '@mastra/loggers';
-import { LibSQLStore } from '@mastra/libsql';
-import { weatherWorkflow } from './workflows/weather-workflow';
-import { weatherAgent } from './agents/weather-agent';
-
-export const mastra = new Mastra({
-  workflows: { weatherWorkflow },
-  agents: { weatherAgent },
-  storage: new LibSQLStore({
-    url: ":memory:",
-  }),
-  logger: new PinoLogger({
-    name: 'Mastra',
-    level: 'info',
-  }),
-});
-```
-
-## Constructor parameters
-
-<PropertiesTable
-  content={[
-    {
-      name: "agents",
-      type: "Agent[]",
-      description: "Array of Agent instances to register",
-      isOptional: true,
-      defaultValue: "[]",
-    },
-    {
-      name: "tools",
-      type: "Record<string, ToolApi>",
-      description:
-        "Custom tools to register. Structured as a key-value pair, with keys being the tool name and values being the tool function.",
-      isOptional: true,
-      defaultValue: "{}",
-    },
-    {
-      name: "storage",
-      type: "MastraStorage",
-      description: "Storage engine instance for persisting data",
-      isOptional: true,
-    },
-    {
-      name: "vectors",
-      type: "Record<string, MastraVector>",
-      description:
-        "Vector store instance, used for semantic search and vector-based tools (eg Pinecone, PgVector or Qdrant)",
-      isOptional: true,
-    },
-    {
-      name: "logger",
-      type: "Logger",
-      description: "Logger instance created with new PinoLogger()",
-      isOptional: true,
-      defaultValue: "Console logger with INFO level",
-    },
-    {
-      name: "idGenerator",
-      type: "() => string",
-      description: "Custom ID generator function. Used by agents, workflows, memory, and other components to generate unique identifiers.",
-      isOptional: true,
-    },
-    {
-      name: "workflows",
-      type: "Record<string, Workflow>",
-      description:
-        "Workflows to register. Structured as a key-value pair, with keys being the workflow name and values being the workflow instance.",
-      isOptional: true,
-      defaultValue: "{}",
-    },
-    {
-      name: "tts",
-      type: "Record<string, MastraTTS>",
-      isOptional: true,
-      description: "An object for registering Text-To-Speech services.",
-    },
-    {
-      name: "telemetry",
-      type: "OtelConfig",
-      isOptional: true,
-      description: "Configuration for OpenTelemetry integration.",
-    },
-    {
-      name: "deployer",
-      type: "MastraDeployer",
-      isOptional: true,
-      description: "An instance of a MastraDeployer for managing deployments.",
-    },
-    {
-      name: "server",
-      type: "ServerConfig",
-      description:
-        "Server configuration including port, host, timeout, API routes, middleware, CORS settings, and build options for Swagger UI, API request logging, and OpenAPI docs.",
-      isOptional: true,
-      defaultValue:
-        "{ port: 4111, host: localhost,  cors: { origin: '*', allowMethods: ['GET', 'POST', 'PUT', 'PATCH', 'DELETE', 'OPTIONS'], allowHeaders: ['Content-Type', 'Authorization', 'x-mastra-client-type'], exposeHeaders: ['Content-Length', 'X-Requested-With'], credentials: false } }",
-    },
-    {
-      name: "mcpServers",
-      type: "Record<string, MCPServerBase>",
-      isOptional: true,
-      description:
-        "An object where keys are unique server identifiers and values are instances of MCPServer or classes extending MCPServerBase. This allows Mastra to be aware of and potentially manage these MCP servers.",
-    },
-    {
-      name: "bundler",
-      type: "BundlerConfig",
-      description: "Configuration for the asset bundler with options for externals, sourcemap, and transpilePackages.",
-      isOptional: true,
-      defaultValue: "{ externals: [], sourcemap: false, transpilePackages: [] }",
-    },
-    {
-      name: "scorers",
-      type: "Record<string, MastraScorer>",
-        description: "Scorers to register for scoring traces and overriding default scorers used during agent generation or workflow execution. Structured as a key-value pair, with keys being the scorer name and values being the scorer instance.",
-      isOptional: true,
-      defaultValue: "{}",
-    },
-  ]}
-/>
-
-
-

package/.docs/raw/reference/core/setLogger.mdx

@@ -1,47 +0,0 @@
----
-title: "Reference: Mastra.setLogger() | Core | Mastra Docs"
-description: "Documentation for the `Mastra.setLogger()` method in Mastra, which sets the logger for all components (agents, workflows, etc.)."
----
-
-# Mastra.setLogger()
-
-The `.setLogger()` method is used to set the logger for all components (agents, workflows, etc.) in the Mastra instance. This method accepts a single object parameter with a logger property.
-
-## Usage example
-
-```typescript copy
-mastra.setLogger({ logger: new PinoLogger({ name: "testLogger" }) });
-```
-
-## Parameters
-
-<PropertiesTable
-  content={[
-    {
-      name: "options",
-      type: "{ logger: TLogger }",
-      description: "An object containing the logger instance to set for all components.",
-    },
-  ]}
-/>
-
-### Options
-
-<PropertiesTable
-  content={[
-    {
-      name: "logger",
-      type: "TLogger",
-      description: "The logger instance to set for all components (agents, workflows, etc.).",
-    },
-  ]}
-/>
-
-## Returns
-
-This method does not return a value.
-
-## Related
-
-- [Logging overview](../../docs/observability/logging.mdx)
-- [Logger reference](../../reference/observability/logger.mdx)

package/.docs/raw/reference/core/setStorage.mdx

@@ -1,39 +0,0 @@
----
-title: "Reference: Mastra.setStorage() | Core | Mastra Docs"
-description: "Documentation for the `Mastra.setStorage()` method in Mastra, which sets the storage instance for the Mastra instance."
----
-
-# Mastra.setStorage()
-
-The `.setStorage()` method is used to set the storage instance for the Mastra instance. This method accepts a single `MastraStorage` parameter.
-
-## Usage example
-
-```typescript copy
-mastra.setStorage(
-  new LibSQLStore({
-    url: ":memory:"
-  })
-);
-```
-
-## Parameters
-
-<PropertiesTable
-  content={[
-    {
-      name: "storage",
-      type: "MastraStorage",
-      description: "The storage instance to set for the Mastra instance.",
-    },
-  ]}
-/>
-
-## Returns
-
-This method does not return a value.
-
-## Related
-
-- [Storage overview](../../docs/server-db/storage.mdx)
-- [Storage reference](../../reference/storage/libsql.mdx)

package/.docs/raw/reference/core/setTelemetry.mdx

@@ -1,35 +0,0 @@
----
-title: "Reference: Mastra.setTelemetry() | Core | Mastra Docs"
-description: "Documentation for the `Mastra.setTelemetry()` method in Mastra, which sets the telemetry configuration for all components."
----
-
-# Mastra.setTelemetry()
-
-The `.setTelemetry()` method is used to set the telemetry configuration for all components in the Mastra instance. This method accepts a single telemetry configuration object.
-
-## Usage example
-
-```typescript copy
-mastra.setTelemetry({ export: { type: "console" } });
-```
-
-## Parameters
-
-<PropertiesTable
-  content={[
-    {
-      name: "telemetry",
-      type: "OtelConfig",
-      description: "The telemetry configuration object to set for all components.",
-    },
-  ]}
-/>
-
-## Returns
-
-This method does not return a value.
-
-## Related
-
-- [Logging](../../docs/observability/logging.mdx)
-- [PinoLogger](../../reference/observability/logger.mdx)

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

@@ -1,91 +0,0 @@
----
-title: "Cloudflare Deployer"
-description: "Documentation for the CloudflareDeployer class, which deploys Mastra applications to Cloudflare Workers."
----
-
-# CloudflareDeployer
-
-The `CloudflareDeployer` class handles deployment of standalone Mastra applications to Cloudflare Workers. It manages configuration, deployment, and extends the base [Deployer](/reference/deployer/deployer) class with Cloudflare specific functionality.
-
-## Usage example
-
-```typescript filename="src/mastra/index.ts" showLineNumbers copy
-import { Mastra } from "@mastra/core/mastra";
-import { CloudflareDeployer } from "@mastra/deployer-cloudflare";
-
-export const mastra = new Mastra({
-  // ...
-  deployer: new CloudflareDeployer({
-    projectName: "hello-mastra",
-    routes: [
-      {
-        pattern: "example.com/*",
-        zone_name: "example.com",
-        custom_domain: true
-      }
-    ],
-    workerNamespace: "my-namespace",
-    env: {
-      NODE_ENV: "production",
-      API_KEY: "<api-key>"
-    },
-    d1Databases: [
-      {
-        binding: "DB",
-        database_name: "my-database",
-        database_id: "d1-database-id",
-        preview_database_id: "your-preview-database-id"
-      }
-    ],
-    kvNamespaces: [
-      {
-        binding: "CACHE",
-        id: "kv-namespace-id"
-      }
-    ]
-});
-```
-
-## Parameters
-
-<PropertiesTable
-  content={[
-    {
-      name: "projectName",
-      type: "string",
-      description: "Name of your worker project.",
-      isOptional: true,
-      defaultValue: "'mastra'",
-    },
-    {
-      name: "routes",
-      type: "CFRoute[]",
-      description: "Array of route configurations for your worker. Each route requires: pattern (string), zone_name (string), custom_domain (boolean, optional).",
-      isOptional: true,
-    },
-    {
-      name: "workerNamespace",
-      type: "string",
-      description: "Namespace for your worker.",
-      isOptional: true,
-    },
-    {
-      name: "env",
-      type: "Record<string, any>",
-      description: "Environment variables to be included in the worker configuration.",
-      isOptional: true,
-    },
-    {
-      name: "d1Databases",
-      type: "D1DatabaseBinding[]",
-      description: "Array of D1 database bindings. Each binding requires: binding (string), database_name (string), database_id (string), preview_database_id (string, optional).",
-      isOptional: true,
-    },
-    {
-      name: "kvNamespaces",
-      type: "KVNamespaceBinding[]",
-      description: "Array of KV namespace bindings. Each binding requires: binding (string), id (string).",
-      isOptional: true,
-    },
-  ]}
-/>

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

@@ -1,165 +0,0 @@
----
-title: "Mastra Deployer"
-description: Documentation for the Deployer abstract class, which handles packaging and deployment of Mastra applications.
----
-
-# Deployer
-
-The Deployer handles the deployment of standalone Mastra applications by packaging code, managing environment files, and serving applications using the Hono framework. Concrete implementations must define the deploy method for specific deployment targets.
-
-## Usage Example
-
-```typescript
-import { Deployer } from "@mastra/deployer";
-
-// Create a custom deployer by extending the abstract Deployer class
-class CustomDeployer extends Deployer {
-  constructor() {
-    super({ name: "custom-deployer" });
-  }
-
-  // Implement the abstract deploy method
-  async deploy(outputDirectory: string): Promise<void> {
-    // Prepare the output directory
-    await this.prepare(outputDirectory);
-
-    // Bundle the application
-    await this._bundle("server.ts", "mastra.ts", outputDirectory);
-
-    // Custom deployment logic
-    // ...
-  }
-}
-```
-
-## Parameters
-
-### Constructor Parameters
-
-<PropertiesTable
-  content={[
-    {
-      name: "args",
-      type: "object",
-      description: "Configuration options for the Deployer.",
-      isOptional: false,
-    },
-    {
-      name: "args.name",
-      type: "string",
-      description: "A unique name for the deployer instance.",
-      isOptional: false,
-    },
-  ]}
-/>
-
-### deploy Parameters
-
-<PropertiesTable
-  content={[
-    {
-      name: "outputDirectory",
-      type: "string",
-      description:
-        "The directory where the bundled and deployment-ready application will be output.",
-      isOptional: false,
-    },
-  ]}
-/>
-
-## Methods
-
-<PropertiesTable
-  content={[
-    {
-      name: "getEnvFiles",
-      type: "() => Promise<string[]>",
-      description:
-        "Returns a list of environment files to be used during deployment. By default, it looks for '.env.production' and '.env' files.",
-    },
-    {
-      name: "deploy",
-      type: "(outputDirectory: string) => Promise<void>",
-      description:
-        "Abstract method that must be implemented by subclasses. Handles the deployment process to the specified output directory.",
-    },
-  ]}
-/>
-
-## Inherited Methods from Bundler
-
-The Deployer class inherits the following key methods from the Bundler class:
-
-<PropertiesTable
-  content={[
-    {
-      name: "prepare",
-      type: "(outputDirectory: string) => Promise<void>",
-      description:
-        "Prepares the output directory by cleaning it and creating necessary subdirectories.",
-    },
-    {
-      name: "writeInstrumentationFile",
-      type: "(outputDirectory: string) => Promise<void>",
-      description:
-        "Writes an instrumentation file to the output directory for telemetry purposes.",
-    },
-    {
-      name: "writePackageJson",
-      type: "(outputDirectory: string, dependencies: Map<string, string>) => Promise<void>",
-      description:
-        "Generates a package.json file in the output directory with the specified dependencies.",
-    },
-    {
-      name: "_bundle",
-      type: "(serverFile: string, mastraEntryFile: string, outputDirectory: string, bundleLocation?: string) => Promise<void>",
-      description:
-        "Bundles the application using the specified server and Mastra entry files.",
-    },
-  ]}
-/>
-
-## Core Concepts
-
-### Deployment Lifecycle
-
-The Deployer abstract class implements a structured deployment lifecycle:
-
-1. **Initialization**: The deployer is initialized with a name and creates a Deps instance for dependency management.
-2. **Environment Setup**: The `getEnvFiles` method identifies environment files (.env.production, .env) to be used during deployment.
-3. **Preparation**: The `prepare` method (inherited from Bundler) cleans the output directory and creates necessary subdirectories.
-4. **Bundling**: The `_bundle` method (inherited from Bundler) packages the application code and its dependencies.
-5. **Deployment**: The abstract `deploy` method is implemented by subclasses to handle the actual deployment process.
-
-### Environment File Management
-
-The Deployer class includes built-in support for environment file management through the `getEnvFiles` method. This method:
-
-- Looks for environment files in a predefined order (.env.production, .env)
-- Uses the FileService to find the first existing file
-- Returns an array of found environment files
-- Returns an empty array if no environment files are found
-
-```typescript
-getEnvFiles(): Promise<string[]> {
-  const possibleFiles = ['.env.production', '.env.local', '.env'];
-
-  try {
-    const fileService = new FileService();
-    const envFile = fileService.getFirstExistingFile(possibleFiles);
-
-    return Promise.resolve([envFile]);
-  } catch {}
-
-  return Promise.resolve([]);
-}
-```
-
-### Bundling and Deployment Relationship
-
-The Deployer class extends the Bundler class, establishing a clear relationship between bundling and deployment:
-
-1. **Bundling as a Prerequisite**: Bundling is a prerequisite step for deployment, where the application code is packaged into a deployable format.
-2. **Shared Infrastructure**: Both bundling and deployment share common infrastructure like dependency management and file system operations.
-3. **Specialized Deployment Logic**: While bundling focuses on code packaging, deployment adds environment-specific logic for deploying the bundled code.
-4. **Extensibility**: The abstract `deploy` method allows for creating specialized deployers for different target environments.

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

@@ -1,20 +0,0 @@
----
-title: "Netlify Deployer"
-description: "Documentation for the NetlifyDeployer class, which deploys Mastra applications to Netlify Functions."
----
-
-# NetlifyDeployer
-
-The `NetlifyDeployer` class handles deployment of standalone Mastra applications to Netlify. It manages configuration, deployment, and extends the base [Deployer](/reference/deployer/deployer) class with Netlify specific functionality.
-
-## Usage example
-
-```typescript filename="src/mastra/index.ts" showLineNumbers copy
-import { Mastra } from "@mastra/core/mastra";
-import { NetlifyDeployer } from "@mastra/deployer-netlify";
-
-export const mastra = new Mastra({
-  // ...
-  deployer: new NetlifyDeployer()
-});
-```

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

@@ -1,46 +0,0 @@
----
-title: "Vercel Deployer"
-description: "Documentation for the VercelDeployer class, which deploys Mastra applications to Vercel."
----
-
-# VercelDeployer
-
-The `VercelDeployer` class handles deployment of standalone Mastra applications to Vercel. It manages configuration, deployment, and extends the base [Deployer](/reference/deployer/deployer) class with Vercel specific functionality.
-
-## Usage example
-
-```typescript filename="src/mastra/index.ts" showLineNumbers copy
-import { Mastra } from "@mastra/core/mastra";
-import { VercelDeployer } from "@mastra/deployer-vercel";
-
-export const mastra = new Mastra({
-  // ...
-  deployer: new VercelDeployer()
-});
-```
-
-## Constructor options
-
-The deployer supports a small set of high‑value overrides that are written to the Vercel Output API function config (`.vc-config.json`):
-
-- `maxDuration?: number` — Function execution timeout (in seconds)
-- `memory?: number` — Function memory (in MB)
-- `regions?: string[]` — Regions to deploy the function (e.g. `['sfo1','iad1']`)
-
-These options are merged into `.vercel/output/functions/index.func/.vc-config.json` while preserving default fields (`handler`, `launcherType`, `runtime`, `shouldAddHelpers`).
-
-### Example with overrides
-
-```typescript filename="src/mastra/index.ts" showLineNumbers copy
-import { Mastra } from "@mastra/core/mastra";
-import { VercelDeployer } from "@mastra/deployer-vercel";
-
-export const mastra = new Mastra({
-  // ...
-  deployer: new VercelDeployer({
-    maxDuration: 600,
-    memory: 1536,
-    regions: ["sfo1", "iad1"],
-  }),
-});
-```