BEFOREVIBE vs StyleKit
A side-by-side look at the BEFOREVIBE and StyleKit MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
B
BEFOREVIBEArchitecture & Design · Remote HTTP/SSEPRD, logo, and AI UI mockups from any app idea — PRD free, logo 1 credit, screens 1 credit each.43FairAuth: oauth 2.0Verdict: choose BEFOREVIBE for architecture & design work over a hosted endpoint; 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?
BChoose BEFOREVIBE when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
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 | B BEFOREVIBE | |
|---|---|---|
| Category | Architecture & Design | Architecture & Design |
| Quality signal | 43/100 · Fair | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 649 |
| Directory activity | 2 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View BEFOREVIBE | View StyleKit |
Tools & capabilities
BEFOREVIBE 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.
BEFOREVIBE
{
"mcpServers": {
"beforevibe": {
"url": "https://beforevibe.com/mcp"
}
}
}
StyleKit
{
"mcpServers": {
"stylekit": {
"command": "npx",
"args": [
"-y",
"shadcn"
]
}
}
}
Frequently asked questions
BEFOREVIBE is categorized under Architecture & Design and uses a remote HTTP/SSE transport. StyleKit belongs to Architecture & Design and uses a local stdio subprocess. Pick BEFOREVIBE 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.
BEFOREVIBE has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 beforevibe and stylekit as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, BEFOREVIBE has a quality signal of 43/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. StyleKit has 52/100 (Good) with 3 views, 0 installs and 649 GitHub stars.