Cezzis Com Cocktails MCP Server

If you already use Cezzis Com Cocktails MCP, the cezzis com cocktails mcp mcp server is the piece that lets your assistant work with it directly. This repository contains the Go-based MCP server for Cezzis.com cocktails. It exposes a streamable HTTP MCP interface that lets MCP clients search cocktail data, retrieve cocktail details, authenticate against Auth0, and submit user.

What the server does

The server is an integration layer, not the source of cocktail data. It registers MCP tools, forwards requests to the upstream Cocktails, AI Search, and Accounts APIs, stores authentication tokens in PostgreSQL per MCP session, and emits telemetry through OpenTelemetry.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• search_cocktails — Searches cocktail data using the upstream AI Search API
• get_cocktail — Returns detailed cocktail data for a specific cocktail ID
• convert_to_plaintext — Converts markdown or HTML-rich content into plain text
• authentication_login_flow — Starts the Auth0 device login flow
• auth_status — Returns the authentication state for the current MCP session
• authentication_logout_flow — Clears tokens for the current MCP session
• cocktail_rate — Submits a cocktail rating for an authenticated user
• Prerequisites — The Prerequisites tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: COCKTAILS_API_HOST, ACCOUNTS_API_HOST, AISEARCH_API_HOST, AUTH0_NATIVE_CLIENT_ID, CEZZIS_BASE_URL, POSTGRES_HOST. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Go 1.25.1+ - PostgreSQL - Valid values for the upstream API hosts and subscription keys - Auth0 settings if you want to use authenticated tools

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Cezzis Com Cocktails MCP's toolset — search_cocktails, get_cocktail, convert_to_plaintext and 5 more — is a fair guide to whether it matches your workflow. It is maintained by mtnvencenzo; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Cezzis Com Cocktails MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.