Enables analysis of clinical trial data from the AACT database, tracking development trends, and generating analysis memos.
Enables analysis of clinical trial data from the AACT database, tracking development trends, and generating analysis memos. The ctgov mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 7 defined tools rather than through you.
Query the AACT (ClinicalTrials.gov) database directly from Claude. Explore 70+ tables of clinical trial data — studies, interventions, outcomes, sponsors, facilities — using read-only SQL with buffered pagination.
Everything the assistant can do here goes through one of these:
database_info — Confirm database connection, server time, and data currencylist_tables — Discover all available tables with approximate row countsdescribe_table — Inspect column names, types, distinct counts, and sample valuesget_column_values — Get distinct values for a column with counts — essential before filteringsearch_columns — Find columns by keyword across all tables (e.g. masking -> designs.masking)read_query — Execute a SELECT, CTE, or EXPLAIN query with buffered results and previewfetch_rows — Page through buffered query results without re-queryingYou will need 2 environment variables: DB_USER, DB_PASSWORD. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
The server ships on PyPI as ENOENT, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Ctgov's toolset — database_info, list_tables, describe_table and 4 more — is a fair guide to whether it matches your workflow. It is maintained by navisbio; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Ctgov's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| database_info | Confirm database connection, server time, and data currency |
| list_tables | Discover all available tables with approximate row counts |
| describe_table | Inspect column names, types, distinct counts, and sample values |
| get_column_values | Get distinct values for a column with counts — essential before filtering |
| search_columns | Find columns by keyword across all tables (e.g. masking -> designs.masking) |
| read_query | Execute a SELECT, CTE, or EXPLAIN query with buffered results and preview |
| fetch_rows | Page through buffered query results without re-querying |
{
"mcpServers": {
"aact": {
"command": "uvx",
"args": ["mcp-server-aact"],
"env": {
"DB_USER": "your_username",
"DB_PASSWORD": "your_password"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| DB_USER | Configuration value read at startup. | Optional |
| DB_PASSWORD | Configuration value read at startup. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.