FHIR MCP Server

MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications

Connector by wso2 · GitHub account verified by the MCP Registry

IndexedApache-2.0Local (stdio)★ 136

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/wso2-fhir-mcp-server

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications

Use cases: api-integration

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.

Tools: 4 read · 2 write · 1 delete
Secrets: None asked for
Install scripts: None found
Runs as: Python package

Tools by what they do 7

Read from the source code; the running server may list different tools.

Read 4 · Look things up without changing anything.

get_capabilities
get_user
read
search

Write 2 · Create, change, send or run things.

create
update

Delete 1 · Delete, drop, revoke or wipe things.

delete

Secrets and settings it asks for

Other settings (environment variables or headers).

FHIR_SERVER_BASE_URL

Network hosts it talks to 2

github.com · found in code
hapi.fhir.org · found in code

Tools (7)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

create
Creates a new FHIR resource on the server (FHIR `create` interaction: POST [base]/{type}). Use it to add a record that does not exist yet, such as a new Patient, Observation or Appointment. Do not use it to change an existing resource; use `update` for that. The server assigns a new id on every call, so repeating a call creates duplicates; use `search` first if the record may already exist. On success it returns the resource as stored, including the server-assigned `id` and `meta`. On failure it returns OperationOutcome issues whose `diagnostics` explain what to fix, such as a missing required…
delete
Execute a FHIR `delete` interaction on a specific resource instance. Use this tool when you need to remove a single resource identified by its logical ID or optionally filtered by search parameters. The optional `id` parameter must match an existing resource instance when present. If you include `searchParam`, the server will perform a conditional delete, deleting the resource only if it matches the given criteria. If you supply `operation`, it will execute the named FHIR operation (e.g., `$expunge`) on the resource. This tool returns a FHIR `OperationOutcome` describing success or failure of …
get_capabilities
Retrieves metadata about a specified FHIR resource type, including its supported search parameters and custom operations. This tool MUST always be invoked before performing any resource operation (such as search, read, create, update, or delete) to discover the valid searchParams and operations permitted for that resource type. Do not use this tool to fetch actual resources.
get_user
Retrieves the authenticated user's FHIR profile. Use this tool when you need to access the current user's demographic and contact details.
read
Performs a FHIR `read` interaction to retrieve a single resource instance by its type and resource ID, optionally refining the response with search parameters or custom operations. Use it when you know the exact resource ID and require that one resource; do not use it for bulk queries. If additional query-level parameters or operations are needed (e.g., _elements or $validate), include them in searchParam or operation. Optionally specify fields to filter the response to only the data your task needs (e.g., Patient.birthDate, Observation.valueQuantity).
search
Executes a standard FHIR `search` interaction on a given resource type, returning a bundle or list of matching resources. Use this when you need to query for multiple resources based on one or more search-parameters. Do not use this tool for create, update, or delete operations, and be aware that large result sets may be paginated by the FHIR server. Optionally specify fields to filter the response to only the data your task needs (e.g., Patient.birthDate, Observation.valueQuantity).
update
Replaces the full content of an existing FHIR resource (FHIR `update` interaction: PUT [base]/{type}/{id}). Use it to correct or complete a record whose logical id you already know. Elements left out of the payload are removed from the stored resource, not kept, so first get the current version with `read`, change what you need, and send the whole resource back. Do not use it to add new records; use `create` for that. On success it returns the resource as stored, with an updated `meta.versionId` and `meta.lastUpdated`. On failure it returns OperationOutcome issues whose `diagnostics` explain w…

Compare and alternatives

Featured in

Best MCP servers for healthcare

Signals

Stars: 136
Forks: 59
Open issues: 5
Contributors: 13
Weekly downloads: 623
Last commit: Oct 12, 2026 (15 days ago)
Last release: Mar 31, 2026 (7 months ago)
Last package publish: Oct 30, 2025 (0 years ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name: io.github.wso2/fhir-mcp-server
Version: 0.10.0
Auth: No auth
Packages: pypi fhir-mcp-server
License: Apache-2.0
Repository: github.com/wso2/fhir-mcp-server
Website: github.com/wso2/fhir-mcp-server
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: Official MCP Registry github-graphql