Do I need an API Key or registration?

No. ClinicalTrials.gov is a fully public service maintained by the US National Library of Medicine. All data is accessible without any authentication.

What types of studies can I search for?

The database covers interventional trials (testing drugs, devices, procedures), observational studies, and expanded access programs. You can search across all phases, from early Phase 1 research to post-market Phase 4 surveillance.

Is the trial recruiting status updated in real time?

The data reflects what is currently published on the ClinicalTrials.gov database. Sponsors typically update the registry directly, so you will see the latest status logged in their system.

ClinicalTrials.gov MCP Server for CrewAI 3 tools — connect in under 2 minutes

Name: ClinicalTrials.gov
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 3 Tools Framework

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

The ClinicalTrials.gov MCP Server connects your AI agent to the United States National Institutes of Health (NIH) clinical research database — the gold standard for clinical trial transparency worldwide.

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

Core Capabilities

Universal Trial Search — Query over 500,000 registered studies by condition, drug name, sponsor, or any keyword. Filter by recruitment status and trial phase to pinpoint exactly what matters.
Deep Trial Profiles — Retrieve full study protocols including eligibility criteria, enrollment targets, intervention details, and sponsor information for any registered trial.
Active Recruitment Finder — Dedicated tool for patients and clinicians to discover trials actively enrolling participants right now, searchable by medical condition.

Zero authentication required. Fully open public data maintained by the National Library of Medicine. Critical for pharmaceutical researchers, healthcare professionals, patient advocates, and biotech analysts.

The ClinicalTrials.gov MCP Server exposes 3 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 ClinicalTrials.gov to CrewAI via MCP

Follow these steps to integrate the ClinicalTrials.gov 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 3 tools from ClinicalTrials.gov

Why Use CrewAI with the ClinicalTrials.gov MCP Server

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

ClinicalTrials.gov + CrewAI Use Cases

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

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

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

ClinicalTrials.gov MCP Tools for CrewAI (3)

These 3 tools become available when you connect ClinicalTrials.gov to CrewAI via MCP:

find_recruiting_trials

Useful for patients and healthcare providers looking for active enrollment opportunities. Find clinical trials that are actively recruiting participants for a specific medical condition

get_trial_details

Retrieve full details of a specific clinical trial by its NCT identifier

search_clinical_trials

Can filter by recruitment status and trial phase. Search the ClinicalTrials.gov database for studies by keyword, condition, drug name, or sponsor

Example Prompts for ClinicalTrials.gov in CrewAI

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

"Are there any clinical trials recruiting participants for Alzheimer's disease right now?"

"Show me Phase 3 trials related to breast cancer treatment."

"Get me the full details for trial NCT04280705."

Troubleshooting ClinicalTrials.gov MCP Server with CrewAI

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

ClinicalTrials.gov + CrewAI FAQ

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