@vibesharingapp/mcp-server 0.4.1 → 0.4.2

package/README.md

@@ -22,21 +22,26 @@ Until now.
 VibeSharing's MCP server connects Claude Code directly to your team's prototype hub. Every prototype you build becomes instantly shareable, trackable, and open for feedback.
 
 ```
-You: "Register this on VibeSharing, it's deployed at my-app.vercel.app"
+You: "Post this prototype to VibeSharing"
 
-Claude: Done! Your team can now view and leave feedback at:
-        vibesharing.app/dashboard/projects/abc123
+Claude: I found these collections in your org:
+        1. All Hero Use Cases
+        2. Compliance Hub
+        3. Internal Tools
+
+        Which collection should this go in? And do you want a custom URL
+        like erg-v3-teams.vercel.app?
 ```
 
-That's it. Your prototype is live on VibeSharing. Your team gets notified. Feedback flows back to you.
+No guessing. No duplicates. Just a quick confirmation and your prototype is live.
 
 ## What You Can Do
 
 ### Ship prototypes without leaving your terminal
 ```
-"Deploy this to Vercel and register it on VibeSharing"
+"Deploy this to VibeSharing in the Hero Use Cases collection as erg-v3-teams"
 ```
-Claude handles the deployment AND registers it with your team—in one conversation.
+Claude confirms the collection, names the deployment, and handles everything—GitHub repo, Vercel deploy, team registration—in one conversation.
 
 ### Check what your team thinks
 ```
@@ -53,32 +58,34 @@ Your project context persists on VibeSharing, so any team member (or AI session)
 ### See all your work in one place
 ```
 "List my prototypes"
