Cellarion Wine Registry

Name: Cellarion Wine Registry
Author: jagduvi1

by jagduvi1version 1.296.0i★ –iRuns in the cloud

Registry nameapp.cellarion/wine-registry

Install

Overview

Description from the maker (original English)

Public wine registry and guides: search wines, grapes, regions, appellations. No account.

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 checksi3 of 3 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

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 in the cloud
Transport: Streamable HTTP
Category: Search & AI memory

Install

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

Before you install

Basic checks: 3 of 3 passed
Runs on the maker’s server: what you ask it goes through their server.
Can do 6 things (tools) get_source_info, search_registry, get_wine, find_similar_wines …
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

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

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://cellarion.app/api/mcp/public

Run this in your terminal

claude mcp add --transport http wine-registry https://cellarion.app/api/mcp/public

Open in Cursor

Or copy the settings yourself

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

{
  "mcpServers": {
    "wine-registry": {
      "url": "https://cellarion.app/api/mcp/public"
    }
  }
}

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": {
    "wine-registry": {
      "type": "http",
      "url": "https://cellarion.app/api/mcp/public"
    }
  }
}

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.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://cellarion.app/api/mcp/public

Menu names can differ slightly by plan and over time.

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

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

What it can do

Tool names and descriptions exactly as the server reported them on Nov 7, 2026. The maker wrote them, not us; we show them as plain text.

