StyleKit vs Whoogy
A side-by-side look at the StyleKit and Whoogy MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose StyleKit for architecture & design work as a local process; choose Whoogy for architecture & design over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose StyleKit when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
Choose Whoogy when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Architecture & Design | Architecture & Design |
| Quality signal | 52/100 · Good | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| 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 | 630 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View StyleKit | View Whoogy |
Tools & capabilities
StyleKit tools
No tool names declared yet. Check the project README from the listing page.
Whoogy 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.
StyleKit
{
"mcpServers": {
"stylekit": {
"command": "npx",
"args": [
"-y",
"shadcn"
]
}
}
}
Whoogy
{
"mcpServers": {
"whoogy": {
"url": "https://mcp.whoogy.com/mcp"
}
}
}
Frequently asked questions
StyleKit is categorized under Architecture & Design and uses a local stdio subprocess. Whoogy belongs to Architecture & Design and uses a remote HTTP/SSE transport. Pick StyleKit for architecture & design work and Whoogy 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.
StyleKit has no declared pricing — check the project's own site. Whoogy 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 stylekit and whoogy as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, StyleKit has a quality signal of 52/100 (Good) with 2 views, 0 installs and 630 GitHub stars. Whoogy has 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.