untappd-mcp 1.3.1 → 1.5.0

package/.claude-plugin/marketplace.json

@@ -7,7 +7,7 @@
   },
   "metadata": {
     "description": "MCP server for Untappd — beers, breweries, venues, check-ins, wishlists, and your friend feed",
-    "version": "1.3.1"
+    "version": "1.5.0"
   },
   "plugins": [
     {
@@ -15,7 +15,7 @@
       "displayName": "Untappd",
       "source": "./",
       "description": "MCP server for Untappd — search beers/breweries/venues, read profiles/check-ins/wishlists, and post check-ins, toasts, and comments",
-      "version": "1.3.1",
+      "version": "1.5.0",
       "author": {
         "name": "Chris Hall"
       },

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "untappd-mcp",
   "displayName": "Untappd",
-  "version": "1.3.1",
+  "version": "1.5.0",
   "description": "MCP server for Untappd — search beers/breweries/venues, read check-ins and wishlists, and post check-ins, toasts, and comments",
   "author": {
     "name": "Chris Hall",

package/README.md

@@ -82,18 +82,19 @@ Writes (confirm-gated — return a dry-run preview unless called with
 `untappd_wishlist_add`, `untappd_wishlist_remove`, `untappd_delete_checkin`,
 `untappd_add_friend`, `untappd_accept_friend`, `untappd_reject_friend`, `untappd_remove_friend`.
 
-Local check-in cache (stdio/local only — needs a filesystem, so not available on
-the remote connector): `untappd_sync_checkins`, `untappd_cache_has_had`,
-`untappd_cache_has_had_many`, `untappd_cache_query`.
+Check-in cache: `untappd_sync_checkins`, `untappd_cache_has_had`,
+`untappd_cache_has_had_many`, `untappd_cache_not_had`, `untappd_cache_query`.
 
-## Local check-in cache
+## Check-in cache
 
 The Untappd API only exposes paged, most-recent-first check-in lists (50 per
 page) and has **no** "has this user ever had beer X?" lookup — answering that
 from the API alone means paging an entire history (often 11k+ check-ins) against
-a tight ~100-calls/hour rate limit. These tools maintain a local SQLite mirror
-of a user's check-ins so the question is answered instantly, offline, with zero
-API calls.
+a tight ~100-calls/hour rate limit. These tools maintain a SQLite mirror of a
+user's check-ins so the question is answered instantly, offline, with zero API
+calls. The mirror is a local file on the stdio/desktop server (`node:sqlite`,
+path via `UNTAPPD_CACHE_DB`) and a per-user Durable Object on the remote
+connector — the tools and behaviour are identical either way.
 
 **Recommended workflow — sync first, then query:**
 
@@ -113,6 +114,8 @@ API calls.
      date, and the matching check-ins.
    - `untappd_cache_has_had_many` — cross-check a whole list of `bids` in one
      call (e.g. a venue's menu) → had/not-had per beer.
+   - `untappd_cache_not_had` — given a list of `bids`, return just the ones the
+     user has **not** had — the "what's new to me on this menu?" filter.
    - `untappd_cache_query` — filter cached check-ins by brewery, style,
      `min_rating`, venue, and/or date range, with sorting and a limit.
 
@@ -126,6 +129,14 @@ Syncing **another** user goes through the same authed endpoint as
 account is public or your friend. Otherwise the sync returns a clear error
 telling you to add them as a friend first.
 
+On the remote connector each logged-in user gets their **own** durable cache
+(keyed by their account), holding only the check-ins their account was allowed
+to fetch — one user can never read another's cache. See
+[`docs/DEPLOY-CONNECTOR.md`](docs/DEPLOY-CONNECTOR.md) for the one-time deploy
+step this adds. `untappd_healthcheck` reports the running version and the exact
+tool set (count + names + a stable hash), so you can confirm which build a
+connector is serving.
+
 ## Development
 
 ```sh

package/SKILL.md

@@ -46,13 +46,13 @@ Each returns a dry-run preview and makes NO network call unless called with
 
 Photo attachment and wishlist add/remove are not yet supported.
 
-## Local check-in cache (stdio/local only)
+## Check-in cache
 
 The API can't answer "has this user ever had beer X?" without paging their whole
-history (50/page, rate-limited). These tools keep a local SQLite mirror so that
-question is answered instantly with **no** API calls. `UNTAPPD_CACHE_DB` sets the
-db path (default `~/.untappd-mcp/checkins.db`). Not available on the remote
-connector (no filesystem).
+history (50/page, rate-limited). These tools keep a SQLite mirror so that
+question is answered instantly with **no** API calls. On the stdio server the
+mirror is a local file (`UNTAPPD_CACHE_DB`, default `~/.untappd-mcp/checkins.db`);
+on the remote connector it's a per-user Durable Object. Same tools either way.
 
 **Sync first, then query:**
 
@@ -68,6 +68,8 @@ connector (no filesystem).
   case-insensitive `beer_name` substring.
 - `untappd_cache_has_had_many` — batch had/not-had for a list of `bids` in one
   call (venue-menu cross-check).
+- `untappd_cache_not_had` — given a list of `bids`, return only the ones the user
+  has NOT had ("what's new to me on this menu?").
 - `untappd_cache_query` — filter cached check-ins by brewery, style, `min_rating`,
   venue, and date range, with sort + limit.