untappd-mcp 1.8.3 → 1.8.5

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.8.3"
+    "version": "1.8.5"
   },
   "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.8.3",
+      "version": "1.8.5",
       "author": {
         "name": "Chris Hall"
       },

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "untappd-mcp",
   "displayName": "Untappd",
-  "version": "1.8.3",
+  "version": "1.8.5",
   "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

@@ -52,21 +52,6 @@ your own app's traffic with an HTTPS proxy:
 
 Keep these values private; do not commit them.
 
-## Remote connector
-
-This server can also run as a hosted Cloudflare Worker — an unlisted, shareable
-"remote connector" you add to claude.ai (Settings → Connectors) instead of
-running it locally. It works on Claude web, desktop, and mobile alike, since
-connectors added on any of those sync to the rest. Each person you share it
-with logs in with their *own* Untappd username and password; the operator only
-ever supplies the shared Untappd app credentials, never anyone's personal
-login. The `.mcpb` / stdio install above remains the desktop-only alternative
-if you'd rather run it locally against just your own account.
-
-Setting this up requires a Cloudflare account and is a manual, one-time
-process for whoever hosts it — see
-[`docs/DEPLOY-CONNECTOR.md`](docs/DEPLOY-CONNECTOR.md) for the full runbook.
-
 ## Tools
 
 Reads: `untappd_search_beer`, `untappd_beer_info`, `untappd_beer_activity`,
@@ -92,9 +77,9 @@ The Untappd API only exposes paged 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 SQLite mirror 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.
+offline, with zero API calls. The mirror is a local file
+(`node:sqlite`, path via `UNTAPPD_CACHE_DB`); the store is injectable, so another
+deployment can back it differently without the tools changing.
 
 Two sync sources fill the cache:
 
@@ -147,13 +132,9 @@ 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.
+A cache holds only the check-ins the account it belongs to was allowed to
+fetch. `untappd_healthcheck` reports the running version and the exact tool set
+(count + names + a stable hash), so you can confirm which build is serving.
 
 ## Development
 

package/dist/bundle.js

@@ -31232,7 +31232,7 @@ function toolAnnotations(opts = {}) {
 }
 
 // src/version.ts
-var VERSION = "1.8.3";
+var VERSION = "1.8.5";
 
 // src/client.ts
 import { dirname, join } from "path";
