untappd-mcp 2.5.2 → 2.6.1

package/dist/tools/wishlist.js

@@ -1,4 +1,5 @@
 import { z } from 'zod';
+import { foodMeta } from './hints.js';
 import { confirmTokenParam, minifiedResult, toolAnnotations } from '@chrischall/mcp-utils';
 import { CONFIRM_FLOW, confirmWrite } from './confirm.js';
 const BidSchema = z.number().int().positive().describe('Untappd beer id (bid) — from untappd_search_beer');
@@ -7,6 +8,7 @@ export function registerWishlistTools(server, client) {
         title: 'Add a beer to your wishlist',
         description: `Add a beer to YOUR Untappd wishlist by its bid. Writes to your account. ${CONFIRM_FLOW}`,
         annotations: toolAnnotations({ title: 'Add a beer to your wishlist', readOnly: false, idempotent: true, openWorld: true, destructive: false }),
+        _meta: foodMeta('change', { aliases: ['want to try', 'save a beer'] }),
         inputSchema: z.object({
             bid: BidSchema,
             confirmToken: confirmTokenParam,
@@ -33,6 +35,7 @@ export function registerWishlistTools(server, client) {
         title: 'Remove a beer from your wishlist',
         description: `Remove a beer from YOUR Untappd wishlist by its bid. Writes to your account. ${CONFIRM_FLOW}`,
         annotations: toolAnnotations({ title: 'Remove a beer from your wishlist', readOnly: false, idempotent: true, openWorld: true, destructive: false }),
+        _meta: foodMeta('change'),
         inputSchema: z.object({
             bid: BidSchema,
             confirmToken: confirmTokenParam,

package/dist/version.js

@@ -3,4 +3,4 @@
 // json's `extra-files`), and `versionSyncTest` guards that it stays equal to
 // package.json. Import VERSION wherever the version is needed rather than
 // re-declaring it.
-export const VERSION = '2.5.2'; // x-release-please-version
+export const VERSION = '2.6.1'; // x-release-please-version

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "untappd-mcp",
-  "version": "2.5.2",
+  "version": "2.6.1",
   "mcpName": "io.github.chrischall/untappd-mcp",
   "description": "Untappd MCP server for Claude — developed and maintained by AI (Claude Code)",
   "author": "Claude Code (AI) <https://www.anthropic.com/claude>",

package/server.json

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

package/skills/untappd-mcp/SKILL.md

@@ -73,6 +73,16 @@ answer, wrong reason. **The same silence bites the other way**: `compact:
 false` no longer buys you the full record either. It is dropped identically
 and you still get compact. `view: "full"` is the only way back.
 
+`untappd_activity_feed` also takes a third rung, `view: "brief"`: one line per
+check-in, `<user>: <beer> (<brewery>) at <venue> — <ISO date | no date> —
+<rated N | not rated>`, each at most 120 characters, answered inside the
+untrusted-data envelope as `data: string[]` (the names are other Untappd
+users'). A line starting `-- ` is a note, not a check-in: `-- none` for an
+empty feed, `-- more` when an older page exists; a name that itself starts
+with `-- ` or `\` is escaped with one leading `\`. It is the shape a
+context-group host reads aloud (below); use it when you only need to say what
+friends have been drinking.
+
 Compact comes in two tiers here, and they are not the same thing:
 
 **A hand-written field projection — 9 tools.**
@@ -245,3 +255,25 @@ owner-only (dir `0700`, file `0600`).
 Every cache read returns a `freshness` block reporting each source's completeness
 separately (plus `coverage_complete` and a `caveat` when incomplete), so you can
 flag a "not found" as possibly a false negative until the relevant sync finishes.
+
+## In context groups
+
+On an mcp-host connector this server is a member of the **food** group (every
+tool but `untappd_healthcheck` carries a `_meta.mint` hint with
+`domain: "food"`). Its one canonical read is **`untappd_activity_feed`** for
+**what's new** — the friend feed, answered with `view: "brief"`. It takes no
+subject and no date range: Untappd has no listable set of the person's own
+subjects (no children, properties or accounts to fan out over), so the group
+asks it once, not once per person. Nothing here answers what's due or what's
+on; every other read is a `lookup` (`untappd_notifications` is a non-canonical
+what's-new), and the writes are `send` (toast, comment, friend request),
+`change` (check-in, deletes, wishlist, favourites, friend accept/reject/remove)
+or `other` (the cache syncs and the pickers, which refresh the local cache as
+they read).
+
+A compound ask looks like *"what's new with food — any new reservations, and
+what have my friends been drinking?"*: the host answers the Untappd half from
+the feed's brief lines beside the group's other members. This server calls the
+Untappd API directly, so it never answers "needs your browser open"; if it is
+not configured, the group reports it as unable to answer and
+`untappd_healthcheck` says which credential is missing.