CellarTracker

Name: CellarTracker
Author: slavins-co

by slavins-coversion 0.5.4i★ 7iRuns on your computer

Registry nameio.github.slavins-co/cellartracker-mcp

Install

Overview

Description from the maker (original English)

Read-only access to your CellarTracker wine cellar: inventory, drinking windows, purchases, notes.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi2 of 2 passedChecked from public information; code not scanned yet
UsageiEarly↓ 143/wk · ★ 7

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Online shops & payments
You need to fill in: CT_PASSWORD

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 2 of 2 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: CT_USERNAME, CT_PASSWORD

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "cellartracker": {
      "command": "npx",
      "args": [
        "-y",
        "cellartracker-mcp"
      ],
      "env": {
        "CT_USERNAME": "your-value",
        "CT_PASSWORD": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add cellartracker --env CT_USERNAME=your-value --env CT_PASSWORD=your-value -- npx -y cellartracker-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "cellartracker": {
      "command": "npx",
      "args": [
        "-y",
        "cellartracker-mcp"
      ],
      "env": {
        "CT_USERNAME": "your-value",
        "CT_PASSWORD": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "cellartracker": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "cellartracker-mcp"
      ],
      "env": {
        "CT_USERNAME": "your-value",
        "CT_PASSWORD": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

CT_USERNAME env
CellarTracker username. Optional at install: the setup-credentials tool can store login locally instead.
CT_PASSWORD secret env
CellarTracker password. Optional at install: the setup-credentials tool can store login locally instead.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 10, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account slavins-co, which owns the repo
✓ Pass
Still maintained
Code last changed 6 days ago
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Online shops & paymentsi

More stars than 96% of the other 2657 servers in this category
Published to the registry more recently than 50% of the other 2657 servers in this category
Basic checks equal to or better than 100% of the other 2657 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is CellarTracker safe?

It passed 2 of 2 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: CT_PASSWORD

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 6 days ago, and the latest version (0.5.4) reached the registry 28 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spree Commerce developer docs for AI agents, Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spree Commerce developer docs for AI agents

Spree Commerce docs for AI coding agents: build headless B2B and marketplace ecommerce on its APIs.

by spreeWidely used★ 15.8KUpdated 11 days ago

Runs in the cloud

Install

Spree Commerce: open-source B2B and marketplace ecommerce

Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.

by spreeWidely used★ 15.8KUpdated 11 days ago

Runs in the cloud

Install

Stripe MCP

Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.

by stripeWidely used★ 2.1KUpdated 13 months ago

Runs in the cloud✓ stripe.com

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

CellarTracker MCP

Disclaimer: This is a community-maintained project with no affiliation to, or endorsement by, CellarTracker! LLC. It uses CellarTracker's self-serve data export on your own account's behalf.

Connect Claude to your CellarTracker wine cellar. Query your inventory, get drinking recommendations, and analyze purchases and drinking history, all through natural conversation. No need to refresh your inventory, or share your tasting notes. Claude pulls them directly from your CellarTracker account.

Install

Two install methods for different Claude interfaces. You may need one or both:

	Desktop Extension (.mcpb)	Claude Code Plugin
Works in	Chat (Desktop), Cowork	Cowork, Code
Tools	11 cellar tools	All 13 tools (includes `setup-credentials` and `clear-user-data`)
Skills	No	Yes
Setup	One-click download	Marketplace or CLI
Credentials	Prompted on install, stored in OS keychain	Run `setup-credentials` after install

Which do I need?

Chat (Desktop) only → Desktop Extension
Code only → Claude Code Plugin
Cowork only → Either works (plugin adds skills)
Full coverage → Install both

Installing both is safe. The extension covers Chat (Desktop); the plugin covers Cowork and Code. In Cowork, both are accessible without conflict. Note, there is no coverage for claude.ai web chat sessions.

Desktop Extension (Chat & Cowork)

One-click install. No terminal needed.

Download cellartracker-mcp.mcpb from the latest release
Double-click the file to install in Claude Desktop
Enter your CellarTracker username and password when prompted
Start chatting (e.g. *"What wines should I open this month?"*)

Credentials are stored in your OS keychain (macOS Keychain / Windows Credential Manager). To update them later, go to Customize > Connectors > CellarTracker.

Claude Code Plugin (Cowork & Code)

Full experience with tools and skills.

Via Desktop app

Open the Code tab > Customize > Browse plugins > Personal > + > Add marketplace from GitHub > enter slavins-co/cellartracker-mcp
Find "CellarTracker MCP" in the plugin browser and click Install
Set up credentials immediately: In a new Code or Cowork session, say *"Set up my CellarTracker credentials"*

Via terminal

Step 1: Add the marketplace

/plugin marketplace add slavins-co/cellartracker-mcp

Step 2: Install the plugin

/plugin install cellartracker-mcp@cellartracker-mcp

Step 3: Set up credentials immediately — say:

*"Set up my CellarTracker credentials"*

Claude will verify and save them. No restart needed. Without credentials, tools will return errors and skills won't have data to work with.

Alternative: Set CT_USERNAME and CT_PASSWORD as environment variables in your shell profile.

Credentials are stored only on your machine. When using the setup tool, they pass through Anthropic's servers as part of the conversation. They are sent to CellarTracker's servers for authentication.

What you can do

Tool	What it does
`setup-credentials`	Connect your CellarTracker account (Claude Code plugin only — Desktop Extension handles credentials during install)
`search-cellar`	Find wines by name, color, region, varietal, location, or vintage
`drinking-recommendations`	Wines to open now, sorted by drinking window urgency
`cellar-stats`	Collection overview — totals and breakdowns by any dimension
`purchase-history`	Spending analysis by store, date range, or wine
`recent-deliveries`	Wines actually received in a date range, by delivery date (not order date)
`incoming-orders`	Wines ordered but not yet received — what's on the way
`get-wishlist`	Your wishlist with notes on why each wine was added and a max price
`consumption-history`	Wines you've opened — by name, color, or date range
`tasting-notes`	Your tasting notes and reviews with ratings and scores
`bottle-details`	Find individual bottles by name, location, bin, size, or barcode — cellar and consumed
`refresh-data`	Force a fresh pull (auto-refreshes every 24 hours)
`clear-user-data`	Remove stored credentials and cached data from this machine (Claude Code plugin only)

Every tool returns structured JSON alongside its readable text, so clients can compute over results directly. List tools support offset pagination past the 25-per-page cap.

Resources

For bulk analysis without per-tool result caps, the server also exposes the cached table exports as MCP resources: cellartracker://tables/ (raw CSV, one per table — List, Notes, Purchase, Consumed, Availability, Tag, Bottles, Pending) and cellartracker://meta/cache (JSON freshness timestamps per table plus the server version, readable without credentials).

Included skills

Note: Skills are available in Cowork and Code modes via the Claude Code plugin. Chat mode (Desktop Extension) provides tools only.

cellartracker-data — Teaches Claude to interpret CellarTracker data: table relationships, score abbreviations, drinking windows, and query routing.

wine-purchase-evaluator — Framework for evaluating wine purchases. Two-score system (Quality + Personal Fit) with BUY/CONSIDER/PASS verdicts. Checks your cellar for redundancy, verifies pricing, and applies drinking window discipline.

To customize the evaluator for your preferences, copy skills/wine-purchase-evaluator/references/preferences-example.md to preferences.md in the same directory and edit it.

How it works

CellarTracker has no official API. This server uses their CSV export endpoint, which authenticates with your username and password over HTTPS. Data is cached locally and auto-refreshes every 24 hours.

The server can only access your data — inventory, purchases, notes, and wishlist. It cannot search CellarTracker's full wine database.

Security & credentials

CellarTracker API limitations

CellarTracker has no OAuth, API keys, or scoped tokens. Authentication requires your actual account username and password, sent as URL query parameters over HTTPS. While encrypted on the wire, query parameters are routinely logged in server-side access logs on CellarTracker's infrastructure. There is no way to create read-only or limited-access credentials, therefore, this MCP only performs read operations, but it authenticates with your full account.

How this server protects your credentials

Protection	Details
File permissions	Config directory `0700`, `.env` file `0600` — only your OS user can read
Error stripping	Network errors are caught and re-thrown without the URL, which contains credentials
No logging	Credentials never appear in stdout, stderr, or error messages
OS keychain	Desktop Extension (`.mcpb`) stores credentials in macOS Keychain / Windows Credential Manager
Env var support	Set `CT_USERNAME` / `CT_PASSWORD` environment variables to avoid storing credentials on disk

The Claude Code plugin stores credentials as plaintext in ~/.config/cellartracker-mcp/.env. We evaluated OS keychain integration (#22) and decided against it. The native dependency cost (node-gyp / keytar) outweighs the security benefit for wine cellar data, and the Desktop Extension path already uses the OS keychain.

Recommendations

Use a unique password for CellarTracker. Do not reuse a password from other services.
Prefer environment variables over the setup-credentials tool if you want to avoid persisting credentials to disk.
Pin to a specific version in your MCP config (e.g., cellartracker-mcp@0.5.2) rather than relying on @latest.

Development

For contributors or anyone who wants to run from source:

git clone https://github.com/slavins-co/cellartracker-mcp.git

cd cellartracker-mcp npm install npm run build

Set credentials

cp .env.example .env

Edit .env with your CT login

Test as Claude Code plugin

claude --plugin-dir .

npx local-resolution footgun

If you run npx -y cellartracker-mcp (e.g. via an MCP client config) with your working directory inside a local checkout of this repo, npm can resolve the bare package name to that local folder instead of downloading it from the registry — so whatever is on disk in dist/ gets served, not the published version. npm install/npm ci now runs a prepare script that rebuilds dist/ automatically, so a fresh clone is always current. But if you edit src/ directly and don't run npm install or npm run build again, dist/ will silently go stale — the server keeps running the old compiled code with no error. If output looks wrong while developing, rebuild (npm run build) before assuming the bug is in src/.

AI Disclosure

This project was developed with AI assistance.

Trademark Disclosure

This project is in no way affiliated or connected to CellarTracker! LLC. "CellarTracker" is a trademark of CellarTracker! LLC.

License

MIT

CellarTracker

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Online shops & paymentsi

Common questions

Alternatives

Spree Commerce developer docs for AI agents

Spree Commerce: open-source B2B and marketplace ecommerce

Stripe MCP

README from the maker

CellarTracker MCP

Install

Desktop Extension (Chat & Cowork)

Claude Code Plugin (Cowork & Code)

Via Desktop app

Via terminal

What you can do

Resources

Included skills

How it works

Security & credentials

CellarTracker API limitations

How this server protects your credentials

Recommendations

Development

Set credentials

Edit .env with your CT login

Test as Claude Code plugin

npx local-resolution footgun

AI Disclosure

Trademark Disclosure

License