Last EHR — Medplum MCP Server

What the code does

We read the source, 6 d ago · rules 995398eba69f

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

        Object.entries(process.env).filter(

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add last-ehr -- npx -y @lastehr/mcp

{
  "mcpServers": {
    "last-ehr": {
      "command": "npx",
      "args": [
        "-y",
        "@lastehr/mcp"
      ]
    }
  }
}

[mcp_servers.last-ehr]
command = "npx"
args = ["-y", "@lastehr/mcp"]

{
  "mcpServers": {
    "last-ehr": {
      "command": "npx",
      "args": [
        "-y",
        "@lastehr/mcp"
      ]
    }
  }
}

{
  "servers": {
    "last-ehr": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@lastehr/mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: MEDPLUM_ACCESS_TOKEN (FHIR chart tools over Medplum or a local HAPI stack: read-only by default, with an opt-in elicitation-gated write profile (human-approved per action)), MEDPLUM_CLIENT_ID (FHIR chart tools over Medplum or a local HAPI stack: read-only by default, with an opt-in elicitation-gated write profile (human-approved per action)), MEDPLUM_CLIENT_SECRET (FHIR chart tools over Medplum or a local HAPI stack: read-only by default, with an opt-in elicitation-gated write profile (human-approved per action)), MEDPLUM_BASE_URL (FHIR chart tools over Medplum or a local HAPI stack: read-only by default, with an opt-in elicitation-gated write profile (human-approved per action)).