Medplum MCP Server
Official hosted Medplum MCP server. Exposes the Medplum FHIR API to AI clients through a single general-purpose FHIR request tool plus two client-compatibility shims, authenticated with OAuth 2.0 against the user's own Medplum login, so the agent inherits that user's existing FHIR permissions rather than a separate service credential.
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.
Documentation
Documentation link · transport streamable-http
Tools
fhir-request— Low-level tool that performs a direct FHIR API request against the server's FHIR R4 base URL. Full CRUD — create, read, update, delete. Medplum annotates the tool as data-modifying. This is the tool behind nearly every interaction.search— Lightweight standard tool that some MCP clients (Medplum names ChatGPT) expect every server to implement in order to connect. Exists for client compatibility; Medplum states the real work is done through fhir-request, which performs searches directly against the FHIR API.fetch— Second client-compatibility shim, documented jointly with `search` and for the same reason — connection requirements of clients that assume a search/fetch pair on every MCP server.
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.