+"Search collections for hero"
 ```
-Every prototype you've registered, with links and recent activity.
+Every prototype you've registered, with links and recent activity. Fuzzy search included.
 
 ## Quick Start
 
-### 1. Install
-
-```bash
-npm install -g @vibesharingapp/mcp-server
-```
-
-### 2. Get Your Token & Connect GitHub
+### 1. Get Your Token & Connect GitHub
 
 Sign up at [vibesharing.app](https://vibesharing.app), then go to [Account Settings](https://vibesharing.app/dashboard/account) to:
 - **Connect your GitHub account** — required for Push to Deploy (gives you automatic push access to prototype repos)
 - **Copy your deploy token** — needed for the MCP server config below
 
-### 3. Configure Claude Code
+### 2. Configure Claude Code
 
-Add to your Claude Code settings:
+```bash
+claude mcp add vibesharing \
+  -e VIBESHARING_TOKEN=vs_your_token_here \
+  -- npx -y @vibesharingapp/mcp-server@latest
+```
+
+Or add to your Claude Code settings manually:
 
 ```json
 {
   "mcpServers": {
     "vibesharing": {
-      "command": "vibesharing-mcp",
+      "command": "npx",
+      "args": ["-y", "@vibesharingapp/mcp-server@latest"],
       "env": {
         "VIBESHARING_TOKEN": "vs_your_token_here"
       }
@@ -87,7 +94,9 @@ Add to your Claude Code settings:
 }
 ```
 
-### 4. Start Building
+Using `@latest` ensures you always get new features and fixes automatically.
+
+### 3. Start Building
 
 That's it. Ask Claude to register prototypes, check feedback, or sync context. It just works.
 
@@ -106,11 +115,21 @@ See the full picture of your team's prototyping velocity. Guide feedback with cu
 
 | Tool | Description |
 |------|-------------|
-| `deploy_prototype` | **NEW** Deploy code directly to VibeSharing (builds & hosts it for you) |
+| `resolve_target` | **Start here.** Fuzzy-matches collection/project names and confirms where to deploy before proceeding. |
+| `import_repo` | Import a GitHub repo into VibeSharing with a named Vercel deployment |
+| `deploy_files` | Deploy multi-file projects to VibeSharing with named deployments |
+| `deploy_prototype` | Deploy a single code file directly |
 | `register_prototype` | Register an already-deployed prototype with name, description, and URL |
-| `list_prototypes` | List all prototypes in your organization |
+| `list_prototypes` | List/search all prototypes in your organization |
+| `list_collections` | List/search all collections |
 | `get_feedback` | Get feedback and comments for any prototype |
 | `sync_context` | Push CLAUDE.md, AGENTS.md, or project notes to VibeSharing |
+| `create_collection` | Create a new collection |
+| `upload_source` | Upload source code to an existing prototype |
+| `add_context_link` | Attach reference links (Figma, PRDs, docs) to collections or projects |
+| `list_context_links` | List reference links on a collection or project |
+| `remove_context_link` | Remove a reference link |
+| `verify_token` | Check that your deploy token is valid |
 
 ## Environment Variables
 
@@ -121,25 +140,23 @@ See the full picture of your team's prototyping velocity. Guide feedback with cu
 
 ## Examples
 
-### Deploy directly from Claude Code
+### Deploy with a named URL
 ```
-You: "Deploy this to VibeSharing as 'Checkout Flow v2'"
+You: "Deploy this to VibeSharing as erg-v3-teams in the Hero Use Cases collection"
 
-Claude: Deployed successfully!
+Claude: Deployed!
 
-        Live URL: https://proto-checkout-flow-v2-abc123.vercel.app
+        Live URL: https://erg-v3-teams.vercel.app
         VibeSharing: https://vibesharing.app/dashboard/projects/xyz789
 
         Your team can now view the prototype and leave feedback.
 ```
 
-### Register after deploying
+### Fuzzy search for collections
 ```
-You: "I just deployed to https://checkout-v2.vercel.app - register it on VibeSharing
-      as 'Checkout Flow v2' and mention it simplifies the payment step"
+You: "Put this in the hero collection"
 
-Claude: Registered! Your team can view and leave feedback at:
-        https://vibesharing.app/dashboard/projects/xyz789
+Claude: I found "All Hero Use Cases" — is that the right collection?
 ```
 
 ### Get feedback before your next session
@@ -154,7 +171,7 @@ Claude: 3 new comments on Dashboard Redesign:
 
 ### Keep your AI context in sync
 ```
-You: "Sync my CLAUDE.md (or AGENTS.md) to the Dashboard project on VibeSharing"
+You: "Sync my CLAUDE.md to the Dashboard project on VibeSharing"
 
 Claude: Context synced! Your team can now see your project notes at:
         https://vibesharing.app/dashboard/projects/abc123
@@ -164,21 +181,25 @@ Claude: Context synced! Your team can now see your project notes at:
 
 VibeSharing isn't just another tool to check. It's infrastructure for teams building with AI:
 
+- **Smart deploy targeting** — fuzzy-matches collections and projects so you don't need exact IDs
+- **Named deployments** — deterministic URLs like `erg-v3-teams.vercel.app` instead of random hashes
 - **Context file sync** (CLAUDE.md, AGENTS.md) keeps context alive across sessions and team members
 - **Guided feedback topics** help stakeholders give useful input
 - **Email notifications** when prototypes update or get feedback
-- **Works with any deploy target** - Vercel, Netlify, Replit, Lovable, v0, or paste any URL
+- **Works with any deploy target** — Vercel, Netlify, Replit, Lovable, v0, or paste any URL
 
 ## Learn More
 
-- [VibeSharing](https://vibesharing.app) - Sign up free
-- [Documentation](https://vibesharing.app/get-started) - Full setup guide
-- [GitHub](https://github.com/erova/vibesharing) - Source code
+- [VibeSharing](https://vibesharing.app) — Sign up free
+- [Documentation](https://vibesharing.app/get-started) — Full setup guide
+- [GitHub](https://github.com/erova/vibesharing) — Source code
 
 ---
 
 **Stop building in isolation. Start shipping with your team.**
 
 ```bash
-npm install -g @vibesharingapp/mcp-server
+claude mcp add vibesharing \
+  -e VIBESHARING_TOKEN=vs_your_token_here \
+  -- npx -y @vibesharingapp/mcp-server@latest
 ```

package/dist/index.js

@@ -178,7 +178,7 @@ function fuzzyMatch(query, items, getName, threshold = 0.3) {
         .sort((a, b) => b.score - a.score);
 }
 // ---- Version tracking & What's New ----
-const CURRENT_VERSION = "0.4.1";
+const CURRENT_VERSION = "0.4.2";
 const WHATS_NEW = {
     "0.4.0": [
         "🆕 VibeSharing MCP v0.4.0 — What's New:",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vibesharingapp/mcp-server",
-  "version": "0.4.1",
+  "version": "0.4.2",
   "description": "MCP server for VibeSharing - register prototypes and get feedback directly from Claude Code",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",