LayoutPilot MCP Server
Official# LayoutPilot MCP Server
An MCP (Model Context Protocol) server that exposes [LayoutPilot](https://layoutpilot.vercel.app/)'s AI UI generation capabilities as tools.
## Features
- **generate_ui** - Generate full UI layouts with AI
- **generate_component** - Generate individual UI components
- **open_layoutpilot** - Open LayoutPilot with optional pre-filled prompt
## Installation
```bash
npm install
```
## Usage
### With Claude Desktop
Add to your Claude Desktop config (`%APPDATA%\Claude\claude_desktop_config.json` on Windows):
```json
{
"mcpServers": {
"layoutpilot": {
"command": "node",
"args": ["C:\\Users\\survi\\New folder (3)\\src\\index.js"]
}
}
}
```
### Standalone
```bash
npm start
```
## Tools
### generate_ui
Generate a full UI layout.
**Parameters:**
- `prompt` (required): Description of the UI to generate
- `auto_submit` (optional): Auto-start generation (default: true)
**Example:**
```
Generate a modern dashboard with sidebar navigation
```
### generate_component
Generate a single UI component.
**Parameters:**
- `prompt` (required): Description of the component
- `auto_submit` (optional): Auto-start generation (default: true)
**Example:**
```
Create an animated pricing card with hover effects
```
### open_layoutpilot
Open LayoutPilot in browser.
**Parameters:**
- `prompt` (optional): Pre-fill the prompt field
## License
MIT
TDQS
Scored across 3 tools
generate_ui and generate_component are reasonably distinct (full layout vs. single component), but open_layoutpilot overlaps significantly with both since it also accepts a prompt and opens the same tool. An agent could easily select open_layoutpilot when it intends a specific generation mode.
All three tools use snake_case with a clear 'generate_' and 'open_' verb prefix followed by a noun, maintaining a consistent verb_noun pattern. Minor deviation is that open_layoutpilot uses the tool name as the object while the others use the output type.
Three tools is on the low end but appropriate for a thin wrapper that primarily generates URLs to an external service. It feels slightly thin since there are no supporting operations, but the scope is intentionally narrow.
The tools only cover generation (full layout and component) plus a general open. There are notable gaps: no update, preview, iterate on existing layouts, manage versions, or retrieve generated results. Agents have no way to act on output beyond following a URL, creating dead ends for common workflows.