@cplace/mcp-server 1.3.14

package/dist/widget-specifications/de.2lforge.toolbar.dropDownWidget/_overview.md

@@ -0,0 +1,58 @@
+## Overview
+
+This widget provides a comprehensive demonstration and testing page for three specialized dropdown components from the 2lForge Toolbar plugin. It showcases reusable selection UI elements designed for form-based data entry, filtering interfaces, and interactive selection scenarios.
+
+The widget serves primarily as a demo/test page displaying working examples of:
+- **Single Dropdown**: Select one value from a list
+- **Multi Dropdown**: Select multiple values from a list
+- **Draggable Dropdown**: Select and reorder multiple values via drag-and-drop
+
+All dropdown components feature consistent Bootstrap-based styling, type-safe implementation, and rich configurability including optional search/filter functionality, reset capabilities, change tracking, and custom CSS styling per entry.
+
+## Use Cases
+
+### 1. Simple Form Selection
+Select a single option from a predefined list (status, priority, category). The single dropdown component provides visual selection indicators and optional reset functionality for clearing selections.
+
+### 2. Multi-Criteria Filtering
+Filter data by selecting multiple values simultaneously (tags, departments, project phases). The multi dropdown component intelligently displays either a single label or a count (e.g., "3 elements") based on the number of selections.
+
+### 3. Large List Navigation with Search
+Select from extensive lists using the built-in search/filter functionality (countries, products, users). The searchable dropdown automatically focuses the filter input and provides real-time filtering by label text.
+
+### 4. Prioritized Selection and Ordering
+Select and arrange multiple items in priority order using drag-and-drop interaction (task prioritization, step sequences, preference ranking). The draggable dropdown maintains selection order as a significant part of the data model.
+
+### 5. Color-Coded Options
+Differentiate option types visually using custom CSS classes per entry (severity levels, status indicators, risk classifications). Each entry can include CSS classes for custom styling.
+
+### 6. Resettable Optional Fields
+Explicitly clear selections using the reset functionality (unassigning tickets, clearing optional filters). The reset-active mode allows clicking the current selection to deselect it.
+
+### 7. Component Testing and Development
+Test and demonstrate dropdown functionality with working code examples. The widget serves as a comprehensive demo page showing all configuration options, edge cases, and integration patterns for developers building forms with the 2lForge Toolbar components.
+
+## Design Considerations
+
+### Component Selection
+- Use **Single Dropdown** for mutually exclusive choices where one value must be selected
+- Use **Multi Dropdown** when multiple selections are needed but order doesn't matter
+- Use **Draggable Dropdown** when the order of selections is significant and users need to prioritize/sequence items
+
+### Search Functionality
+Enable the optional `searchable` attribute for lists with more than ~10-15 items to improve user experience. The search component automatically focuses on dropdown open and clears on close.
+
+### Type Safety
+All dropdown components support generic types (string, number, boolean, custom) with automatic type inference from the first entry. Explicitly declare types when entries are empty or ambiguous.
+
+### Default Values
+Configure defaults using either `defaultRef` (object reference) or `defaultString` (parsed string). For multi/draggable dropdowns, use the `defaultStringSeparator` to customize parsing of comma-separated value strings.
+
+## Related Widgets
+
+### Within ToolbarPlugin
+- **DatePickerWidgetDefinition** (`de.2lforge.toolbar.datePickerWidget`): Companion date selection components with similar toolbar-based UI patterns
+- **MiscWidgetDefinition** (`de.2lforge.toolbar.miscWidget`): Other complementary toolbar UI elements
+
+### Alternative Selection Patterns
+Consider standard cplace form widgets for basic selection needs when the advanced features of these toolbar dropdowns (search, drag-drop, custom styling) are not required.

package/dist/widget-specifications/de.2lforge.toolbar.dropDownWidget/_summary.md

@@ -0,0 +1 @@
+Provides three reusable dropdown components (single selection, multi-selection, and draggable multi-selection with ordering) for form-based data entry and filtering. Part of the 2lForge Toolbar plugin offering generic, configurable selection UI elements with optional search and reset functionality.

package/dist/widget-specifications/de.2lforge.toolbar.miscWidget/_catalog-data.json

