vibo-mcp 2.2.2 → 2.3.0

package/.claude-plugin/marketplace.json

@@ -7,7 +7,7 @@
   },
   "metadata": {
     "description": "MCP server for Vibo (vibodj.com) — plan & manage event music, song requests, ideas, guests, and playlists via natural language",
-    "version": "2.2.2"
+    "version": "2.3.0"
   },
   "plugins": [
     {
@@ -15,7 +15,7 @@
       "displayName": "Vibo",
       "source": "./",
       "description": "MCP server for Vibo — browse & manage events, timeline, songs, the DJ song ideas/questions, guests, and exports to Spotify/Apple Music",
-      "version": "2.2.2",
+      "version": "2.3.0",
       "author": {
         "name": "Chris Hall"
       },

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "vibo-mcp",
   "displayName": "Vibo",
-  "version": "2.2.2",
+  "version": "2.3.0",
   "description": "MCP server for Vibo (vibodj.com) — plan & manage event music, song requests, ideas, guests, and playlists via natural language",
   "author": {
     "name": "Chris Hall",

package/README.md

@@ -38,14 +38,38 @@ Choose one method:
 The server boots without credentials; the config error only surfaces on the
 first tool call.
 
+### Uploads
+
+`vibo_set_profile_photo` and photo/file answers to `vibo_answer_question` only
+read local files from the upload directory — `VIBO_UPLOAD_DIR`, default
+`~/Downloads/vibo-mcp`. Copy a file there before asking Claude to upload it.
+Hidden files, symlinks that lead outside the directory, and files over 25 MiB
+are refused, and photo slots need an image file.
+
+### Confirmations
+
+Every write (adding or removing songs, comments, invites, exports, answers,
+uploads, …) is confirmed before anything is sent to Vibo.
+
+| variable | default | |
+|---|---|---|
+| `MCP_CONFIRM_MODE` | `ask-user` | What a write does on a client that cannot show a confirmation prompt (claude.ai, Claude Desktop). `ask-user`: two steps — the first call does nothing and returns a preview plus a token, and the model must get your approval in chat before calling again with it. `auto`: the same two steps, but the model may use the token after reviewing the preview itself. `refuse`: writes are refused on such clients. A client that can show prompts (Claude Code) always gets the real prompt. An unrecognised value is treated as `refuse`. |
+| `MCP_CONFIRM_TTL_SECONDS` | `600` | How long a token stays valid. |
+| `MCP_CONFIRM_SECRET` | random per process | Signing key; set it only if tokens must survive a server restart. |
+
+A token works once, only for the tool and arguments it was previewed with: a
+changed argument or a reused token is refused and nothing is sent.
+
 ## How it works
 
 Vibo's app talks to a GraphQL API at `https://api.vibodj.com/v2/graphql`,
 authenticating with an `x-token` header obtained from an email/password
 `signIn`. This server reuses that same flow server-side (no browser needed) and
-wraps the host/couple operations as MCP tools. Every mutating tool is
-confirm-gated: without `confirm: true` it returns a dry-run preview and makes no
-network call.
+wraps the host/couple operations as MCP tools. Every mutating tool asks you to
+confirm first: a client that can show a confirmation prompt (Claude Code) shows
+one; otherwise the first call makes no network call and returns a preview plus a
+`confirmToken`, and only a repeat call with that token makes the change (see
+[Confirmations](#confirmations)).
 
 See [docs/VIBO-API.md](docs/VIBO-API.md) for the reverse-engineered API notes
 and [skills/vibo-mcp/SKILL.md](skills/vibo-mcp/SKILL.md) for the full tool list.