@mastra/mcp-docs-server 0.0.0-error-handler-fix-20251020202607 → 0.0.0-esbuild-bundle-worker-20260807182016

package/.docs/raw/reference/auth/supabase.mdx

@@ -1,62 +0,0 @@
----
-title: "MastraAuthSupabase Class"
-description: "API reference for the MastraAuthSupabase class, which authenticates Mastra applications using Supabase Auth."
----
-
-# MastraAuthSupabase Class
-
-The `MastraAuthSupabase` class provides authentication for Mastra using Supabase Auth. It verifies incoming requests using Supabase's authentication system and integrates with the Mastra server using the `experimental_auth` option.
-
-## Usage example
-
-```typescript filename="src/mastra/index.ts" showLineNumbers copy
-import { Mastra } from "@mastra/core/mastra";
-import { MastraAuthSupabase } from '@mastra/auth-supabase';
-
-export const mastra = new Mastra({
-  // ..
-  server: {
-    experimental_auth: new MastraAuthSupabase({
-      url: process.env.SUPABASE_URL,
-      anonKey: process.env.SUPABASE_ANON_KEY
-    }),
-  },
-});
-```
-
-## Constructor parameters
-
-<PropertiesTable
-  content={[
-    {
-      name: "url",
-      type: "string",
-      description: "The URL of your Supabase project. Can be found in your Supabase project settings.",
-      isOptional: true,
-      defaultValue: "process.env.SUPABASE_URL"
-    },
-    {
-      name: "anonKey",
-      type: "string",
-      description: "The anonymous/public key for your Supabase project. Used for client-side authentication.",
-      isOptional: true,
-      defaultValue: "process.env.SUPABASE_ANON_KEY"
-    },
-    {
-      name: "name",
-      type: "string",
-      description: "Custom name for the auth provider instance.",
-      isOptional: true,
-    },
-    {
-      name: "authorizeUser",
-      type: "(user: User, request: HoneRequest) => Promise<boolean> | boolean",
-      description: "Custom authorization function to determine if a user should be granted access. Called after token verification. By default, checks the 'isAdmin' column in the 'users' table.",
-      isOptional: true,
-    },
-  ]}
-/>
-
-## Related
-
-[MastraAuthSupabase](/docs/auth/supabase.mdx)

package/.docs/raw/reference/auth/workos.mdx

