Clinical Trials

Created By
JackKuo666a year ago
Overview

What is Clinical Trials MCP Server?

The Clinical Trials MCP Server is a tool that enables AI assistants to search and access data from ClinicalTrials.gov, providing a simple interface for retrieving clinical trial information.

How to use Clinical Trials MCP Server?

To use the Clinical Trials MCP Server, install it via Smithery or manually set it up in your development environment. Once running, you can utilize various MCP tools to search for trials and retrieve data programmatically.

Key features of Clinical Trials MCP Server?

  • 🔎 Trial Search: Custom search strings or advanced parameters for querying clinical trials.
  • 🚀 Efficient Retrieval: Fast access to trial metadata.
  • 📊 Metadata Access: Retrieve detailed metadata using NCT ID.
  • 📋 CSV Management: Save, load, and list CSV files with trial data.
  • 🗃️ Local Storage: Trials saved locally for faster access.
  • 📊 Statistics: Get statistics about clinical trials.

Use cases of Clinical Trials MCP Server?

  1. Searching for clinical trials related to specific conditions.
  2. Retrieving detailed information about a particular trial using its NCT ID.
  3. Saving search results to CSV for further analysis.

FAQ from Clinical Trials MCP Server?

  • Can I search for any clinical trial?

Yes! You can search for trials using various parameters and keywords.

  • Is there a limit to the number of studies I can retrieve?

You can specify the maximum number of studies to return in your search queries.

  • How do I get detailed information about a specific trial?

Use the get_full_study_details tool with the trial's NCT ID to retrieve detailed information.

Server Config

{
  "mcpServers": {
    "ClinicalTrials": {
      "command": "python",
      "args": [
        "-m",
        "ClinicalTrials-mcp-server"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
JackKuo666
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago