ct_count_by_condition — Clinicaltrials MCP Tool
ct_count_by_condition
(ct count by condition) is one of 50 tools on the
Clinicaltrials
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call ct_count_by_condition from your client
- Claude Code Clinicaltrials ct_count_by_condition run in your project directory
- Claude Desktop Clinicaltrials ct_count_by_condition ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Clinicaltrials ct_count_by_condition ~/.cursor/mcp.json
- VS Code Clinicaltrials ct_count_by_condition .vscode/mcp.json
- Zed Clinicaltrials ct_count_by_condition ~/.config/zed/settings.json
- Windsurf Clinicaltrials ct_count_by_condition ~/.codeium/windsurf/mcp_config.json
- Cline Clinicaltrials ct_count_by_condition ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Clinicaltrials ct_count_by_condition ~/.gemini/settings.json
- Grok Clinicaltrials ct_count_by_condition .mcp.json (in your project root)
- ChatGPT Clinicaltrials ct_count_by_condition Settings → Connectors → Advanced → Developer mode
- Claude.ai Clinicaltrials ct_count_by_condition Settings → Connectors → Add custom connector
- LangChain Clinicaltrials ct_count_by_condition pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http clinicaltrials https://gateway.pipeworx.io/clinicaltrials/mcpOther tools on this server
- ask_pipeworx
- ask_pipeworx_beta
- ask_pipeworx_grounded
- search_within
- deep_research
- discover_tools
- resolve_entity
- compare_entities
- subscribe
- unsubscribe
- list_subscriptions
- recent_alerts
- entity_profile
- recent_changes
- validate_claim
- company_facts
- scan_dependency
- bet_research
- polymarket_arbitrage
- polymarket_edges
- polymarket_kalshi_spread
- polymarket_fill_risk
- polymarket_edge_tracker
- kalshi_weather_edge
- resolution_audit
- resolution_diff
- release_calendar_markets
- pipeworx_trending
- suggest_questions
- generate_llms_txt
- ai_visibility_check
- scan_competitor_ai_presence
- pipeworx_feedback
- remember
- recall
- forget
- ct_search
- ct_get_study
- ct_sponsor_trials
- ct_compare_sponsors
- ct_recent_updates
- ct_trials_by_location
- ct_catalyst_calendar
- ct_sponsor_pipeline
- ct_competitive_landscape
- ct_enrollment_watch
- ct_results_summary
- ct_phase_transition_rates
- ct_sponsor_activity
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.