Vibesharing

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/erova-vibesharing

About

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools

10 read · 18 write · 3 delete · 1 not yet classified

Secrets

1 (API keys, tokens or passwords)

Install scripts

Not scanned yet

Runs as

Node.js package

Tools (32)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• 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 the resolutions 4. Stakeholders get email: 'Your feedback was addressed' with per-item explanations

• create_campaign

  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 multiple choice, and/or a free comment. Ask the user which prototypes and what to ask before calling — or pass preset: 'critique' to skip that and use a fixed structured-critique question set instead.

• create_collection

  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_prototype

  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_files

  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_files for code you generated or small projects. Before calling this, use resolve_target to confirm the target prototype with the user.

• deploy_prototype

  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 collection_id and parent_project_id so the prototype lands in the right place from the start.

• diagnose

  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 4. Vision alignment — does this match where we're going 5. Interaction design — usability, flow, UX patterns 6. Structured critique — fixed design-crit prompts (directional fit, reasonin…

• 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 can decide to build, skip, or discuss each one. Can also filter by status, priority, or assignee.

• get_prototype_context

  Read what a prototype is and what it's doing: description, project context (CLAUDE.md), deploy history with decisions and known issues, the feedback brief and questions, reference links, and recent feedback. Use this whenever the user shares a prototype link (vibesharing.app/s/...), names a prototype, or asks what a prototype is for. Fetching the share link directly only returns an empty page shell — this tool returns the real context.

• 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 name with the user.

• 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).

Signals

Stars

0

Forks

0

Open issues

0

Last commit

Oct 15, 2026 (15 days ago)

Last release

Sep 3, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name

io.github.erova/vibesharing

Version

0.17.0

Auth

API key

Packages

npm @vibesharingapp/mcp-server

License

License unknown

Repository

github.com/erova/vibesharing-mcp

First seen

Oct 24, 2026

Last checked

Oct 25, 2026

Source

Official MCP Registrygithub-graphql