get_source_info
Returns what Cellarion is, the version this instance is running, the open-source repository, and the license. Call this when the user asks what Cellarion is, which version they are on, whether it is open source, where to find / contribute to the code — or how to support the proje
search_registry
Searches Cellarion's shared wine database (vintage-neutral wines, community data) by name, producer, region or grape. Returns up to 10 matches. Call to identify a wine the user mentions, before recommending, or to check whether a wine exists in the registry. This searches ALL kno
get_wine
Full registry record for one wine: producer, region, appellation, classification, grapes, community rating, the AI tasting profile when the wine has been enriched, and the registry image (url + credit) when one is published — null means the wine has no public picture yet; to see
find_similar_wines
Given a registry wine_id (or, on an authenticated connection, one of the user's bottle_ids), returns wines with the closest taste/style profile from the shared registry, using vector similarity over wine embeddings. Call for "more like this", "what else is like my favourite Barol
list_guides
Cellarion's published guides and blog articles (cellar management, drink windows, storage, buying) — title, slug, excerpt and tags. Call when the user wants a how-to or background reading; follow with read_guide for the full text.
read_guide
The full text of one published Cellarion guide or blog article, by slug (from list_guides). Public website content — quote or summarise freely, and link the public_url when pointing the user to 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 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain cellarion.app (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
✓ Pass
Endpoint responds
Responded in 843 ms (HTTP 200)
– Not applicable
Sign-in with OAuth
No sign-in needed
✓ Pass
No hidden instructions in tool descriptions
Read 6 tool descriptions and found no hidden instructions to the AI

Compared with others in Search & AI memoryi

More stars than 0% of the other 5650 servers in this category
Published to the registry more recently than 97% of the other 5650 servers in this category
Basic checks equal to or better than 100% of the other 5650 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 Cellarion Wine Registry safe?

It passed 3 of 3 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?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.296.0) reached the registry yesterday.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

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

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

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated yesterday

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 21 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month

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.

Cellarion

Cellarion is a hosted wine cellar app — a ready-to-use online service at [cellarion.app](https://cellarion.app). Create a free account and start tracking your bottles, organizing them into cellars and racks, searching a shared wine registry, getting sommelier-curated drink-window recommendations, and chatting with an AI sommelier about your collection. No installation, no server, no setup — just sign up and go. Every feature is free, forever.

Just want to use Cellarion? Go to [cellarion.app](https://cellarion.app) and sign up. You do not need to clone this repository, run Docker, or host anything yourself. There's also a public [demo account](https://cellarion.app) (Try the demo on the landing page) and an Android app on [Google Play](https://play.google.com/store/apps/details?id=app.cellarion.twa).

Cellarion is *also* open-source (AGPL-3.0), so if you'd prefer to run your own private instance, you can self-host it. The rest of this README covers self-hosting — see Quick Start. Most people should just use the hosted service at cellarion.app.

Hosted Service (recommended)

Cellarion is live and publicly available at:

👉 https://cellarion.app

This is the primary way to use Cellarion. Create an account and start using the full service today — every feature is free, forever. No credit card, no trial clock, no paywalled features, nothing to install or maintain. If you want to chip in, optional Supporter, Patron and Benefactor tiers (monthly or yearly) and GitHub Sponsors fund development — they unlock nothing extra, just our thanks.

Features

Your cellar

Bottle tracking — Log every bottle with vintage, producer, region, price, rating, and tasting notes; add more of a bottle you already own in one click
Cellar & rack management — Multiple cellars with customizable rack grids (up to 20×20) and a 3D cellar room view for physical placement
Open-bottle tracking — Open a bottle, pour glasses over days, close or finish it — with preservation-aware drink-soon nudges
Offline mode — Keeps a copy of your cellars, racks and bottles on the device, so the app works in the cellar with no signal: browse, find a bottle in its rack, consume/open/pour, place and move bottles, edit notes and ratings. Changes sync when you're back online — applied once (idempotency keys), and never silently over someone else's change (conflicts land in *Needs attention*). Off until the user chooses it: the installed app asks once, and Settings switches it anywhere
Reserved bottles — Mark bottles as "spoken for" (a birthday, a dinner) so suggestions and consume flows respect them
Drink-window alerts — Sommelier-curated maturity windows per wine and vintage; alerts when bottles approach peak, are in window, or slipping past it
Rich statistics — Charts, world choropleth map, breakdowns by country, grape, value, and drink status
Import & export — Bring collections from Vivino (incl. drinking history), CellarTracker, Ploc, generic CSV, or Cellarion's own JSON; export everything as JSON or a ZIP with your images

The shared registry

Smart search — Meilisearch-powered fuzzy search with aggressive deduplication and canonical-key matching
Label scanning — Snap a photo of a wine label and let AI fill in the details
Regional grape names — One canonical variety per grape, displayed the way the label writes it (a Douro Port shows *Tinta Roriz*, an Alentejo red *Aragonez* — both stored as Tempranillo)
Registry quality tooling — Duplicate/fragmentation queues, cross-field domain checks, name checks, and a sommelier correction-proposal workflow keep the shared data clean

AI cellar chat — Ask questions about your collection — food pairings, occasion picks, cellar health (Claude + Voyage embeddings, searched in MongoDB; only ever answers from wines you actually own)
Connect your own AI — A built-in MCP server lets Claude, and any MCP-capable client, read and manage your cellar conversationally
Bring your own models — Self-hosters can point every AI feature at any OpenAI-compatible endpoint (Ollama, vLLM, LM Studio) instead of Anthropic/Voyage

Community & sharing

Cellar sharing — Invite others to browse or co-manage a cellar with role-based access
Wine lists, reviews & discussions — Build shareable lists, review wines, discuss them, follow other users, and get restock alerts
Tasting journal & wishlist — Keep private notes and a want-to-try list

Platform

Climate monitoring — Connect cellar temperature/humidity sensors (Home Assistant-friendly ingest API) with per-cellar dashboards
Single sign-on — Optional Google SSO, or your own OIDC provider (Pocket ID, Authentik, Keycloak, Zitadel, Authelia), alongside email/password
Installable app — PWA with push notifications and offline support (the service worker keeps each build for offline use), plus an Android app on Google Play
Internationalization — Community-translated via Weblate (help translate)
Privacy & GDPR — Full data export, account deletion with cooling-off, one-click email opt-out, optional self-hosted cookie-free analytics (Umami)
Everything free — Optional Supporter/Patron/Benefactor tiers (Stripe, monthly or yearly) and GitHub Sponsors fund development; they unlock nothing extra
Sommelier & admin tools — Maturity/pricing curation surfaces, wine requests, quality reports, registry health watchdog, audit log, super-admin dashboard

Stack

MongoDB 7 — Database (Mongoose 8)
Express 4 — Backend API
React 19 — Frontend (React Router 6, built with Vite 7)
Node.js 24 — Runtime
Meilisearch — Fuzzy search engine
Voyage AI — Wine embedding generation (swappable for any OpenAI-compatible endpoint); the vectors are stored in MongoDB and compared by the backend — no vector database
Anthropic Claude — Label scanning + AI chat (swappable, same mechanism)
MCP — Model Context Protocol server (/api/mcp) with OAuth, for AI assistants
Stripe — Optional supporter payments (hosted Checkout + Portal)
nginx — Serves the React SPA and proxies /api/ to the backend (internal)
Traefik — External reverse proxy (bring your own; not included in this Compose file)
Docker Compose — Containerization
rembg — Python/Flask background removal microservice
Umami — Optional self-hosted, cookie-free analytics (compose --profile analytics)

Self-Hosting (Quick Start)

This section is only for people who want to run their own private instance. If you just want to use Cellarion, head to [cellarion.app](https://cellarion.app) instead — no setup required.

Prerequisites

Docker + Docker Compose

Run the app

The app is routed through Traefik, so create the external web Docker network before the first up (compose declares it external — the first command fails otherwise):

git clone https://github.com/jagduvi1/Cellarion.git

cd Cellarion cp .env.example .env

Edit .env and set JWT_SECRET and MEILI_MASTER_KEY to strong random strings

docker network create web # once; skip if it already exists docker-compose up --build

URL	Description
http://localhost	Frontend (React SPA) — served via Traefik
http://localhost/api/health	Backend health check

Make yourself admin

A fresh install has no admin. Register your own account in the app, then run:

docker exec cellarion-backend node src/scripts/make-admin.js <your username or email>

Sign out and in again to see the admin pages. --remove takes the role away again.

Seed demo data

After the containers are running:

docker exec cellarion-backend node src/seed-demo.js

This creates demo accounts plus a starter taxonomy, wine registry entries, and a demo cellar with sample bottles:

Account	Email	Password	Role
Admin	admin@cellarion.app	Admin1234!demo	admin
Demo user	user@cellarion.app	User1234!demo	user

These are local development credentials. Change them before deploying anywhere public.

Stop

docker-compose down          # keep data

docker-compose down -v # also remove all volumes (wipes database)

Upgrade

git pull

docker-compose up -d --build

Upgrading from v1.241.0 or earlier: Qdrant is retired. The wine vectors behind the AI cellar chat, restock suggestions and the MCP similarity tools now live in MongoDB, and the backend compares them itself — there is no vector database to run any more. After the upgrade the old qdrant container keeps running as an orphan, so its vectors can be copied over once, with no re-embedding and no embedding cost:

# dry run (counts only), then the real copy

docker-compose exec -e QDRANT_URL=http://qdrant:6333 backend node src/scripts/migrate-vectors-from-qdrant.js docker-compose exec -e QDRANT_URL=http://qdrant:6333 backend node src/scripts/migrate-vectors-from-qdrant.js --apply

then remove the old container, and later its volume

docker-compose up -d --remove-orphans docker volume ls | grep qdrant # e.g. cellarion_qdrant-data → docker volume rm cellarion_qdrant-data

If you had set QDRANT_API_KEY, add -e QDRANT_API_KEY= to both commands (the new compose no longer passes it).
Instead of copying, you can run a full embedding job in SuperAdmin → AI, which re-embeds every wine through your embedding provider.
If embeddings were never configured (no VOYAGE_API_KEY / EMBEDDING_PROVIDER), there is nothing to copy — just remove the old container.
Going back to v1.241.0 afterwards works, but run a full embedding job after that downgrade, and again after upgrading once more.

Architecture

The tree below shows the shape of the codebase — the highlights, not every file. The backend has 57 Mongoose schemas and ~65 route modules (44 top-level + admin/ + somm/), plus the MCP server.

Cellarion/

├── backend/ │ ├── server.js # Entry point │ └── src/ │ ├── app.js # Express app setup, mounting, rate limiters │ ├── config/ # db, plans, upload, aiConfig (models, prompts, limits) │ ├── middleware/ │ │ ├── auth.js # JWT + role middleware (requireAuth, requireAdmin, requireSomm) │ │ └── bottleAccess.js # requireBottleAccess(minRole) factory │ ├── models/ # 57 Mongoose schemas — core: User, WineDefinition, │ │ # Bottle, Cellar, Rack, WineVintageProfile/Price, │ │ # WineRequest, WineCorrectionProposal, BottleImage, │ │ # AuditLog, Country/Region/Appellation/Grape; │ │ # community: Discussion*, Review, JournalEntry, │ │ # WishlistItem, WineList, Follow, RestockAlert; │ │ # infra: Notification, PushSubscription, SupportTicket, │ │ # ImportSession, StripeWebhookEvent, WineEmbedding, │ │ # ClimateDevice/Reading, OAuth*, McpActionLog, … │ ├── routes/ # ~44 top-level route modules: auth (incl. Google SSO), │ │ # cellars, bottles, wines (public read), racks, chat, │ │ # stats, import, export, wineRequests, wineReports, │ │ # discussions, reviews, journal, wishlist, wineLists, │ │

Only the beginning is shown; read the rest in the repo

Cellarion Wine Registry

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

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 Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

Cellarion

Hosted Service (recommended)

Features

Stack

Self-Hosting (Quick Start)

Prerequisites

Run the app

Edit .env and set JWT_SECRET and MEILI_MASTER_KEY to strong random strings

Make yourself admin

Seed demo data

Stop

Upgrade

then remove the old container, and later its volume

Architecture