ClinicalTrials.gov MCP integration
Search ClinicalTrials.gov study records, retrieve trial details, and monitor updated studies.
Sign in and add ClinicalTrials.gov in Apps. No ClinicalTrials.gov account is required.
Tools
| Name | Description |
|---|---|
search_studiesSearch ClinicalTrials.gov studies with v2 API filters and cursor pagination. | Search ClinicalTrials.gov studies with v2 API filters and cursor pagination. |
get_studyGet one ClinicalTrials.gov study by NCT ID. | Get one ClinicalTrials.gov study by NCT ID. |
list_study_metadataReturn ClinicalTrials.gov v2 API metadata and field definitions. | Return ClinicalTrials.gov v2 API metadata and field definitions. |
Triggers
| Name | Description |
|---|---|
updated_studiesPoll for recently updated ClinicalTrials.gov studies matching a query. | Poll for recently updated ClinicalTrials.gov studies matching a query. |
Quick Start
import { WeavzClient } from '@weavz-io/sdk'
const weavz = new WeavzClient({ apiKey: 'wvz_...' })
const result = await weavz.actions.execute('clinicaltrials', 'search_studies', {
workspaceId: '550e8400-e29b-41d4-a716-446655440000',
integrationAlias: 'clinicaltrials',
input: { /* ... */ },
})Related Integrations
Works well with
Frequently Asked Questions
Is there a ClinicalTrials.gov MCP server through Weavz?
Yes. Add the ClinicalTrials.gov integration to a Weavz workspace, enable the actions you need and connect any required account. Weavz provides the workspace MCP endpoint in Tool Mode or Code Mode. The catalog currently lists 3 ClinicalTrials.gov actions.
What can an AI agent do with ClinicalTrials.gov?
Available actions include Search Studies, Get Study, List Study Metadata. Your workspace exposes only the actions you enable. The agent also needs the intended account access and any required input values.
How do I connect ClinicalTrials.gov to Claude or ChatGPT?
Use a compatible remote MCP client, add the Weavz connector and choose a workspace. Add ClinicalTrials.gov, connect the required account and review the enabled actions. Client availability and account requirements vary; adding the connector does not authorize every app automatically.
Can I use ClinicalTrials.gov through an API or SDK?
Yes, supported actions can run through the Weavz REST API, TypeScript SDK or Python SDK. Configure a workspace and the required connections, use scoped access, and pass the intended end-user context when acting for a customer.
What authentication does ClinicalTrials.gov require?
This catalog integration does not require a stored external account connection. Provider terms, rate limits and tool-specific inputs can still apply.
How do I review sensitive ClinicalTrials.gov actions?
Limit enabled actions, scope credentials to the intended user and configure Human Gates for the operations that need review. A matching policy can pause a send, record change or other sensitive action for an approver before execution.
What limits or costs apply to ClinicalTrials.gov?
Weavz plan limits apply to the actions and resources you use. The external provider may also require an account, a paid plan, API credits or specific permissions, and may enforce its own rate limits. Check current Weavz pricing and the provider’s terms before rollout.
What ClinicalTrials.gov triggers are available?
The catalog lists 1 triggers, including Updated Studies. Configure the trigger and your event handler before using incoming events to start work.
Connect ClinicalTrials.gov in minutes
Get 20,000 free action executions every month. No credit card required.