Log inSubmit server

Hidden while we check this listing

Our automated checks found a problem, so this listing is out of search, browse and the API until it clears. It comes back on its own once the problem is fixed.

  • Package no longer on the registry
Own this project? Claim it
CellarTracker logo

CellarTracker

Read-only wine cellar access through CellarTracker exports, with inventory, drinking windows, purchases, notes, and history.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install CellarTracker

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "cellartracker": {
      "command": "npx",
      "args": [
        "-y",
        "local-resolution"
      ],
      "env": {
        "CT_USERNAME": "YOUR_VALUE_HERE",
        "CT_PASSWORD": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The CellarTracker MCP server reads your CellarTracker account through its CSV export endpoint and exposes cellar data to supported Claude interfaces. It provides tools for inventory searches, drinking recommendations, purchase and consumption analysis, tasting notes, bottle details, deliveries, orders, and wishlist data, with local caching and structured JSON results. Reach for it when you want conversational analysis of your own cellar rather than searches across CellarTracker’s complete wine database.

Use cases

  • Search a personal wine inventory by region, varietal, vintage, or location
  • Find bottles that are ready to drink
  • Analyze wine purchases and delivery history
  • Review tasting notes and consumption history
  • Inspect cellar data in bulk through MCP resources

Key features

  • Read-only access to account cellar exports
  • Drinking-window recommendations
  • Purchase, delivery, order, and consumption analysis
  • Tasting notes, wishlist, and bottle lookup
  • Local caching with 24-hour refresh
  • Structured JSON results and paginated lists

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

5/5 checks healthy over the last 46d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 11d ago via OSV.dev · local-resolution (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars7Stargazers on the source repository.
Last commit3d agoMost recent push to the default branch.

How CellarTracker works

What CellarTracker MCP server does

The CellarTracker MCP server gives Claude read-only access to data exported from your CellarTracker account. It can search wines by attributes such as name, color, region, varietal, location, or vintage; identify bottles approaching or within their drinking windows; summarize cellar totals; and analyze purchases, deliveries, incoming orders, consumption, tasting notes, and wishlist entries.

Bottle lookup supports details such as location, bin, size, and barcode, including bottles that have already been consumed. The server also offers a refresh operation when the cached copy needs to be updated. Results include readable text and structured JSON, allowing an MCP client to calculate over returned data. List-oriented tools support offset pagination beyond 25 results per page.

How it works

CellarTracker does not provide an official API for this integration. Instead, the server authenticates to the account’s CSV export endpoint over HTTPS and stores the exported tables locally. Cached data refreshes automatically every 24 hours. Available MCP resources expose raw CSV tables through cellartracker://tables/<Table> for bulk analysis, while cellartracker://meta/cache reports cache freshness timestamps and the server version.

The integration reads only the account connected to it. It cannot search CellarTracker’s broader wine catalog. The Claude Code plugin also includes skills for interpreting the exported tables and evaluating potential wine purchases. Those skills are available in Cowork and Code modes, not through the Desktop Extension’s chat tools.

Setup and configuration

The Desktop Extension is installed by downloading the .mcpb release file and opening it in Claude Desktop. Installation prompts for the CellarTracker username and password, which are stored in the macOS Keychain or Windows Credential Manager. Credentials can later be changed through the connector settings.

The Claude Code Plugin can be installed from the project’s GitHub marketplace or with the Claude plugin commands. After installation, start a Code or Cowork session and request credential setup. The plugin can alternatively read CT_USERNAME and CT_PASSWORD from the shell environment. Its setup tool stores credentials in ~/.config/cellartracker-mcp/.env; using environment variables avoids that file-based storage.

The Desktop Extension provides 11 cellar tools. The plugin provides all 13 tools, including credential setup and local data removal. Desktop covers Chat and Cowork, while the plugin covers Cowork and Code. Neither method provides access to claude.ai web chat sessions.

Limitations and notes

CellarTracker MCP server authentication requires the account’s actual username and password because CellarTracker does not offer OAuth, API keys, or scoped credentials. Although requests use HTTPS, credentials are sent as URL query parameters and may be recorded in service-side access logs. The integration therefore performs read operations only, but the account credentials still have the permissions of the full account.

The project removes credential-bearing URLs from network errors and does not write credentials to standard output, standard error, or error messages. Its configuration directory is restricted to the local user, and the plugin’s .env file uses restrictive permissions. The Desktop Extension uses the operating system keychain, while the Claude Code Plugin stores its credentials as plaintext in its configuration file.

Use a unique CellarTracker password, consider environment variables when avoiding disk persistence matters, and pin a specific package version instead of relying on @latest. The project is community-maintained and is not affiliated with or endorsed by CellarTracker LLC.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about CellarTracker

CellarTracker is an MCP server that connects Claude to your CellarTracker account through its CSV export endpoint. Its main tools search cellar inventory, recommend wines by drinking window, analyze cellar statistics and purchases, retrieve deliveries and orders, inspect notes and bottles, and refresh cached data. It performs read-only operations.

Install the Desktop Extension by downloading the `.mcpb` release and opening it in Claude Desktop, or install the Claude Code Plugin from the project marketplace or plugin commands. The extension supports Chat and Cowork; the plugin supports Cowork and Code.

Configure credentials by entering your username and password during Desktop Extension installation, using the plugin’s setup-credentials tool, or setting `CT_USERNAME` and `CT_PASSWORD` in the shell environment. The plugin stores setup-tool credentials in its local configuration file.

No, it can access only data from the connected account. Searches cover the account’s inventory and related exports, but the server cannot query CellarTracker’s complete wine database.

Related MCP servers

All in Other Tools and Integrations All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewCellarTracker AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/cellartracker?style=directory)](https://allmcps.com/mcp/cellartracker)
HTML Embed
<a href="https://allmcps.com/mcp/cellartracker"><img src="https://allmcps.com/api/badge/cellartracker?style=directory" alt="CellarTracker on AllMCPs" /></a>