How do I find my API Ninjas Key?

Log in to your [**API Ninjas dashboard**](https://api-ninjas.com/profile), 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.

Cocktail API MCP Server for CrewAI 8 tools — connect in under 2 minutes

Name: Cocktail API
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 8 Tools Framework

Connect your CrewAI agents to Cocktail API through the Vinkius — pass the Edge URL in the `mcps` parameter and every Cocktail API tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Cocktail API Specialist",
    goal="Help users interact with Cocktail API effectively",
    backstory=(
        "You are an expert at leveraging Cocktail API tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Cocktail API "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 8 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Cocktail API MCP Server

Empower your AI agent to orchestrate your entire mixology research and recipe auditing workflow with the Cocktail API, the comprehensive source for global drink data. By connecting the API Ninjas Cocktail API to your agent, you transform complex recipe searches into a natural conversation. Your agent can instantly retrieve cocktail details, audit ingredient lists, and query preparation instructions without you ever touching a drink portal. Whether you are planning a menu or conducting regional mixology research, your agent acts as a real-time sommelier, ensuring your data is always precise and localized.

When paired with CrewAI, Cocktail API becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Cocktail API tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

What you can do

Recipe Auditing — Search for thousands of cocktail recipes by name and retrieve detailed metadata, including ingredient lists and instructions.
Ingredient Oversight — Find cocktails matching specific ingredients to understand the thematic distribution of flavors instantly.
Discovery by Theme — Query recipes containing base spirits like 'vodka' or 'tequila' to identify relevant assets for your menu.
Preparation Intelligence — Retrieve full step-by-step instructions for any cocktail to assist in deep-dive mixology classification.
Classic Variations — Instantly retrieve classic iterations of standard beverages, from margaritas to martinis.

The Cocktail API MCP Server exposes 8 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Cocktail API to CrewAI via MCP

Follow these steps to integrate the Cocktail API MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 8 tools from Cocktail API

Why Use CrewAI with the Cocktail API MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Cocktail API through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Cocktail API + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Cocktail API MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Cocktail API for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Cocktail API, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Cocktail API tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Cocktail API against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Cocktail API MCP Tools for CrewAI (8)

These 8 tools become available when you connect Cocktail API to CrewAI via MCP:

get_classic_margaritas

Get classic Margarita variations

get_classic_martinis

Get classic Martini variations

get_cocktails_by_ingredients

Find cocktail recipes by specific ingredients

get_gin_cocktails

Get popular Gin cocktails

get_rum_cocktails

Get popular Rum cocktails

get_tequila_cocktails

Get popular Tequila cocktails

get_vodka_cocktails

Get popular Vodka cocktails

search_cocktails

Search for cocktail recipes by name

Example Prompts for Cocktail API in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Cocktail API immediately.

"Get the recipe for a 'Margarita' using Cocktail API."

"Find cocktails that contain 'vodka' and 'coffee'."

"Show recipes for 'Gin and Tonic'."

Troubleshooting Cocktail API MCP Server with CrewAI

Common issues when connecting Cocktail API to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Cocktail API + CrewAI FAQ

Common questions about integrating Cocktail API MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.