VibeSharing
← Back to Docs

MCP tools reference

23 tools, accessible from any MCP-compatible editor.

The complete VibeSharing MCP surface — deployment, feedback, context, collections, diagnostics. Available in Claude Code, Cursor, and any other MCP client.

Deployment

Deploy prototypes directly from your editor

deploy_prototype

Deploy a single-file React/Next.js page to VibeSharing. Creates a Vercel project and registers it as a prototype in one step.

Parameters

  • code*React/Next.js page code to deploy
  • name*Name for the prototype
  • prototype_idExisting prototype ID to update

Tip: Best for single-page prototypes. For multi-file projects, use deploy_files instead.

deploy_files

Deploy a multi-file Next.js project. Pushes files to a GitHub repo, deploys to Vercel, and makes the prototype live.

Parameters

  • prototype_id*Prototype ID to deploy to (create one first with register_prototype)
  • files*Array of { path, content } objects
  • commit_messageGit commit message

Tip: Requires an existing prototype ID. Create one first with register_prototype.

share_html

Share a static HTML page — the simplest deploy path. No Vercel, no GitHub, no React wrapper. Uploads the HTML and gives you a shareable link with the feedback widget built in.

Parameters

  • name*Name for the prototype
  • htmlFull HTML content (use this or file_path)
  • file_pathAbsolute path to an HTML file on disk (use for large files)
  • prototype_idExisting prototype ID to update
  • collection_idCollection to place it in

Tip: Great for standalone HTML files, one-page prototypes, or static content that doesn't need a build step.

import_repo

Import an existing GitHub repo into VibeSharing. Pulls the code into a VibeSharing-hosted repo and auto-deploys to Vercel.

Parameters

  • repo_url*GitHub repo URL
  • nameName for the prototype (defaults to repo name)
  • prototype_idExisting prototype ID (creates new if omitted)
  • collection_idCollection to place it in
  • parent_project_idParent project ID for versioning
  • descriptionPrototype description

register_prototype

Register an already-deployed prototype by URL. Use this when you've deployed to Vercel, Netlify, or any other host and want to add it to VibeSharing for feedback and tracking.

Parameters

  • name*Name of the prototype
  • descriptionBrief description
  • external_urlURL where the prototype is deployed
  • collection_idCollection to place it in
  • parent_project_idParent project for versioning
  • source_codeSource code to upload alongside
  • source_filenameFilename for uploaded source

upload_source

Upload source code for an existing prototype. Colleagues can download the source from the prototype page.

Parameters

  • prototype_id*Prototype ID to upload to
  • source_code*The source code to upload
  • filenameFilename (default: page.tsx)
  • storage_option'permanent', 'auto-delete' (7 days), or 'delete-on-download'

Feedback

Collect, triage, and close the loop on stakeholder feedback

get_feedback

Get feedback and comments for a prototype. Supports filtering by status, priority, or assignee.

Parameters

  • project_id*Prototype ID
  • statusFilter: open, in_progress, resolved, wont_fix, deferred (comma-separated)
  • priorityFilter: critical, high, medium, low
  • assigned_toFilter by user ID or 'unassigned'

generate_feedback_topics

Auto-generate feedback questions for a prototype based on what was built. Asks the user what type of feedback matters most (design, feasibility, vision, interaction, or full review) and generates 3-5 targeted questions.

Parameters

  • project_id*Prototype ID
  • focus'awareness', 'design', 'feasibility', 'vision', 'interaction', or 'full'
  • topicsArray of { title, description?, theme? } questions
  • briefShort feedback brief shown to stakeholders in the Context tab

Tip: Ask the user what type of feedback they want before generating. 'awareness' skips questions entirely.

triage_feedback

Update status, priority, or assignee on one or more feedback items. Bulk-triage directly from your editor.

Parameters

  • feedback_ids*Array of feedback IDs to update
  • statusopen, in_progress, resolved, wont_fix, deferred
  • prioritycritical, high, medium, low
  • assigned_toUser ID to assign (empty string to unassign)
  • resolution_noteExplanation shown to stakeholder (for resolved/wont_fix/deferred)

close_feedback_loop

After deploying, match what you built to open feedback items, resolve them with explanations, and notify stakeholders. Each stakeholder gets an email showing exactly what happened to their feedback.

Parameters

  • project_id*Prototype ID
  • resolutions*Array of { feedback_id, status, note } — status is resolved/wont_fix/deferred/in_progress
  • deploy_urlURL of the new deploy (included in notification)

Tip: Call this after deploying when there's open feedback. Pull feedback first with get_feedback to see what needs resolving.

Context & References

Sync project context and attach reference materials

sync_context

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

Parameters

  • project_id*Prototype ID to sync context to
  • content*Context content (typically CLAUDE.md or AGENTS.md)

Organization

Browse and organize prototypes and collections

list_prototypes

List all prototypes in your organization. Shows name, URL, and recent activity.

list_collections

List all collections (folders) in your organization. Use this to find collection IDs when deploying.

create_collection

Create a new collection to group related prototypes. Use this before deploying if you need a new folder.

Parameters

  • name*Collection name
  • descriptionBrief description

resolve_target

Fuzzy-match collection and project names, check deploy name availability, and suggest where to put a prototype. Call this before deploying when the user hasn't provided exact IDs.

Parameters

  • collection_nameApproximate collection name to search for
  • project_nameApproximate prototype name to search for
  • deploy_nameDesired Vercel deploy name to check

Tip: Use this to avoid asking the user for exact IDs. Fuzzy matches names and returns structured options to confirm.

Design System Templates

Browse and use org templates for themed prototypes

list_templates

List design system templates available in your org. Shows template names, slugs, CSS variable counts, and whether design instructions are included.

Parameters

  • active_onlyOnly show active templates (default: true)

Tip: Use this to see what templates are available before deploying with a template parameter.

quick_prototype

Create and deploy a themed prototype in one step. Describe what you want, pick a template, and get step-by-step instructions to generate code and deploy — all on-brand from the start.

Parameters

  • description*What the prototype should show or do
  • templateTemplate slug to use (lists available if omitted)
  • namePrototype name (auto-generated if omitted)
  • collection_idCollection to place the prototype in
  • parent_project_idParent project ID

Tip: The fastest way to go from idea to live URL. Combines template selection, code generation guidance, and deploy into one workflow.

Diagnostics

Troubleshoot and get help

verify_token

Verify that your deploy token is valid. Checks connectivity and authentication.

diagnose

Run a comprehensive health check. Verifies token, GitHub connection, checks for stuck deploy locks (auto-clears them), recent deploy errors, and prototype status.

Tip: Run this first when something isn't working. It auto-fixes stuck deploy locks.

send_support_request

Send a support request to the VibeSharing admin. Use when you can't resolve an issue, need a configuration change, or want to report a bug.

Parameters

  • subject*Short subject line
  • description*Detailed description of the issue
  • contextSession context, error messages, or logs

* = required parameter. All others are optional.

Not set up yet?

Follow the setup guide to connect Claude Code to VibeSharing in under 5 minutes.

Claude Code setup guide →