MCP server · 1upHealth

1uphealth-fhir

View descriptor → 1upHealth provider profile

One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.

⚠ Proposed MCP surface. No official hosted MCP server was found for 1upHealth. The tools below are a candidate set derived from this provider's API, and the link points at the source descriptor rather than a live server. If 1upHealth publishes an official server, this page will update to it on the next build.

Provider: 1upHealth Type: Candidate descriptor Transport: http Host: raw.githubusercontent.com

Descriptor

https://raw.githubusercontent.com/api-evangelist/1uphealth/refs/heads/main/mcp/1uphealth-mcp.yml

Candidate descriptor · transport http

Tools

search_fhir_resources — Search any supported FHIR resource type with FHIR search parameters.
read_fhir_resource — Read a single FHIR resource by type and id.
vread_fhir_resource — Read a specific historical version of a resource.
create_fhir_resource — Create a FHIR resource (optionally conditional via If-None-Exist).
update_fhir_resource — Update a FHIR resource with optimistic concurrency (If-Match / ETag).
patient_everything — Retrieve all data in a patient's compartment.
bulk_export — Kick off a Bulk Data (Flat FHIR) NDJSON export for a Group or the system.
validate_fhir_resource — Validate a resource against its profile via $validate.

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.