Cellarion — Claude Code MCP server: what it does, how to install
Connects your AI assistant to a Cellarion account to browse bottles, check rack locations, and track drinking windows.
claude mcp add --transport http cellarion https://cellarion.app/api/mcpWhat Cellarion does
This bridge translates stdio MCP client calls to the Cellarion /api/mcp endpoint using a personal API credential. Tool schemas and available resources originate directly from the host application. Because the remote instance dictates the tool definitions, new features appear in the assistant without modifying the local runner.
Operation requires an existing account token minted with the read permission scope. Without CELLARION_TOKEN, the process terminates. By default, queries route to https://cellarion.app, while self-hosted instances can be targeted by supplying CELLARION_URL in the environment settings.
What it helps with
- locate specific wine varieties across home cellar racks
- identify bottles nearing the end of their drinking window
- review past tastings and personal scores from your log
Example prompts for the agent
- Check which bottles in my collection should be opened this week before they decline
- Do I have any bottles of Barolo left, and which rack are they in?
- Show what wines I logged last month alongside my ratings
How to install Cellarion
1Platform CLI: remote server
claude mcp add --transport http cellarion https://cellarion.app/api/mcp2Platform CLI
claude mcp add --env CELLARION_TOKEN=<CELLARION_TOKEN> --env CELLARION_URL=<CELLARION_URL> --transport stdio cellarion-mcp -- npx -y cellarion-mcpReplace <…> with your own values
1Platform CLI: remote server
codex mcp add cellarion-mcp --url https://cellarion.app/api/mcp2Platform CLI
codex mcp add cellarion-mcp --env CELLARION_TOKEN=<CELLARION_TOKEN> --env CELLARION_URL=<CELLARION_URL> -- npx -y cellarion-mcpReplace <…> with your own values
Config file
{
"mcpServers": {
"cellarion-mcp": {
"url": "https://cellarion.app/api/mcp"
}
}
}{
"mcpServers": {
"cellarion-mcp": {
"command": "npx",
"args": [
"-y",
"cellarion-mcp"
],
"env": {
"CELLARION_TOKEN": "<CELLARION_TOKEN>",
"CELLARION_URL": "<CELLARION_URL>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"cellarion-mcp": {
"type": "http",
"url": "https://cellarion.app/api/mcp"
}
}
}{
"servers": {
"cellarion-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"cellarion-mcp"
],
"env": {
"CELLARION_TOKEN": "<CELLARION_TOKEN>",
"CELLARION_URL": "<CELLARION_URL>"
}
}
}
}Replace <…> with your own values
1Platform CLI: remote server
gemini mcp add -t http cellarion-mcp https://cellarion.app/api/mcp2Platform CLI
gemini mcp add -e CELLARION_TOKEN=<CELLARION_TOKEN> -e CELLARION_URL=<CELLARION_URL> cellarion-mcp npx -y cellarion-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 Cellarion
How to install Cellarion in Claude Code?
Run claude mcp add --env CELLARION_TOKEN=<CELLARION_TOKEN> --env CELLARION_URL=<CELLARION_URL> --transport stdio cellarion-mcp -- npx -y cellarion-mcp with your actual token value.
What does Cellarion do?
It lets your coding assistant read inventory records, cellar positions, and pairing notes directly from your personal wine tracker.
Does this bridge support self-hosted instances?
Yes, specify your domain through the CELLARION_URL environment variable or the --url argument during startup.
