Step-by-step guide

Set Up Claude Code with VibeSharing

Connect your terminal to your team. Register prototypes, check feedback, and sync context — all without leaving Claude Code.

Before you begin

Node.js 18+ installed — download here
Git installed and configured with your name and email
Claude Code installed — install guide

Verify Git is configured:

git config --global user.name "Your Name"
git config --global user.email "you@example.com"

Create your VibeSharing account

Go to vibesharing.app and create your free account. You'll be prompted to create or join an organization — this is your team workspace.

Joining an existing org? Ask your admin for a join link, or request to join from the signup flow if your email domain matches.

Get your deploy token

Your deploy token authenticates the MCP server with your VibeSharing account. It starts with vs_.

1.Log in to vibesharing.app
2.Go to Account Settings (click your avatar in the top-right)
3.Find the Deploy Token section
4.Click Generate Token and copy it

Keep this token private. You can regenerate or revoke it any time from Account Settings.

Add the MCP server to your editor

Choose your editor and add the VibeSharing MCP server. Replace vs_your_token_here with the token you copied in Step 2.

Claude Code

Run this in your terminal:

claude mcp add vibesharing -s user -e VIBESHARING_TOKEN=vs_your_token_here -- npx -y @vibesharingapp/mcp-server@latest

Then restart Claude Code.

Cursor — one click

Paste your deploy token

Opens Cursor and prompts you to add the VibeSharing MCP server. You’ll need your deploy token from Account Settings.

Cursor / Windsurf — manual config

Add this to your MCP config file (.cursor/mcp.json for Cursor):

{
  "mcpServers": {
    "vibesharing": {
      "url": "https://vibesharing.app/api/mcp",
      "headers": {
        "Authorization": "Bearer vs_your_token_here"
      }
    }
  }
}

No install needed — connects directly to VibeSharing. Always up to date.

Claude Desktop

Add this to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "vibesharing": {
      "url": "https://vibesharing.app/api/mcp",
      "headers": {
        "Authorization": "Bearer vs_your_token_here"
      }
    }
  }
}

Then quit and reopen Claude Desktop.

Verify the connection

Restart Claude Code (or open a new session), then try:

You

List my prototypes on VibeSharing

Claude

Found 0 prototypes in your organization. Create one from the dashboard or deploy directly with "Deploy this to VibeSharing".

An empty list is fine — it means the connection works. You can also run:

Verify my VibeSharing token

You're ready to go

Here's what you can now do from Claude Code:

Quick prototype

"Use quick_prototype to build a deploy monitoring dashboard"

Picks a template, generates themed code, deploys — one step

Browse templates

"What templates are available on VibeSharing?"

See your org's design system templates

Deploy

"Deploy this to VibeSharing"

"Register my-app.vercel.app on VibeSharing"

Feedback

"What feedback came in on the dashboard?"

Sync context

"Sync my CLAUDE.md to VibeSharing"

Reference links

"Add the Figma link to this project"

Browse

"List my collections"

MCP Tools Reference

Tool	What it does
quick_prototype	Describe what you want → picks template → deploy instructions. Idea to live URL
list_templates	Browse your org's design system templates
deploy_prototype	Deploy a single-file prototype (supports template parameter)
deploy_files	Deploy multi-file projects with named deployments
share_html	Share a static HTML page — simplest deploy path
import_repo	Import a GitHub repo into VibeSharing with a named Vercel deployment
register_prototype	Register an already-deployed prototype by URL
upload_source	Upload source code for an existing prototype
resolve_target	Fuzzy-match collections and projects — confirms where things go
list_prototypes	List or search all prototypes in your org
list_collections	List or search your org's collections
create_collection	Create a new collection to organize prototypes
get_feedback	Get feedback with filtering by status/priority/assignee
generate_feedback_topics	Auto-generate feedback questions for a prototype
triage_feedback	Bulk-update status, priority, and assignee on feedback
close_feedback_loop	Resolve feedback and notify stakeholders
sync_context	Push CLAUDE.md or project notes
add_context_link	Attach reference links (Figma, PRDs, docs)
list_context_links	List reference materials for a project
remove_context_link	Remove a reference link
verify_token	Test that your token is valid
diagnose	Run a health check — token, GitHub, deploy locks, recent errors
send_support_request	Send a support request to the admin with context

See full tools reference with parameters and usage tips →

Recommended: Connect GitHub

Connecting your GitHub account is required for Push to Deploy workflows. It gives you automatic push access to prototype repos so you can git push to deploy.

1.Go to Account Settings
2.Click Connect GitHub
3.Authorize the OAuth app

Now when creating prototypes, you can choose Push to Deploy to get a Git repo. Clone it, push changes, and Vercel auto-deploys.

Optional: Install the CLI

The CLI is useful for deploying from scripts or CI, outside of Claude Code.

npm install -g vibesharing

# One-time login
npx vibesharing login --token vs_your_token_here

# Link a local project
npx vibesharing init --prototype YOUR_PROTOTYPE_ID

# Deploy
npx vibesharing deploy

Troubleshooting

"Tool not found" or MCP server not loading

Restart Claude Code after running the claude mcp add command
Verify it was added: claude mcp list
Make sure Node.js 18+ is installed

"Unauthorized" or token errors

Verify your token at Account Settings — is it still active?
No extra spaces or quotes around the token value
Try regenerating the token and re-running the claude mcp add command

Deploy fails

Check that your org admin has configured a Vercel token in org settings
For push-to-deploy, make sure your GitHub account is connected