CellarTracker — Claude Code MCP server: query your wine cellar
Hooks your CellarTracker account into an AI agent so it can read inventory, drinking windows, purchases and tasting notes on request.
claude mcp add --env CT_USERNAME=<CT_USERNAME> --env CT_PASSWORD=<CT_PASSWORD> --transport stdio cellartracker -- npx -y cellartracker-mcpWhat CellarTracker does
CellarTracker MCP reaches your wine cellar through CellarTracker's CSV export, since the service ships no official API. Results are cached on your machine and pulled again every 24 hours; refresh-data forces a fresh pull when you need one. Only your own account is visible — the server cannot search CellarTracker's public wine database.
Thirteen tools come with it. search-cellar filters by name, colour, region, varietal or vintage, drinking-recommendations ranks bottles by how urgent their drinking window is, and purchase-history plus consumption-history break down spending and opened bottles. For bulk work the server exposes cached table exports as MCP resources at cellartracker://tables/, which sidesteps the 25-per-page cap on list tools. The Claude plugin adds two skills: cellartracker-data explains table relationships and score abbreviations, while wine-purchase-evaluator scores a purchase on Quality and Personal Fit and returns BUY, CONSIDER or PASS.
Login happens with your real username and password, passed as URL query parameters over HTTPS. CellarTracker offers no OAuth and no scoped tokens, so the server authenticates with full account rights even though every operation it performs is read-only. Skip CT_USERNAME and CT_PASSWORD and the tools return errors while the skills sit idle — run setup-credentials first.
What it helps with
- see which bottles are ready to open this month
- total wine spending by store over a date range
- check whether a new purchase duplicates something already in the cellar
- locate a bottle by bin, size or barcode
- pull up your own tasting notes and scores for a wine
Example prompts for the agent
- Which wines should I open this month?
- Show my wine spending by store over the last year
- Is this bottle worth the price — check my cellar for duplicates
How to install CellarTracker
Platform CLI
claude mcp add --env CT_USERNAME=<CT_USERNAME> --env CT_PASSWORD=<CT_PASSWORD> --transport stdio cellartracker -- npx -y cellartracker-mcpReplace <…> with your own values
Platform CLI
codex mcp add cellartracker --env CT_USERNAME=<CT_USERNAME> --env CT_PASSWORD=<CT_PASSWORD> -- npx -y cellartracker-mcpReplace <…> with your own values
Config file
{
"mcpServers": {
"cellartracker": {
"command": "npx",
"args": [
"-y",
"cellartracker-mcp"
],
"env": {
"CT_USERNAME": "<CT_USERNAME>",
"CT_PASSWORD": "<CT_PASSWORD>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"cellartracker": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"cellartracker-mcp"
],
"env": {
"CT_USERNAME": "<CT_USERNAME>",
"CT_PASSWORD": "<CT_PASSWORD>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e CT_USERNAME=<CT_USERNAME> -e CT_PASSWORD=<CT_PASSWORD> cellartracker npx -y cellartracker-mcpReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about CellarTracker
How do I install CellarTracker in Claude Code?
Add the marketplace with /plugin marketplace add slavins-co/cellartracker-mcp, then install the plugin: /plugin install cellartracker-mcp@cellartracker-mcp. Right after that, tell the agent "Set up my CellarTracker credentials".
What does CellarTracker MCP do?
It reads your CellarTracker account and hands the agent your inventory, drinking windows, purchase history and tasting notes. Every tool is read-only.
How is the Claude plugin different from the Desktop Extension?
The plugin ships all 13 tools plus two skills; the Claude Desktop extension has 11 tools and no skills. Installing both is safe — they do not conflict in Cowork.
