4,000+ servers built on vurb.ts
Vinkius

Harvard ClinicalTrials MCP Server for CrewAIGive CrewAI instant access to 16 tools to Get Api Version, Get Study, Get Study Results, and more

MCP Inspector GDPR Free for Subscribers

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

Ask AI about this MCP Server for CrewAI

The Harvard ClinicalTrials MCP Server for CrewAI is a standout in the Data Analytics category — giving your AI agent 16 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Harvard ClinicalTrials Specialist",
    goal="Help users interact with Harvard ClinicalTrials effectively",
    backstory=(
        "You are an expert at leveraging Harvard ClinicalTrials 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 Harvard ClinicalTrials "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 16 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
Harvard ClinicalTrials
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 Harvard ClinicalTrials MCP Server

Connect to the ClinicalTrials.gov API v2 — the largest database of clinical studies worldwide, maintained by the U.S. National Library of Medicine.

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

  • Study Search — Search 400K+ clinical trials from 220+ countries
  • Condition Filter — Find trials for specific diseases (cancer, diabetes, Alzheimer's)
  • Intervention Filter — Search by drug, device, or therapy name
  • Sponsor Search — Find trials by organization (Pfizer, NIH, Roche)
  • Phase Filter — Filter by Phase 1-4 to track drug development stages
  • Recruiting — Find trials currently enrolling participants
  • Location — Search by city or country for accessible trials
  • FDA Regulated — Filter for FDA-regulated drug and device trials
  • Pediatric — Find trials including children
  • Rare Diseases — Discover research for orphan conditions
  • Results — Get outcome data from completed studies

The Harvard ClinicalTrials MCP Server exposes 16 tools through the Vinkius. Connect it to CrewAI in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 16 Harvard ClinicalTrials tools available for CrewAI

When CrewAI connects to Harvard ClinicalTrials through Vinkius, your AI agent gets direct access to every tool listed below — spanning clinical-trials, medical-research, drug-development, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

get

Get api version on Harvard ClinicalTrials

gov API version and the timestamp of the most recent data update. Useful for verifying data currency and API availability. Get API version and data timestamp

get

Get study on Harvard ClinicalTrials

g. "NCT04368728"). Returns title, status, phase, enrollment, conditions, interventions, eligibility criteria, sponsor, and study locations. Get clinical trial details by NCT ID

get

Get study results on Harvard ClinicalTrials

Not all trials report results — this is most useful for completed Phase 2-4 studies. Get primary outcome results for a trial

get

Get study timeline on Harvard ClinicalTrials

Essential for understanding the progress and currency of a study. Get the complete timeline of a clinical trial

search

Search by condition on Harvard ClinicalTrials

Examples: "diabetes", "breast cancer", "Alzheimer disease", "COVID-19", "depression", "hypertension". Search trials by medical condition

search

Search by intervention on Harvard ClinicalTrials

Examples: "pembrolizumab", "metformin", "radiation therapy", "cognitive behavioral therapy". Search trials by drug or treatment

search

Search by location on Harvard ClinicalTrials

Essential for finding trials accessible to patients in a particular area. Search trials by geographic location

search

Search by phase on Harvard ClinicalTrials

Phase values: "PHASE1", "PHASE2", "PHASE3", "PHASE4", "EARLY_PHASE1". Phase 3 trials are the largest and most definitive, while Phase 1 trials focus on safety. Search trials by study phase

search

Search by sponsor on Harvard ClinicalTrials

Examples: "Pfizer", "National Cancer Institute", "Roche", "Novartis", "NIH". Search trials by sponsoring organization

search

Search completed on Harvard ClinicalTrials

Completed trials are more likely to have published results and outcomes data. Search completed clinical trials

search

Search device trials on Harvard ClinicalTrials

Covers diagnostic devices, surgical tools, implants, and digital health technologies. Search medical device clinical trials

search

Search fda regulated on Harvard ClinicalTrials

S. Food and Drug Administration. These trials follow the most rigorous regulatory standards. Search FDA-regulated drug trials

search

Search pediatric on Harvard ClinicalTrials

Essential for pediatricians, child health researchers, and parents seeking trials for children. Search pediatric clinical trials

search

Search rare diseases on Harvard ClinicalTrials

Examples: "cystic fibrosis", "sickle cell disease", "Huntington disease", "amyotrophic lateral sclerosis". Search rare disease clinical trials

search

Search recruiting on Harvard ClinicalTrials

Essential for patients seeking to enroll in trials or researchers tracking active studies. Search for currently recruiting studies

search

Search studies on Harvard ClinicalTrials

gov database of over 400,000 clinical studies from 200+ countries. Returns NCT IDs, titles, status, phases, sponsors, conditions, interventions, and locations. Search 400K+ clinical trials worldwide

Connect Harvard ClinicalTrials to CrewAI via MCP

Follow these steps to wire Harvard ClinicalTrials into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

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 16 tools from Harvard ClinicalTrials

Why Use CrewAI with the Harvard ClinicalTrials MCP Server

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

Harvard ClinicalTrials + CrewAI Use Cases

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

01

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

03

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

Example Prompts for Harvard ClinicalTrials in CrewAI

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

01

"Find recruiting Phase 3 trials for breast cancer immunotherapy"

02

"Search for Alzheimer's disease trials sponsored by NIH in Boston"

03

"Find pediatric clinical trials for cystic fibrosis"

Troubleshooting Harvard ClinicalTrials MCP Server with CrewAI

Common issues when connecting Harvard ClinicalTrials to CrewAI through 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.

Harvard ClinicalTrials + CrewAI FAQ

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

Explore More MCP Servers

View all →