@@ -0,0 +1,12 @@
+{
+  "Widget": "de.2lforge.toolbar.miscWidget",
+  "Description": null,
+  "Localized Name": "{\"en\":\"miscWidget\",\"de\":\"miscWidget\"}",
+  "Icon": "cf-widget",
+  "Plugin": "de.toolforge.toolbar",
+  "App": "de.toolforge.toolbar",
+  "Localized App Name": "{\"en\":\"ToolbarApp\",\"de\":\"ToolbarApp\"}",
+  "Repository": "cplace-2lforge-toolbar",
+  "* Details DE": null,
+  "* Details EN": null
+}

package/dist/widget-specifications/de.2lforge.toolbar.miscWidget/_meta.json

@@ -0,0 +1,8 @@
+{
+  "tags": [
+    "form",
+    "attributes",
+    "inline-edit"
+  ],
+  "requiredApp": "de.toolforge.toolbar"
+}

package/dist/widget-specifications/de.2lforge.toolbar.miscWidget/_overview.md

@@ -0,0 +1,43 @@
+## Overview
+
+The Misc Widget is an internal development and testing tool that demonstrates the usage of various toolbar components from the 2lforge Toolbar plugin. It displays interactive examples alongside their HTML code snippets, helping developers understand how to implement toolbar components in their own pages.
+
+This widget is **not intended for end-user production use**. It serves as living documentation and a testing playground for the toolbar component library.
+
+## Use Cases
+
+### Developer Learning and Reference
+Developers learning the toolbar component library can view this widget to see working examples of buttons, toggle switches (flipflops), and date pickers alongside the HTML code required to implement them.
+
+### Component Testing
+QA engineers and developers can use this widget to validate that toolbar components work correctly in different contexts, including standalone usage, within forms, and within nested forms.
+
+### Integration Testing
+The widget helps verify that toolbar components integrate properly with AngularJS forms, validating form data collection and various submission mechanisms (console, AJAX, GET, POST).
+
+## Demonstrated Components
+
+The widget showcases components from the 2lforge Toolbar plugin:
+
+- **tlf-button**: Action buttons with customizable callbacks
+- **tlf-submit**: Form submission buttons supporting multiple methods (console, ajax, get, post)
+- **tlf-flipflop**: Toggle switches with two-state values
+- **tlf-date-range-picker**: Date range selection components
+
+## Design Considerations
+
+### When to Use This Widget
+- When learning how to use toolbar components
+- When testing toolbar functionality during development
+- When validating component behavior in different form contexts
+
+### When NOT to Use This Widget
+- In production pages visible to end users
+- As a replacement for actual form or input widgets
+- For any purpose other than development and testing
+
+## Related Widgets
+
+Other toolbar demonstration widgets in the 2lforge Toolbar plugin:
+- `de.2lforge.toolbar.datePickerWidget` - Focused on date picker component testing
+- `de.2lforge.toolbar.dropDownWidget` - Focused on dropdown component testing

package/dist/widget-specifications/de.2lforge.toolbar.miscWidget/_summary.md

@@ -0,0 +1 @@
+A developer-facing demonstration widget that showcases toolbar components including buttons, toggle switches, and date pickers with interactive examples and code snippets.

package/dist/widget-specifications/de.visualistik.visualRoadmap.widget/_catalog-data.json

@@ -0,0 +1,12 @@
+{
+  "Widget": "de.visualistik.visualRoadmap.widget",
+  "Description": null,
+  "Localized Name": "{\"en\":\"Visual Roadmap\",\"de\":\"Visual Roadmap\"}",
+  "Icon": "cf-widget",
+  "Plugin": "de.visualistik.visualRoadmap",
+  "App": "de.visualistik.visualRoadmap",
+  "Localized App Name": "{\"en\":\"VisualRoadmapApp\",\"de\":\"VisualRoadmapApp\"}",
+  "Repository": "cplace-gtv",
+  "* Details DE": null,
+  "* Details EN": null
+}

package/dist/widget-specifications/de.visualistik.visualRoadmap.widget/_meta.json

