@cplace/mcp-server 1.5.1 → 1.5.2
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.
- package/README.md +0 -2
- package/dist/widget-specifications/_research_from_ga_products/cf-cplace-treeTableWidget/research.md +2 -0
- package/dist/widget-specifications/cf.cplace.dynamicCodeBlockWidget.dynamicCodeBlockWidget/_overview.md +4 -1
- package/dist/widget-specifications/cf.cplace.lowCodeWidgets.lowCodeText/_overview.md +1 -0
- package/dist/widget-specifications/cf.cplace.treeTableWidget/_overview.md +4 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -35,8 +35,6 @@ claude mcp add --transport http cplace https://mcp.cplace.com --header "cplace-u
|
|
|
35
35
|
}
|
|
36
36
|
```
|
|
37
37
|
|
|
38
|
-
Authentication is handled through the remote server's OAuth flow — no API token configuration needed in the MCP client.
|
|
39
|
-
|
|
40
38
|
### Local Installation (Alternative)
|
|
41
39
|
|
|
42
40
|
If you prefer to run the MCP server locally (e.g., for development or air-gapped environments), you can install it via npx.
|
package/dist/widget-specifications/_research_from_ga_products/cf-cplace-treeTableWidget/research.md
CHANGED
|
@@ -62,6 +62,7 @@ The `cf.cplace.treeTableWidget` is a concrete implementation of the platform's a
|
|
|
62
62
|
- Create dashboard pages with hierarchical navigation
|
|
63
63
|
- Provide overview pages showing entire page structures
|
|
64
64
|
- Serve as entry points to complex information architectures
|
|
65
|
+
- Place on type layout pages where the embedding page is a concrete data instance
|
|
65
66
|
|
|
66
67
|
### When to Use This Widget:
|
|
67
68
|
|
|
@@ -385,6 +386,7 @@ src/main/resources/
|
|
|
385
386
|
2. **Single Hierarchy**: Uses one parent attribute at a time (no multiple relationship types)
|
|
386
387
|
3. **Platform Rendering**: Limited to platform's rendering capabilities (can't customize without TypeScript)
|
|
387
388
|
4. **Error Handling**: Throws `TreeUnconstructableException` if embedded in a TypeDefinition page
|
|
389
|
+
5. **Dashboard limitation without explicit root**: Root node resolves as: (1) connected table selection, (2) configured `rootNode`, (3) embedding page fallback. On dashboards without a configured root, the fallback uses the dashboard page — which has no hierarchy children — resulting in a single empty row. Configure an explicit `rootNode` to use on dashboards, or prefer `cf.platform.embeddedSearchAsTable` with grouping.
|
|
388
390
|
|
|
389
391
|
### Best Practices:
|
|
390
392
|
|
|
@@ -2,6 +2,8 @@
|
|
|
2
2
|
|
|
3
3
|
Represents a dynamically generated code block with content defined using cplaceJS. The widget displays formatted code snippets with syntax highlighting, where the code content is generated dynamically through a cplaceJS script. This widget is useful for showing code examples, configuration snippets, or any text content that benefits from code formatting, with the content determined at runtime based on page data or other dynamic criteria.
|
|
4
4
|
|
|
5
|
+
> **Text-only rendering**: This widget renders content as **plain text** inside `<pre><code>` using `ng-bind` (equivalent to `textContent`). It does **not** render HTML. Any HTML tags in the script return value are displayed as literal text, not rendered. For scripted HTML output (KPI cards, pivot tables, dynamic banners, formatted content), use the **Low-Code Text** widget (`cf.cplace.lowCodeWidgets.lowCodeText`) embedded inside a **Rich String** or **Text without Widget Frame** container.
|
|
6
|
+
|
|
5
7
|
**Use when you need to:**
|
|
6
8
|
- Display code examples or snippets that change based on page context
|
|
7
9
|
- Show dynamically generated configuration files or scripts
|
|
@@ -10,7 +12,7 @@ Represents a dynamically generated code block with content defined using cplaceJ
|
|
|
10
12
|
|
|
11
13
|
**Alternatives:**
|
|
12
14
|
- **Rich Text Widget** - For static code blocks or when content doesn't need to be generated dynamically
|
|
13
|
-
- **Low-Code Text Widget** - For
|
|
15
|
+
- **Low-Code Text Widget** (`cf.cplace.lowCodeWidgets.lowCodeText`) - For scripted HTML output rendered inline within a rich string container
|
|
14
16
|
|
|
15
17
|
## Operating Modes
|
|
16
18
|
|
|
@@ -40,6 +42,7 @@ Use the Dynamic Code Block when:
|
|
|
40
42
|
|
|
41
43
|
Avoid when:
|
|
42
44
|
- The code content is static and doesn't change (use Rich Text instead)
|
|
45
|
+
- You need rendered HTML output such as KPI cards, formatted tables, or styled content (use Low-Code Text embedded in a Rich String instead)
|
|
43
46
|
- You need user interaction with the code (editing, copying with click)
|
|
44
47
|
- The output is better suited to table or structured display
|
|
45
48
|
- Performance is critical and the script is computationally expensive
|
|
@@ -53,6 +53,7 @@ This widget can **only** be embedded inside rich string widgets. It cannot be pl
|
|
|
53
53
|
## Design Considerations
|
|
54
54
|
|
|
55
55
|
### When to Use This Widget
|
|
56
|
+
- You need scripted HTML output — this is the correct widget for rendering HTML from cplaceJS scripts (not `dynamicCodeBlockWidget`, which is text-only)
|
|
56
57
|
- You need dynamic, script-computed content within a rich text layout
|
|
57
58
|
- The content should update reactively based on connected table interactions
|
|
58
59
|
- You want inline computed values (metrics, status text, formatted data) mixed with static rich text
|
|
@@ -19,7 +19,10 @@ Show document folder structures and content hierarchies such as chapters, sectio
|
|
|
19
19
|
Display product hierarchies, component breakdowns, and system architectures. Navigate through technical structures and dependencies.
|
|
20
20
|
|
|
21
21
|
### Navigation and Overview Pages
|
|
22
|
-
|
|
22
|
+
Provide overview pages showing entire page structures and serve as entry points to complex information architectures. Place this widget on type layout pages where the embedding page is a concrete data instance with hierarchy relationships.
|
|
23
|
+
|
|
24
|
+
### Limitations
|
|
25
|
+
- **Not suitable for dashboards without explicit root node configuration**: The widget resolves its root node in priority order: (1) connected table selection, (2) explicitly configured `rootNode`, (3) embedding page fallback. On a dashboard page without a configured root node, the fallback uses the dashboard page itself as root. Since no data pages reference the dashboard page through hierarchy attributes, the tree shows only the dashboard page as a single empty row. To use this widget on a dashboard, configure an explicit `rootNode` — or prefer `cf.platform.embeddedSearchAsTable` with grouping for dashboard-based hierarchical views.
|
|
23
26
|
|
|
24
27
|
## Design Considerations
|
|
25
28
|
|