Skip to main content
Glama
deenesjakoruzh
TerminallyLazy

featherless

by TerminallyLazy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

featherless

TypeScript SHARP-on-MCP-konformer FHIR R4 MCP-Server mit MCP-UI klinischen Dashboards. Läuft auf Cloudflare Workers.

Schwesterprojekt zu sharp-fhir-mcp (Python, FastMCP 2.x). Gleiche SHARP-Semantik, gleicher Tool-Satz, gleiche MCP-UI Chart.js-Visualisierungen — neu implementiert in TypeScript für die Edge.

Was ist enthalten

Kern

  • SHARP HTTP-Transport via Cloudflare agents SDK (McpAgent, Durable Object-basierte Sitzungen)

  • Header-basierter Kontext (X-FHIR-Server-URL, X-FHIR-Access-Token, X-Patient-ID) mit Fallback auf SMART JWT-Claims

  • Strenge und permissive Kontextmodi

  • experimental.fhir_context_required Capability, die in initialize injiziert wird

Tools (Parität mit sharp-fhir-mcp)

  • tools/fhir.ts — generische FHIR R4 Suche/Lesen

  • tools/clinical.ts — Patient / Encounter / Appointment / Allergy / Medication / Problem

  • tools/lab-imaging.ts — Observation / DiagnosticReport / DocumentReference

  • tools/clinical-context.ts — aggregierter Besuchskontext mit abgeleiteten Warnungen

  • tools/memory.ts — klinischer Speicher, unterstützt durch Cloudflare Vectorize + Workers AI + D1

  • tools/visualization.ts — MCP-UI Chart.js Dashboards (visualize_lab_trend, visualize_vitals, visualize_patient_dashboard)

Related MCP server: sharp-on-fhir-mcp

Erste Schritte

pnpm install
# create the Vectorize index (once)
pnpm wrangler vectorize create featherless-memory --dimensions=768 --metric=cosine
# create the D1 database (once), put the id into wrangler.jsonc
pnpm wrangler d1 create featherless-memory-meta
pnpm db:migrate:remote
# develop
pnpm dev

SHARP-Kontext

Leiten Sie diese Header bei jedem tools/call weiter:

Header

Zweck

X-FHIR-Server-URL

FHIR R4 Basis-URL

X-FHIR-Access-Token

OAuth2/SMART Zugriffstoken (Bearer optional)

X-Patient-ID

Optional; Fallback auf JWT patient Claim

Lizenz

MIT.

This server cannot be deployed

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • FHIR MCP Server

    sumithasb
    A
    license
    Not graded
    quality
    Not graded
    maintenance
    Enables seamless integration with FHIR APIs for healthcare applications, allowing users to search, retrieve, create, update, and analyze clinical information through natural language interactions. Supports SMART-on-FHIR authentication and works with various healthcare systems like EPIC and HAPI FHIR servers.
    Apache 2.0

  • sharp-on-fhir-mcp

    TerminallyLazy
    A
    license
    Not graded
    quality
    C
    maintenance
    A clean-room SHARP-on-MCP compliant FHIR R4 MCP server that enables AI agents to interact with any FHIR R4 endpoint using SHARP context headers, without server-side OAuth. It provides clinical tools, lab results, imaging, and interactive MCP-UI dashboards.
    MIT

  • FHIR MCP Server

    baala-saravanan
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI applications to query and retrieve healthcare data (patients, conditions, observations, medications) from a public FHIR R4 server via MCP tools.
    MIT