Appendix vs Fhir MCP Server
A side-by-side look at the Appendix 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 Appendix for biology & bioinformatics work over a hosted endpoint; 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 Appendix when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
API_BASE_URL, PORT. - You want tools like
search_knowledge_base, submit_encounter, list_conditions.
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 | 48/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | API_BASE_URLPORT | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 102 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 3 | 1 |
| Full listing | View Appendix | View Fhir MCP Server |
Tools & capabilities
Appendix tools 3
search_knowledge_baseSearch medical literature and treatment guidelinessubmit_encounterSubmit a clinical letter for physician reviewlist_conditionsList available conditions and medications
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.
Appendix
{
"mcpServers": {
"appendix": {
"url": "https://mcp.appendix.com/mcp"
}
}
}
Fhir MCP Server
{
"mcpServers": {
"the-momentum-fhir-mcp-server": {
"url": "https://api.medplum.com"
}
}
}
Frequently asked questions
Appendix is categorized under Biology & Bioinformatics and uses a remote HTTP/SSE transport. Fhir MCP Server belongs to Biology & Bioinformatics and uses a remote HTTP/SSE transport. Pick Appendix 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.
Appendix 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 appendix 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, Appendix has a quality signal of 48/100 (Fair) with 2 views, 0 installs and 2 GitHub stars. Fhir MCP Server has 53/100 (Good) with 2 views, 0 installs and 102 GitHub stars.