MCP.so
Sign In

Example MCP SSE Server intgrated with FHIR Server

@j4jayant

Basic information

Category

Other

Transports

stdio

Author

j4jayant

About Example MCP SSE Server intgrated with FHIR Server

Example MCP SSE Server with FHIR Integration

#mcp-fhir-server#fhir#mcp

Example MCP SSE Server intgrated with FHIR Server config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Example MCP SSE Server intgrated with FHIR Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Example MCP SSE Server integrated with FHIR Server?

It is a Model Context Protocol (MCP) server implementation that integrates with a FHIR server to provide FHIR-specific tool definitions. This is a quick and dirty demonstration of MCP + FHIR integration, and it does not cover FHIR server OAuth; it depends on a supplied auth token.

How to use Example MCP SSE Server integrated with FHIR Server?

—

Key features of Example MCP SSE Server integrated with FHIR Server

  • Provides Create FHIR Resource tool
  • Provides Read FHIR Resource tool
  • Uses Express web framework
  • Depends on supplied auth token (no OAuth)
  • Tested with Patient and Appointment resources

Use cases of Example MCP SSE Server integrated with FHIR Server

  • Demonstrate how MCP can interact with a FHIR server
  • Create FHIR resources (e.g., Patient, Appointment) via MCP
  • Read FHIR resources by type and ID
  • Quick prototyping of MCP–FHIR integration

Frequently asked questions

1

What does this MCP server do?

It integrates with a FHIR server to expose FHIR-specific tools via the Model Context Protocol.

2

What tools does it provide?

Two tools: Create FHIR Resource (takes ResourceType and ResourceBody) and Read FHIR Resource (takes ResourceType and ResourceID).

3

Does it support FHIR OAuth?

No. It depends on a supplied auth token and does not cover FHIR server OAuth.

4

Which FHIR resources have been tested?

Patient and Appointment resources were tested without any issues.

5

What are the runtime dependencies?

The server depends on the @modelcontextprotocol/sdk and Express web framework.

Comments

More Other MCP servers