@@ -0,0 +1,11 @@
+{
+  "tags": [
+    "timeline",
+    "time-series",
+    "low-code",
+    "connected",
+    "selectable",
+    "searchable"
+  ],
+  "requiredApp": "de.visualistik.visualRoadmap"
+}

package/dist/widget-specifications/de.visualistik.visualRoadmap.widget/_overview.md

@@ -0,0 +1,47 @@
+## Overview
+
+The Visual Roadmap widget renders hierarchical, time-based data in a roadmap format. It transforms cplace page data into structured roadmap elements through a configurable JavaScript script, allowing visualization of project timelines, releases, milestones, or any date-based data with rich visual customization options.
+
+The widget uses a three-level hierarchy: **groups** contain **swimlanes**, which contain **base items** displayed on a timeline.
+
+## Use Cases
+
+### Project Timeline Visualization
+Display project phases, milestones, and deliverables on a timeline. Organize projects into categories (groups) and sub-categories (swimlanes) to visualize start and end dates for different project elements.
+
+### Release Planning and Roadmapping
+Show product releases and feature rollouts over time. Group features by release cycles or product lines and categorize items using visual indicators like colors, patterns, and icons.
+
+### Portfolio Management
+Aggregate multiple projects or initiatives into a unified view. Group by business units, departments, or strategic themes to provide executive-level overviews of organizational initiatives.
+
+### Resource Planning
+Display resource allocation across different projects or teams. Visualize overlapping timelines and track different work item types with distinct visual styling.
+
+## Design Considerations
+
+### Scripting Requirement
+The widget requires a JavaScript script to transform source pages into the roadmap data structure. This script has access to `pages` (search results) and `embeddingPage` (context), and can use the cplace low-code API for complex data transformations.
+
+### Visual Configuration
+All visual customization (colors, hatching patterns, icons) is defined within the transformation script rather than through UI configuration. This provides maximum flexibility but requires script modification to change visual properties.
+
+### Data Sources
+The widget supports three data source modes:
+- **Search-based**: Dynamically find pages via search query
+- **Connected Table**: Link to a table widget for synchronized data
+- **Manual Selection**: Explicitly select specific pages
+
+### Performance Considerations
+The script executes on each data load, and all matching pages are loaded at once without pagination. Consider the volume of data when configuring search queries.
+
+## Common Pitfalls
+
+- **Date Format**: The script output must use the format "MM-dd-yyyy" for dates
+- **Script Complexity**: Complex transformations require solid JavaScript knowledge
+- **No Pagination**: Large datasets may impact performance
+
+## Related Patterns
+
+- **Master-Detail with Table**: Connect to a table widget to filter roadmap data based on table selection
+- **Event Synchronization**: The widget emits selection events that can be used with other connected widgets

package/dist/widget-specifications/de.visualistik.visualRoadmap.widget/_summary.md

@@ -0,0 +1 @@
+Displays timeline-based data in a customizable roadmap visualization, organizing items into groups and swimlanes with configurable visual properties including colors, hatching patterns, and icons.

package/dist/widget-specifications/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/widget-specifications/index.ts"],"names":[],"mappings":"AA+BA,MAAM,MAAM,cAAc,GAAG;IAC3B,IAAI,CAAC,EAAE,MAAM,EAAE,CAAC;IAChB,WAAW,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;CAC7B,CAAC;AAGF,MAAM,MAAM,oBAAoB,GAAG,MAAM,CAAC,MAAM,EAAE;IAChD,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,eAAe,CAAC,EAAE,MAAM,CAAC;IACzB,KAAK,CAAC,EAAE,cAAc,CAAC;IACvB,CAAC,YAAY,EAAE,MAAM,GAAG,MAAM,GAAG,cAAc,GAAG,SAAS,CAAC;CAC7D,CAAC,CAAC;AA2EH,eAAO,MAAM,qBAAqB,sBAA6B,CAAC"}

package/dist/widget-specifications/index.js

