@mastra/mcp-docs-server 1.2.23-alpha.15 → 1.2.23-alpha.16

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 (2) hide show
  1. package/.docs/docs/mastra-platform/trace-intelligence.md +17 -4
  2. package/package.json +4 -4
package/.docs/docs/mastra-platform/trace-intelligence.md CHANGED
@@ -4,7 +4,7 @@
4
4
 
5
5
  # Trace Intelligence on Mastra platform
6
6
 
7
- Trace Intelligence finds recurring patterns across your agent's interactions. It analyzes traces captured by Mastra Observability and produces trace signals for four dimensions. It then clusters similar trace signals into themes.
7
+ Trace Intelligence finds recurring patterns across your agent's interactions. It analyzes traces captured by Mastra Observability and produces trace signals for four built-in dimensions plus any custom signals enabled for the project. It then clusters similar trace signals into themes.
8
8
 
9
9
  Use Trace Intelligence to investigate questions such as:
10
10
 
@@ -37,7 +37,7 @@ Use representative traffic. A small set of repeated test prompts can produce unr
37
37
 
38
38
  ## Understand the analysis
39
39
 
40
- Each analyzable completed trace produces four trace signals:
40
+ Each analyzable completed trace produces four built-in trace signals, along with any custom signals enabled for the project:
41
41
 
42
42
  | Trace signal | Meaning |
43
43
  | ------------- | ------------------------------------------------------------------------------------------------------ |
@@ -74,11 +74,24 @@ A theme can persist, disappear, split, merge, or return across snapshots. Treat
74
74
 
75
75
  ## Use the Trace Intelligence page
76
76
 
77
- 1. Use the **Agent** selector to switch between agents after their first themes are ready and analysis becomes available.
77
+ 1. Open **Intelligence** to see the entity index. Search or sort the index, then select an entity to open its analysis.
78
78
  2. Select a theme in the flow to open its details and filter every column to traces containing that theme.
79
79
  3. The details panel shows the theme's description, its share of the snapshot, paged example summaries, and a trend of its trace count over time.
80
80
  4. Select **Clear filter** to restore the complete flow.
81
81
 
82
+ Entities appear while their signals are still collecting or processing. The index shows each entity's analyzed trace count, ready and enabled signal counts, lifecycle status, and last update.
83
+
84
+ ### Configure a custom signal
85
+
86
+ Users with project management permission can configure custom signals without leaving Intelligence:
87
+
88
+ 1. Return to the entity index and select **Signal settings**.
89
+ 2. Select **Create signal**, provide a stable signal name, display label, description, and signal instructions, then save it. Definitions and their versions are shared across the organization.
90
+ 3. Enable the signal under **Current project**. Project enablement affects only the current project and applies to newly processed traces.
91
+ 4. Open an entity from the index and follow its signal status as it moves from collecting to processing and ready.
92
+
93
+ You can edit a custom signal's label, description, or instructions. Instruction changes create a new version and apply only to new traces. You can also archive definitions that should no longer be available or restore archived definitions later.
94
+
82
95
  You can also:
83
96
 
84
97
  - Select **Noise** in the flow to inspect its share and generated example summaries.
@@ -96,7 +109,7 @@ Confirm that Mastra enrolled the correct project, that you use the beta-compatib
96
109
 
97
110
  ### An agent is missing
98
111
 
99
- Confirm that its completed traces are listed under **Traces**. The agent is listed only after its first themes are ready. If it recently reached 100 traces, allow time for asynchronous processing.
112
+ Confirm that its completed traces are listed under **Traces** and that the project is enrolled. Trace Intelligence lists an entity after signal generation begins, before its first themes are ready. If it recently reached 100 traces, allow time for asynchronous processing.
100
113
 
101
114
  ### The relationship flow is unavailable
102
115
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mastra/mcp-docs-server",
3
- "version": "1.2.23-alpha.15",
3
+ "version": "1.2.23-alpha.16",
4
4
  "description": "MCP server for accessing Mastra.ai documentation, changelogs, and news.",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
@@ -27,8 +27,8 @@
27
27
  "jsdom": "^26.1.0",
28
28
  "local-pkg": "^1.1.2",
29
29
  "zod": "^4.4.3",
30
- "@mastra/mcp": "^1.17.3-alpha.2",
31
- "@mastra/core": "1.64.0-alpha.7"
30
+ "@mastra/core": "1.64.0-alpha.8",
31
+ "@mastra/mcp": "^1.17.3-alpha.2"
32
32
  },
33
33
  "devDependencies": {
34
34
  "@hono/node-server": "^2.0.0",
@@ -46,7 +46,7 @@
46
46
  "vitest": "4.1.10",
47
47
  "@internal/lint": "0.0.129",
48
48
  "@internal/types-builder": "0.0.104",
49
- "@mastra/core": "1.64.0-alpha.7"
49
+ "@mastra/core": "1.64.0-alpha.8"
50
50
  },
51
51
  "homepage": "https://mastra.ai",
52
52
  "repository": {