What is the goal of this project?
To evaluate whether an MCP server on Azure PostgreSQL can improve developer productivity and maintain or enhance runtime efficiency compared to direct SQL for clinical analytics on MIMIC‑IV.
@ambakick
基本情報
概要はまだありません
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"mcpServers": {
"mimic-mcp-server": {
"command": "python",
"args": [
"02_bulk_copy.py",
"--csv-root",
"/path/to/mimic-iv"
]
}
}
}ツール一覧はまだありません
この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。
ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。
This project evaluates whether a Model Context Protocol (MCP) server layered on Azure Database for PostgreSQL can match or outperform direct SQL while reducing developer effort for large‑scale clinical analytics on the MIMIC‑IV dataset.
Install Python 3.10+ and required libraries (psycopg, mcp[cli], azure‑identity, etc.). Load MIMIC‑IV data into an Azure Database for PostgreSQL Flexible Server using the provided SQL scripts and bulk copy script. Start the MCP server by running python azure_postgresql_mcp.py with environment variables PGHOST, PGUSER, PGPASSWORD, PGDATABASE set (or use Microsoft Entra authentication by setting AZURE_USE_AAD=True). Benchmarks can be run with python benchmarks/run_sql.py --query <name> for direct SQL or python benchmarks/run_mcp.py --query <name> for the MCP server.
To evaluate whether an MCP server on Azure PostgreSQL can improve developer productivity and maintain or enhance runtime efficiency compared to direct SQL for clinical analytics on MIMIC‑IV.
Python 3.10+, Node 18+ (optional), an Azure Database for PostgreSQL – Flexible Server (Standard_D4s v5 or larger), MIMIC‑IV credentials and data download permission, and the Python packages listed in the README.
Set the required environment variables (`PGHOST`, `PGUSER`, `PGPASSWORD`, `PGDATABASE`) or configure Entra ID authentication, then run `python azure_postgresql_mcp.py` from the `mcp-server` directory.
For a `COUNT(*)` on `emar_detail` (≈87 million rows), the MCP server averaged 67,560 ms vs. direct SQL’s 101,550 ms, a 33% improvement. The MCP implementation required 23 lines of code vs. 68 for direct SQL.
Data loading scripts are in the `mimic-postgres/` directory, including SQL schema files and a bulk copy script (`02_bulk_copy.py`). Estimated ingest time on Standard_D4s is ~45 minutes for 72 GB of data.
Postgres MCP Pro provides configurable read/write access and performance analysis for you and your AI agents.
A Model Context Protocol (MCP) server that enables secure interaction with MySQL databases

Connect Karma.Domains to ChatGPT, Claude, Cursor, VS Code, or another MCP client — and find a domain in plain language. The same auctions, expired, backorder, and buy-now data you use in the app, plus saved filters, note

Model Context Protocol Servers
コメント