@@ -0,0 +1,55 @@
+import { readFileSync, readdirSync } from 'fs';
+import { fileURLToPath } from 'url';
+import { dirname, join } from 'path';
+const __filename = fileURLToPath(import.meta.url);
+const __dirname = dirname(__filename);
+function loadWidgetSpecifications() {
+    const specs = {};
+    try {
+        const entries = readdirSync(__dirname, { withFileTypes: true });
+        const widgetKindDirs = entries.filter(d => d.isDirectory());
+        for (const dir of widgetKindDirs) {
+            const widgetKind = dir.name;
+            const widgetDir = join(__dirname, widgetKind);
+            specs[widgetKind] = {};
+            const files = readdirSync(widgetDir);
+            const mdFiles = files.filter(f => f.endsWith('.md'));
+            for (const mdFile of mdFiles) {
+                const attrShortName = mdFile.replace('.md', '');
+                try {
+                    const content = readFileSync(join(widgetDir, mdFile), 'utf8');
+                    if (attrShortName === '_summary') {
+                        specs[widgetKind]['_summary'] = content;
+                    }
+                    else if (attrShortName === '_overview') {
+                        specs[widgetKind]['_overview'] = content;
+                    }
+                    else if (attrShortName === '_implementation') {
+                        specs[widgetKind]['_implementation'] = content;
+                    }
+                    else {
+                        const fullAttrName = `${widgetKind}.${attrShortName}`;
+                        specs[widgetKind][fullAttrName] = content;
+                    }
+                }
+                catch (error) {
+                    console.error(`Warning: Could not read widget specification ${widgetDir}/${mdFile}:`, error);
+                }
+            }
+            const metaPath = join(widgetDir, '_meta.json');
+            try {
+                const metaContent = readFileSync(metaPath, 'utf8');
+                const metaData = JSON.parse(metaContent);
+                specs[widgetKind]['_meta'] = metaData;
+            }
+            catch {
+            }
+        }
+    }
+    catch (error) {
+        console.error('Warning: Could not load widget specifications:', error);
+    }
+    return specs;
+}
+export const WIDGET_SPECIFICATIONS = loadWidgetSpecifications();
+//# sourceMappingURL=index.js.map

