Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Cellarion Wine Registry is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Public wine registry and guides: search wines, grapes, regions, appellations. No account.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http cellarion-wine-registry-mcp https://cellarion.app/api/mcp/public
# 2 — ask your agent for something these tools do
# get_source_info, search_registry, get_wine and 4 more
Cellarion Wine Registry costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http cellarion-wine-registry-mcp https://cellarion.app/api/mcp/publicReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 project.
No parameter schema on file.
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 known wines — use search_bottles for what the user owns.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Wine name, producer, appellation or grape |
Full registry record for one wine: producer, region, appellation, classification, grapes, community rating, and the AI tasting profile when the wine has been enriched. Vintage-neutral (bottles carry the vintage). Call after search_registry when the user wants depth on a specific wine.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wine_id | string | yes | Registry wine id from search_registry or a bottle's wine |
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 Barolo", or to seed purchase ideas from a wine the user loves. Only wines that have been embedded are searchable — an empty r
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wine_id | string | no | Registry wine id (24-hex) from search_registry or a bottle's wine |
| bottle_id | string | no | Alternatively: one of the user's bottle ids (24-hex). Needs an authenticated connection — not available on the public endpoint. |
| limit | integer | no | How many to return (1-10, default 8; larger values are capped, not rejected) |
Sommelier-curated drink windows for a registry wine: per vintage, when it is young, at peak, and in late maturity, with where the vintage stands right now. Call for "when should I drink <wine> <vintage>", aging questions, or buy-now-drink-later advice. Only sommelier-REVIEWED vintages are returned — an empty result means no curated window exists yet (reason from grape/region/structure yourself, an
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wine_id | string | yes | Registry wine id (from search_registry) |
| vintage | string | no | One vintage year; omit for all curated vintages of the wine |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tag | string | no | Filter by tag |
| limit | integer | no | How many to return (1-20, default 10; larger values are capped, not rejected) |
| offset | integer | no | Skip this many (default 0) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Article slug from list_guides |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Cellarion Wine Registry or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.175.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Cellarion Wine Registry can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.