@mastra/mcp-docs-server 1.1.32 → 1.1.33-alpha.3

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.
@@ -59,7 +59,7 @@ for await (const chunk of stream) {
59
59
  | `ollama-cloud/minimax-m2` | 205K | | | | | | — | — |
60
60
  | `ollama-cloud/minimax-m2.1` | 205K | | | | | | — | — |
61
61
  | `ollama-cloud/minimax-m2.5` | 205K | | | | | | — | — |
62
- | `ollama-cloud/minimax-m2.7` | 205K | | | | | | — | — |
62
+ | `ollama-cloud/minimax-m2.7` | 197K | | | | | | — | — |
63
63
  | `ollama-cloud/ministral-3:14b` | 262K | | | | | | — | — |
64
64
  | `ollama-cloud/ministral-3:3b` | 262K | | | | | | — | — |
65
65
  | `ollama-cloud/ministral-3:8b` | 262K | | | | | | — | — |
@@ -1,6 +1,6 @@
1
1
  # ![Vivgrid logo](https://models.dev/logos/vivgrid.svg)Vivgrid
2
2
 
3
- Access 12 Vivgrid models through Mastra's model router. Authentication is handled automatically using the `VIVGRID_API_KEY` environment variable.
3
+ Access 13 Vivgrid models through Mastra's model router. Authentication is handled automatically using the `VIVGRID_API_KEY` environment variable.
4
4
 
5
5
  Learn more in the [Vivgrid documentation](https://docs.vivgrid.com/models).
6
6
 
@@ -35,9 +35,9 @@ for await (const chunk of stream) {
35
35
  | Model | Context | Tools | Reasoning | Image | Audio | Video | Input $/1M | Output $/1M |
36
36
  | --------------------------------------- | ------- | ----- | --------- | ----- | ----- | ----- | ---------- | ----------- |
37
37
  | `vivgrid/deepseek-v3.2` | 128K | | | | | | $0.28 | $0.42 |
38
+ | `vivgrid/deepseek-v4-pro` | 1.0M | | | | | | $2 | $3 |
38
39
  | `vivgrid/gemini-3.1-flash-lite-preview` | 1.0M | | | | | | $0.25 | $2 |
39
40
  | `vivgrid/gemini-3.1-pro-preview` | 1.0M | | | | | | $2 | $12 |
40
- | `vivgrid/glm-5` | 203K | | | | | | $1 | $3 |
41
41
  | `vivgrid/gpt-5-mini` | 272K | | | | | | $0.25 | $2 |
42
42
  | `vivgrid/gpt-5.1-codex` | 400K | | | | | | $1 | $10 |
43
43
  | `vivgrid/gpt-5.1-codex-max` | 400K | | | | | | $1 | $10 |
@@ -46,6 +46,7 @@ for await (const chunk of stream) {
46
46
  | `vivgrid/gpt-5.4` | 400K | | | | | | $3 | $15 |
47
47
  | `vivgrid/gpt-5.4-mini` | 400K | | | | | | $0.75 | $5 |
48
48
  | `vivgrid/gpt-5.4-nano` | 400K | | | | | | $0.20 | $1 |
49
+ | `vivgrid/gpt-5.5` | 1.1M | | | | | | $5 | $30 |
49
50
 
50
51
  ## Advanced configuration
51
52
 
@@ -75,7 +76,7 @@ const agent = new Agent({
75
76
  model: ({ requestContext }) => {
76
77
  const useAdvanced = requestContext.task === "complex";
77
78
  return useAdvanced
78
- ? "vivgrid/gpt-5.4-nano"
79
+ ? "vivgrid/gpt-5.5"
79
80
  : "vivgrid/deepseek-v3.2";
80
81
  }
81
82
  });
@@ -1,6 +1,6 @@
1
1
  # ![xAI logo](https://models.dev/logos/xai.svg)xAI
2
2
 
3
- Access 25 xAI models through Mastra's model router. Authentication is handled automatically using the `XAI_API_KEY` environment variable.
3
+ Access 26 xAI models through Mastra's model router. Authentication is handled automatically using the `XAI_API_KEY` environment variable.
4
4
 
5
5
  Learn more in the [xAI documentation](https://docs.x.ai/docs/models).
6
6
 
@@ -54,6 +54,7 @@ for await (const chunk of stream) {
54
54
  | `xai/grok-4.20-0309-non-reasoning` | 2.0M | | | | | | $2 | $6 |
55
55
  | `xai/grok-4.20-0309-reasoning` | 2.0M | | | | | | $2 | $6 |
56
56
  | `xai/grok-4.20-multi-agent-0309` | 2.0M | | | | | | $2 | $6 |
57
+ | `xai/grok-4.3` | 1.0M | | | | | | $1 | $3 |
57
58
  | `xai/grok-beta` | 131K | | | | | | $5 | $15 |
58
59
  | `xai/grok-code-fast-1` | 256K | | | | | | $0.20 | $2 |
59
60
  | `xai/grok-vision-beta` | 8K | | | | | | $5 | $15 |
@@ -208,4 +208,53 @@ A workflow run result yields the following:
208
208
 
209
209
  **eventTimestamp** (`Date`): The timestamp of the event
210
210
 
211
- **payload** (`object`): Contains currentStep (id, status, output, payload) and workflowState (status, steps record)
211
+ **payload** (`object`): Contains currentStep (id, status, output, payload) and workflowState (status, steps record)
212
+
213
+ ## Schedules
214
+
215
+ Schedules are declared in code via the `schedule` field on `createWorkflow`. The client SDK exposes read and operational methods for managing them at runtime. See [Scheduled workflows](https://mastra.ai/docs/workflows/scheduled-workflows).
216
+
217
+ ### `listSchedules()`
218
+
219
+ List all schedules, optionally filtered by workflow id or status.
220
+
221
+ ```typescript
222
+ const schedules = await mastraClient.listSchedules({
223
+ workflowId: 'daily-report',
224
+ status: 'active',
225
+ })
226
+ ```
227
+
228
+ ### `getSchedule()`
229
+
230
+ Fetch a single schedule by id.
231
+
232
+ ```typescript
233
+ const schedule = await mastraClient.getSchedule('daily-report')
234
+ ```
235
+
236
+ ### `pauseSchedule()`
237
+
238
+ Pause a schedule so the scheduler stops firing it. Returns the updated schedule. Idempotent.
239
+
240
+ ```typescript
241
+ await mastraClient.pauseSchedule('daily-report')
242
+ ```
243
+
244
+ ### `resumeSchedule()`
245
+
246
+ Resume a paused schedule. The next fire time is recomputed from now, so a long-paused schedule does not fire a backlog. Returns the updated schedule. Idempotent.
247
+
248
+ ```typescript
249
+ await mastraClient.resumeSchedule('daily-report')
250
+ ```
251
+
252
+ ### `listScheduleTriggers()`
253
+
254
+ List the trigger history for a schedule, including the joined run summary for each fire.
255
+
256
+ ```typescript
257
+ const { triggers } = await mastraClient.listScheduleTriggers('daily-report', {
258
+ limit: 50,
259
+ })
260
+ ```
@@ -0,0 +1,211 @@
1
+ # DatadogBridge
2
+
3
+ > **Warning:** The Datadog Bridge is currently **experimental**. APIs and configuration options may change in future releases.
4
+
5
+ Enables bidirectional integration between Mastra tracing and Datadog. Creates native `dd-trace` APM spans in real time so that auto-instrumented operations inside tools and processors are correctly nested under their parent Mastra span. Emits LLM Observability data through `dd-trace`'s pipeline when spans end.
6
+
7
+ ## Constructor
8
+
9
+ ```typescript
10
+ new DatadogBridge(config?: DatadogBridgeConfig)
11
+ ```
12
+
13
+ ## `DatadogBridgeConfig`
14
+
15
+ ```typescript
16
+ interface DatadogBridgeConfig extends BaseExporterConfig {
17
+ apiKey?: string
18
+ mlApp?: string
19
+ site?: string
20
+ service?: string
21
+ env?: string
22
+ agentless?: boolean
23
+ integrationsEnabled?: boolean
24
+ requestContextKeys?: string[]
25
+ }
26
+ ```
27
+
28
+ Extends `BaseExporterConfig`, which includes:
29
+
30
+ - `logger?: IMastraLogger` - Logger instance
31
+ - `logLevel?: LogLevel | 'debug' | 'info' | 'warn' | 'error'` - Log level (default: INFO)
32
+
33
+ ## Methods
34
+
35
+ ### `createSpan`
36
+
37
+ ```typescript
38
+ createSpan(options: CreateSpanOptions<SpanType>): SpanIds | undefined
39
+ ```
40
+
41
+ Called by the Mastra observability instance during span construction. Creates a dd-trace APM span eagerly via `tracer.startSpan()` and returns Mastra-compatible identifiers. The returned IDs are used by Mastra throughout the span's lifetime; the dd-trace span object is stored internally and used for scope activation.
42
+
43
+ **Returns:** `SpanIds | undefined` - `{ spanId, traceId, parentSpanId }`, or `undefined` if the bridge is disabled.
44
+
45
+ ### `executeInContext`
46
+
47
+ ```typescript
48
+ executeInContext<T>(spanId: string, fn: () => Promise<T>): Promise<T>
49
+ ```
50
+
51
+ Executes an async function within the dd-trace context of a Mastra span. dd-trace auto-instrumented operations running inside the function (HTTP, database, etc.) will be parented to this span.
52
+
53
+ **Returns:** `Promise<T>` - The result of the function execution.
54
+
55
+ ### `executeInContextSync`
56
+
57
+ ```typescript
58
+ executeInContextSync<T>(spanId: string, fn: () => T): T
59
+ ```
60
+
61
+ Executes a synchronous function within the dd-trace context of a Mastra span.
62
+
63
+ **Returns:** `T` - The result of the function execution.
64
+
65
+ ### `flush`
66
+
67
+ ```typescript
68
+ async flush(): Promise<void>
69
+ ```
70
+
71
+ Force-flushes any buffered LLM Observability data to Datadog without shutting down the bridge. Useful in serverless environments where you need to ensure data is exported before the runtime terminates.
72
+
73
+ ### `shutdown`
74
+
75
+ ```typescript
76
+ async shutdown(): Promise<void>
77
+ ```
78
+
79
+ Force-finishes any APM spans that weren't properly closed, flushes pending LLM Observability data, disables the LLM Observability integration, and clears all internal state.
80
+
81
+ ## Usage examples
82
+
83
+ ### Basic Usage
84
+
85
+ ```typescript
86
+ import tracer from 'dd-trace'
87
+
88
+ tracer.init({
89
+ service: process.env.DD_SERVICE || 'my-mastra-app',
90
+ env: process.env.DD_ENV || 'production',
91
+ })
92
+
93
+ import { Mastra } from '@mastra/core'
94
+ import { Observability } from '@mastra/observability'
95
+ import { DatadogBridge } from '@mastra/datadog'
96
+
97
+ const mastra = new Mastra({
98
+ observability: new Observability({
99
+ configs: {
100
+ default: {
101
+ serviceName: 'my-mastra-app',
102
+ bridge: new DatadogBridge({
103
+ mlApp: process.env.DD_LLMOBS_ML_APP!,
104
+ }),
105
+ },
106
+ },
107
+ }),
108
+ agents: { myAgent },
109
+ })
110
+ ```
111
+
112
+ ### Agentless Mode (LLM Observability only, no local agent)
113
+
114
+ If you don't have a local Datadog Agent and only want LLM Observability data, enable agentless mode:
115
+
116
+ ```typescript
117
+ new DatadogBridge({
118
+ mlApp: process.env.DD_LLMOBS_ML_APP!,
119
+ apiKey: process.env.DD_API_KEY!,
120
+ agentless: true,
121
+ })
122
+ ```
123
+
124
+ Note: APM data cannot be sent in agentless mode. If you only need LLM Observability data without `dd-trace` APM, the [Datadog Exporter](https://mastra.ai/reference/observability/tracing/exporters/datadog) is a simpler choice.
125
+
126
+ ### With Additional Exporters
127
+
128
+ The bridge can be combined with non-Datadog exporters to send traces to additional destinations:
129
+
130
+ ```typescript
131
+ import { Mastra } from '@mastra/core'
132
+ import { Observability, DefaultExporter } from '@mastra/observability'
133
+ import { DatadogBridge } from '@mastra/datadog'
134
+
135
+ const mastra = new Mastra({
136
+ observability: new Observability({
137
+ configs: {
138
+ default: {
139
+ serviceName: 'my-mastra-app',
140
+ bridge: new DatadogBridge({
141
+ mlApp: process.env.DD_LLMOBS_ML_APP!,
142
+ }),
143
+ exporters: [
144
+ new DefaultExporter(), // Studio access
145
+ ],
146
+ },
147
+ },
148
+ }),
149
+ })
150
+ ```
151
+
152
+ > **Note:** Don't combine `DatadogBridge` with `DatadogExporter` in the same configuration — both emit to LLM Observability and would double-write the same data.
153
+
154
+ ## Setup requirements
155
+
156
+ The DatadogBridge requires `dd-trace` to be initialized before any other imports so its auto-instrumentation can patch HTTP, database, and framework libraries at load time.
157
+
158
+ See the [DatadogBridge Guide](https://mastra.ai/docs/observability/tracing/bridges/datadog) for complete setup instructions, including dd-trace initialization, bundler externals, and agent configuration.
159
+
160
+ ## Span mapping
161
+
162
+ Mastra span types are mapped to Datadog LLM Observability span kinds:
163
+
164
+ | Mastra SpanType | Datadog Kind |
165
+ | ------------------ | ------------ |
166
+ | `AGENT_RUN` | `agent` |
167
+ | `MODEL_GENERATION` | `workflow` |
168
+ | `MODEL_STEP` | `llm` |
169
+ | `TOOL_CALL` | `tool` |
170
+ | `MCP_TOOL_CALL` | `tool` |
171
+ | `WORKFLOW_RUN` | `workflow` |
172
+ | All other types | `task` |
173
+
174
+ ## Tags support
175
+
176
+ `tracingOptions.tags` values become structured LLM Observability annotation tags: `key:value` entries are split into key/value pairs, and tags without a colon are set to `true`.
177
+
178
+ ```typescript
179
+ const result = await agent.generate('Hello', {
180
+ tracingOptions: {
181
+ tags: ['production', 'instance_name:career-scout-api'],
182
+ },
183
+ })
184
+ ```
185
+
186
+ This produces:
187
+
188
+ ```json
189
+ {
190
+ "production": true,
191
+ "instance_name": "career-scout-api"
192
+ }
193
+ ```
194
+
195
+ ## Environment variables
196
+
197
+ The bridge reads configuration from these environment variables:
198
+
199
+ | Variable | Description |
200
+ | ----------------------------- | -------------------------------------------------- |
201
+ | `DD_API_KEY` | Datadog API key (only required for agentless mode) |
202
+ | `DD_LLMOBS_ML_APP` | ML application name |
203
+ | `DD_SITE` | Datadog site |
204
+ | `DD_ENV` | Environment name |
205
+ | `DD_LLMOBS_AGENTLESS_ENABLED` | Set to `'true'` or `'1'` to enable agentless mode |
206
+
207
+ ## Related
208
+
209
+ - [DatadogBridge Guide](https://mastra.ai/docs/observability/tracing/bridges/datadog) - Setup guide with examples
210
+ - [Tracing Overview](https://mastra.ai/docs/observability/tracing/overview) - General tracing concepts
211
+ - [DatadogExporter Reference](https://mastra.ai/reference/observability/tracing/exporters/datadog) - LLM Observability only, no `dd-trace` APM
@@ -2,6 +2,8 @@
2
2
 
3
3
  Sends Tracing data to Datadog's LLM Observability product for monitoring and analytics.
4
4
 
5
+ > **Info:** If you also use `dd-trace` APM auto-instrumentation and need it correctly parented under Mastra spans, use the [DatadogBridge](https://mastra.ai/reference/observability/tracing/bridges/datadog) instead. The exporter sends LLM Observability data after execution completes, so it doesn't participate in `dd-trace`'s live scope.
6
+
5
7
  ## Constructor
6
8
 
7
9
  ```typescript
@@ -89,7 +91,7 @@ const exporter = new DatadogExporter({
89
91
 
90
92
  ## Span mapping
91
93
 
92
- Mastra span types are mapped to Datadog LLMObs span kinds:
94
+ Mastra span types are mapped to Datadog LLM Observability span kinds:
93
95
 
94
96
  | Mastra SpanType | Datadog Kind |
95
97
  | ------------------ | ------------ |
@@ -99,6 +99,22 @@ export const testWorkflow = createWorkflow({
99
99
 
100
100
  **requestContextSchema** (`StandardJSONSchemaV1`): Standard JSON Schema for validating request context values. When provided, the context is validated at the start of run.start(), throwing an error if validation fails.
101
101
 
102
+ **schedule** (`WorkflowScheduleConfig | WorkflowScheduleConfig[]`): Optional cron schedule for the workflow. Accepts a single config or an array of configs to fire on multiple cadences. Setting this auto-promotes the workflow to the evented execution engine. See the scheduled workflows guide for usage.
103
+
104
+ **schedule.id** (`string`): Stable identifier for the schedule. Required when passing an array of schedules. Defaults to the workflow id when passing a single schedule object.
105
+
106
+ **schedule.cron** (`string`): A 5-, 6-, or 7-part cron expression. Validated at workflow construction time.
107
+
108
+ **schedule.timezone** (`string`): IANA timezone, for example "America/New\_York". Defaults to the host's local timezone. Set this explicitly in production so fire times do not depend on server locale.
109
+
110
+ **schedule.inputData** (`TInput`): Payload passed as the workflow's input on every fire.
111
+
112
+ **schedule.initialState** (`TState`): Initial state for the run.
113
+
114
+ **schedule.requestContext** (`Record<string, unknown>`): Request context attached to the run.
115
+
116
+ **schedule.metadata** (`Record<string, unknown>`): Arbitrary metadata persisted alongside the schedule row.
117
+
102
118
  **options** (`WorkflowOptions`): Optional options for the workflow
103
119
 
104
120
  **options.tracingPolicy** (`TracingPolicy`): Optional tracing policy for the workflow
package/CHANGELOG.md CHANGED
@@ -1,5 +1,20 @@
1
1
  # @mastra/mcp-docs-server
2
2
 
3
+ ## 1.1.33-alpha.2
4
+
5
+ ### Patch Changes
6
+
7
+ - Updated dependencies [[`c05c9a1`](https://github.com/mastra-ai/mastra/commit/c05c9a13230988cef6d438a62f37760f31927bc7), [`e24aacb`](https://github.com/mastra-ai/mastra/commit/e24aacba07bd66f5d95b636dc24016fca26b52cf), [`c721164`](https://github.com/mastra-ai/mastra/commit/c7211643f7ac861f83b19a3757cc921487fc9d75), [`1b55954`](https://github.com/mastra-ai/mastra/commit/1b559541c1e08a10e49d01ffc51a634dfc37a286), [`5adc55e`](https://github.com/mastra-ai/mastra/commit/5adc55e63407be8ee977914957d68bcc2a075ceb), [`70017d7`](https://github.com/mastra-ai/mastra/commit/70017d72ab741b5d7040e2a15c251a317782e39e), [`e4942bc`](https://github.com/mastra-ai/mastra/commit/e4942bc7fdc903572f7d84f26d5e15f9d39c763d)]:
8
+ - @mastra/core@1.32.0-alpha.1
9
+
10
+ ## 1.1.33-alpha.0
11
+
12
+ ### Patch Changes
13
+
14
+ - Updated dependencies [[`6dcd65f`](https://github.com/mastra-ai/mastra/commit/6dcd65f2a34069e6dc43ba35f1d11119b9b40bef), [`1c2dda8`](https://github.com/mastra-ai/mastra/commit/1c2dda805fbfccc0abf55d4cb20cc34402dc3f0c), [`568777e`](https://github.com/mastra-ai/mastra/commit/568777ea8af77a672270b448dfd3996f9e75a964)]:
15
+ - @mastra/core@1.31.1-alpha.0
16
+ - @mastra/mcp@1.6.1-alpha.0
17
+
3
18
  ## 1.1.32
4
19
 
5
20
  ### Patch Changes
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mastra/mcp-docs-server",
3
- "version": "1.1.32",
3
+ "version": "1.1.33-alpha.3",
4
4
  "description": "MCP server for accessing Mastra.ai documentation, changelogs, and news.",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
@@ -29,8 +29,8 @@
29
29
  "jsdom": "^26.1.0",
30
30
  "local-pkg": "^1.1.2",
31
31
  "zod": "^4.3.6",
32
- "@mastra/core": "1.31.0",
33
- "@mastra/mcp": "^1.6.0"
32
+ "@mastra/core": "1.32.0-alpha.1",
33
+ "@mastra/mcp": "^1.6.1-alpha.0"
34
34
  },
35
35
  "devDependencies": {
36
36
  "@hono/node-server": "^1.19.11",
@@ -47,8 +47,8 @@
47
47
  "typescript": "^6.0.3",
48
48
  "vitest": "4.1.5",
49
49
  "@internal/lint": "0.0.90",
50
- "@internal/types-builder": "0.0.65",
51
- "@mastra/core": "1.31.0"
50
+ "@mastra/core": "1.32.0-alpha.1",
51
+ "@internal/types-builder": "0.0.65"
52
52
  },
53
53
  "homepage": "https://mastra.ai",
54
54
  "repository": {