Healthcare Fhir MCP vs Fhir MCP Server
A side-by-side look at the Healthcare Fhir MCP and Fhir MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Healthcare Fhir MCP for biology & bioinformatics work as a local process; choose Fhir MCP Server for biology & bioinformatics over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Healthcare Fhir MCP when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
Choose Fhir MCP Server when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
- You want tools like
Security.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 39/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 102 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 1 |
| Full listing | View Healthcare Fhir MCP | View Fhir MCP Server |
Tools & capabilities
Healthcare Fhir MCP tools
No tool names declared yet. Check the project README from the listing page.
Fhir MCP Server tools 1
SecurityOAuth2 authentication and proper access control for all operations
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Healthcare Fhir MCP
{
"mcpServers": {
"healthcare-fhir-mcp": {
"command": "npx",
"args": [
"-y",
"meok-setup"
]
}
}
}
Fhir MCP Server
{
"mcpServers": {
"the-momentum-fhir-mcp-server": {
"url": "https://api.medplum.com"
}
}
}
Frequently asked questions
Healthcare Fhir MCP is categorized under Biology & Bioinformatics and uses a local stdio subprocess. Fhir MCP Server belongs to Biology & Bioinformatics and uses a remote HTTP/SSE transport. Pick Healthcare Fhir MCP for biology & bioinformatics work and Fhir MCP Server for biology & bioinformatics.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Healthcare Fhir MCP has no declared pricing — check the project's own site. Fhir MCP Server is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add healthcare-fhir-mcp and the-momentum-fhir-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Healthcare Fhir MCP has a quality signal of 39/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Fhir MCP Server has 53/100 (Good) with 2 views, 0 installs and 102 GitHub stars.