2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 8 Tools Framework

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

Vinkius supports streamable HTTP and SSE.

python
from crewai import Agent, Task, Crew

agent = Agent(
    role="API Ninjas Specialist",
    goal="Help users interact with API Ninjas effectively",
    backstory=(
        "You are an expert at leveraging API Ninjas 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 API Ninjas "
        "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)
API Ninjas
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 API Ninjas MCP Server

Connect to API Ninjas and access a comprehensive suite of health and fitness tools through natural conversation.

When paired with CrewAI, API Ninjas becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call API Ninjas 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

  • Exercise Search — Search 1000+ exercises by name, type, muscle group and difficulty with step-by-step instructions
  • Calories Burned — Calculate calories burned for various activities based on weight and duration
  • Body Fat — Estimate body fat percentage using the US Navy method
  • BMR & TDEE — Calculate Basal Metabolic Rate and Total Daily Energy Expenditure
  • Nutrition — Get nutritional info for any food item (calories, protein, carbs, fat)
  • Sleep — Get recommended sleep duration based on age and gender
  • Steps — Calculate calories burned and distance from step count

The API Ninjas 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 API Ninjas to CrewAI via MCP

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

01

Install CrewAI

Run pip install crewai

02

Replace the token

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

03

Customize the agent

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

04

Run the crew

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

Why Use CrewAI with the API Ninjas MCP Server

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

01

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

02

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

03

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

04

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

API Ninjas + CrewAI Use Cases

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

01

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

02

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

03

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

04

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

API Ninjas MCP Tools for CrewAI (8)

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

01

get_bmr

Requires weight (kg), height (cm), age and gender. Returns BMR value in calories/day. Calculate Basal Metabolic Rate

02

get_body_fat

Requires waist, neck and height measurements (in cm). For women, also requires hip measurement. Returns body fat percentage and category (lean, fitness, acceptable, obese). Estimate body fat percentage

03

get_calories_burned

Requires activity name, weight (kg) and duration (minutes). Returns activity name, duration, calories burned and MET value. Calculate calories burned for an activity

04

get_exercises

Supports filtering by name, type (cardio, olympic_weightlifting, plyometrics, powerlifting, strength, stretching, strongman), muscle (abdominals, abductors, adductors, biceps, calves, chest, forearms, glutes, hamstrings, lats, lower_back, middle_back, neck, quadriceps, traps, triceps) and difficulty (beginner, intermediate, expert). Returns exercise name, type, muscle worked, equipment needed, difficulty level and step-by-step instructions. Search exercises by name, type, muscle or difficulty

05

get_nutrition

Returns calories, protein, carbohydrates, fat, saturated fat, cholesterol, sodium, potassium, fiber and sugar per 100g serving. Get nutrition info for a food item

06

get_sleep

Returns recommended sleep range and whether current sleep is adequate. Get recommended sleep duration

07

get_steps

Requires step count and optionally weight (kg), height (cm), age and gender for more accurate calculations. Calculate calories and distance from steps

08

get_tdee

Requires weight (kg), height (cm), age, gender and activity level. Returns TDEE value in calories/day with breakdown by activity level. Calculate Total Daily Energy Expenditure

Example Prompts for API Ninjas in CrewAI

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

01

"Find chest exercises for beginners."

02

"What's the nutritional info for a banana?"

03

"Calculate my BMR. I'm 30 years old, male, 80kg, 180cm."

Troubleshooting API Ninjas MCP Server with CrewAI

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

01

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

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.

API Ninjas + CrewAI FAQ

Common questions about integrating API Ninjas MCP Server with CrewAI.

01

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.
02

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.
03

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.
04

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.
05

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.

Connect API Ninjas to CrewAI

Get your token, paste the configuration, and start using 8 tools in under 2 minutes. No API key management needed.