Cellarion Wine Registry
Server Details
Public wine registry and guides: search wines, grapes, regions, appellations. No account.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- jagduvi1/Cellarion
- GitHub Stars
- 14
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
7 toolsdrink_window_forDrink window for a wineRead-onlyInspect
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 ", 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, and say it is an estimate).
| Name | Required | Description | Default |
|---|---|---|---|
| vintage | No | One vintage year; omit for all curated vintages of the wine | |
| wine_id | Yes | Registry wine id (from search_registry) |
find_similar_winesFind similar wines ("more like this")Read-onlyInspect
Given a registry wine_id (or 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 result does not mean nothing similar exists.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| wine_id | No | Registry wine id (from search_registry or a bottle's wine) | |
| bottle_id | No | Alternatively: one of the user's bottle ids |
get_source_infoAbout this Cellarion instanceRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_wineGet one registry wineRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| wine_id | Yes | Registry wine id from search_registry or a bottle's wine |
list_guidesList wine guides & articlesRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| tag | No | Filter by tag | |
| limit | No | ||
| offset | No |
read_guideRead a guide / articleRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Article slug from list_guides |
search_registrySearch the shared wine registryRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Wine name, producer, appellation or grape |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!