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.

Oracle MCP server with no run-sql tool: It generates tools for each of the PL/SQL procedures, tables and approved SQL you choose. The server doesn't expose a SQL prompt, and can't reveal how it's connected to Oracle.

Local database MCP server: your agent sees a migration's impact before it runs, for PostgreSQL, MySQL, SQL Server and SQLite, with no database credentials.
A Model Context Protocol server that provides read-only access to MySQL databases. This server enables LLMs to inspect database schemas and execute read-only queries.
Postgres MCP Pro provides configurable read/write access and performance analysis for you and your AI agents.
评论