@@ -33772,9 +33772,8 @@ await runMcp({
     (s) => registerWishlistTools(s, client),
     (s) => registerCheckinTools(s, client),
     (s) => registerUtilityTools(s, client),
-    // The stdio server backs the cache with a local `node:sqlite` file; the
-    // remote Cloudflare connector (src/worker.ts) backs the same cache tools
-    // with a per-user Durable Object instead.
+    // The cache is backed by a local `node:sqlite` file here; the provider is
+    // injectable, so another deployment can back the same tools differently.
     (s) => registerCacheTools(s, client, nodeCacheProvider),
     // Keep last: logs the full registered toolset (count + names) at startup.
     (s) => logRegisteredTools(s, "stdio")

package/dist/cache/db.js

@@ -7,8 +7,8 @@ import { CheckinStoreCore, LocalCacheStore } from './store.js';
 // The `node:sqlite` backend for the check-in cache — a local on-disk SQLite file
 // used by the stdio/desktop server. The query logic lives in CheckinStoreCore
 // (src/cache/store.ts); this file only adapts `node:sqlite` to the SqlDriver
-// surface and manages the file handle. (The remote Cloudflare connector uses a
-// Durable Object backend instead — see src/cache/durable.ts.)
+// surface and manages the file handle. Another deployment can adapt a
+// different driver to the same surface.
 /** Adapts a `node:sqlite` DatabaseSync to the driver surface the core needs. */
 class NodeSqlDriver {
     db;

package/dist/cache/store.js

@@ -14,9 +14,9 @@
 //    anyone — this is what gives full "has had" coverage.
 //
 // The SQL lives here ONCE, over a tiny synchronous {@link SqlDriver}, so the same
-// schema/queries back both engines: `node:sqlite` on the stdio server and a
-// Durable Object's SQLite on the connector. This module imports nothing
-// platform-specific.
+// schema/queries back any engine: `node:sqlite` is the one that ships, and a
+// different deployment can adapt another driver to the same surface. This
+// module imports nothing platform-specific.
 function asDict(v) {
     return v && typeof v === 'object' && !Array.isArray(v) ? v : {};
 }

package/dist/client.js

@@ -61,9 +61,8 @@ function xauthHeaders(userAgent) {
 /**
  * Performs the one-shot Untappd xauth login POST (username/password →
  * access token). Standalone so it can be reused both by `UntappdClient`'s
- * own on-demand login and by the Cloudflare-connector login flow
- * (`src/untappd-auth.ts`), which authenticates a user before a client even
- * exists — without duplicating the request/parsing logic.
+ * own on-demand login and by any login flow that authenticates a user before
+ * a client even exists — without duplicating the request/parsing logic.
  */
 export async function xauthLogin(creds, opts = {}) {
     const fetchImpl = opts.fetchImpl ?? fetch;

package/dist/index.js

@@ -40,9 +40,8 @@ await runMcp({
         (s) => registerWishlistTools(s, client),
         (s) => registerCheckinTools(s, client),
         (s) => registerUtilityTools(s, client),
-        // The stdio server backs the cache with a local `node:sqlite` file; the
-        // remote Cloudflare connector (src/worker.ts) backs the same cache tools
-        // with a per-user Durable Object instead.
+        // The cache is backed by a local `node:sqlite` file here; the provider is
+        // injectable, so another deployment can back the same tools differently.
         (s) => registerCacheTools(s, client, nodeCacheProvider),
         // Keep last: logs the full registered toolset (count + names) at startup.
         (s) => logRegisteredTools(s, 'stdio'),

package/dist/tools/cache.js

@@ -79,8 +79,8 @@ async function freshness(cache, username) {
 }
 /**
  * Register the check-in cache tools. `cacheProvider` supplies the backing store
- * (a `node:sqlite` file on the stdio server, a Durable Object on the remote
- * connector) and is required so this module imports no platform-specific code.
+ * (a `node:sqlite` file here) and is required so this module imports no
+ * platform-specific code.
  */
 export function registerCacheTools(server, client, cacheProvider) {
     server.registerTool('untappd_sync_checkins', {

package/dist/tools/diagnostics.js

@@ -1,7 +1,7 @@
 // Small helpers so the live build's exact toolset is visible from the client
 // (via untappd_healthcheck) and from server logs (a startup line). This is how
 // you confirm a deploy actually shipped the tools you expect — e.g. that the
-// remote connector is exposing the cache tools, not a stale 37-tool build.
+// server is exposing the cache tools, not a stale 37-tool build.
 /** The names of every tool registered on `server`, sorted. Defensive if the SDK internal shape drifts. */
 export function registeredToolNames(server) {
     const reg = server._registeredTools;

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 = '1.8.3'; // x-release-please-version
+export const VERSION = '1.8.5'; // x-release-please-version

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "untappd-mcp",
-  "version": "1.8.3",
+  "version": "1.8.5",
   "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>",
@@ -37,29 +37,20 @@
     "dev": "node dist/index.js",
     "test": "vitest run",
     "test:watch": "vitest",
-    "test:coverage": "vitest run --coverage",
-    "worker:dev": "wrangler dev",
-    "worker:deploy": "wrangler deploy",
-    "worker:test": "vitest run --config vitest.workers.config.ts"
+    "test:coverage": "vitest run --coverage"
   },
   "dependencies": {
-    "@chrischall/mcp-utils": "^0.13.1",
+    "@chrischall/mcp-utils": "^0.14.0",
     "@modelcontextprotocol/sdk": "^1.29.0",
     "ai": "^7.0.19",
     "dotenv": "^17.4.0",
     "zod": "^4.4.2"
   },
   "devDependencies": {
-    "@chrischall/mcp-connector": "^1.1.1",
-    "@cloudflare/vitest-pool-workers": "^0.19.0",
-    "@cloudflare/workers-oauth-provider": "^0.8.1",
-    "@cloudflare/workers-types": "^5.20260708.1",
     "@types/node": "^26.1.1",
     "@vitest/coverage-v8": "^4.1.2",
-    "agents": "^0.19.0",
     "esbuild": "^0.28.0",
     "typescript": "^7.0.2",
-    "vitest": "^4.1.2",
-    "wrangler": "^4.110.0"
+    "vitest": "^4.1.2"
   }
 }

package/server.json

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

package/skills/untappd-mcp/SKILL.md

@@ -58,7 +58,7 @@ 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 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.
+the store is injectable, so another deployment can back it differently. Same tools either way.
 
 **Sync first, then query.** Two sources; both resumable (`max_pages`/call,
 progress saved per page, `another_run_needed` until done). Omit `username` for