# CellarTracker [Health: Active]

**Category:** 🛠️ Other Tools and Integrations  
**Repository:** https://github.com/slavins-co/cellartracker-mcp  
**GitHub Stars:** 7  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/cellartracker

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

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "cellartracker": {
    "command": "npx",
    "args": ["-y","local-resolution"],
    "env": {
      "CT_USERNAME": "",
      "CT_PASSWORD": ""
    }
  }
}
```

**Requires environment variables:** `CT_USERNAME`, `CT_PASSWORD` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/cellartracker/readme_