A side-by-side look at the Vibie MCP and Claude Debugs For You MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Vibie MCP for developer tools work as a local process; choose Claude Debugs For You for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.
VIBIE_API_BASE.vibie_create_site, vibie_update_site, vibie_list_sites.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 59/100 · Good | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | OAuth 2.0 | No auth required |
| Pricing | Free | Free |
| Required env vars | VIBIE_API_BASE | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 516 |
| Directory activity | 3 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Vibie MCP | View Claude Debugs For You |
vibie_create_siteCreate a NEW Vibie site by uploading a local folder. Use this when the user wants to publish a brand new site, or when no .vibie/site.json marker exists in the folder. Vibie hosts static HTML/CSS/JS at a permanent URL like my-site-a3f9.vibie.page. Auto-creates a .vibie/site.json marker in the folder for future updates.vibie_update_siteUpdate an existing Vibie site with new content from a local folder. Use this when the user wants to re-deploy or push changes to an already-published site. If .vibie/site.json marker exists in the folder, the slug is read automatically; otherwise pass slug explicitly. Same URL, new content.vibie_list_sitesList all sites owned by the current Vibie user. Returns slug, display name, category, URL, visibility, and last update time. Use this to discover what sites the user already has, e.g. before update.vibie_get_siteGet metadata for a single Vibie site by slug. Returns name, category, URL, visibility, like count, timestamps.No tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"shdomi8599-vibie-mcp": {
"command": "npx",
"args": [
"-y",
"vibie-mcp"
],
"env": {
"VIBIE_API_BASE": "YOUR_VIBIE_API_BASE_HERE"
}
}
}
}
{
"mcpServers": {
"jasonjmcghee-claude-debugs-for-you": {
"url": "https://docs.anthropic.com/en/docs/build-with-claude/mcp"
}
}
}