Reference

MCP Tools Reference

Complete reference for all 23 tools available through the VibeSharing MCP server. These tools are available in Claude Code, Cursor, and any MCP-compatible editor.

Deployment(6)Feedback(4)Context & References(4)Organization(4)Design System Templates(2)Diagnostics(3)

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.

Parameter	Description
code*	React/Next.js page code to deploy
name*	Name for the prototype
prototype_id	Existing 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.

Parameter	Description
prototype_id*	Prototype ID to deploy to (create one first with register_prototype)
files*	Array of { path, content } objects
commit_message	Git 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.

Parameter	Description
name*	Name for the prototype
html	Full HTML content (use this or file_path)
file_path	Absolute path to an HTML file on disk (use for large files)
prototype_id	Existing prototype ID to update
collection_id	Collection 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.

Parameter	Description
repo_url*	GitHub repo URL
name	Name for the prototype (defaults to repo name)
prototype_id	Existing prototype ID (creates new if omitted)
collection_id	Collection to place it in
parent_project_id	Parent project ID for versioning
description	Prototype 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.

Parameter	Description
name*	Name of the prototype
description	Brief description
external_url	URL where the prototype is deployed
collection_id	Collection to place it in
parent_project_id	Parent project for versioning
source_code	Source code to upload alongside
source_filename	Filename for uploaded source

upload_source

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

Parameter	Description
prototype_id*	Prototype ID to upload to
source_code*	The source code to upload
filename	Filename (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.

Parameter	Description
project_id*	Prototype ID
status	Filter: open, in_progress, resolved, wont_fix, deferred (comma-separated)
priority	Filter: critical, high, medium, low
assigned_to	Filter 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.

Parameter	Description
project_id*	Prototype ID
focus	'awareness', 'design', 'feasibility', 'vision', 'interaction', or 'full'
topics	Array of { title, description?, theme? } questions
brief	Short 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.

Parameter	Description
feedback_ids*	Array of feedback IDs to update
status	open, in_progress, resolved, wont_fix, deferred
priority	critical, high, medium, low
assigned_to	User ID to assign (empty string to unassign)
resolution_note	Explanation 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.

Parameter	Description
project_id*	Prototype ID
resolutions*	Array of { feedback_id, status, note } — status is resolved/wont_fix/deferred/in_progress
deploy_url	URL 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.

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

add_context_link

Attach a reference link or note to a collection or prototype. Links to Figma designs, PRDs, Confluence docs, or free-text notes for reviewers.

Parameter	Description
title*	Title for the reference
folder_id	Collection ID (provide this or project_id)
project_id	Prototype ID (provide this or folder_id)
url	URL to the reference material (omit for text notes)
note	Description or notes

list_context_links

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

Parameter	Description
folder_id	Collection ID
project_id	Prototype ID

remove_context_link

Remove a reference link or note by its ID.

Parameter	Description
link_id*	ID of the context link to remove

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.

Parameter	Description
name*	Collection name
description	Brief 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.

Parameter	Description
collection_name	Approximate collection name to search for
project_name	Approximate prototype name to search for
deploy_name	Desired 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.

Parameter	Description
active_only	Only 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.

Parameter	Description
description*	What the prototype should show or do
template	Template slug to use (lists available if omitted)
name	Prototype name (auto-generated if omitted)
collection_id	Collection to place the prototype in
parent_project_id	Parent 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.

Parameter	Description
subject*	Short subject line
description*	Detailed description of the issue
context	Session context, error messages, or logs

* = required parameter. All other parameters are optional.

Not set up yet?

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

Claude Code setup guide