Statpearls MCP Server

Give your AI system a relaible source of medical knowledge for its next conversation. The statpearls mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 12 defined tools rather than through you.

What it actually does

• Searches for diseases and medical conditions on StatPearls
• Retrieve comprehensive, reliable medical information from StatPearls
• Convert HTML content to well-formatted Markdown to make it AI-friendly
• Integrates with AI models via the Model Context Protocol

Adding it to your client

The server ships on npm as @smithery/cli, 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.

Its toolset

Everything the assistant can do here goes through one of these:

• statpearls_disease_info — Fetches comprehensive, reliable medical information about diseases from StatPearls
• query — Disease or medical condition to search for (required)
• format_options — Optional formatting preferences
• includeToc — Whether to include a table of contents (default: true)
• maxLength — Maximum length of the returned content in characters (default: 50000)
• statpearls — mcp (default executable)
• statpearls-mcp-linux — x64 (Linux)
• statpearls-mcp-windows — x64.exe (Windows)
• statpearls-mcp-darwin — x64 (macOS)
• Building — The build process creates a single JavaScript file that can run with vanilla Node.js:
• Releasing — The release process handles versioning, building, compiling, and Git operations:
• Versioning — The project follows semantic versioning. You can check the current version with:

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Statpearls MCP.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the statpearls mcp mcp server does with a few real requests.

When to reach for it

Among the developer tooling 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. Statpearls MCP's toolset — statpearls_disease_info, query, format_options and 9 more — is a fair guide to whether it matches your workflow. It is maintained by jpoles1; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Statpearls MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.