npm - @mastra/mcp-docs-server - Versions diffs - 1.2.14-alpha.1 → 1.2.14-alpha.4 - Mend

@mastra/mcp-docs-server 1.2.14-alpha.1 → 1.2.14-alpha.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (127) hide show

package/.docs/docs/agents/a2a.md +1 -1
package/.docs/docs/agents/acp.md +1 -1
package/.docs/docs/agents/agent-approval.md +1 -1
package/.docs/docs/agents/networks.md +2 -2
package/.docs/docs/agents/overview.md +2 -2
package/.docs/docs/agents/processors.md +25 -1
package/.docs/docs/agents/using-tools.md +2 -2
package/.docs/docs/capabilities/channels/overview.md +1 -1
package/.docs/docs/{agents/supervisor-agents.md → capabilities/subagents.md} +58 -58
package/.docs/docs/deployment/sandbox.md +95 -1
package/.docs/docs/getting-started/develop.md +2 -0
package/.docs/docs/harness/agent-controller.md +370 -0
package/.docs/docs/long-running-agents/background-tasks.md +1 -1
package/.docs/docs/long-running-agents/goals.md +3 -3
package/.docs/docs/mcp/overview.md +222 -281
package/.docs/docs/memory/overview.md +2 -2
package/.docs/docs/observability/integrations/exporters/confident-ai.md +140 -0
package/.docs/docs/observability/integrations/overview.md +1 -1
package/.docs/docs/observability/overview.md +122 -8
package/.docs/docs/observability/tracing/overview.md +2 -2
package/.docs/docs/server/mastra-client.md +1 -1
package/.docs/docs/server/server-adapters.md +2 -0
package/.docs/docs/storage/overview.md +2 -2
package/.docs/docs/workflows/agents-and-tools.md +29 -0
package/.docs/docs/workflows/stored-workflows.md +146 -0
package/.docs/guides/build-your-ui/copilotkit/channels.md +49 -39
package/.docs/guides/concepts/multi-agent-systems.md +7 -7
package/.docs/guides/guide/coding-agent.md +2 -2
package/.docs/guides/guide/research-coordinator.md +1 -1
package/.docs/guides/migrations/network-to-supervisor.md +1 -1
package/.docs/models/environment-variables.md +1 -1
package/.docs/models/gateways/neon.md +71 -0
package/.docs/models/gateways/netlify.md +6 -6
package/.docs/models/gateways/openrouter.md +6 -6
package/.docs/models/gateways/vercel.md +6 -6
package/.docs/models/gateways.md +1 -0
package/.docs/models/index.md +96 -97
package/.docs/models/providers/alibaba-cn.md +23 -25
package/.docs/models/providers/alibaba-token-plan-cn.md +24 -24
package/.docs/models/providers/alibaba-token-plan.md +23 -25
package/.docs/models/providers/alibaba.md +23 -25
package/.docs/models/providers/ambient.md +23 -25
package/.docs/models/providers/baseten.md +23 -25
package/.docs/models/providers/chutes.md +23 -25
package/.docs/models/providers/cortecs.md +23 -25
package/.docs/models/providers/crof.md +23 -25
package/.docs/models/providers/crossmodel.md +23 -25
package/.docs/models/providers/deepinfra.md +22 -24
package/.docs/models/providers/digitalocean.md +32 -34
package/.docs/models/providers/empiriolabs.md +23 -25
package/.docs/models/providers/fireworks-ai.md +24 -24
package/.docs/models/providers/greenpt.md +23 -25
package/.docs/models/providers/groq.md +23 -25
package/.docs/models/providers/huggingface.md +23 -25
package/.docs/models/providers/hyper.md +23 -25
package/.docs/models/providers/impossibl.md +23 -25
package/.docs/models/providers/infomaniak.md +24 -24
package/.docs/models/providers/kilo.md +24 -26
package/.docs/models/providers/llmgateway.md +24 -26
package/.docs/models/providers/mistral.md +23 -25
package/.docs/models/providers/modal.md +23 -25
package/.docs/models/providers/modelis.md +23 -25
package/.docs/models/providers/nano-gpt.md +23 -25
package/.docs/models/providers/neuralwatt.md +23 -25
package/.docs/models/providers/ofox.md +23 -25
package/.docs/models/providers/ollama-cloud.md +23 -25
package/.docs/models/providers/opencode-go.md +23 -25
package/.docs/models/providers/opencode.md +25 -26
package/.docs/models/providers/pioneer.md +23 -25
package/.docs/models/providers/requesty.md +23 -25
package/.docs/models/providers/routing-run.md +23 -25
package/.docs/models/providers/scx.md +23 -25
package/.docs/models/providers/tensorx.md +23 -25
package/.docs/models/providers/togetherai.md +22 -24
package/.docs/models/providers/umans-ai-coding-plan.md +24 -24
package/.docs/models/providers/umans-ai.md +23 -25
package/.docs/models/providers/wandb.md +23 -25
package/.docs/models/providers/xai.md +26 -28
package/.docs/models/providers/zai-coding-plan.md +23 -25
package/.docs/models/providers/zhipuai-coding-plan.md +23 -25
package/.docs/models/providers.md +0 -1
package/.docs/reference/acp/acp-agent.md +1 -1
package/.docs/reference/agent-controller/agent-controller-class.md +195 -506
package/.docs/reference/agent-controller/session.md +274 -111
package/.docs/reference/agents/network.md +1 -1
package/.docs/reference/ai-sdk/handle-network-stream.md +1 -1
package/.docs/reference/ai-sdk/network-route.md +1 -1
package/.docs/reference/cli/create-mastra.md +1 -1
package/.docs/reference/client-js/workflows.md +92 -0
package/.docs/reference/core/addStoredWorkflow.md +62 -0
package/.docs/reference/core/addStoredWorkflows.md +40 -0
package/.docs/reference/editor/versioning.md +1 -1
package/.docs/reference/evals/rubric.md +1 -1
package/.docs/reference/file-based-agents/observability.md +2 -2
package/.docs/reference/file-based-agents/storage.md +1 -1
package/.docs/reference/file-based-agents/subagents.md +1 -1
package/.docs/reference/file-based-agents/tools.md +1 -1
package/.docs/reference/index.md +5 -0
package/.docs/reference/observability/tracing/configuration.md +1 -1
package/.docs/reference/observability/tracing/exporters/confident-ai.md +138 -0
package/.docs/reference/observability/tracing/interfaces.md +29 -0
package/.docs/reference/processors/processor-interface.md +121 -10
package/.docs/reference/server/routes.md +13 -0
package/.docs/reference/signals/signal-provider.md +2 -0
package/.docs/reference/storage/overview.md +9 -8
package/.docs/reference/streaming/workflows/observeStream.md +1 -1
package/.docs/reference/streaming/workflows/resumeStream.md +1 -1
package/.docs/reference/streaming/workflows/stream.md +1 -1
package/.docs/reference/tools/mcp-server.md +1 -1
package/.docs/reference/tools/submit-plan-tool.md +1 -1
package/.docs/reference/workflows/stored-workflow-definition.md +292 -0
package/.docs/reference/workflows/workflow-methods/agent.md +62 -0
package/.docs/reference/workflows/workflow-methods/tool.md +43 -0
package/.docs/reference/workspace/railway-sandbox.md +5 -5
package/CHANGELOG.md +14 -0
package/package.json +4 -4
package/.docs/docs/agent-controller/channels.md +0 -111
package/.docs/docs/agent-controller/modes.md +0 -147
package/.docs/docs/agent-controller/overview.md +0 -136
package/.docs/docs/agent-controller/session.md +0 -161
package/.docs/docs/agent-controller/subagents.md +0 -110
package/.docs/docs/agent-controller/threads-and-state.md +0 -148
package/.docs/docs/agent-controller/tool-approvals.md +0 -147
package/.docs/docs/mcp/mcp-apps.md +0 -306
package/.docs/docs/observability/config.md +0 -140
package/.docs/docs/observability/storage.md +0 -81
package/.docs/models/providers/neon.md +0 -109

