get_trial_changes — Clinical Trial Tracker MCP Tool Read-only
get_trial_changes
(get trial changes) is one of 7 tools on the
Clinical Trial Tracker
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_trial_changes from your client
- Claude Code Clinical Trial Tracker get_trial_changes run in your project directory
- Claude Desktop Clinical Trial Tracker get_trial_changes ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Clinical Trial Tracker get_trial_changes ~/.cursor/mcp.json
- VS Code Clinical Trial Tracker get_trial_changes .vscode/mcp.json
- Zed Clinical Trial Tracker get_trial_changes ~/.config/zed/settings.json
- Windsurf Clinical Trial Tracker get_trial_changes ~/.codeium/windsurf/mcp_config.json
- Cline Clinical Trial Tracker get_trial_changes ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Clinical Trial Tracker get_trial_changes ~/.gemini/settings.json
- Grok Clinical Trial Tracker get_trial_changes .mcp.json (in your project root)
- ChatGPT Clinical Trial Tracker get_trial_changes Settings → Connectors → Advanced → Developer mode
- Claude.ai Clinical Trial Tracker get_trial_changes Settings → Connectors → Add custom connector
- LangChain Clinical Trial Tracker get_trial_changes pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http clinical https://clinicaltracker.org/mcp/publicOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.