// MCP TOOL REFERENCE

MEDPLUM MCP SERVER TOOLS

37 tools from the Medplum MCP Server MCP Server, categorised by risk level.

View the Medplum MCP Server policy →
// ALL 37 MEDPLUM MCP SERVER TOOLS
READ 20 tools
Read generalFhirSearch Performs a generic FHIR search operation on any resource type with custom query parameters. Read getConditionById Retrieves a condition resource by its unique ID. Read getEncounterById Retrieves an encounter by its unique ID. Read getEpisodeOfCareById Retrieves an episode of care by its unique ID. Read getMedicationById Retrieves a medication by its unique ID. Read getMedicationRequestById Retrieves a medication request by its unique ID. Read getObservationById Retrieves an observation by its unique ID. Read getOrganizationById Retrieves an organization by its unique ID. Read getPatientById Retrieves a patient resource by their unique ID. Read getPractitionerById Retrieves a practitioner resource by their unique ID. Read searchConditions Searches for conditions based on patient and other criteria. Requires a patient ID. Read searchEncounters Searches for encounters based on criteria like patient ID or status. Read searchEpisodesOfCare Searches for episodes of care based on criteria like patient ID or status. Read searchMedicationRequests Searches for medication requests based on criteria like patient ID or medication. Read searchMedications Searches for medications based on criteria like code or name. Read searchObservations Searches for observations based on criteria like patient ID or code. Read searchOrganizations Searches for organizations based on criteria like name or address. Provide at least one criterion. Read searchPatients Searches for patients based on criteria like name or birth date. Read searchPractitioners Searches for practitioners based on various criteria like name, specialty, or identifier. Read searchPractitionersByName Searches for medical practitioners based on their given name, family name, or a general name string.
WRITE 17 tools
Write createCondition Creates a new condition or diagnosis for a patient. Requires a patient ID and a condition code. Write createEncounter Creates a new encounter (patient visit). Requires patient ID and status. Write createEpisodeOfCare Creates a new episode of care for a patient. Requires patient ID and status. Write createMedication Creates a new medication resource. Requires medication code or identifier. Write createMedicationRequest Creates a new medication request (prescription). Requires patient ID, medication reference, and prescriber. Write createObservation Creates a new observation (lab result, vital sign, etc.). Requires patient ID and code. Write createOrganization Creates a new organization (e.g., hospital, clinic). Requires organization name. Write createPatient Creates a new patient resource. Requires first name, last name, and birth date. Write createPractitioner Creates a new medical practitioner. Requires given name and family name. Write updateCondition Updates an existing condition. Requires the condition ID and at least one field to update. Write updateEncounter Updates an existing encounter. Requires the encounter ID and the fields to update. Write updateEpisodeOfCare Updates an existing episode of care. Requires the episode ID and fields to update. Write updateMedicationRequest Updates an existing medication request. Requires the medication request ID and fields to update. Write updateObservation Updates an existing observation. Requires the observation ID and the fields to update. Write updateOrganization Updates an existing organization. Requires the organization ID and the fields to update. Write updatePatient Updates an existing patient Write updatePractitioner Updates an existing practitioner

Route Medplum MCP Server through PolicyLayer and every one of its 37 tools is checked against your policy before it runs.

CHECK YOUR STACK →

See every tool, the dangerous ones, and the token cost across your stack.

// FAQ
How many tools does the Medplum MCP Server MCP server have? +

The Medplum MCP Server MCP server exposes 37 tools across 2 categories: Read, Write.

How do I enforce policies on Medplum MCP Server tools? +

Route the Medplum MCP Server server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do Medplum MCP Server tools fall into? +

Medplum MCP Server tools are categorised as Read (20), Write (17). Each category has a recommended default policy.

Enforce policy on every Medplum MCP Server tool call.

Start from Medplum MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.