{
  "markdown": "# VibeSharing MCP Server\n\n**The missing link between your AI coding assistant and your team.**\n\n> **Note for anyone reading this on GitHub:** [erova/vibesharing-mcp](https://github.com/erova/vibesharing-mcp)\n> is a read-only mirror, published automatically on each release. Pull requests against it will be\n> overwritten by the next sync. To report a bug or request a change, please\n> [open an issue](https://github.com/erova/vibesharing-mcp/issues) or write to\n> [hello@vibesharing.app](mailto:hello@vibesharing.app).\n\nBuild 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.\n\n## Quick Start\n\n### 1. Get Your Token\n\nSign up at [vibesharing.app](https://vibesharing.app), then go to [Account Settings](https://vibesharing.app/dashboard/account) to:\n- **Copy your deploy token** — starts with `vs_`\n- **Connect your GitHub account** (optional) — enables Push to Deploy\n\n### 2. Connect Your Editor\n\n**Cursor / Windsurf / Claude Desktop** (recommended — always up to date):\n\n```json\n{\n  \"mcpServers\": {\n    \"vibesharing\": {\n      \"url\": \"https://vibesharing.app/api/mcp\",\n      \"headers\": {\n        \"Authorization\": \"Bearer vs_YOUR_TOKEN\"\n      }\n    }\n  }\n}\n```\n\nAdd to `.cursor/mcp.json` (Cursor) or `~/Library/Application Support/Claude/claude_desktop_config.json` (Claude Desktop).\n\n**Claude Code:**\n\n```bash\nclaude mcp add vibesharing -s user \\\n  -e VIBESHARING_TOKEN=vs_YOUR_TOKEN \\\n  -- npx -y @vibesharingapp/mcp-server@latest\n```\n\nThen restart your editor. That's it.\n\n### 3. Start Sharing\n\n```\nYou: \"Share this page on VibeSharing\"\nYou: \"Deploy this to the Product Redesign collection\"\nYou: \"What feedback came in on the dashboard?\"\n```\n\n## What You Can Do\n\n### Share a static HTML page instantly\n```\n\"Share this HTML file on VibeSharing\"\n```\nOne command. No Vercel, no GitHub, no React wrapper. Your HTML page goes live with a feedback widget built in. CSS, SVGs, and images are auto-bundled into a self-contained file.\n\n### Deploy full projects\n```\n\"Deploy this to VibeSharing in the Hero Use Cases collection as checkout-v3\"\n```\nClaude confirms the collection, names the deployment, and handles everything — GitHub repo, deploy, team registration — in one conversation. Your first three prototypes are hosted on us; connect your own Vercel or Netlify account and the limit disappears.\n\n### Match your design system from the first prompt\n```\n\"Build a settings page using our design system\"\n```\n`quick_prototype` picks the right template from your org, hands the AI its CSS variables and written design instructions, and deploys — so the prototype is on-brand as it's generated, instead of built generic and retrofitted. Browse what's available with `list_templates`.\n\n### Go through feedback one person at a time\n```\n\"What feedback did I get on the checkout flow?\"\n\"Walk me through Jordan's comments\"\n```\nOn the local server, open feedback across your recent prototypes is summarized on the first VibeSharing tool call of a session — you find out something is waiting without asking. (Not yet on the remote endpoint.)\n\nAsked without a name, `get_feedback` groups everything by author — \"9 items from 4 people, 6 open\" — instead of returning a wall of text. Asked with a name, it walks that person's comments one at a time, each carrying the page it was left on, the pinned position, the question it answered, the replies underneath, and **the screenshot itself as an image** — so you see what they saw rather than opening a link. You decide per comment whether to build it, skip it, or discuss — and `close_feedback_loop` tells the person what you did.\n\n### Keep every version, and branch safely\n```\n\"Show me the version history\"\n\"Fork this so I can try a dark variant\"\n\"Roll back to v3\"\n```\nEvery deploy is a numbered version with its own immutable URL. `fork_prototype` copies one to a separate URL so you can explore without touching the original, and `rollback_deploy` restores any earlier version — for git-based and static prototypes alike.\n\n### Put it in front of customers\n```\n\"Set up a study comparing these three variants\"\n```\n`create_campaign` bundles several prototypes behind one gated portal with your own questions — star ratings, multiple choice, free text — and supports blind randomized A/B/C ordering so a name like \"v2\" can't skew a preference test. It lands as a draft; opening it and inviting the cohort stays a deliberate step in the dashboard.\n\n### Catch build failures before deploying\n```\n\"Check this will build before we ship it\"\n```\n`validate_project` looks for the things that actually break deploys — a missing framework dependency, no build script, conflicting configs — and returns fixes rather than a stack trace after the fact.\n\n### Keep context alive across sessions\n```\n\"Sync my CLAUDE.md to VibeSharing\"\n```\nYour project context persists on VibeSharing, so any team member (or AI session) can pick up where you left off. CLAUDE.md and AGENTS.md auto-sync on deploy.\n\n### Troubleshoot issues\n```\n\"Run a VibeSharing health check\"\n```\nThe `diagnose` tool checks your token, GitHub connection, deploy locks, and recent errors — and auto-fixes what it can. If it can't fix something, `send_support_request` sends a detailed report to the admin.\n\n## Available Tools (31)\n\n| Tool | Description |\n|------|-------------|\n| **Deploy & Share** | |\n| `quick_prototype` | Idea to live URL in one step — picks a design system template, generates on-brand code, deploys |\n| `share_html` | Share static HTML instantly — no hosting account, no GitHub. Auto-bundles CSS/SVGs/images. |\n| `deploy_files` | Deploy multi-file projects to GitHub + your hosting provider with named deployments |\n| `deploy_prototype` | Deploy a single code file directly |\n| `import_repo` | Import a GitHub repo into VibeSharing |\n| `register_prototype` | Register an already-deployed prototype by URL |\n| `validate_project` | Check a project will build before deploying — missing frameworks, build scripts, conflicting configs |\n| **Design systems** | |\n| `list_templates` | List your org's design system templates |\n| `get_template` | Get a template's CSS variables, starter page, and AI design instructions — call before writing code |\n| **Organize** | |\n| `resolve_target` | Fuzzy-match collections and projects — confirms where to deploy |\n| `create_collection` | Create a new collection |\n| `list_prototypes` | List/search all prototypes in your org |\n| `list_collections` | List/search all collections |\n| `update_prototype` | Rename a prototype or update its description and URL, in place |\n| `delete_prototype` | Delete a prototype and its history — irreversible, creator or org admin only |\n| **Versions & variants** | |\n| `list_versions` | Version history — version numbers, file counts, commit info, what can be rolled back |\n| `fork_prototype` | Copy a prototype to its own URL to explore a variant; the original is untouched |\n| `rollback_deploy` | Restore a previous version, for git-based and static prototypes |\n| **Research** | |\n| `create_campaign` | Set up a customer study — several prototypes, your questions, optional blind A/B/C ordering |\n| **Feedback** | |\n| `get_feedback` | Feedback grouped by author, or one person's comments as a queue with full context |\n| `triage_feedback` | Update status, priority, or assignee on feedback |\n| `generate_feedback_topics` | Create guided feedback questions for reviewers |\n| `close_feedback_loop` | Resolve feedback with a note back to the stakeholder |\n| **Context** | |\n| `sync_context` | Push CLAUDE.md, AGENTS.md, or project notes |\n| `upload_source` | Upload source code to an existing prototype |\n| `add_context_link` | Attach reference links (Figma, PRDs, docs) |\n| `list_context_links` | List reference links on a collection or project |\n| `remove_context_link` | Remove a reference link |\n| **Diagnostics** | |\n| `diagnose` | Health check — token, GitHub, deploy locks, recent errors |\n| `send_support_request` | Send a support request to the admin with context |\n| `verify_token` | Check that your deploy token is valid |\n\n## Remote vs Local\n\n**Remote** (recommended): Connect to `vibesharing.app/api/mcp`. Always up to date, no installs, no cache issues. Works everywhere.\n\n**Local** (advanced): Run via `npx`. Supports reading files from disk with `file_path` parameter. Requires Node.js 18+. May need `npx clear-npx-cache` after updates.\n\n## Environment Variables (local only)\n\n| Variable | Required | Description |\n|----------|----------|-------------|\n| `VIBESHARING_TOKEN` | Yes | Your deploy token from VibeSharing |\n| `VIBESHARING_URL` | No | Custom API URL (defaults to https://vibesharing.app) |\n\n## Learn More\n\n- [VibeSharing](https://vibesharing.app) — Sign up free\n- [Setup Guide](https://vibesharing.app/get-started/claude-code-setup) — Step-by-step for all editors\n- [Troubleshooting](https://vibesharing.app/DEPLOY-TROUBLESHOOTING.md) — Common issues and fixes\n- [GitHub](https://github.com/erova/vibesharing-mcp) — Source code\n\n---\n\n**Stop building in isolation. Start shipping with your team.**\n",
  "bytes": 9123,
  "sha": "0b34afc9b07007d8c907afe26c84201b92c8e278f275fd845b53111cec477f8a",
  "repo_slug": "erova/vibesharing-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_erova_vibesharing_2b4aaec8/readme"
}