Cellarion

What the Cellarion MCP server does

The Cellarion MCP server exposes a user's wine cellar to compatible AI assistants through Model Context Protocol. It is part of Cellarion, a wine cellar application for tracking bottles, organizing multiple cellars and racks, recording open-bottle activity, and searching a shared wine registry.

The MCP connection is intended for conversational collection management. The README describes support for reading and managing a cellar, along with similarity-related capabilities used by Cellarion's AI features. An assistant can work with collection information such as bottles, locations, notes, ratings, and drink status, subject to the permissions and data available to the connected account.

Cellarion also includes other wine features outside MCP, including food-pairing and occasion suggestions, maturity windows, label scanning, statistics, imports, exports, and cellar sharing. These should not be assumed to be separate MCP tools unless exposed by the connected deployment.

How it works

The MCP service is available at /api/mcp on the Cellarion application and uses OAuth for access. A client connects to that endpoint, authenticates with a Cellarion account, and then uses the capabilities exposed by the server in an assistant conversation.

Cellarion can be used as the public hosted service at cellarion.app, which requires no local installation. The same application can also be self-hosted for a private deployment. In either case, the MCP client must be configured to reach the relevant Cellarion instance and authenticate successfully.

Cellarion stores wine embeddings in MongoDB and compares them in the backend. The project notes that Qdrant is no longer required for current versions; older self-hosted installations may need to migrate vectors during an upgrade.

Setup and configuration

For the hosted service, create an account at cellarion.app and connect an MCP-capable client to the Cellarion MCP endpoint using the service's OAuth flow. The README does not provide client-specific configuration examples or a list of individual MCP tool names.

Self-hosting requires Docker and Docker Compose. The documented setup clones the repository, copies .env.example to .env, sets strong values for JWT_SECRET and MEILI_MASTER_KEY, creates the external Docker network named web, and starts the Compose deployment. The MCP endpoint is then served by that Cellarion installation under /api/mcp.

A local deployment can be seeded with demo accounts and sample wine data. Those credentials are for development only and must be changed before exposing a deployment publicly.

Tools and capabilities

The documented MCP scope includes:

• Reading a user's Cellarion wine collection conversationally.
• Managing cellar data through an MCP-capable assistant.
• Working with collection-related similarity capabilities backed by MongoDB-stored embeddings.
• Using OAuth-authenticated access to a hosted or self-hosted Cellarion instance.

The source material does not enumerate the server's individual tool names, argument schemas, or return formats.

Limitations and notes

The MCP server operates on Cellarion data available to the authenticated account; it is not described as a general-purpose wine database or unrestricted registry interface. Exact operations depend on the capabilities exposed by the running Cellarion version.

Using the hosted application requires an account but does not require cloning the repository, running Docker, or maintaining a server. Self-hosting adds responsibility for the application stack, authentication secrets, database, search service, and deployment security. The project is licensed under AGPL-3.0.