Read and write patients, facilities, medical documents, and consolidated FHIR records in Metriport. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"metriport": {
"url": "https://metriport.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"metriport": {
"type": "http",
"url": "https://metriport.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
Patient data: Do not use this server with protected health information (PHI). We do not sign HIPAA Business Associate Agreements (BAAs). See Terms, Health data.
The login page asks for your Metriport API key.
Find it in the Metriport dashboard → Developers. Your key is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Metriport API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Metriport connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
metriport_list_facilities | read | List facilities List all Facilities under your Metriport Organization (id, name, npi, address). Medical API: GET /medical/v1/facility. |
metriport_get_facility | read | Get facility Get a single Facility by its Metriport ID. Medical API: GET /medical/v1/facility/{id}. |
metriport_list_patients | read | List patients List Patients — all Patients, or only those at a given Facility if facilityId is supplied. Medical API: GET /medical/v1/patient. |
metriport_get_patient | read | Get patient Get a single Patient by its Metriport ID (demographics + facility IDs). Medical API: GET /medical/v1/patient/{id}. |
metriport_list_documents | read | List documents List the document references currently available for a Patient at Metriport (optionally filtered by date range and content search). Medical API: GET /medical/v1/document. |
metriport_get_document_query_status | read | Get document query status Check the progress/status of a Patient's document query (download + FHIR conversion counts). Medical API: POST /medical/v1/document/query with only patientId (no facilityId) returns current status without starting a new query. |
metriport_get_document_url | read | Get document download URL Get a temporary, downloadable URL for a document by its file name (optionally converting XML/CDA to html or pdf). Medical API: GET /medical/v1/document/download-url. |
metriport_list_consolidated_queries | read | List consolidated queries Get the status of the Patient's consolidated-data (FHIR) queries. Medical API: GET /medical/v1/patient/{id}/consolidated/query. |
metriport_get_medical_record_summary | read | Get medical record summary Get a URL to the Patient's medical record summary rendered as pdf or html. Medical API: GET /medical/v1/patient/{patientId}/medical-record. |
metriport_create_patient | write | Create patient Creates a Patient in Metriport (writes PHI and initiates health-information-exchange queries). Medical API: POST /medical/v1/patient (facilityId is a required query param). |
metriport_start_document_query | write | Start document query Starts a document query — retrieves the patient's medical documents from connected HIE networks. Returns a requestId; results arrive asynchronously. Medical API: POST /medical/v1/document/query (patientId and facilityId are required query params). |
metriport_start_consolidated_query | write | Start consolidated query Starts a consolidated-data (FHIR) query for the patient. Returns a requestId; the bundle is delivered asynchronously (webhook). Medical API: POST /medical/v1/patient/{id}/consolidated/query. |
metriport_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
metriport_request_feature | Request a missing feature Tell usefulapi that the user needs something the Metriport tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
metriport_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Metriport tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
metriport_cancel_subscription | Cancel the Pro subscription Cancel the caller's Metriport Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run metriport_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Pro | $9/mo · $90/yr | Unlimited |
Pro covers this Metriport server only. Subscribe with metriport_upgrade (it returns a Stripe Checkout link). Cancel any time with metriport_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running metriport_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Metriport. The server calls the Metriport API with your own Metriport access, so it sees only the data that your account can see.
No. Do not use this server with protected health information (PHI). We do not sign HIPAA Business Associate Agreements (BAAs). See Terms, Health data.
The login page asks for your Metriport API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Metriport API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Metriport API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Metriport.
Yes, if you approve it. 3 of the 12 Metriport tools can create or change data. The other 9 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Metriport server only. Run metriport_usage_status to see how many calls you used.
Ask the AI to run metriport_upgrade: it returns a Stripe Checkout link. To cancel, run metriport_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with metriport_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.