Health Api MCP Server

A comprehensive FastAPI microservice for health-related operations with JWT authentication, PostgreSQL database, and Alembic migrations.It is backed

Local serverstdioPython

What is the Health Api MCP server?

A comprehensive FastAPI microservice for health-related operations with JWT authentication, PostgreSQL database, and Alembic migrations.It is backed by MCP server using FastApiMCP. The health api mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 8 defined tools rather than through you.

What it actually does

  • JWT-based authentication
  • PostgreSQL database with async SQLAlchemy
  • Alembic database migrations
  • Comprehensive health domain models (Patient, Doctor, Appointment, Medical Record)
  • RESTful API endpoints
  • Interactive API documentation (Swagger UI)

Its toolset

Everything the assistant can do here goes through one of these:

  • ReDochttp://localhost:5000/redoc
  • Doctors — The Doctors tool exposed by this server
  • Patients — The Patients tool exposed by this server
  • Appointments — The Appointments tool exposed by this server
  • Telemedicine — The Telemedicine tool exposed by this server
  • Referral — The Referral tool exposed by this server
  • Pharmacy — The Pharmacy tool exposed by this server
  • Insurance — All these endpoints require the Authorization: Bearer header. Refer to the interactive API docs at /docs for detailed request/response

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Configuration

  • Python 3.13.3+ - PostgreSQL - UV package manager

When to reach for it

Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Health Api's toolset — ReDoc, Doctors, Patients and 5 more — is a fair guide to whether it matches your workflow. It is maintained by AlwaysSany; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the health api mcp server does with a few real requests.

Available tools

ToolWhat it does
ReDochttp://localhost:5000/redoc
DoctorsThe Doctors tool exposed by this server.
PatientsThe Patients tool exposed by this server.
AppointmentsThe Appointments tool exposed by this server.
TelemedicineThe Telemedicine tool exposed by this server.
ReferralThe Referral tool exposed by this server.
PharmacyThe Pharmacy tool exposed by this server.
InsuranceAll these endpoints require the Authorization: Bearer <token> header. Refer to the interactive API docs at /docs for detailed request/response schemas and try out the endpoints interactively.

How to install the Health Api MCP server

{
  "mcpServers": {
    "health-api": {
      "serverUrl": "http://localhost:5000/mcp",
      "headers": {
        "Authorization": "Bearer 
        <put_your_bearer_token_here>"
      } 
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Python 3.13.3+ - PostgreSQL - UV package manager

Example prompts to try

  • Use Health Api to ReDoc.
  • Use Health Api to Doctors.
  • Use Health Api to Patients.

Frequently asked questions

It connects Health Api to MCP-compatible AI assistants such as Claude and Cursor, exposing 8 tools (ReDoc, Doctors, Patients, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Health Api directly.