splitwise-mcp 3.5.1 → 3.7.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "splitwise-mcp",
-  "version": "3.5.1",
+  "version": "3.7.0",
   "mcpName": "io.github.chrischall/splitwise-mcp",
   "description": "Splitwise MCP server for Claude — developed and maintained by AI (Claude Code)",
   "author": "Claude Code (AI) <https://www.anthropic.com/claude>",
@@ -45,10 +45,10 @@
     "typecheck": "tsc -p tsconfig.json --noEmit"
   },
   "dependencies": {
-    "@chrischall/mcp-utils": "^3.3.0",
+    "@chrischall/mcp-utils": "^3.6.0",
     "@modelcontextprotocol/server": "^2.3.0",
     "dotenv": "^18.0.2",
-    "unpdf": "^1.8.1",
+    "unpdf": "^2.0.0",
     "zod": "^4.6.5"
   },
   "devDependencies": {

package/server.json

@@ -6,12 +6,12 @@
     "url": "https://github.com/chrischall/splitwise-mcp",
     "source": "github"
   },
-  "version": "3.5.1",
+  "version": "3.7.0",
   "packages": [
     {
       "registryType": "npm",
       "identifier": "splitwise-mcp",
-      "version": "3.5.1",
+      "version": "3.7.0",
       "transport": {
         "type": "stdio"
       },

package/skills/splitwise-mcp/SKILL.md

@@ -111,9 +111,31 @@ API key auth — no login flow or token rotation. The key is attached to every r
 | `sw_get_categories` | Hierarchical list of expense categories (use `id` as `category_id`) |
 | `sw_get_currencies` | List of supported currency codes |
 
+## In context groups
+
+On an mcp-host gateway, splitwise joins the **money** group (`_meta.mint` on every
+tool but `sw_healthcheck`). Its canonical reads, each answering one line per item
+with `view: "brief"` inside the untrusted-data envelope (`data: string[]`):
+
+- **what's due** — `sw_list_friends`: one line per friend with an outstanding
+  balance, `name — no date — owes you USD 12.50` / `you owe EUR 3.00`, then a
+  `-- N settled up` note; `-- none` when nothing is owed either way.
+- **what's new** — `sw_get_notifications`: recent activity, `text — <ISO date> —
+  <kind>` (expense added, comment added, …), at most 50 lines with a
+  `-- 50 of M shown` note past that; `-- none` for no activity.
+
+Neither names a subject (one API key is one account; friends and groups are who
+you split with, not whose question it is) and neither takes a date range. Nothing
+here answers what's on. Every other read is a `lookup`; the writes are `change`
+(`sw_create_comment` is `send`). A compound ask looks like "what do I owe on
+Splitwise, and is anything due at school?" — the money group reads the balances
+while the school group answers the rest. Splitwise is a direct API with a key,
+not a browser bridge, so it never answers "needs your browser open".
+
 ## Response shape (`view`)
 
-Nine read tools take `view: "compact" | "full"`, and **`compact` is the
+Nine read tools take `view: "compact" | "full"` (`sw_list_friends` and
+`sw_get_notifications` also take `"brief"`, above), and **`compact` is the
 default** — you get the slim rung without asking. Two of them are not in the
 table above: `sw_get_user(id, view?)` and `sw_get_comments(expense_id, view?)`.
 
@@ -215,7 +237,7 @@ sw_create_expense(group_id, "Band camp water jug", "54.11", split_equally: true,
 sw_attach_receipt(expense_id, receipt: { base64: "<png/jpeg/gif/pdf bytes>", filename: "order.pdf" })
 ```
 
-`receipt` takes `filename` plus exactly one of `upload_id` (hosted server: from `sw_get_upload_url`, after `curl -X PUT` of the file — keeps the bytes out of the conversation and out of the second, confirming call), `path` (only on a local server with `SPLITWISE_INPUT_DIR` set, and only inside that directory) or `base64` (fallback when you have no shell that can reach the upload URL). PNG, JPEG, GIF or PDF, ≤ 10 MiB, type detected from the bytes. It replaces any existing receipt. Use `sw_attach_receipt` to add a file to an existing expense — it sends nothing but the file. If Splitwise saves the expense but drops the file, the tool returns an error naming the expense: do not re-create it, retry with `sw_attach_receipt`.
+`receipt` takes `filename` plus exactly one of `upload_id` (hosted server: from `sw_get_upload_url`, after `curl -X PUT` of the file — keeps the bytes out of the conversation and out of the second, confirming call), `path` (only on a local server with `SPLITWISE_INPUT_DIR` set, and only inside that directory) or `base64` (fallback when you have no shell that can reach the upload URL). PNG, JPEG, GIF or PDF, ≤ 10 MiB, type detected from the bytes. It replaces any existing receipt. Use `sw_attach_receipt` to add a file to an existing expense — it sends nothing but the file. If Splitwise saves the expense but drops the file, the tool returns an error naming the expense: do not re-create it, retry with `sw_attach_receipt`. An `upload_id` is single use: once the receipt is stored the upload is deleted (`upload_deleted: true`), so attaching the same file again needs a fresh `sw_get_upload_url`. A declined preview or a failed write keeps it — retry with the same `upload_id`. `upload_deleted: false` (with `upload_delete_error`) is not a failure: the receipt is attached; the copy just waits for the server's retention cleanup.
 
 **Log a 50/50 expense the other person paid:**
 ```