package/dist/widget-specifications/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/widget-specifications/index.ts"],"names":[],"mappings":"AAuBA,OAAO,EAAE,YAAY,EAAE,WAAW,EAAE,MAAM,IAAI,CAAC;AAC/C,OAAO,EAAE,aAAa,EAAE,MAAM,KAAK,CAAC;AACpC,OAAO,EAAE,OAAO,EAAE,IAAI,EAAE,MAAM,MAAM,CAAC;AAErC,MAAM,UAAU,GAAG,aAAa,CAAC,MAAM,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;AAClD,MAAM,SAAS,GAAG,OAAO,CAAC,UAAU,CAAC,CAAC;AA6BtC,SAAS,wBAAwB;IAC/B,MAAM,KAAK,GAAyB,EAAE,CAAC;IAEvC,IAAI,CAAC;QAEH,MAAM,OAAO,GAAG,WAAW,CAAC,SAAS,EAAE,EAAE,aAAa,EAAE,IAAI,EAAE,CAAC,CAAC;QAChE,MAAM,cAAc,GAAG,OAAO,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,WAAW,EAAE,CAAC,CAAC;QAE5D,KAAK,MAAM,GAAG,IAAI,cAAc,EAAE,CAAC;YACjC,MAAM,UAAU,GAAG,GAAG,CAAC,IAAI,CAAC;YAC5B,MAAM,SAAS,GAAG,IAAI,CAAC,SAAS,EAAE,UAAU,CAAC,CAAC;YAC9C,KAAK,CAAC,UAAU,CAAC,GAAG,EAAE,CAAC;YAGvB,MAAM,KAAK,GAAG,WAAW,CAAC,SAAS,CAAC,CAAC;YACrC,MAAM,OAAO,GAAG,KAAK,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,QAAQ,CAAC,KAAK,CAAC,CAAC,CAAC;YAErD,KAAK,MAAM,MAAM,IAAI,OAAO,EAAE,CAAC;gBAC7B,MAAM,aAAa,GAAG,MAAM,CAAC,OAAO,CAAC,KAAK,EAAE,EAAE,CAAC,CAAC;gBAEhD,IAAI,CAAC;oBACH,MAAM,OAAO,GAAG,YAAY,CAAC,IAAI,CAAC,SAAS,EAAE,MAAM,CAAC,EAAE,MAAM,CAAC,CAAC;oBAG9D,IAAI,aAAa,KAAK,UAAU,EAAE,CAAC;wBAEjC,KAAK,CAAC,UAAU,CAAC,CAAC,UAAU,CAAC,GAAG,OAAO,CAAC;oBAC1C,CAAC;yBAAM,IAAI,aAAa,KAAK,WAAW,EAAE,CAAC;wBAEzC,KAAK,CAAC,UAAU,CAAC,CAAC,WAAW,CAAC,GAAG,OAAO,CAAC;oBAC3C,CAAC;yBAAM,IAAI,aAAa,KAAK,iBAAiB,EAAE,CAAC;wBAE/C,KAAK,CAAC,UAAU,CAAC,CAAC,iBAAiB,CAAC,GAAG,OAAO,CAAC;oBACjD,CAAC;yBAAM,CAAC;wBAEN,MAAM,YAAY,GAAG,GAAG,UAAU,IAAI,aAAa,EAAE,CAAC;wBACtD,KAAK,CAAC,UAAU,CAAC,CAAC,YAAY,CAAC,GAAG,OAAO,CAAC;oBAC5C,CAAC;gBACH,CAAC;gBAAC,OAAO,KAAK,EAAE,CAAC;oBACf,OAAO,CAAC,KAAK,CAAC,gDAAgD,SAAS,IAAI,MAAM,GAAG,EAAE,KAAK,CAAC,CAAC;gBAC/F,CAAC;YACH,CAAC;YAGD,MAAM,QAAQ,GAAG,IAAI,CAAC,SAAS,EAAE,YAAY,CAAC,CAAC;YAC/C,IAAI,CAAC;gBACH,MAAM,WAAW,GAAG,YAAY,CAAC,QAAQ,EAAE,MAAM,CAAC,CAAC;gBACnD,MAAM,QAAQ,GAAG,IAAI,CAAC,KAAK,CAAC,WAAW,CAAC,CAAC;gBACzC,KAAK,CAAC,UAAU,CAAC,CAAC,OAAO,CAAC,GAAG,QAAQ,CAAC;YACxC,CAAC;YAAC,MAAM,CAAC;YAET,CAAC;QACH,CAAC;IACH,CAAC;IAAC,OAAO,KAAK,EAAE,CAAC;QACf,OAAO,CAAC,KAAK,CAAC,gDAAgD,EAAE,KAAK,CAAC,CAAC;IACzE,CAAC;IAED,OAAO,KAAK,CAAC;AACf,CAAC;AAGD,MAAM,CAAC,MAAM,qBAAqB,GAAG,wBAAwB,EAAE,CAAC"}

package/dist/widget-specifications/msg.scripts.imagegallery.basic/_catalog-data.json

@@ -0,0 +1,12 @@
+{
+  "Widget": "msg.scripts.imagegallery.basic",
+  "Description": "{\"en\":\"Gallery for displaying PDF documents and web graphic files of a page.\",\"de\":\"Galerie zur Anzeige von PDF-Dokumenten und Web-Grafikdateien einer Seite.\"}",
+  "Localized Name": "{\"en\":\"Document Gallery\",\"de\":\"Dokumentengalerie\"}",
+  "Icon": "cf-widget",
+  "Plugin": "com.msgsystems.cplace.imagegallery",
+  "App": "cf.cplace.platform",
+  "Localized App Name": "{\"en\":\"cplace Basis\",\"de\":\"cplace Basis\"}",
+  "Repository": "cplace-paw",
+  "* Details DE": null,
+  "* Details EN": "<p><strong>More Details</strong></p><p>The 'Document Gallery' widget can be used to display a gallery of PDF documents and web graphic files on a page.</p><p><strong>Settings</strong></p><p>// * Title: Bilingual text.</p><p>// * Page:</p><p>// * Height:</p><p>// * Ratio (e.g. \"4/3\"):</p><p>// * Show widget frame*: True/false.</p>"
+}

package/dist/widget-specifications/msg.scripts.imagegallery.basic/_meta.json

