VibeSharing
Back to Docs
Setup Guide

Claude Code + VibeSharing MCP Setup

Connect your terminal to your team. Deploy prototypes, collect feedback, triage issues, 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
1

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.

2

Get your deploy token

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

  1. 1.Log in to vibesharing.app
  2. 2.Go to Account Settings
  3. 3.Find the Deploy Token section
  4. 4.Click Generate Token and copy it

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

3

Install the MCP server

The MCP (Model Context Protocol) server is what lets Claude Code talk to VibeSharing. Choose one of these methods:

RecommendedOne-line install via Claude Code CLI

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

Or install globally via npm

npm install -g @vibesharingapp/mcp-server

Verify it installed:

vibesharing-mcp --help
4

Configure your editor

If you used the claude mcp add command above, you're already configured. Otherwise, choose your editor:

One ClickCursor

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

Claude Code — project-level config

Create .claude/mcp.json in your project root:

{
  "mcpServers": {
    "vibesharing": {
      "command": "npx",
      "args": ["-y", "@vibesharingapp/mcp-server@latest"],
      "env": {
        "VIBESHARING_TOKEN": "vs_your_token_here"
      }
    }
  }
}

Global config (all projects)

Create or edit ~/.claude/mcp.json with the same content.

HTTP mode (no npm install needed)

Connect directly to the hosted MCP endpoint:

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

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 means the connection works. You can also run:

Verify my VibeSharing token

Something not working? Try: "Run VibeSharing diagnostics" — this checks your token, GitHub connection, deploy locks, and recent errors.

You're ready to go

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

Deploy

"Deploy this to VibeSharing"

Share HTML

"Share this HTML on VibeSharing"

Register

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

Get feedback

"What feedback came in on the dashboard?"

Generate questions

"Set up feedback questions for this prototype"

Triage

"Triage the open feedback on ERG v3"

Close the loop

"Resolve the feedback I just addressed"

Sync context

"Sync my CLAUDE.md to VibeSharing"

Reference links

"Add the Figma link to this project"

Find & organize

"List my collections"

Diagnose

"Run VibeSharing diagnostics"

Import repo

"Import my GitHub repo to VibeSharing"

See all 21 tools in the MCP reference
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. 1.Go to Account Settings
  2. 2.Click Connect GitHub
  3. 3.Authorize the OAuth app
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

  • Make sure @vibesharingapp/mcp-server is installed or that you're using the npx command
  • Restart Claude Code after editing MCP config
  • Check that the config file is valid JSON (no trailing commas)
  • Try the HTTP mode config if the command-based approach isn't working

"Unauthorized" or token errors

  • Verify your token at Account Settings — is it still active?
  • No extra spaces or quotes around the token in your config
  • Try regenerating the token and updating your config

Deploy fails or gets stuck

  • Ask Claude to "Run VibeSharing diagnostics" — this auto-clears stuck deploy locks
  • Check that your org admin has configured a Vercel token in org settings
  • For push-to-deploy, make sure your GitHub account is connected

Still stuck?

  • Ask Claude to "Send a support request to VibeSharing" — it will include diagnostic context automatically