package/.docs/docs/mcp/mcp-apps.md DELETED Viewed

@@ -1,306 +0,0 @@
-> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
-# MCP Apps
-The [MCP Apps extension](https://github.com/modelcontextprotocol/ext-apps) allows MCP tools to serve interactive HTML UIs via `ui://` resources. When a tool has an associated app resource, Mastra Studio renders it in a sandboxed iframe alongside the tool form or inline in agent chat.
-## When to use MCP Apps
-Use MCP Apps when a tool result is better presented as an interactive UI rather than plain text. For example:
-- A calculator that renders input fields and buttons for computation
-- A color picker that displays swatches and hex values
-- A form builder that captures structured user input
-- A data visualizer that renders charts
-## Quickstart
-Define app resources on your `MCPServer` by providing a `ui://` URI mapped to inline HTML or an HTML file path.
-```typescript
-import { MCPServer } from '@mastra/mcp'
-import { createTool } from '@mastra/core/tools'
-import { z } from 'zod'
-const calculatorTool = createTool({
-  id: 'calculatorWithUI',
-  description: 'An interactive calculator',
-  inputSchema: z.object({
-    num1: z.number(),
-    num2: z.number(),
-    operation: z.enum(['add', 'subtract']),
-  }),
-  execute: async ({ num1, num2, operation }) => {
-    const result = operation === 'add' ? num1 + num2 : num1 - num2
-    return {
-      content: [{ type: 'text', text: 'An interactive calculator is displayed.' }],
-      structuredContent: { result },
-    }
-  },
-})
-const server = new MCPServer({
-  id: 'my-app-server',
-  name: 'My App Server',
-  version: '1.0.0',
-  tools: { calculatorTool },
-  appResources: {
-    'ui://calculator/main': {
-      name: 'Interactive Calculator',
-      html: `<html>
-        <body>
-          <h2>Calculator</h2>
-          <button id="btn">Compute</button>
-          <script type="module">
-            import { App } from 'https://cdn.jsdelivr.net/npm/@modelcontextprotocol/ext-apps/+esm';
-            const app = new App({ name: 'Calculator', version: '1.0.0' });
-            app.ontoolinput = (params) => {
-              console.log('Tool input:', params.arguments);
-            };
-            document.getElementById('btn').addEventListener('click', async () => {
-              const result = await app.callServerTool({
-                name: 'calculatorWithUI',
-                arguments: { num1: 10, num2: 5, operation: 'add' }
-              });
-              document.body.innerHTML += '<p>Result: ' + JSON.stringify(result) + '</p>';
-            });
-            await app.connect();
-          </script>
-        </body>
-      </html>`,
-    },
-  },
-})
-```
-Link the tool to its app resource by adding `_meta.ui.resourceUri` to the tool definition:
-```typescript
-calculatorTool._meta = {
-  ui: { resourceUri: 'ui://calculator/main' },
-}
-```
-Visit [MCPServer reference](https://mastra.ai/reference/tools/mcp-server) for the full `appResources` configuration.
-## Connecting MCP Apps to agents
-Agents consume tools, they don't need to know about MCP servers. Pass tools to the agent's `tools` config, and register the MCP server at the Mastra level so Studio can resolve app resources.
-```typescript
-import { Agent } from '@mastra/core/agent'
-import { calculatorTool } from '../mcp/tools'
-export const myAgent = new Agent({
-  id: 'my-agent',
-  name: 'My Agent',
-  instructions: 'You have access to interactive UI tools.',
-  model: 'openai/gpt-5-mini',
-  tools: { calculatorTool },
-})
-```
-Register the MCP server at the Mastra level. Studio scans registered MCP servers to map tools to their app resources.
-```typescript
-import { Mastra } from '@mastra/core/mastra'
-import { myAgent } from './agents'
-import { myAppServer } from './mcp/server'
-export const mastra = new Mastra({
-  agents: { myAgent },
-  mcpServers: { myAppServer },
-})
-```
-For remote MCP servers, use `MCPClient.listTools()` to get tools and `toMCPServerProxies()` to register the server:
-```typescript
-import { MCPClient } from '@mastra/mcp'
-const mcpClient = new MCPClient({
-  servers: {
-    remoteApp: { url: new URL('https://remote-mcp-server.example.com/mcp') },
-  },
-})
-const myAgent = new Agent({
-  id: 'my-agent',
-  name: 'My Agent',
-  model: 'openai/gpt-5-mini',
-  tools: await mcpClient.listTools(),
-})
-export const mastra = new Mastra({
-  agents: { myAgent },
-  mcpServers: { ...mcpClient.toMCPServerProxies() },
-})
-```
-When tools come from `MCPClient.listTools()`, each tool's `_meta.ui` is automatically stamped with a `serverId` so Studio can resolve its app resources without scanning all servers.
-## How MCP Apps work
-MCP Apps follow a specific communication pattern between the host (Mastra Studio) and the iframe:
-1. The tool executes and returns a brief summary in `content` (visible to the model) and detailed data in `structuredContent` (visible to the UI only).
-2. The host renders the app HTML in a sandboxed iframe.
-3. The iframe communicates with the host via a JSON-RPC postMessage protocol.
-4. The app can call server tools using `callServerTool()` and inject messages into the chat using `sendMessage()`.
-```text
-Agent calls tool → Tool returns brief content + structuredContent
-  → Host renders iframe with app HTML
-  → User interacts with UI
-  → UI calls callServerTool() for computation
-  → UI calls sendMessage() to inject result into chat
-```
-## Tool result format
-Tools with app resources should return two fields:
-- `content`: A brief text summary for the model. Keep this short so the agent doesn't parrot the full result.
-- `structuredContent`: The data payload that hydrates the UI. The model doesn't see this field.
-```typescript
-execute: async ({ num1, num2, operation }) => {
-  const result = operation === 'add' ? num1 + num2 : num1 - num2
-  return {
-    content: [{ type: 'text', text: 'An interactive calculator is displayed.' }],
-    structuredContent: { result },
-  }
-}
-```
-## App API (guest-side)
-MCP App HTML uses the standard [`App` class from `@modelcontextprotocol/ext-apps`](https://github.com/modelcontextprotocol/ext-apps) to communicate with the host. Import it via ESM CDN or bundle it.
-```javascript
-import { App } from 'https://cdn.jsdelivr.net/npm/@modelcontextprotocol/ext-apps/+esm'
-const app = new App({ name: 'MyApp', version: '1.0.0' })
-```
-### `app.callServerTool(params)`
-Calls an MCP server tool from within the iframe. This is useful for interactive computation without leaving the UI.
-```javascript
-const result = await app.callServerTool({
-  name: 'calculatorWithUI',
-  arguments: { num1: 42, num2: 8, operation: 'add' },
-})
-```
-### `app.sendMessage(params)`
-Injects a user message into the agent chat, triggering a new model turn. Use this for sharing results or requesting follow-up actions.
-```javascript
-await app.sendMessage({
-  role: 'user',
-  content: [{ type: 'text', text: 'The result of 42 + 8 is 50' }],
-})
-```
-### `app.ontoolinput`
-A callback that fires when the host delivers tool input data to the iframe, allowing pre-population of form fields. The `params.arguments` object contains the tool call arguments.
-```javascript
-app.ontoolinput = params => {
-  document.getElementById('num1').value = params.arguments.num1
-}
-```
-> **Preventing UI flicker:** If your app has default form values, the user may briefly see them before `ontoolinput` hydrates the correct values. To prevent this, start the body hidden and reveal it after hydration:
->
-> ```html
-> <style>
->   body {
->     opacity: 0;
->     transition: opacity 0.15s;
->   }
->   body.ready {
->     opacity: 1;
->   }
-> </style>
-> <script type="module">
->   import { App } from 'https://cdn.jsdelivr.net/npm/@modelcontextprotocol/ext-apps/+esm'
->   const app = new App({ name: 'MyApp', version: '1.0.0' })
->
->   app.ontoolinput = params => {
->     // Hydrate form fields from params.arguments
->     document.body.classList.add('ready')
->   }
->
->   await app.connect()
->   // Fallback: reveal after connection if no tool input arrives
->   setTimeout(() => document.body.classList.add('ready'), 150)
-> </script>
-> ```
-### `app.connect()`
-Establishes the connection to the host. Call this after registering all event handlers.
-```javascript
-await app.connect()
-```
-See the [`App` class API reference](https://apps.extensions.modelcontextprotocol.io/api/classes/app.App.html) for the full list of methods, callbacks, and lifecycle hooks.
-## Using external MCP servers with apps
-External (non-Mastra) MCP servers that implement the MCP Apps extension work with Mastra via `MCPClient`. Use `listTools()` for agent tools and `toMCPServerProxies()` to register them in Studio.
-```typescript
-import { Mastra } from '@mastra/core/mastra'
-import { MCPClient } from '@mastra/mcp'
-import { Agent } from '@mastra/core/agent'
-const mcpClient = new MCPClient({
-  servers: {
-    'external-server': {
-      command: 'node',
-      args: ['path/to/external-server.js'],
-    },
-  },
-})
-const myAgent = new Agent({
-  id: 'my-agent',
-  name: 'My Agent',
-  model: 'openai/gpt-5-mini',
-  tools: await mcpClient.listTools(),
-})
-export const mastra = new Mastra({
-  agents: { myAgent },
-  mcpServers: {
-    ...mcpClient.toMCPServerProxies(),
-  },
-})
-```
-Visit [MCPClient reference](https://mastra.ai/reference/tools/mcp-client) for more details on proxying external servers.
-## Sandbox security
-Mastra Studio uses [`@mcp-ui/client`](https://www.npmjs.com/package/@mcp-ui/client) to render MCP App iframes through a sandbox proxy. The proxy loads app HTML via `postMessage` rather than `srcDoc`, providing additional isolation.
-App iframes are sandboxed with the following permissions:
-- `allow-scripts`: Enables JavaScript execution
-- `allow-forms`: Allows form submission
-- `allow-popups`: Permits `window.open()` and link targets
-The iframe doesn't have access to the parent page's DOM, cookies, or storage. All communication happens through the JSON-RPC postMessage protocol managed by `@mcp-ui/client`'s `AppRenderer` on the host side and `@modelcontextprotocol/ext-apps`'s `App` class on the guest side.
-## Related
-- [MCP overview](https://mastra.ai/docs/mcp/overview)
-- [MCPServer reference](https://mastra.ai/reference/tools/mcp-server)
-- [MCPClient reference](https://mastra.ai/reference/tools/mcp-client)
-- [MCP Apps extension spec](https://github.com/modelcontextprotocol/ext-apps)

package/.docs/docs/observability/config.md DELETED Viewed

@@ -1,140 +0,0 @@
-> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
-# Configuration
-Observability is configured once on your Mastra instance and applies across traces, logs, and metrics.
-## When to use configuration
-- Set up a default observability pipeline for local development.
-- Route different environments or request types to different observability configs.
-- Keep Mastra Studio and Mastra platform access enabled while also sending data to external providers.
-## Quickstart
-The following example demonstrates the standard starter setup: composite storage with DuckDB for the observability domain, plus Mastra storage, Mastra platform, and sensitive-data redaction.
-```ts
-import { Mastra } from '@mastra/core/mastra'
-import { MastraCompositeStore } from '@mastra/core/storage'
-import { DuckDBStore } from '@mastra/duckdb'
-import { LibSQLStore } from '@mastra/libsql'
-import {
-  Observability,
-  MastraStorageExporter,
-  MastraPlatformExporter,
-  SensitiveDataFilter,
-} from '@mastra/observability'
-export const mastra = new Mastra({
-  storage: new MastraCompositeStore({
-    id: 'composite-storage',
-    default: new LibSQLStore({
-      id: 'mastra-storage',
-      url: 'file:./mastra.db',
-    }),
-    domains: {
-      observability: await new DuckDBStore().getStore('observability'),
-    },
-  }),
-  observability: new Observability({
-    configs: {
-      default: {
-        serviceName: 'mastra',
-        exporters: [new MastraStorageExporter(), new MastraPlatformExporter()],
-        spanOutputProcessors: [new SensitiveDataFilter()],
-        logging: {
-          enabled: true,
-          level: 'info',
-        },
-      },
-    },
-  }),
-})
-```
-## Basic config
-An observability config usually contains:
-- `serviceName`: The service identifier attached to exported observability data.
-- `exporters`: One or more destinations for traces, logs, and derived metrics.
-- `spanOutputProcessors`: Transformations that run before spans are exported.
-- `logging`: Log forwarding settings for observability storage.
-For destinations and processors, see [Integrations overview](https://mastra.ai/docs/observability/integrations/overview).
-## Maintaining Studio access
-When you add external exporters, keep `MastraStorageExporter` for Studio observability and/or `MastraPlatformExporter` for hosted Mastra platform observability.
-This example shows only the observability config. Configure storage separately.
-```ts
-import { Observability, MastraStorageExporter, MastraPlatformExporter } from '@mastra/observability'
-import { ArizeExporter } from '@mastra/arize'
-export const observability = new Observability({
-  configs: {
-    production: {
-      serviceName: 'my-service',
-      exporters: [
-        new ArizeExporter({
-          endpoint: process.env.PHOENIX_COLLECTOR_ENDPOINT,
-          apiKey: process.env.PHOENIX_API_KEY,
-        }),
-        new MastraStorageExporter(),
-        new MastraPlatformExporter(),
-      ],
-    },
-  },
-})
-```
-## Flushing in serverless environments
-In serverless environments, flush observability exporters before the runtime pauses or exits:
-```ts
-await mastra.observability.flush()
-```
-Use external storage in serverless environments instead of local file storage. For storage selection and routing, see [Storage](https://mastra.ai/docs/observability/storage).
-## Multi-config setup
-Use multiple configs when different environments or request types need different exporters or sampling behavior. Select the active config at runtime with `configSelector`.
-```ts
-import { Mastra } from '@mastra/core'
-import { Observability, MastraStorageExporter } from '@mastra/observability'
-import { LangfuseExporter } from '@mastra/langfuse'
-const storageExporter = new MastraStorageExporter()
-const langfuseExporter = new LangfuseExporter()
-export const mastra = new Mastra({
-  observability: new Observability({
-    configs: {
-      development: {
-        serviceName: 'my-service-dev',
-        exporters: [storageExporter],
-      },
-      production: {
-        serviceName: 'my-service-prod',
-        exporters: [storageExporter, langfuseExporter],
-      },
-    },
-    configSelector: () => process.env.NODE_ENV || 'development',
-  }),
-})
-```
-For trace sampling, see [Tracing](https://mastra.ai/docs/observability/tracing/overview).
-## Related
-- [Observability overview](https://mastra.ai/docs/observability/overview)
-- [Storage](https://mastra.ai/docs/observability/storage)
-- [Tracing](https://mastra.ai/docs/observability/tracing/overview)
-- [Integrations overview](https://mastra.ai/docs/observability/integrations/overview)

package/.docs/docs/observability/storage.md DELETED Viewed

@@ -1,81 +0,0 @@
-> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
-# Storage
-Storage determines which observability signals persist, which queries are available, and whether metrics aggregation works. Use a dedicated observability store instead of your primary application store.
-## When to use storage
-- Keep traces, logs, and metrics available in Mastra Studio during development.
-- Enable metrics with an OLAP-capable observability store.
-- Route the observability domain to a dedicated production backend.
-## Quickstart
-The following example demonstrates the recommended local testing setup: route observability data to DuckDB while keeping the rest of your application on LibSQL.
-```ts
-import { Mastra } from '@mastra/core/mastra'
-import { LibSQLStore } from '@mastra/libsql'
-import { DuckDBStore } from '@mastra/duckdb'
-import { MastraCompositeStore } from '@mastra/core/storage'
-import { Observability, MastraStorageExporter } from '@mastra/observability'
-export const mastra = new Mastra({
-  storage: new MastraCompositeStore({
-    id: 'composite-storage',
-    default: new LibSQLStore({
-      id: 'mastra-storage',
-      url: 'file:./mastra.db',
-    }),
-    domains: {
-      observability: await new DuckDBStore().getStore('observability'),
-    },
-  }),
-  observability: new Observability({
-    configs: {
-      default: {
-        serviceName: 'mastra',
-        exporters: [new MastraStorageExporter()],
-      },
-    },
-  }),
-})
-```
-## Signal support
-Mastra storage-backed observability currently depends on an OLAP-capable backend for full signal support:
-- DuckDB: Recommended for local testing and development.
-- ClickHouse: Recommended for production observability.
-- Mastra platform: Use `MastraPlatformExporter` if you want hosted observability without managing the backend yourself.
-Primary application stores such as LibSQL or PostgreSQL shouldn't be used as the observability store. Route the `observability` domain separately with composite storage when you use `MastraStorageExporter`.
-## Local development
-For local development, the recommended setup is:
-- `LibSQLStore` for primary application storage
-- `DuckDBStore` for the `observability` domain
-- `MastraStorageExporter` for local Studio access
-This setup is for local testing and development. It gives you persisted traces, logs, and metrics without introducing external infrastructure.
-## Production deployment
-Observability traffic is usually more write-heavy than the rest of the application. In production:
-- Use `MastraStorageExporter` with ClickHouse for the `observability` domain when you keep observability in your own storage.
-- Use `MastraPlatformExporter` if you want hosted Mastra platform observability instead of managing the backend yourself.
-- Don't route observability to your primary application store.
-For backend compatibility details and exporter batching behavior, see [Mastra Storage exporter](https://mastra.ai/docs/observability/integrations/exporters/mastra-storage).
-## Next steps
-- [Configuration](https://mastra.ai/docs/observability/config)
-- [Logging](https://mastra.ai/docs/observability/logging)
-- [Metrics overview](https://mastra.ai/docs/observability/metrics/overview)
-- [Mastra Storage exporter](https://mastra.ai/docs/observability/integrations/exporters/mastra-storage)

package/.docs/models/providers/neon.md DELETED Viewed

@@ -1,109 +0,0 @@
-> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
-# ![Neon logo](https://models.dev/logos/neon.svg)Neon
-Access 36 Neon models through Mastra's model router. Authentication is handled automatically using the `NEON_AI_GATEWAY_TOKEN` environment variable. Configure `NEON_AI_GATEWAY_BASE_URL` as well.
-Learn more in the [Neon documentation](https://neon.com/docs).
-```bash
-NEON_AI_GATEWAY_BASE_URL=your-value
-NEON_AI_GATEWAY_TOKEN=your-api-token
-```
-```typescript
-import { Agent } from "@mastra/core/agent";
-const agent = new Agent({
-  id: "my-agent",
-  name: "My Agent",
-  instructions: "You are a helpful assistant",
-  model: "neon/claude-haiku-4-5"
-});
-// Generate a response
-const response = await agent.generate("Hello!");
-// Stream a response
-const stream = await agent.stream("Tell me a story");
-for await (const chunk of stream) {
-  console.log(chunk);
-}
-```
-> **Info:** Mastra uses the OpenAI-compatible `/chat/completions` endpoint. Some provider-specific features may not be available. Check the [Neon documentation](https://neon.com/docs) for details.
-## Models
-| Model                              | Context | Tools | Reasoning | Image | Audio | Video | Input $/1M | Output $/1M |
-| ---------------------------------- | ------- | ----- | --------- | ----- | ----- | ----- | ---------- | ----------- |
-| `neon/claude-haiku-4-5`            | 200K    |       |           |       |       |       | $1         | $5          |
-| `neon/claude-opus-4-1`             | 200K    |       |           |       |       |       | $15        | $75         |
-| `neon/claude-opus-4-5`             | 200K    |       |           |       |       |       | $5         | $25         |
-| `neon/claude-opus-4-6`             | 1.0M    |       |           |       |       |       | $5         | $25         |
-| `neon/claude-opus-4-7`             | 1.0M    |       |           |       |       |       | $5         | $25         |
-| `neon/claude-opus-4-8`             | 1.0M    |       |           |       |       |       | $5         | $25         |
-| `neon/claude-sonnet-4`             | 200K    |       |           |       |       |       | $3         | $15         |
-| `neon/claude-sonnet-4-5`           | 200K    |       |           |       |       |       | $3         | $15         |
-| `neon/claude-sonnet-4-6`           | 1.0M    |       |           |       |       |       | $3         | $15         |
-| `neon/gemini-2-5-flash`            | 1.0M    |       |           |       |       |       | $0.30      | $3          |
-| `neon/gemini-2-5-pro`              | 1.0M    |       |           |       |       |       | $1         | $10         |
-| `neon/gemini-3-1-flash-lite`       | 1.0M    |       |           |       |       |       | $0.25      | $2          |
-| `neon/gemini-3-1-pro`              | 1.0M    |       |           |       |       |       | $2         | $12         |
-| `neon/gemini-3-5-flash`            | 1.0M    |       |           |       |       |       | $2         | $9          |
-| `neon/gemini-3-flash`              | 1.0M    |       |           |       |       |       | $0.50      | $3          |
-| `neon/gemini-3-pro`                | 1.0M    |       |           |       |       |       | $2         | $12         |
-| `neon/gemma-3-12b`                 | 131K    |       |           |       |       |       | $0.15      | $0.50       |
-| `neon/gpt-5`                       | 400K    |       |           |       |       |       | $1         | $10         |
-| `neon/gpt-5-1`                     | 400K    |       |           |       |       |       | $1         | $10         |
-| `neon/gpt-5-1-codex-max`           | 400K    |       |           |       |       |       | $1         | $10         |
-| `neon/gpt-5-1-codex-mini`          | 400K    |       |           |       |       |       | $0.25      | $2          |
-| `neon/gpt-5-2`                     | 400K    |       |           |       |       |       | $2         | $14         |
-| `neon/gpt-5-2-codex`               | 400K    |       |           |       |       |       | $2         | $14         |
-| `neon/gpt-5-3-codex`               | 400K    |       |           |       |       |       | $2         | $14         |
-| `neon/gpt-5-4`                     | 1.1M    |       |           |       |       |       | $3         | $15         |
-| `neon/gpt-5-4-mini`                | 400K    |       |           |       |       |       | $0.75      | $5          |
-| `neon/gpt-5-4-nano`                | 400K    |       |           |       |       |       | $0.20      | $1          |
-| `neon/gpt-5-mini`                  | 400K    |       |           |       |       |       | $0.25      | $2          |
-| `neon/gpt-5-nano`                  | 400K    |       |           |       |       |       | $0.05      | $0.40       |
-| `neon/gpt-oss-120b`                | 131K    |       |           |       |       |       | $0.07      | $0.28       |
-| `neon/gpt-oss-20b`                 | 131K    |       |           |       |       |       | $0.05      | $0.20       |
-| `neon/llama-4-maverick`            | 1.0M    |       |           |       |       |       | $0.50      | $2          |
-| `neon/meta-llama-3-1-8b-instruct`  | 131K    |       |           |       |       |       | $0.15      | $0.45       |
-| `neon/meta-llama-3-3-70b-instruct` | 128K    |       |           |       |       |       | $0.50      | $2          |
-| `neon/qwen3-next-80b-a3b-instruct` | 131K    |       |           |       |       |       | $0.15      | $1          |
-| `neon/qwen35-122b-a10b`            | 262K    |       |           |       |       |       | $0.22      | $2          |
-## Advanced configuration
-### Custom headers
-```typescript
-const agent = new Agent({
-  id: "custom-agent",
-  name: "custom-agent",
-  model: {
-    url: "${NEON_AI_GATEWAY_BASE_URL}/v1",
-    id: "neon/claude-haiku-4-5",
-    apiKey: process.env.NEON_AI_GATEWAY_TOKEN,
-    headers: {
-      "X-Custom-Header": "value"
-    }
-  }
-});
-```
-### Dynamic model selection
-```typescript
-const agent = new Agent({
-  id: "dynamic-agent",
-  name: "Dynamic Agent",
-  model: ({ requestContext }) => {
-    const useAdvanced = requestContext.task === "complex";
-    return useAdvanced
-      ? "neon/qwen35-122b-a10b"
-      : "neon/claude-haiku-4-5";
-  }
-});
-```