@@ -0,0 +1,10 @@
+{
+  "tags": [
+    "files",
+    "media",
+    "gallery",
+    "read-only",
+    "detail-view"
+  ],
+  "requiredApp": null
+}

package/dist/widget-specifications/msg.scripts.imagegallery.basic/_overview.md

@@ -0,0 +1,55 @@
+## Overview
+
+The Document Gallery widget provides a gallery for displaying PDF documents and web graphic files of a page. It transforms document attachments into a visual browsing experience, automatically collecting all viewable documents from a page, organizing them into a slideshow format, and providing intuitive navigation through thumbnails or direct clicking. Rather than displaying documents as a simple list, it presents them in a full-featured gallery/carousel interface powered by the Fotorama library.
+
+The widget handles multiple media types seamlessly:
+- **Images** (JPG, JPEG, BMP, GIF, TIFF, SVG, PNG) display directly
+- **Documents** (PDF, ODP presentations) render via an embedded viewer (ViewerJS)
+- **Videos** (MP4, MOV) play with native HTML5 controls
+
+## Use Cases
+
+### Project Photo Documentation
+When a project page has multiple photos documenting progress, milestones, or deliverables, this widget allows stakeholders to browse through all images in a polished gallery format rather than viewing them individually.
+
+### Product/Asset Image Showcase
+For pages representing products, assets, or inventory items that have multiple associated images, this widget enables users to see all product views in an engaging slideshow format.
+
+### Presentation Viewing
+When ODP or PDF presentations are attached to a page, users can view them directly within the widget without downloading, making it easy to share slide decks or reports.
+
+### Video Collection Display
+For pages with attached video content (MP4, MOV), the widget provides an integrated video player experience, useful for training materials, recorded meetings, or media assets.
+
+### Document Hub Pages
+A page can be configured to display documents from another page (via the BASEPAGE configuration), allowing creation of document "hub" views that aggregate content from different sources.
+
+## Design Considerations
+
+### When to Use This Pattern
+- When documents are primarily visual (images, presentations, videos)
+- When users need to browse through multiple related documents
+- When a polished, magazine-style presentation is desired
+- When documents should be viewable without downloading
+
+### Display Configuration
+The widget offers flexible sizing options:
+- **Height**: Set a fixed pixel height (default: 600px)
+- **Ratio**: Override height with an aspect ratio (e.g., "4/3") for responsive layouts
+- **Width**: Always 100% of the container width
+
+### Navigation Options
+- **"When required"** (default): Shows thumbnail navigation when multiple documents exist
+- **"Never"**: Hides navigation completely; users navigate by clicking or swiping
+
+### Source Flexibility
+By default, the widget displays documents from the current page. Optionally, configure the "Page" (basePage) parameter to reference documents from a different page, useful for creating document hubs or aggregated views.
+
+## Related Patterns
+
+### Alternative Widgets
+- **cf.cplace.pdfPreview** - Specialized for PDF preview only, without carousel features
+- **cf.cplace.dragAndDropImageView** - Image-focused widget with drag-and-drop positioning capabilities
+
+### When to Choose Document Gallery
+Choose this widget when you need a unified gallery experience for multiple media types. For single-document PDF viewing, cf.cplace.pdfPreview may be more appropriate. For advanced image positioning needs, cf.cplace.dragAndDropImageView offers more control.

package/dist/widget-specifications/msg.scripts.imagegallery.basic/_summary.md

@@ -0,0 +1 @@
+Gallery for displaying PDF documents and web graphic files of a page in an interactive carousel with configurable navigation and sizing options.

package/dist/widget-specifications/tag-registry.json

