How do I find my ReciPal API Key?

Log in to your [**ReciPal account**](https://recipal.com/), navigate to your account settings, and you will find your API Key in the integrations or developer section. Copy and paste it below.

Can the agent show serving sizes?

Yes. Every recipe record retrieved by your agent includes serving size metadata and the number of servings per recipe.

Does it support ingredient lists?

Yes. The `get_recipe_details` tool retrieves the full list of ingredients used in a specific recipe, along with their weights.

ReciPal MCP Server for CrewAI 4 tools — connect in under 2 minutes

Name: ReciPal
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 4 Tools Framework

Connect your CrewAI agents to ReciPal through Vinkius, pass the Edge URL in the `mcps` parameter and every ReciPal 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="ReciPal Specialist",
    goal="Help users interact with ReciPal effectively",
    backstory=(
        "You are an expert at leveraging ReciPal 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 ReciPal "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 4 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 ReciPal MCP Server

Empower your AI agent to orchestrate your entire food manufacturing and recipe auditing workflow with ReciPal, the specialized source for nutritional labeling data. By connecting ReciPal to your agent, you transform complex ingredient analysis into a natural conversation. Your agent can instantly retrieve recipe details, audit calorie counts, and query ingredient lists without you ever touching a labeling portal. Whether you are conducting product research or managing regional dietary constraints, your agent acts as a real-time nutritional consultant, ensuring your data is always verified and precise.

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

What you can do

Recipe Auditing — Retrieve high-resolution details for all recipes in your catalog, including names, calorie counts, and serving metadata.
Ingredient Oversight — Audit the available ingredients in the ReciPal database to understand the thematic distribution of components instantly.
Nutritional Intelligence — Query full nutritional breakdowns for specific recipes to assist in deep-dive dietary classification.
Resource Discovery — Retrieve unique recipe identifiers to help you identify relevant markers for your food products.
Operational Monitoring — Check API status to ensure your nutritional research workflow is always operational.

The ReciPal MCP Server exposes 4 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 ReciPal to CrewAI via MCP

Follow these steps to integrate the ReciPal 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 4 tools from ReciPal

Why Use CrewAI with the ReciPal MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with ReciPal 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 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

ReciPal + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries ReciPal 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 ReciPal, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain ReciPal 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 ReciPal against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

ReciPal MCP Tools for CrewAI (4)

These 4 tools become available when you connect ReciPal to CrewAI via MCP:

check_api_status

Check if the ReciPal service is operational

get_recipe_details

Get full nutritional and ingredient details for a specific recipe by ID

list_recipal_ingredients

List all ingredients available in the ReciPal database

list_recipal_recipes

List all recipes in your ReciPal account

Example Prompts for ReciPal in CrewAI

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

"List all my recipes using ReciPal."

"What are the details for recipe ID '12345'?"

"List all ingredients available in ReciPal."

Troubleshooting ReciPal MCP Server with CrewAI

Common issues when connecting ReciPal 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

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

ReciPal + CrewAI FAQ

Common questions about integrating ReciPal 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.