awesome-medical

Awesome Medical MCP Server provides a suite of medical calculation tools for Claude AI medical assistants. The server aggregates four dedicated MCP services: an eGFR and creatinine clearance calculator, a pregnancy due date estimator tailored to Chinese population data, a pediatric asthma score calculator, and a McIsaac-based strep throat probability calculator. Each tool is exposed as an MCP server you can invoke via MCP hosts, enabling precise medical calculations, clinical explanations, and treatment guidance. To use these tools, deploy the MCP servers and configure Claude Desktop to route queries to the appropriate server by name, for example egfr-calculator or pregnancy-due-dates, using the provided npx-based commands. The result will include detailed outputs and clinical context in Chinese terminology.

Prerequisites:

• Node.js 18+ and npm
• Git

Install and set up:

1. Clone the repository: git clone https://github.com/shanggqm/awesome-medical-mcp-server.git cd awesome-medical-mcp-server

2. Install dependencies and build all packages: npm install npm run bootstrap # install all dependencies and build all packages

3. Generate DX extensions (optional but recommended for DX Templating): npm run pack:dxt:all

4. Run the MCP servers using your preferred method (see mcp_config for how to reference with npx). Note: The recommended approach is to rely on the npx-based invocations described in the mcp_config.

• The MCP servers are exposed as separate packages under @medical-mcp.*. You can invoke them with npx as shown in the configuration.
• If you use Claude Desktop, add each server under mcpServers with command: "npx" and args corresponding to the MCP server package name, e.g., ["@medical-mcp/egfr-calc-mcp-server"].
• DX extension files (.dxt) can be generated with npm run pack:dxt:all for easier distribution and installation in clients supporting DXT.
• Ensure Node.js version matches the Node.js 18+ badge in the README for compatibility.
• No environment variables are strictly required to run the servers, but you may expose environment-specific configuration (API keys, database URLs) via a standard env block if your deployment requires it.