Cocktail API MCP for AI. Audit global drink data from any client.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
Cocktail API: Access a global database of drink recipes for mixology research and menu auditing. This MCP lets your agent perform detailed searches by spirit, ingredient, or name, retrieving precise instructions and metadata instantly.
It handles everything from finding classic martinis to identifying cocktails built around specific flavor profiles like gin or tequila.
What your AI can do
Get cocktails by ingredients
Finds recipes that contain a list of specified ingredients.
Get classic margaritas
Retrieves data for traditional Margarita variations.
Get classic martinis
Retrieves data for classic Martini variations.
Find specific cocktail recipes using a simple name search.
Identify all cocktails that incorporate one or more specified ingredients.
Pull lists of popular drinks based on a primary base spirit, such as gin, tequila, or vodka.
Look up standard iterations of famous drinks like martinis and margaritas.
Ask an AI about this
Waiting for input…
Cocktail API: 8 Tools Available
These tools allow you to perform highly specific searches on cocktail data, whether filtering by ingredient, finding classic variations, or querying a base spirit.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Cocktail API on VinkiusGet Cocktails By Ingredients
Finds recipes that contain a list of specified ingredients.
Get Classic Margaritas
Retrieves data for traditional Margarita variations.
Get Classic Martinis
Retrieves data for classic Martini variations.
Get Gin Cocktails
Retrieves popular cocktails using gin as the primary spirit.
Get Rum Cocktails
Retrieves popular cocktails using rum as the primary spirit.
Get Tequila Cocktails
Retrieves popular cocktails using tequila as the primary spirit.
Get Vodka Cocktails
Retrieves popular cocktails using vodka as the primary spirit.
Search Cocktails
Searches for recipes by entering a known cocktail name.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Cocktail API, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Cocktail API. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 8 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Keeping Track of Ingredient Variations Is a Mess.
Right now, if you need to know every cocktail that uses coffee and vodka, you're clicking through multiple database sections, filtering by spirit type, then cross-referencing ingredient lists. It’s slow, prone to human error, and you might miss the niche recipes that use slightly different ingredients.
With this MCP connected via Vinkius, your agent handles the logic. You ask it for cocktails containing 'vodka' and 'coffee', and it returns a clean list of matches instantly. It takes the manual data audit and turns it into one conversational query.
Getting Classic Cocktail Data: Use `get_classic_martinis`
Before, you'd have to remember if a drink was called 'standard martini,' 'dry martini,' or just needed specific ingredient checks. You’d be guessing which database section to check next.
Now, simply call `get_classic_martinis`. The agent retrieves the precise metadata and variations for that category immediately. It eliminates guesswork entirely.
What your AI can actually do with this
Your AI agent needs reliable data when planning menus or researching new recipes. The Cocktail API gives you direct access to a massive source of global drink information. You can stop manually cross-referencing different recipe sites and start asking your agent questions about cocktails in plain language.
It instantly retrieves full cocktail details, letting you audit ingredient lists or check preparation steps without leaving your development environment. Need to see what recipes feature tequila? Or maybe find all drinks built around a specific base spirit like rum? You get that data immediately. Whether you're designing a new menu or doing deep mixology research for a regional concept, the API acts as a real-time database lookup tool.
When you connect this MCP via Vinkius, your agent handles complex queries—like finding all drinks containing both vodka and coffee—and returns structured data ready for use.
019d8427-44bd-7047-871d-1a097140a83d Here's how it actually works
The bottom line is you get accurate, formatted drink data without ever opening a web browser or manually managing API calls.
Subscribe to the Cocktail API on Vinkius and provide your unique API key.
Connect this MCP to your preferred client (Claude, Cursor, etc.) in your development workflow.
Ask your agent a mixology question. The agent invokes the necessary tool, retrieves the structured recipe data, and returns it directly.
Who is this actually for?
This MCP is for hospitality professionals who deal with inventory and menu complexity. It's perfect for the Operations Manager tired of juggling spreadsheets when checking stock, or the Mixologist needing instant data on flavor pairings.
Performs rapid audits on potential recipes to check ingredient availability and historical variations.
Verifies drink availability across multiple locations or seasonal menus without manual database queries.
Tests flavor combinations and identifies thematic clusters of drinks using specific base spirits.
What Changes When You Connect
Instantly audit ingredient lists: Use get_cocktails_by_ingredients to see what drinks feature a specific mix of flavors, cutting down hours of manual research.
Target base spirits quickly: Instead of running general searches, specialized tools like get_tequila_cocktails or get_gin_cocktails give you focused results for your menu drafts.
Handle classics automatically: Retrieve the precise data for standard drinks using dedicated functions like get_classic_margaritas or get_classic_martinis. You don't have to guess the variations.
Deep-dive research: Use search_cocktails when you know the exact name of a drink, and then use ingredient tools for variation data. It’s structured querying on steroids.
Operational efficiency: Operations teams can automate recipe data checks—for example, verifying if a seasonal cocktail uses ingredients that are currently stocked.
See it in action
Updating the Seasonal Menu
The menu designer needs to ensure all new drinks fit the current inventory. They ask their agent to use get_cocktails_by_ingredients with 'lime' and 'tequila'. The agent returns a list of matching recipes, allowing them to approve only feasible options.
Troubleshooting Cocktail Recipes
A bartender questions the recipe for an old drink. They prompt their agent to use search_cocktails with the name 'Daiquiri'. The agent pulls the full ingredient list and preparation steps, verifying accuracy immediately.
Checking Spirit Availability
The operations lead needs to know what drinks are popular if they run low on vodka. They prompt for get_vodka_cocktails. The agent returns a curated list of recipes, helping them plan stocking orders.
Comparing Classic Drinks
A mixologist wants to compare the standard preparation methods. They ask their agent to run both get_classic_martinis and get_classic_margaritas. The agent returns two separate, structured data sets for direct comparison.
The honest tradeoffs
Searching everything at once
Asking the agent: 'Show me all cocktails that use tequila and are also classic martinis.' This is too vague and forces the agent to guess which tool to combine.
Break it down. First, run get_tequila_cocktails for general ideas. Then, if you need a specific type of drink, use search_cocktails or filter the results manually.
Assuming a single search function
Trying to find all drinks by 'rum' using only the basic search tool. This misses out on specialized data curated for that spirit.
Always check if a dedicated tool exists. For rum, use get_rum_cocktails directly; it provides a more focused and reliable list than general searching.
Ignoring ingredient overlaps
Manually checking drink books for every combination of ingredients to see what works.
Use get_cocktails_by_ingredients. Give it three or four key components, and the API returns only the recipes that contain all of them.
When It Fits, When It Doesn't
Use this MCP if your core need is querying structured drink data (recipes, ingredients, preparations). If you know the base spirit, use a dedicated tool (get_tequila_cocktails vs. search_cocktails). Use ingredient tools when you have components but no recipe name in mind. Do not use it if your goal is general market trend analysis or checking external news; for that, standard web search remains better. If you just need to validate a single cocktail's basic steps and don't care about its base spirit type, search_cocktails works fine.
Questions you might have
How do I find my API Ninjas Key? +
Log in to your API Ninjas dashboard, and you will find your API Key on the main page. Copy and paste it below.
Can I search for cocktails by ingredients? +
Yes. Use the get_cocktails_by_ingredients tool providing a comma-separated list (e.g., 'vodka,orange juice'). Your agent will return matching recipes instantly.
Does it support detailed instructions? +
Yes. Every cocktail recipe retrieved by your agent includes the official preparation instructions provided by API Ninjas.
What are the usage rate limits when I run `search_cocktails`? +
The MCP handles API rate limiting for you. You'll see specific error codes if your request exceeds the defined quota, signaling that you need to pause or use a different endpoint.
If I use `get_tequila_cocktails`, what format is the returned recipe data? +
The data returns structured JSON objects. Each entry includes the cocktail name, detailed ingredient list, and step-by-step instructions, making it easy for your AI client to parse.
Can I combine results from `get_classic_margaritas` with my own ingredients using a single prompt? +
Yes, your agent can orchestrate this. You ask the MCP to first run get_classic_margaritas, and then use those results as context when querying for additional ingredient overlaps.
How do I ensure accurate translations if I use a tool like `search_cocktails`? +
The recipe data relies on the source API's metadata. While it supports global ingredients, always verify that the specific language of the instructions matches your target locale.
If I only want to find recipes for a base spirit like tequila, should I use `get_tequila_cocktails` or `search_cocktails`? +
get_tequila_cocktails is faster because it provides popular examples immediately. Use search_cocktails if you need to search by a specific cocktail name instead.
We've already built the connector for Cocktail API. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 8 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.