design-clone-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| clone_website_designA | Clone a website design by capturing HTML, CSS, colors, fonts, and layout. Returns structured design data that can be used to recreate the page. |
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 1 tool
With only one tool, there is no possibility of confusion or misselection. The tool's purpose is unambiguous.
The single tool name 'clone_website_design' follows a clear verb_noun pattern in snake_case. No inconsistency can exist with only one tool.
One tool is borderline thin for a server, even though the task is well-defined. The rubric considers 1-2 tools as feeling thin.
The tool covers the entire stated purpose: capturing HTML, CSS, colors, fonts, and layout for design cloning. No obvious gaps exist for this single-operation domain.