@@ -1,128 +0,0 @@
----
-title: "MastraAuthWorkos Class"
-description: "API reference for the MastraAuthWorkos class, which authenticates Mastra applications using WorkOS authentication."
----
-
-# MastraAuthWorkos Class
-
-The `MastraAuthWorkos` class provides authentication for Mastra using WorkOS. It verifies incoming requests using WorkOS access tokens and integrates with the Mastra server using the `experimental_auth` option.
-
-## Usage example
-
-```typescript filename="src/mastra/index.ts" showLineNumbers copy
-import { Mastra } from "@mastra/core/mastra";
-import { MastraAuthWorkos } from '@mastra/auth-workos';
-
-export const mastra = new Mastra({
-  // ..
-  server: {
-    experimental_auth: new MastraAuthWorkos({
-      apiKey: process.env.WORKOS_API_KEY,
-      clientId: process.env.WORKOS_CLIENT_ID
-    }),
-  },
-});
-```
-
-> **Note:** You can omit the constructor parameters if you have the appropriately named environment variables (`WORKOS_API_KEY` and `WORKOS_CLIENT_ID`) set. In that case, simply use `new MastraAuthWorkos()` without any arguments.
-
-## Constructor parameters
-
-<PropertiesTable
-  content={[
-    {
-      name: "apiKey",
-      type: "string",
-      description: "Your WorkOS API key. This is used to authenticate with the WorkOS API for user verification and organization management.",
-      isOptional: true,
-      defaultValue: "process.env.WORKOS_API_KEY"
-    },
-    {
-      name: "clientId",
-      type: "string",
-      description: "Your WorkOS Client ID. This identifies your application when exchanging authorization codes for access tokens.",
-      isOptional: true,
-      defaultValue: "process.env.WORKOS_CLIENT_ID"
-    },
-    {
-      name: "name",
-      type: "string",
-      description: "Custom name for the auth provider instance.",
-      isOptional: true,
-      defaultValue: '"workos"'
-    },
-    {
-      name: "authorizeUser",
-      type: "(user: WorkosUser) => Promise<boolean> | boolean",
-      description: "Custom authorization function to determine if a user should be granted access. Called after token verification. By default, checks if the user has an 'admin' role in any organization membership.",
-      isOptional: true,
-    },
-  ]}
-/>
-
-## Environment Variables
-
-The following environment variables are automatically used when constructor options are not provided:
-
-<PropertiesTable
-  content={[
-    {
-      name: "WORKOS_API_KEY",
-      type: "string",
-      description: "Your WorkOS API key. Can be found in your WorkOS Dashboard under API Keys.",
-      isOptional: true,
-    },
-    {
-      name: "WORKOS_CLIENT_ID",
-      type: "string",
-      description: "Your WorkOS Client ID. Can be found in your WorkOS Dashboard under Applications.",
-      isOptional: true,
-    },
-  ]}
-/>
-
-## Default Authorization Behavior
-
-By default, `MastraAuthWorkos` implements role-based authorization that checks for admin access:
-
-1. **Token Verification**: The access token is verified with WorkOS to ensure it's valid and not expired
-2. **User Retrieval**: User information is extracted from the verified token
-3. **Organization Membership Check**: The system queries WorkOS for all organization memberships associated with the user's ID
-4. **Role Extraction**: All roles from the user's organization memberships are collected
-5. **Admin Check**: The system checks if any role has the slug 'admin'
-6. **Authorization Decision**: Access is granted only if the user has an admin role in at least one organization
-
-This means that by default, only users with admin privileges in at least one organization will be authorized to access your Mastra endpoints.
-
-To implement custom authorization logic (e.g., allow all authenticated users, check for specific roles, or implement custom business logic), provide a custom `authorizeUser` function.
-
-## WorkOS User Type
-
-The `WorkosUser` type used in the `authorizeUser` function corresponds to the JWT token payload returned by WorkOS. WorkOS allows administrators to set up custom JWT templates, so the exact structure may vary based on your configuration. Here's an example of what the user object might look like:
-
-```javascript
-{
-  'urn:myapp:full_name': 'John Doe',
-  'urn:myapp:email': 'john.doe@example.com',
-  'urn:myapp:organization_tier': 'bronze',
-  'urn:myapp:user_language': 'en',
-  'urn:myapp:organization_domain': 'example.com',
-  iss: 'https://api.workos.com/user_management/client_01ABC123DEF456GHI789JKL012',
-  sub: 'user_01XYZ789ABC123DEF456GHI012',
-  sid: 'session_01PQR456STU789VWX012YZA345',
-  jti: '01MNO678PQR901STU234VWX567',
-  org_id: 'org_01DEF234GHI567JKL890MNO123',
-  role: 'member',
-  roles: [ 'member' ],
-  permissions: [],
-  exp: 1758290589,
-  iat: 1758290289
-}
-```
-
-The properties with `urn:myapp:` prefixes are custom claims configured in your WorkOS JWT template. Standard JWT claims include `sub` (user ID), `iss` (issuer), `exp` (expiration), and WorkOS-specific claims like `org_id`, `role`, and `roles`.
-
-## Related
-
-[MastraAuthWorkos Class](/docs/auth/workos)
-

package/.docs/raw/reference/cli/create-mastra.mdx

