Vibesharing MCP server

Read from the package source without running it. The installed server may list more.

• add_context_link

  Attach a reference link or note to a collection or project/prototype. Use this to add links to Figma designs, PRDs, Confluence docs, or free-text notes that provide context for reviewers.

• close_feedback_loop

  CALL THIS AFTER DEPLOYING when there is open feedback. Matches what you just built to open feedback items, resolves them with explanations, and notifies the original stakeholders with a personalized digest. The stakeholder sees exactly what happened to their feedback. Flow: 1. Pull open feedback via get_feedback 2. Look at what you built and match changes to feedback items 3. Call this tool with t

• create_campaignwrite action

  Create a research campaign (customer/user study) in VibeSharing. A campaign bundles several prototypes behind one gated portal and asks reviewers structured questions. Great for A/B/C preference tests across variants. Creates the campaign as a DRAFT — review and open/send it from the dashboard (opening applies access gating and invites the cohort). Each question can collect a 1–5 star rating, a mu

• create_collectionwrite action

  Create a new collection in your VibeSharing organization. Collections group related projects and prototypes. Use this before deploying a prototype if you need a new collection to put it in.

• delete_prototypewrite action

  Delete a prototype from VibeSharing. Removes the prototype, its deployments, version history, and feedback. This is irreversible. IMPORTANT: Always confirm with the user before deleting. Only the prototype creator or an org admin can delete.

• deploy_fileswrite action

  Deploy a multi-file Next.js project to VibeSharing. Pushes files to GitHub, deploys to Vercel. Requires an existing prototype ID. For large files, use file_paths instead of files to read from disk and avoid MCP parameter size limits (~100KB). IMPORTANT: If the code is already in a GitHub repo, use import_repo instead — it's faster, supports branches, and has no payload size limits. Only use deploy

• deploy_prototypewrite action

  Deploy code directly to VibeSharing. Deploys to Vercel with a Git repo and registers it as a prototype in one step. Supports single-file (code) or multi-file (files/file_paths) deploys. For multi-page prototypes, use files or file_paths instead of code. IMPORTANT: Always ask the user WHERE this should go BEFORE deploying — which collection and project. Use resolve_target to confirm. Pass collectio

• diagnosewrite action

  Run a comprehensive health check on the user's VibeSharing setup. Checks token validity, GitHub connection, stuck deploy locks (auto-clears them), recent deploy errors, and prototype status. Use this to troubleshoot issues.

• fork_prototype

  Fork a prototype: creates a new copy with its own deploy URL, linked back to the original. The original is preserved untouched. Use this when the user wants to explore a variant, experiment with changes, or branch from an existing prototype without risking the original. IMPORTANT: Confirm the fork name and target collection with the user before proceeding.

• generate_feedback_topics

  Auto-generate feedback questions for a prototype based on what was built. IMPORTANT: Before generating questions, ask the user: 'What type of feedback is most important for this deploy?' and present these options: 1. Awareness only — just sharing progress, no feedback needed 2. Design direction — brand, visual, layout feedback 3. Technical feasibility — is this buildable, are these features doable

• get_feedback

  Get feedback and comments for a prototype. Called without `author`, it returns a roll-up of who left feedback and what they said — use this for 'show me the feedback'. Called with `author`, it returns that person's items as an ordered queue with full context (page path, pin position, screenshot, the question being answered, replies) plus instructions for reviewing them one at a time so the owner c

• get_template

  Get the full details of a design system template — CSS variables, starter page, and design instructions. Use this BEFORE writing any code to ensure your prototype matches the org's design system from the start.

• import_repo

  Import an existing GitHub repo into VibeSharing. PREFER THIS over deploy_files when code is already in a GitHub repo — it fetches files server-side (no payload size limits) and supports branch selection via the branch parameter. Pulls code into a VibeSharing-hosted repo and deploys to Vercel. IMPORTANT: Before calling this, use resolve_target to confirm the collection, project name, and deploy nam

• list_collections

  List all collections (folders) in your VibeSharing organization. Use this to find the collection_id when registering prototypes. Optionally filter by search query (fuzzy matched).

• list_context_links

  List all reference links and notes attached to a collection or project/prototype.

