TypeUI vs Codesign
A side-by-side look at the TypeUI and Codesign MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose TypeUI for architecture & design work as a local process; choose Codesign 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 TypeUI when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
Choose Codesign when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Architecture & Design | Architecture & Design |
| Quality signal | 47/100 · Fair | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2,134 | 42 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View TypeUI | View Codesign |
Tools & capabilities
TypeUI tools
No tool names declared yet. Check the project README from the listing page.
Codesign tools
No tool names declared yet. Check the project README from the listing page.
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.
TypeUI
{
"mcpServers": {
"typeui": {
"command": "npx",
"args": [
"-y",
"typeui.sh"
]
}
}
}
Codesign
{
"mcpServers": {
"codesign": {
"command": "npx",
"args": [
"-y",
"@imgly/codesign-mcp@0.5.1"
]
}
}
}
Frequently asked questions
TypeUI is categorized under Architecture & Design and uses a local stdio subprocess. Codesign belongs to Architecture & Design and uses a local stdio subprocess. Pick TypeUI for architecture & design work and Codesign 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.
TypeUI has no declared pricing — check the project's own site. Codesign is listed as free. 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 typeui and codesign as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, TypeUI has a quality signal of 47/100 (Fair) with 2 views, 0 installs and 2,134 GitHub stars. Codesign has 49/100 (Fair) with 0 views, 0 installs and 42 GitHub stars.