webasyst

This MCP server provides a set of development tools for Webasyst apps, plugins, themes, and configuration via an AI interface. It exposes commands to list and inspect Webasyst applications, plugins, themes, and routing and system configurations, as well as commands to generate new project structures and UI components. It also includes a CLI integration for executing Webasyst CLI tasks and site/shop-related scaffolding. To use it, run the MCP server locally (for example with node webasyst-mcp.js or via npm start if installed globally) and connect Claude Desktop or your AI interface to the configured mcpServers entry. Once connected, you can query commands like list_webasyst_apps, get_app_info, list_app_themes, create_app_structure, create_plugin_structure, and run_webasyst_cli to perform common development tasks through natural language prompts.

Prerequisites:

• Node.js v18 or newer installed on your machine
• Access to a Webasyst project (with proper directory structure) where the MCP server will operate

Option 1: Install globally via npm (recommended)

1. Install the MCP server globally: npm install -g webasyst-mcp-server
2. Run the server: npm start

Option 2: Install from source

1. Clone the repository: git clone https://github.com/emmy-design/webasyst-mcp.git cd webasyst-mcp
2. Install dependencies: npm install
3. Make the main script executable (if needed): chmod +x webasyst-mcp.js
4. Start the server: npm start

Note: Ensure your environment has network access to install dependencies and that Node.js is in PATH.

Tips and notes:

• The MCP server is designed to be connected to Claude Desktop via the mcpServers configuration. Use an explicit path to the webasyst-mcp.js script when configuring your client.
• The server expects a Webasyst project structure; ensure you point to a valid project directory when using create_* commands.
• Environment variables can be added in the mcp_config under env for each server entry if your workflow requires API keys or local paths.
• If you encounter permission errors when making files executable, adjust your shell permissions or run commands with appropriate privileges.
• Node.js version compatibility is important (v18+ recommended).