• list_prototypes

  List all prototypes in your VibeSharing organization. Shows name, URL, and recent activity. Optionally filter by search query (fuzzy matched).

• list_templates

  List design system templates available in your org. Call this when the user asks about design systems, branding, templates, or wants their prototype to match their org's look and feel. Templates provide themed CSS variables, starter pages, and AI design instructions.

• list_versions

  List version history for a prototype. Shows all deploys with version numbers, file counts, commit info, and whether rollback is available. Use this to review what changed between deploys or to find a version to rollback to.

• quick_prototypewrite action

  Create and deploy a themed prototype in one step. Picks a design system template, registers a new prototype, and deploys generated code — all from a single description. The fastest way to go from idea to live URL.

• register_prototype

  Register a prototype on VibeSharing. Creates a standalone prototype by default. To add it as a version under an existing project, provide parent_project_id. IMPORTANT: Before calling this, use resolve_target to confirm the collection and project name with the user. Do not auto-generate names without user confirmation. Returns the VibeSharing URL where the team can view and leave feedback.

• remove_context_linkwrite action

  Remove a reference link or note by its ID.

• resolve_target

  CALL THIS BEFORE deploying or registering a prototype when the user hasn't provided exact IDs. Fuzzy-matches collection and project names, suggests where to put the prototype, and checks deploy_name availability. Returns structured options so you can confirm with the user before proceeding.

• rollback_deploywrite action

  Rollback a prototype to a previous version. For git deploys, re-pushes the old files to GitHub. For static deploys, restores the HTML snapshot. IMPORTANT: Always call list_versions first and confirm the target version with the user before rolling back.

• send_support_requestwrite action

  Send a support request to the VibeSharing admin. Use this when the user has an issue you can't resolve, needs a configuration change, or wants to report a bug.

• share_html

  Share a static HTML page on VibeSharing — the simplest way to share. No Vercel, no GitHub, no React wrapper. Just uploads the HTML and gives you a shareable link with the feedback widget built in. Use this for standalone HTML files, one-page prototypes, or any static content that doesn't need a build step. For large HTML files, use file_path instead of html to avoid MCP parameter size limits.

• sync_context

  Sync your CLAUDE.md, AGENTS.md, or project context to VibeSharing. This helps maintain context across AI sessions and team members.

• triage_feedbackwrite action

  Update status, priority, or assignee on one or more feedback items. Use this to triage feedback from within your editor.

• update_prototypewrite action

  Update a prototype's metadata (name, description, external URL). Use this to rename prototypes, update descriptions, or fix URLs. Does NOT create a new entry — modifies the existing one in place.

• upload_sourcewrite action

  Upload source code for an existing prototype on VibeSharing. Colleagues can then download the source from the prototype page. Use this when you want to share code without deploying it.

• validate_project

  Validate that the current project will build successfully before deploying. Checks for common issues: missing framework dependencies (next, vite, nuxt, astro, gatsby), missing build scripts, conflicting configs. Use this before deploy_files or deploy_prototype to catch build failures early. Returns warnings and errors with fix suggestions.

• verify_token

  Verify that your VibeSharing deploy token is valid. Use this to check connectivity and authentication before other operations.

• Code scan4 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 1 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Safety score

83/100

higher than 65% of 1,119 Developer tools servers

Tools

31

the typical Developer tools server has 7

Tools that change things

42%

typical: 5%. Fewer write tools means less an agent can break

Downloads a week

55

more than 40% of 442 Developer tools servers with a package

Vibesharing: common questions

Is Vibesharing MCP server safe?

Mostly: it is graded B (83/100). Read the Vibesharing safety report

How do I install Vibesharing?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Vibesharing need an API key?

Yes. The registry entry asks for VIBESHARING_TOKEN.

Is Vibesharing maintained?

The last commit was 21 days ago (2026-10-15). The latest release is v0.17.0.

What can I use instead of Vibesharing?

Servers from other publishers that do the same job: ShipStatic MCP server, walkerOS Flow MCP server and Omnara MCP server.

How does Vibesharing compare with other Developer tools MCP servers?

safety score 83/100 (higher than 65% of 1,119 Developer tools servers); tools 31 (the typical Developer tools server has 7); tools that change things 42% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.