Codesign vs Random Design
A side-by-side look at the Codesign and Random Design MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Codesign for architecture & design work as a local process; choose Random Design for architecture & design as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Codesign when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
Choose Random Design when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
- You want tools like
productType, audience, priority.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Architecture & Design | Architecture & Design |
| Quality signal | 49/100 · Fair | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 42 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 4 |
| Full listing | View Codesign | View Random Design |
Tools & capabilities
Codesign tools
No tool names declared yet. Check the project README from the listing page.
Random Design tools 4
productTypewhat you are designing, such as `landing page`, `dashboard`,audiencewho the interface is for, such as `developers`, `founders`, orprioritywhat the design should optimize for or pay extra attention to,compatibilitycontrols how wild the random combination can be. It defaults
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Codesign
{
"mcpServers": {
"codesign": {
"command": "npx",
"args": [
"-y",
"@imgly/codesign-mcp@0.5.1"
]
}
}
}
Random Design
{
"mcpServers": {
"random-design": {
"command": "npx",
"args": [
"-y",
"random-design-mcp"
]
}
}
}
Frequently asked questions
Codesign is categorized under Architecture & Design and uses a local stdio subprocess. Random Design belongs to Architecture & Design and uses a local stdio subprocess. Pick Codesign for architecture & design work and Random Design for architecture & design.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Codesign is listed as free. Random Design has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add codesign and random-design as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Codesign has a quality signal of 49/100 (Fair) with 1 views, 0 installs and 42 GitHub stars. Random Design has 49/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.