mockit-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_HOST | No | Bind interface for HTTP transport | 127.0.0.1 |
| HTTP_PORT | No | HTTP transport port | 7821 |
| DESIGNS_DIR | No | Where outputs are persisted | ./designs |
| DEVICE_SCALE | No | Retina factor | 2 |
| MCP_TRANSPORT | No | Transport: 'stdio' or 'http' | stdio |
| CLAUDE_BACKEND | No | Backend to use: 'cli' uses the claude CLI; 'api' uses Anthropic SDK directly | cli |
| MCP_HTTP_TOKEN | No | Bearer token for HTTP auth. Required if HTTP_HOST is non-loopback | |
| VIEWPORT_WIDTH | No | Render width in CSS pixels | 390 |
| ANTHROPIC_MODEL | No | Model to use (API backend only) | claude-opus-4-7 |
| CLAUDE_CLI_PATH | No | Path to the claude binary | claude |
| VIEWPORT_HEIGHT | No | Render height in CSS pixels | 844 |
| ANTHROPIC_API_KEY | No | Required only for 'api' backend | |
| CLAUDE_CLI_TIMEOUT_MS | No | Subprocess timeout in milliseconds | 180000 |
| PLAYWRIGHT_NO_SANDBOX | No | Sandbox mode: 'auto', 'true', or 'false' | auto |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_screenA | Generate a premium iOS mobile UI mockup from a text brief. Outputs both the screenshot (PNG) and the underlying HTML. Use this when the user asks to design, mock up, or visualize a mobile app screen. |
| iterate_screenA | Refine an existing generated screen based on feedback. Use this for follow-up edits like 'change color', 'add a section', 'make it more spacious'. |
| list_screensA | List all generated screens, optionally filtered by project name. |
| get_screenA | Get details and metadata for a specific screen. Set include_html=true to also return the HTML source. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool serves a distinct purpose: generate creates, get retrieves, iterate refines, list enumerates. No functional overlap.
All tools follow a consistent verb_noun pattern in snake_case (generate_screen, get_screen, iterate_screen, list_screens).
4 tools is well-scoped for a mockup generation service, covering creation, retrieval, iteration, and listing without excess.
Covers core CRUD except delete, which may be intentional. Users can create, read, update, and list screens, with no obvious dead ends.