Deploy prototypes and collect team feedback from Claude Code, Cursor, or any MCP client.
Connect Vibesharing to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Deploy prototypes and collect team feedback from Claude Code, Cursor, or any MCP client. The vibesharing mcp server is what makes that connection.
Build prototypes with Claude Code, Cursor, or any AI tool — then instantly share them with your team for feedback. No context switching. No copy-pasting URLs. Just ship and collaborate.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
quick_prototype — Idea to live URL in one step — picks a design system template, generates on-brand code, deploysshare_html — Share static HTML instantly — no hosting account, no GitHub. Auto-bundles CSS/SVGs/imagesdeploy_files — Deploy multi-file projects to GitHub + your hosting provider with named deploymentsdeploy_prototype — Deploy a single code file directlyimport_repo — Import a GitHub repo into VibeSharingregister_prototype — Register an already-deployed prototype by URLvalidate_project — Check a project will build before deploying — missing frameworks, build scripts, conflicting configslist_templates — List your org's design system templatesget_template — Get a template's CSS variables, starter page, and AI design instructions — call before writing codeOrganize — The Organize tool exposed by this serverresolve_target — Fuzzy-match collections and projects — confirms where to deploycreate_collection — Create a new collectionConfiguration is passed through the environment: VIBESHARING_TOKEN, VIBESHARING_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Vibesharing's toolset — quick_prototype, share_html, deploy_files and 11 more — is a fair guide to whether it matches your workflow. It is maintained by erova; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| quick_prototype | Idea to live URL in one step — picks a design system template, generates on-brand code, deploys |
| share_html | Share static HTML instantly — no hosting account, no GitHub. Auto-bundles CSS/SVGs/images. |
| deploy_files | Deploy multi-file projects to GitHub + your hosting provider with named deployments |
| deploy_prototype | Deploy a single code file directly |
| import_repo | Import a GitHub repo into VibeSharing |
| register_prototype | Register an already-deployed prototype by URL |
| validate_project | Check a project will build before deploying — missing frameworks, build scripts, conflicting configs |
| list_templates | List your org's design system templates |
| get_template | Get a template's CSS variables, starter page, and AI design instructions — call before writing code |
| Organize | The Organize tool exposed by this server. |
| resolve_target | Fuzzy-match collections and projects — confirms where to deploy |
| create_collection | Create a new collection |
| list_prototypes | List/search all prototypes in your org |
| list_collections | List/search all collections |
{
"mcpServers": {
"vibesharing": {
"url": "https://vibesharing.app/api/mcp",
"headers": {
"Authorization": "Bearer vs_YOUR_TOKEN"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| VIBESHARING_TOKEN | Credential the server authenticates with. | Yes |
| VIBESHARING_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.