Bitbybit CAD MCP vs StyleKit
A side-by-side look at the Bitbybit CAD MCP and StyleKit MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Bitbybit CAD MCP for architecture & design work as a local process; choose StyleKit 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 Bitbybit CAD MCP when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
Choose StyleKit 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 | 51/100 · Good | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 203 | 630 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Bitbybit CAD MCP | View StyleKit |
Tools & capabilities
Bitbybit CAD MCP tools
No tool names declared yet. Check the project README from the listing page.
StyleKit 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.
Bitbybit CAD MCP
{
"mcpServers": {
"bitbybit-cad-mcp": {
"command": "npx",
"args": [
"-y",
"@bitbybit-dev/create-app"
]
}
}
}
StyleKit
{
"mcpServers": {
"stylekit": {
"command": "npx",
"args": [
"-y",
"shadcn"
]
}
}
}
Frequently asked questions
Bitbybit CAD MCP is categorized under Architecture & Design and uses a local stdio subprocess. StyleKit belongs to Architecture & Design and uses a local stdio subprocess. Pick Bitbybit CAD MCP for architecture & design work and StyleKit 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.
Bitbybit CAD MCP has no declared pricing — check the project's own site. StyleKit 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 bitbybit-cad-mcp and stylekit as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Bitbybit CAD MCP has a quality signal of 51/100 (Good) with 0 views, 0 installs and 203 GitHub stars. StyleKit has 52/100 (Good) with 2 views, 0 installs and 630 GitHub stars.