Log inSubmit server
HasteHealth logo

HasteHealth

Provides MCP access to Haste Health’s FHIR R4 clinical data platform for AI-native health applications.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install HasteHealth

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "hastehealth": {
      "command": "npx",
      "args": [
        "-y",
        "haste-health"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command installed and started the server, which then stopped for configuration (such as an API key) that our sandbox does not have — expected for servers that connect to your account.

npx -y haste-health

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked .

Overview

HasteHealth connects AI agents and applications to clinical data stored as FHIR R4 through an MCP-enabled health data platform. The broader system also exposes a FHIR API, SQL-on-FHIR, OAuth2, and SMART on FHIR, with support for importing Epic, Oracle Health, and HL7v2 data. Run it locally with Docker Compose or deploy the published binaries and containers. Reach for it when an AI application needs a self-hosted or hosted foundation for working with standardized clinical records.

Use cases

  • Connect AI agents to FHIR R4 clinical data
  • Self-host a backend for AI-native health applications
  • Import healthcare data into a FHIR-centered platform
  • Run search indexing and FHIR subscription processing
  • Expose clinical data to applications and analytics

Key features

  • MCP access for AI agents
  • FHIR R4 clinical data storage
  • FHIR API and SQL-on-FHIR support
  • OAuth2 and SMART on FHIR
  • Docker Compose deployment
  • Rust server, worker, and CLI

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

13/13 checks healthy over the last 23d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 6d ago via OSV.dev · haste-health (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars86Stargazers on the source repository.
npm downloads6.6kPackage downloads in the last 30 days.
Last commitTodayMost recent push to the default branch.
Install checkRunsOur sandbox started it; it then asked for an API key or config.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How HasteHealth works

What HasteHealth MCP server does

HasteHealth provides an MCP interface to a health data platform built around FHIR R4. It is intended for AI-native health applications that need access to clinical records through an agent-compatible protocol. The same platform serves applications and analytics through a FHIR API and supports SQL-on-FHIR for working with FHIR data in relational query workflows.

Clinical information is stored as FHIR R4. The platform describes inbound support for Epic, Oracle Health, and HL7v2 data, giving teams a way to bring data from those healthcare systems into a FHIR-centered environment before making it available to applications, analytics, and AI agents.

How it works

The project is implemented in Rust and can be operated as a self-hosted deployment. Its architecture includes a server, a background worker, PostgreSQL, and an administrative application. The worker handles search indexing and FHIR subscription processing after the server and database services are running.

Docker Compose provides the quickest local path. The top-level compose file starts PostgreSQL, the server, worker, and admin application together. After the containers become healthy, the admin application is available at the documented local hostname and includes a tenant and user created by the migration step.

For backend development, the repository provides separate commands for starting supporting services, launching the server, running the worker, and developing the frontend. A single haste-health binary also provides server, worker, and administrative CLI commands.

Setup and configuration

A local deployment can be started by downloading the repository’s docker-compose.yml file and running:

Terminal
curl -O https://raw.githubusercontent.com/HasteHealth/HasteHealth/main/docker-compose.yml
docker compose up

The project can also be installed through npm:

Terminal
npm install -g haste-health
haste-health --help

For a one-off invocation, use npx haste-health --help. Published binaries are available for Linux on x64 and arm64, and for macOS on Apple Silicon. Linux builds are static; Windows users can run the binary through WSL.

Configuration is supported through haste.toml or environment variables. Server and worker settings are documented separately in the project. Administrative commands include database migration and tenant creation. The repository also publishes Docker images for the server and admin application.

Tools and capabilities

  • Exposes clinical data to AI agents through MCP.
  • Stores clinical records using FHIR R4.
  • Provides a FHIR API for applications and analytics.
  • Supports OAuth2 and SMART on FHIR.
  • Offers SQL-on-FHIR access patterns.
  • Processes search indexing and FHIR subscriptions in a background worker.

HasteHealth is licensed under Apache-2.0 and can be self-hosted. A hosted option is also offered with a signed BAA.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about HasteHealth

HasteHealth is an MCP server that connects AI agents to Haste Health’s FHIR R4 clinical data platform and exposes MCP access alongside its FHIR API. Its main tool surface is the MCP interface for working with stored clinical data, while OAuth2 and SMART on FHIR support the broader platform.

Run HasteHealth locally with the project’s Docker Compose file, or install the `haste-health` binary through npm. Use `docker compose up` for the full local stack, `npm install -g haste-health` for a global CLI installation, or `npx haste-health --help` without installing it.

Yes, HasteHealth supports self-hosted deployments. Docker Compose starts PostgreSQL, the server, worker, and admin application together, while published Docker images and standalone binaries support other deployment approaches.

HasteHealth stores clinical data as FHIR R4. The platform also describes inbound support for Epic, Oracle Health, and HL7v2 data, with FHIR, SQL-on-FHIR, and MCP available for downstream applications, analytics, and AI agents.

Yes, OAuth2 and SMART on FHIR are built into the HasteHealth platform. They are provided alongside the FHIR API and MCP support for applications and AI agents that work with clinical data.

Related MCP servers

All in Biology & Bioinformatics All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewHasteHealth AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/hastehealth?style=directory)](https://allmcps.com/mcp/hastehealth)
HTML Embed
<a href="https://allmcps.com/mcp/hastehealth"><img src="https://allmcps.com/api/badge/hastehealth?style=directory" alt="HasteHealth on AllMCPs" /></a>