@@ -1,177 +0,0 @@
----
-title: "Reference: create-mastra | CLI"
-description: Documentation for the create-mastra command, which creates a new Mastra project with interactive setup options.
----
-
-import { Tabs, Tab } from "@/components/tabs";
-
-# create-mastra
-
-The `create-mastra` command **creates** a new standalone Mastra project. Use this command to scaffold a complete Mastra setup in a dedicated directory. You can run it with additional flags to customize the setup process.
-
-## Usage
-
-<Tabs items={["npm", "yarn", "pnpm", "bun"]}>
-  <Tab>
-    ```bash copy
-    npx create-mastra@latest
-    ```
-  </Tab>
-  <Tab>
-    ```bash copy
-    yarn dlx create-mastra@latest
-    ```
-  </Tab>
-  <Tab>
-    ```bash copy
-    pnpm create mastra@latest
-    ```
-  </Tab>
-  <Tab>
-    ```bash copy
-    bun create mastra@latest
-    ```
-  </Tab>
-</Tabs>
-
-`create-mastra` automatically runs in _interactive_ mode, but you can also specify your project name and template with command line arguments.
-
-<Tabs items={["npm", "yarn", "pnpm", "bun"]}>
-  <Tab>
-    ```bash copy
-    npx create-mastra@latest my-mastra-project -- --template coding-agent
-    ```
-  </Tab>
-  <Tab>
-    ```bash copy
-    yarn dlx create-mastra@latest --template coding-agent
-    ```
-  </Tab>
-  <Tab>
-    ```bash copy
-    pnpm create mastra@latest --template coding-agent
-    ```
-  </Tab>
-  <Tab>
-    ```bash copy
-    bun create mastra@latest --template coding-agent
-    ```
-  </Tab>
-</Tabs>
-
-Check out the [full list](https://mastra.ai/api/templates.json) of templates and use the `slug` as input to the `--template` CLI flag.
-
-You can also use any GitHub repo as a template (it has to be a valid Mastra project):
-
-```bash
-npx create-mastra@latest my-mastra-project -- --template mastra-ai/template-coding-agent
-```
-
-## CLI flags
-
-Instead of an interactive prompt you can also define these CLI flags.
-
-<PropertiesTable
-  content={[
-    {
-      name: "--version",
-      type: "boolean",
-      description: "Output the version number",
-      isOptional: true,
-    },
-    {
-      name: "--project-name",
-      type: "string",
-      description:
-        "Project name that will be used in package.json and as the project directory name",
-      isOptional: true,
-    },
-    {
-      name: "--default",
-      type: "boolean",
-      description: "Quick start with defaults (src, OpenAI, no examples)",
-      isOptional: true,
-    },
-    {
-      name: "--components",
-      type: "string",
-      description:
-        "Comma-separated list of components (agents, tools, workflows)",
-      isOptional: true,
-    },
-    {
-      name: "--llm",
-      type: "string",
-      description:
-        "Default model provider (openai, anthropic, groq, google, or cerebras)",
-      isOptional: true,
-    },
-    {
-      name: "--llm-api-key",
-      type: "string",
-      description: "API key for the model provider",
-      isOptional: true,
-    },
-    {
-      name: "--example",
-      type: "boolean",
-      description: "Include example code",
-      isOptional: true,
-    },
-    {
-      name: "--no-example",
-      type: "boolean",
-      description: "Do not include example code",
-      isOptional: true,
-    },
-    {
-      name: "--template",
-      type: "string",
-      description:
-        "Create project from a template (use template name, public GitHub URL, or leave blank to select from list)",
-      isOptional: true,
-    },
-    {
-      name: "--timeout",
-      type: "number",
-      description:
-        "Configurable timeout for package installation, defaults to 60000 ms",
-      isOptional: true,
-    },
-    {
-      name: "--dir",
-      type: "string",
-      description: "Target directory for Mastra source code (default: src/)",
-      isOptional: true,
-    },
-    {
-      name: "--mcp",
-      type: "string",
-      description:
-        "MCP Server for code editor (cursor, cursor-global, windsurf, vscode)",
-      isOptional: true,
-    },
-    {
-      name: "--help",
-      type: "boolean",
-      description: "Display help for command",
-      isOptional: true,
-    },
-  ]}
-/>
-
-## Telemetry
-
-By default, Mastra collects anonymous information about your project like your OS, Mastra version or Node.js version. You can read the [source code](https://github.com/mastra-ai/mastra/blob/main/packages/cli/src/analytics/index.ts) to check what's collected.
-
-You can opt out of the CLI analytics by setting an environment variable:
-
-```bash copy
-MASTRA_TELEMETRY_DISABLED=1
-```
-
-You can also set this while using other `mastra` commands:
-
-```bash copy
-MASTRA_TELEMETRY_DISABLED=1 npx create-mastra@latest
-```

package/.docs/raw/reference/cli/mastra.mdx

@@ -1,258 +0,0 @@
----
-title: "Reference: CLI Commands"
-description: Documentation for the Mastra CLI to develop, build, and start your project.
----
-
-import { Callout } from "nextra/components";
-
-# CLI Commands
-
-You can use the Command-Line Interface (CLI) provided by Mastra to develop, build, and start your Mastra project.
-
-## `mastra dev`
-
-Starts a server which exposes a [local dev playground](/docs/server-db/local-dev-playground) and REST endpoints for your agents, tools, and workflows. You can visit [http://localhost:4111/swagger-ui](http://localhost:4111/swagger-ui) for an overview of all available endpoints once `mastra dev` is running.
-
-You can also [configure the server](/docs/server-db/local-dev-playground#configuration).
-
-### Flags
-
-The command accepts [common flags][common-flags] and the following additional flags:
-
-#### `--https`
-
-Enable local HTTPS support. [Learn more](/docs/server-db/local-dev-playground#local-https).
-
-#### `--inspect`
-
-Start the development server in inspect mode, helpful for debugging. This can't be used together with `--inspect-brk`.
-
-#### `--inspect-brk`
-
-Start the development server in inspect mode and break at the beginning of the script. This can't be used together with `--inspect`.
-
-#### `--custom-args`
-
-Comma-separated list of custom arguments to pass to the development server. You can pass arguments to the Node.js process, e.g. `--experimental-transform-types`.
-
-### Configs
-
-You can set certain environment variables to modify the behavior of `mastra dev`.
-
-#### Disable build caching
-
-Set `MASTRA_DEV_NO_CACHE=1` to force a full rebuild rather than using the cached assets under `.mastra/`:
-
-```bash copy
-MASTRA_DEV_NO_CACHE=1 mastra dev
-```
-
-This helps when you are debugging bundler plugins or suspect stale output.
-
-#### Limit parallelism
-
-`MASTRA_CONCURRENCY` caps how many expensive operations run in parallel (primarily build and evaluation steps). For example:
-
-```bash copy
-MASTRA_CONCURRENCY=4 mastra dev
-```
-
-Leave it unset to let the CLI pick a sensible default for the machine.
-
-#### Custom provider endpoints
-
-When using providers supported by the Vercel AI SDK you can redirect requests through proxies or internal gateways by setting a base URL. For OpenAI:
-
-```bash copy
-OPENAI_API_KEY=<your-api-key> \
-OPENAI_BASE_URL=https://openrouter.example/v1 \
-mastra dev
-```
-
-For Anthropic:
-
-```bash copy
-ANTHROPIC_API_KEY=<your-api-key> \
-ANTHROPIC_BASE_URL=https://anthropic.internal \
-mastra dev
-```
-
-These are forwarded by the AI SDK and work with any `openai()` or `anthropic()` calls.
-
-## `mastra build`
-
-The `mastra build` command bundles your Mastra project into a production-ready Hono server. [Hono](https://hono.dev/) is a lightweight, type-safe web framework that makes it easy to deploy Mastra agents as HTTP endpoints with middleware support.
-
-Under the hood Mastra's Rollup server locates your Mastra entry file and bundles it to a production-ready Hono server. During that bundling it tree-shakes your code and generates source maps for debugging.
-
-The output in `.mastra` can be deployed to any cloud server using [`mastra start`](#mastra-start).
-
-If you're deploying to a [serverless platform](/docs/deployment/serverless-platforms) you need to install the correct deployer in order to receive the correct output in `.mastra`.
-
-It accepts [common flags][common-flags].
-
-### Configs
-
-You can set certain environment variables to modify the behavior of `mastra build`.
-
-#### Limit parallelism
-
-For CI or when running in resource constrained environments you can cap how many expensive tasks run at once by setting `MASTRA_CONCURRENCY`.
-
-```bash copy
-MASTRA_CONCURRENCY=2 mastra build
-```
-
-## `mastra start`
-
-<Callout type="info">
-You need to run `mastra build` before using `mastra start`.
-</Callout>
-
-Starts a local server to serve your built Mastra application in production mode. By default, [OTEL Tracing](/docs/observability/otel-tracing) is enabled.
-
-### Flags
-
-The command accepts [common flags][common-flags] and the following additional flags:
-
-#### `--dir`
-
-The path to your built Mastra output directory. Defaults to `.mastra/output`.
-
-#### `--no-telemetry`
-
-Disable the [OTEL Tracing](/docs/observability/otel-tracing).
-
-## `mastra lint`
-
-The `mastra lint` command validates the structure and code of your Mastra project to ensure it follows best practices and is error-free.
-
-It accepts [common flags][common-flags].
-
-## `mastra scorers`
-
-The `mastra scorers` command provides management capabilities for evaluation scorers that measure the quality, accuracy, and performance of AI-generated outputs.
-
-Read the [Scorers overview](/docs/scorers/overview) to learn more.
-
-### `add`
-
-Add a new scorer to your project. You can use an interactive prompt:
-
-```bash copy
-mastra scorers add
-```
-
-Or provide a scorer name directly:
-
-```bash copy
-mastra scorers add answer-relevancy
-```
-
-Use the [`list`](#list) command to get the correct ID.
-
-### `list`
-
-List all available scorer templates. Use the ID for the `add` command.
-
-## `mastra init`
-
-The `mastra init` command initializes Mastra in an existing project. Use this command to scaffold the necessary folders and configuration without generating a new project from scratch.
-
-### Flags
-
-The command accepts the following additional flags:
-
-#### `--default`
-
-Creates files inside `src` using OpenAI. It also populates the `src/mastra` folders with example code.
-
-#### `--dir`
-
-The directory where Mastra files should be saved to. Defaults to `src`.
-
-#### `--components`
-
-Comma-separated list of components to add. For each component a new folder will be created. Defaults to `['agents', 'tools', 'workflows']`.
-
-#### `--llm`
-
-Default model provider. Choose from: `"openai" | "anthropic" | "groq" | "google" | "cerebras" | "mistral"`.
-
-#### `--llm-api-key`
-
-The API key for your chosen model provider. Will be written to an environment variables file (`.env`).
-
-#### `--example`
-
-If enabled, example code is written to the list of components (e.g. example agent code).
-
-#### `--no-example`
-
-Do not include example code. Useful when using the `--default` flag.
-
-#### `--mcp`
-
-Configure your code editor with Mastra's MCP server. Choose from: `"cursor" | "cursor-global" | "windsurf" | "vscode"`.
-
-## Common flags
-
-### `--dir`
-
-**Available in:** `dev`, `build`, `lint`
-
-The path to your Mastra folder. Defaults to `src/mastra`.
-
-### `--debug`
-
-**Available in:** `dev`, `build`
-
-Enable verbose logging for Mastra's internals. Defaults to `false`.
-
-### `--env`
-
-**Available in:** `dev`, `start`
-
-Custom environment variables file to include. By default, includes `.env.development`, `.env.local`, and `.env`.
-
-### `--root`
-
-**Available in:** `dev`, `build`, `lint`
-
-Path to your root folder. Defaults to `process.cwd()`.
-
-### `--tools`
-
-**Available in:** `dev`, `build`, `lint`
-
-Comma-separated list of tool paths to include. Defaults to `src/mastra/tools`.
-
-## Global flags
-
-Use these flags to get information about the `mastra` CLI.
-
-### `--version`
-
-Prints the Mastra CLI version and exits.
-
-### `--help`
-
-Prints help message and exits.
-
-## Telemetry
-
-By default, Mastra collects anonymous information about your project like your OS, Mastra version or Node.js version. You can read the [source code](https://github.com/mastra-ai/mastra/blob/main/packages/cli/src/analytics/index.ts) to check what's collected.
-
-You can opt out of the CLI analytics by setting an environment variable:
-
-```bash copy
-MASTRA_TELEMETRY_DISABLED=1
-```
-
-You can also set this while using other `mastra` commands:
-
-```bash copy
-MASTRA_TELEMETRY_DISABLED=1 mastra dev
-```
-
-[common-flags]: #common-flags