Set Up Claude Code with VibeSharing
Connect your terminal to your team. Register prototypes, check feedback, and sync context — all without leaving Claude Code.
- 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"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@latestThen restart Claude Code.
Cursor / Windsurf / other editors
Add this to your MCP config file (.cursor/mcp.json for Cursor):
{
"mcpServers": {
"vibesharing": {
"url": "https://vibesharing.app/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/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:
List my prototypes on VibeSharing
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:
Deploy
"Deploy this to VibeSharing"
Register
"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"
| Tool | What it does |
|---|---|
| resolve_target | Fuzzy-match collections and projects before deploying — confirms where things go |
| import_repo | Import a GitHub repo into VibeSharing with a named Vercel deployment |
| deploy_files | Deploy multi-file projects with named deployments |
| create_collection | Create a new collection to organize prototypes |
| deploy_prototype | Deploy code directly to VibeSharing hosting |
| register_prototype | Register an already-deployed prototype by URL |
| list_prototypes | List or search all prototypes in your org |
| list_collections | List or search your org's collections |
| get_feedback | Get feedback and comments on a prototype |
| sync_context | Push CLAUDE.md or project notes |
| upload_source | Upload source code for an existing prototype |
| 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 |
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.
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"Tool not found" or MCP server not loading
- Restart Claude Code after running the
claude mcp addcommand - 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 addcommand
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