sap-extension-creator

What it does

Creates SAP extensions (static frontend or Node.js backend) and scaffolds necessary files and workflows. Supports registering MCP tools via WebSocket, and provides templates for package.json, index.html, and index.js. Guides gathering requirements and scaffolding from templates, including optional Node.js dependencies and appearance options. Also documents WebSocket MCP lifecycle (startup, runtime, shutdown) and how to manage extension UI via iframe compatibility, theming, i18n, responsiveness, and compact mode for transparent windows.

How it works

• It outlines two extension modes: Static (UI-only) and Node.js (Express backend), both of which can register MCP tools and connect via WebSocket.
• It prescribes scaffold steps: gather requirements (extension name, description, type, dependencies, repository URL, window properties), scaffold templates from assets, and write package.json with required fields.
• For Node.js extensions, it requires an index.js entry point that starts an Express server on a specified port, serves static files, and provides a /health endpoint.
• It defines MCP lifecycle: on ws.onopen call registerMcpTools(), on ws.onmessage handleMcpCall(), and on window.beforeunload call unregisterMcpTools(). Tools are registered via a structured JSON message, and must be implemented as separate named functions.
• It specifies UI and behavior patterns: include index.html with a self-contained page, use Font Awesome from CDN, enable dark/light theme with CSS variables, and bilingual UI via i18n object.
• It describes responsive behavior, iframe compatibility, and compact mode for transparent windows, including CSS and JS patterns for drag regions and a close button.
• It provides a WebSocket protocol reference and a simple chat HTTP API endpoint (/simple_chat) for one-off AI tasks separate from the WebSocket chat flow.

When to use it

Use when you need to create a new SAP extension, either static UI or a full Node.js backend, and you want to scaffold the project structure, wire up MCP tool registration, and follow SAP’s extension conventions.

What it can touch

• WebSocket at ws://host/ws for MCP lifecycle and tool calls.
• HTTP endpoint /simple_chat on the same origin for stateless AI tasks.
• Local filesystem through templates and assets for scaffolding (assets/static-template/, assets/node-template/ used for starting points).

Caveats

• License is AGPL-3.0.
• Requires tools: claude-code.
• The workflow assumes templates exist under assets, and that Node.js extensions expose an index.js with specified behavior.
• No outcomes guaranteed beyond described steps and messaging patterns.