How do I get an ExerciseDB API key?

Sign up on [**RapidAPI**](https://rapidapi.com/justin-w-fns/api/exercisedb) and subscribe to the ExerciseDB API. Free tier includes 10 requests/day. Paid plans offer more requests.

What body parts are available?

The database includes: back, chest, shoulders, upper arms, lower arms, upper legs, lower legs, neck, waist and cardio. Use get_body_part_list to see the complete list.

Does the API include exercise instructions?

Yes! Each exercise includes step-by-step instructions (numbered list) and an animated GIF URL showing the proper form and movement.

ExerciseDB MCP Server for CrewAI 9 tools — connect in under 2 minutes

Name: ExerciseDB
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 9 Tools Framework

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

Connect to ExerciseDB and explore a comprehensive exercise database through natural conversation.

When paired with CrewAI, ExerciseDB becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call ExerciseDB 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 — Browse 1300+ exercises with detailed instructions and animated GIFs
Filter by Body Part — Find exercises for back, chest, shoulders, legs, arms, waist and more
Filter by Target Muscle — Search exercises targeting specific muscles (abs, biceps, quads, glutes)
Filter by Equipment — Find exercises by equipment type (dumbbell, barbell, body weight, cable)
Search by Name — Find exercises by name (crunches, curls, presses, squats)
Reference Lists — Get complete lists of body parts, target muscles and equipment types

The ExerciseDB MCP Server exposes 9 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 ExerciseDB to CrewAI via MCP

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

Why Use CrewAI with the ExerciseDB MCP Server

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

ExerciseDB + CrewAI Use Cases

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

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

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

ExerciseDB MCP Tools for CrewAI (9)

These 9 tools become available when you connect ExerciseDB to CrewAI via MCP:

get_all_exercises

Returns exercise names, body parts, target muscles, equipment needed, GIF URLs and step-by-step instructions. Supports limit and offset parameters for pagination. Get all exercises with pagination

get_body_part_list

Useful for discovering valid body part values to use with get_exercises_by_body_part. Get list of all body parts

get_equipment_list

Useful for discovering valid equipment values to use with get_exercises_by_equipment. Get list of all equipment types

get_exercise_by_id

Returns exercise name, body part, target muscle, equipment, secondary muscles, step-by-step instructions and animated GIF URL. Get a specific exercise by ID

get_exercises_by_body_part

Common body parts include: "back", "chest", "shoulders", "upper arms", "lower arms", "upper legs", "lower legs", "neck", "waist", "cardio". Returns exercise details with target muscles, equipment and instructions. Get exercises by body part

get_exercises_by_equipment

Common equipment includes: "assisted", "band", "barbell", "body weight", "bosu ball", "cable", "dumbbell", "elliptical machine", "ez barbell", "hammer", "kettlebell", "leverage machine", "medicine ball", "olympic barbell", "resistance band", "roller", "rope", "skierg machine", "sled machine", "smith machine", "stability ball", "stationary bike", "stepmill machine", "tire", "trap bar", "upper body ergometer", "weighted", "wheel roller". Returns exercise details with body part, target muscles and instructions. Get exercises by equipment type

get_exercises_by_name

Returns matching exercises with full details including body part, target muscles, equipment, instructions and GIF URLs. Get exercises by name search

get_exercises_by_target

Common targets include: "abductors", "abs", "adductors", "biceps", "calves", "cardiovascular system", "delts", "forearms", "glutes", "hamstrings", "lats", "levator scapulae", "pectorals", "quads", "serratus anterior", "spine", "traps", "triceps", "upper back". Returns exercise details with body part, equipment and instructions. Get exercises by target muscle

get_target_list

Useful for discovering valid target values to use with get_exercises_by_target. Get list of all target muscles

Example Prompts for ExerciseDB in CrewAI

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

"Show me exercises for chest with dumbbells."

"What exercises target the abs?"

"Show me exercises I can do with just body weight."

Troubleshooting ExerciseDB MCP Server with CrewAI

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

ExerciseDB + CrewAI FAQ

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