@@ -0,0 +1,63 @@
+{
+  "dimensions": {
+    "dataContentType": {
+      "description": "What the widget works with",
+      "tags": {
+        "attributes": "Works with page attributes/properties",
+        "files": "Handles file attachments/documents",
+        "rich-text": "Formatted text content (HTML, Wiki)",
+        "media": "Images, video, visual content",
+        "comments": "Discussion threads, feedback",
+        "references": "Page relationships, links between pages",
+        "metadata": "System info (versions, timestamps, tags)",
+        "time-series": "Date-based, time-phased data"
+      }
+    },
+    "displayFormat": {
+      "description": "How data is presented visually",
+      "tags": {
+        "chart": "Graphical visualization (bar, pie, line)",
+        "table": "Tabular rows and columns",
+        "list": "Simple sequential display",
+        "board": "Card-based layout (Kanban-style)",
+        "timeline": "Gantt, roadmap, schedule visualization",
+        "tree": "Hierarchical/nested structure",
+        "matrix": "Two-dimensional grid",
+        "form": "Input fields layout",
+        "gallery": "Visual thumbnail grid"
+      }
+    },
+    "interaction": {
+      "description": "What users can do with the widget",
+      "tags": {
+        "read-only": "Display only, no editing",
+        "inline-edit": "Edit values in place",
+        "filterable": "User can filter displayed data",
+        "sortable": "User can reorder/sort data",
+        "searchable": "Content driven by search queries",
+        "drag-drop": "Supports drag and drop interaction",
+        "selectable": "Items can be selected (for master-detail)"
+      }
+    },
+    "purposeContext": {
+      "description": "Why you'd use this widget",
+      "tags": {
+        "dashboard": "Aggregated overview, KPIs",
+        "kpi": "Simple number/metric display (prefer over charts)",
+        "detail-view": "Single page/item details",
+        "navigation": "Browsing, finding pages",
+        "collaboration": "Team communication",
+        "reporting": "Export, report generation",
+        "scheduling": "Time/resource planning"
+      }
+    },
+    "technical": {
+      "description": "Implementation considerations",
+      "tags": {
+        "low-code": "Requires cplaceJS scripting",
+        "connected": "Links to other widgets (master-detail)",
+        "container": "Holds other widgets/layouts"
+      }
+    }
+  }
+}

package/package.json

@@ -0,0 +1,70 @@
+{
+  "name": "@cplace/mcp-server",
+  "version": "1.3.14",
+  "description": "MCP server that provides Claude Desktop with tools to interact with cplace APIs",
+  "main": "dist/index.js",
+  "types": "dist/index.d.ts",
+  "type": "module",
+  "bin": {
+    "cplace-mcp-server": "dist/index.js"
+  },
+  "scripts": {
+    "build": "tsc && npm run copy-widget-specs",
+    "copy-widget-specs": "cp -r src/widget-specifications dist/ && find dist/widget-specifications -name '*.ts' -delete",
+    "start": "node dist/index.js",
+    "start:dev": "node dist/index.js --remote",
+    "test": "vitest",
+    "clean": "rm -rf dist",
+    "lint": "eslint src --ext .ts",
+    "format": "prettier --write src/**/*.ts",
+    "prepare": "npm run clean && npm run build"
+  },
+  "keywords": [
+    "mcp",
+    "model-context-protocol",
+    "cplace",
+    "api",
+    "claude"
+  ],
+  "author": "collaboration Factory AG",
+  "license": "ISC",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/collaborationFactory/cplace-mcp-server.git"
+  },
+  "homepage": "https://github.com/collaborationFactory/cplace-mcp-server#readme",
+  "bugs": {
+    "url": "https://github.com/collaborationFactory/cplace-mcp-server/issues"
+  },
+  "files": [
+    "dist",
+    "README.md",
+    "package.json",
+    "cplace_search_filters.md"
+  ],
+  "engines": {
+    "node": ">=18.0.0"
+  },
+  "dependencies": {
+    "@modelcontextprotocol/sdk": "^1.17.4",
+    "axios": "^1.6.0",
+    "cors": "^2.8.5",
+    "dot-prop": "^8.0.2",
+    "dotenv": "^16.3.0",
+    "express": "^5.1.0",
+    "semver": "^7.6.0",
+    "zod": "^3.25.67"
+  },
+  "devDependencies": {
+    "@types/cors": "^2.8.19",
+    "@types/express": "^5.0.3",
+    "@types/node": "^20.0.0",
+    "@typescript-eslint/eslint-plugin": "^6.0.0",
+    "@typescript-eslint/parser": "^6.0.0",
+    "eslint": "^8.0.0",
+    "prettier": "^3.0.0",
+    "tsx": "^4.0.0",
+    "typescript": "^5.5.0",
+    "vitest": "^1.0.0"
+  }
+}