@mastra/mcp-docs-server 1.2.25-alpha.6 → 1.2.25-alpha.8

package/.docs/docs/harness/agent-controller.md

@@ -133,6 +133,32 @@ const session = await controller.createSession({
 
 Use [`session.thread.create()`](https://mastra.ai/reference/agent-controller/session) and [`session.thread.switch()`](https://mastra.ai/reference/agent-controller/session) to move one live Session between conversations.
 
+### List stored messages from the client
+
+Use the Agent Controller client to page through a thread's stored messages. Passing an options object returns the messages with pagination metadata:
+
+```typescript
+import { MastraClient } from '@mastra/client-js'
+
+const client = new MastraClient({ baseUrl: 'http://localhost:4111' })
+const session = client.getAgentController('assistant-controller').session('user-123')
+
+const result = await session.listMessages('support-ticket-42', {
+  page: 0,
+  perPage: 20,
+  orderBy: { field: 'createdAt', direction: 'DESC' },
+  filter: {
+    dateRange: { start: new Date('2026-01-01') },
+  },
+})
+
+console.log(result.messages)
+console.log(result.total)
+console.log(result.hasMore)
+```
+
+`page` is zero-indexed. Omitting `perPage` uses the storage default of 40 messages. Use `include` to request a message by ID with adjacent messages. `limit` is a deprecated alias for `perPage`; existing paged callers may use `{ limit, page }`, but must use `perPage` with `orderBy`, `filter`, or `include`. The existing numeric form, `session.listMessages(threadId, limit)`, remains available when you need the newest message window as an array, ordered oldest-first.
+
 ## Switch modes and models
 
 Modes change the instructions and tools used by the shared backing agent without replacing the Session or thread. Configure mode-specific tools and visibility on the controller:

package/.docs/docs/harness/signal-providers.md

@@ -210,4 +210,5 @@ For a production provider that watches GitHub pull requests, see the [GitHub Cha
 - [Signals](https://mastra.ai/docs/harness/signals)
 - [Notification signals](https://mastra.ai/docs/harness/signals)
 - [`SignalProvider` reference](https://mastra.ai/reference/signals/signal-provider)
-- [`WebhookSignalProvider` reference](https://mastra.ai/reference/signals/webhook-signal-provider)
+- [`WebhookSignalProvider` reference](https://mastra.ai/reference/signals/webhook-signal-provider)
+- [Mastra Factory](https://factory.mastra.ai/) uses signal providers to integrate with external systems like GitHub and Linear, bringing issues and pull requests into a collaborative work board.

package/.docs/docs/index.md

@@ -192,6 +192,17 @@ Templates: [Docs Chatbot](https://mastra.ai/templates/docs-chatbot), [Slack Agen
 
 </details>
 
+<details>
+**Software factories**
+
+Coordinate coding agents to turn issues into tested code and pull requests. Let people review plans and changes before they're merged.
+
+Used by Mastra.
+
+Get started with [Mastra Factory](https://factory.mastra.ai/).
+
+</details>
+
 <details>
 **Internal copilots**
 

package/.docs/docs/mastra-platform/deploy.md

@@ -6,7 +6,7 @@
 
 [`mastra deploy`](https://mastra.ai/reference/cli/mastra) is the single command for releasing a Mastra application to the [Mastra platform](https://mastra.ai/docs/mastra-platform/overview).
 
-One command builds your project and validates it before anything includes, plus creates the platform project and environment on your first run, deploys, streams build logs, and prints your public URL once the deploy is serving traffic.
+One command builds your project and validates it before deploying, plus creates the platform project and environment on your first run, deploys, streams build logs, and prints your public URL once the deploy is serving traffic.
 
 ```bash
 mastra deploy
@@ -63,6 +63,10 @@ A local `.env` file is optional. Environment variables stored on the platform ar
    > })
    > ```
 
+   If the build statically finds `backgroundTasks.enabled: true`, the deploy artifact includes a worker manifest. Mastra Cloud automatically provisions or updates a dedicated worker service from the same artifact. No separate toggle or add-on is required.
+
+   Removing `backgroundTasks` or setting `enabled: false` in a later deploy removes the manifest and spins down the existing worker service. Values that can't be determined statically are omitted from the manifest display, but the worker process still reads the complete configuration from your bundled code.
+
 3. Run `mastra deploy` again. Preflight passes, the build uploads, and the CLI streams build logs until the deploy is live. Expect the full build and deploy to take between 30 seconds and a few minutes. The success message prints only when the new version is serving traffic.
 
 4. Verify your deployment at the URL printed by the CLI. Append `/api/agents` to confirm it returns a JSON list of your agents.
@@ -87,7 +91,7 @@ See [Environments](https://mastra.ai/docs/mastra-platform/environments) for the
 
 ## Choose a region
 
-Pass `--region` when a deploy creates a new environment to control where it runs. Use the `us` or `eu` shorthand:
+When a deploy creates an environment interactively, select the United States or Europe from the region prompt. To skip the prompt, pass `--region` with the `us` or `eu` shorthand:
 
 ```bash
 mastra deploy --env production --region eu
@@ -97,7 +101,7 @@ The region is fixed when the environment is created. Databases attached to an en
 
 ## Preflight checks
 
-Preflight validates the built output before anything includes, and only flags issues in your own code:
+Preflight validates the built output before the deploy uploads and only flags issues in your own code:
 
 - **Local storage paths**: A hard block. File-backed storage (for example `file:./mastra.db`) is lost on every deploy. Preflight passes when the path is guarded by an environment variable that's set locally or stored on the platform, including values provided by a managed database:
 

package/.docs/docs/mastra-platform/overview.md

@@ -23,6 +23,7 @@ Choose the path that matches what you want to do:
 - **Add hosted observability**: Use [Observability](https://mastra.ai/docs/mastra-platform/observability) to collect searchable traces, logs, and metrics across projects and deploys. Start here if you want monitoring without deploying Studio or Server first.
 - **Deploy Studio**: Use [Studio](https://mastra.ai/docs/mastra-platform/studio) to host the visual development environment for your team. Start here if you want a shared UI for testing agents and running workflows, as well as inspecting traces.
 - **Deploy Server**: Use [Server](https://mastra.ai/docs/mastra-platform/server) to run your Mastra application as a production API server. Start here when you’re ready to serve agents, tools, and workflows from the cloud.
+- **Build a software factory:** Deploy [Mastra Factory](https://factory.mastra.ai) to Mastra platform and connect your repository to turn issues into plans, implementations, and reviewed pull requests.
 
 ## Key concepts
 

package/.docs/docs/sandbox/overview.md

@@ -6,7 +6,7 @@
 
 A sandbox gives your agent an isolated environment where it can run commands, execute code, install dependencies, and manage processes. This lets agents perform work that would be risky, resource-intensive, or impractical to run directly inside your application.
 
-Sandboxes are often temporary, so files created inside them may disappear when the environment stops. A [filesystem](https://mastra.ai/docs/sandbox/filesystem) gives the agent a place to read, write, and [search](https://mastra.ai/docs/sandbox/search) files that can outlive the sandbox. You can use one to keep outputs between runs, seed a new sandbox with existing files, or give the agent documents it can search while working. Filesystems also work without a sandbox, for example when an agent only needs a knowledge base or access to files in a service such as Google Drive.
+Sandboxes are often temporary, so files created inside them may disappear when the environment stops. A [filesystem](https://mastra.ai/docs/sandbox/filesystem) gives the agent a place to read, write, and [search](https://mastra.ai/docs/sandbox/search) files that can outlive the sandbox. You can use one to keep outputs between runs, seed a new sandbox with existing files, or give the agent documents it can search while working. Filesystems also work without a sandbox, for example when an agent only needs a knowledge base or access to files in a service such as Google Drive. A real-world example is [Mastra Factory](https://factory.mastra.ai/) which uses sandboxes to give coding-agent sessions an environment for repository checkouts, dependencies, and commands.
 
 ## When to use sandboxes
 
@@ -344,4 +344,5 @@ await sandbox.executeCommand('node', ['scripts/download-reports.js'], {
 
 - [`SandboxProcessManager` reference](https://mastra.ai/reference/workspace/process-manager)
 - [Sandbox provider interface](https://mastra.ai/reference/workspace/sandbox)
-- [Filesystem](https://mastra.ai/docs/sandbox/filesystem)
+- [Filesystem](https://mastra.ai/docs/sandbox/filesystem)
+- [Mastra Factory](https://factory.mastra.ai)

package/.docs/reference/migrations/upgrade-to-v1/overview.md

@@ -10,7 +10,7 @@ Mastra v1 was released in January 2026. We recommend starting any new projects w
 
 This guide covers the breaking changes when upgrading from Mastra 0.x to v1.0. The migration is organized by package and feature area to help you systematically update your codebase.
 
-> **Need help?:** Need help with the migration? Join our [Discord community](https://discord.gg/BTYqqHKUrf) to ask questions.
+> **Need help?:** Need help with the migration? Join our [Discord community](https://discord.gg/mastra-ai) to ask questions.
 
 > **Coming from Mastra Cloud?:** The legacy Mastra Cloud product has been replaced by the [Mastra platform](https://mastra.ai/docs/mastra-platform/overview), which splits hosting into two separate products: **Studio** (visual environment, observability) and **Server** (production API). Because old Mastra Cloud access tokens don't work with Mastra platform, create new ones with `mastra auth tokens create`.
 >

package/.docs/reference/observability/tracing/trace-query.md

@@ -111,6 +111,9 @@ Hono and Fastify enforce the request-body limit before JSON parsing. Express and
 | Score             | `scorerId`, `scorerVersion`, `scoreSource`, `entityVersionId`, `parentEntityVersionId`, `rootEntityVersionId`                                                | `eq`, `ne`, `in`, `notIn`, `exists`, `notExists`                           |
 | Score             | `score`, `timestamp`                                                                                                                                         | `eq`, `ne`, `in`, `notIn`, `lt`, `lte`, `gt`, `gte`, `exists`, `notExists` |
 | Score             | `spanId`                                                                                                                                                     | `exists`, `notExists`                                                      |
+| Feedback          | `feedbackType`, `feedbackSource`, `feedbackUserId`, `sourceId`, `entityVersionId`, `parentEntityVersionId`, `rootEntityVersionId`                            | `eq`, `ne`, `in`, `notIn`, `exists`, `notExists`                           |
+| Feedback          | `value`, `timestamp`                                                                                                                                         | `eq`, `ne`, `in`, `notIn`, `lt`, `lte`, `gt`, `gte`, `exists`, `notExists` |
+| Feedback          | `comment`                                                                                                                                                    | `exists`, `notExists`                                                      |
 
 Compose predicates with `{ op: 'and', args: [...] }`, `{ op: 'or', args: [...] }`, and `{ op: 'not', arg: ... }`. Comparison predicates place a field reference on the left and a literal on the right. Membership predicates use a field reference in `value` and a homogeneous literal array in `set`.
 
@@ -270,6 +273,45 @@ The key must name one top-level property. Empty keys and nested paths are reject
 
 Metadata fields aren't available for grouping or field discovery.
 
+### Filter by feedback
+
+Every condition inside one `feedback.some` or `feedback.none` clause applies to the same current feedback record. `feedbackType` and `feedbackSource` are exact application-defined strings rather than built-in enums. This query finds traces with a numeric patient rating below zero:
+
+```typescript
+const negativePatientRating = {
+  feedback: {
+    some: {
+      op: 'and',
+      args: [
+        { op: 'eq', left: { path: 'feedbackType' }, right: { literal: 'rating' } },
+        { op: 'eq', left: { path: 'feedbackSource' }, right: { literal: 'patient' } },
+        { op: 'lt', left: { path: 'value' }, right: { literal: 0 } },
+      ],
+    },
+  },
+}
+```
+
+Strict stored-value types are the portable contract for feedback predicates. PostgreSQL and ClickHouse distinguish numeric `3` from textual `'3'` for equality and ordered comparisons. DuckDB currently persists feedback values as `VARCHAR`, so numeric-looking strings may be coerced for equality and ordered numeric predicates. OBS-306 will remove this DuckDB exception through typed persistence. Ordered operators require a finite numeric literal. `eq` and `ne` accept one string or number, while `in` and `notIn` require a non-empty set containing only strings or only numbers. `exists` and `notExists` test for either value type.
+
+Use `none` to select traces without a matching record. Traces with no feedback also match:
+
+```typescript
+const missingClinicianReview = {
+  feedback: {
+    none: {
+      op: 'and',
+      args: [
+        { op: 'eq', left: { path: 'feedbackType' }, right: { literal: 'clinical-review' } },
+        { op: 'eq', left: { path: 'feedbackSource' }, right: { literal: 'clinician' } },
+      ],
+    },
+  },
+}
+```
+
+Feedback `timestamp` predicates are independent of the root `timeRange`. Use `comment` only with `exists` or `notExists`. Comment contents aren't searchable. The deprecated feedback fields `source` and `userId` aren't available. Use `feedbackSource` and `feedbackUserId`.
+
 ## Responses
 
 An ungrouped query returns only lightweight completed traces:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mastra/mcp-docs-server",
-  "version": "1.2.25-alpha.6",
+  "version": "1.2.25-alpha.8",
   "description": "MCP server for accessing Mastra.ai documentation, changelogs, and news.",
   "type": "module",
   "main": "dist/index.js",
@@ -27,7 +27,7 @@
     "jsdom": "^26.1.0",
     "local-pkg": "^1.1.2",
     "zod": "^4.4.3",
-    "@mastra/core": "1.66.0-alpha.3",
+    "@mastra/core": "1.66.0-alpha.4",
     "@mastra/mcp": "^1.17.3"
   },
   "devDependencies": {
@@ -44,9 +44,9 @@
     "tsx": "^4.23.1",
     "typescript": "^7.0.2",
     "vitest": "4.1.10",
-    "@internal/types-builder": "0.0.106",
     "@internal/lint": "0.0.131",
-    "@mastra/core": "1.66.0-alpha.3"
+    "@internal/types-builder": "0.0.106",
+    "@mastra/core": "1.66.0-alpha.4"
   },
   "homepage": "https://mastra.ai",
   "repository": {