metriport
Server Details
Read and write patients, facilities, medical documents, and consolidated FHIR records in Metriport.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
12 toolsmetriport_create_patientCreate patientDestructiveInspect
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).
| Name | Required | Description | Default |
|---|---|---|---|
| dob | Yes | Date of birth, yyyy-mm-dd. | |
| address | Yes | One or more addresses for the Patient. | |
| contact | No | Optional contact info (phone / email). | |
| lastName | Yes | The Patient's last name(s). | |
| firstName | Yes | The Patient's first name(s). | |
| facilityId | Yes | REQUIRED. The Facility ID where the Patient receives care. | |
| middleName | No | The Patient's middle name(s). | |
| genderAtBirth | Yes | Gender at birth: M, F, O (other), or U (unknown). | |
| personalIdentifiers | No | Optional personal IDs (driver's license / SSN). |
metriport_get_document_query_statusGet document query statusRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| patientId | Yes | The Patient ID whose document-query status to check. |
metriport_get_document_urlGet document download URLRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| fileName | Yes | The file name of the document (from metriport_list_documents). | |
| conversionType | No | Optional doc type to convert to, e.g. pdf, html, xml (for XML/CDA files). |
metriport_get_facilityGet facilityRead-onlyInspect
Get a single Facility by its Metriport ID. Medical API: GET /medical/v1/facility/{id}.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The Metriport Facility ID. |
metriport_get_medical_record_summaryGet medical record summaryRead-onlyInspect
Get a URL to the Patient's medical record summary rendered as pdf or html. Medical API: GET /medical/v1/patient/{patientId}/medical-record.
| Name | Required | Description | Default |
|---|---|---|---|
| patientId | Yes | The Metriport Patient ID. | |
| conversionType | Yes | The format to render: pdf or html. |
metriport_get_patientGet patientRead-onlyInspect
Get a single Patient by its Metriport ID (demographics + facility IDs). Medical API: GET /medical/v1/patient/{id}.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The Metriport Patient ID. |
metriport_list_consolidated_queriesList consolidated queriesRead-onlyInspect
Get the status of the Patient's consolidated-data (FHIR) queries. Medical API: GET /medical/v1/patient/{id}/consolidated/query.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The Metriport Patient ID. |
metriport_list_documentsList documentsRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| dateTo | No | Inclusive end date yyyy-mm-dd. | |
| content | No | Text to search within the document reference and contents (min 3 chars). | |
| dateFrom | No | Inclusive start date yyyy-mm-dd. | |
| patientId | Yes | The Patient ID whose available documents to list. |
metriport_list_facilitiesList facilitiesRead-onlyInspect
List all Facilities under your Metriport Organization (id, name, npi, address). Medical API: GET /medical/v1/facility.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
metriport_list_patientsList patientsRead-onlyInspect
List Patients — all Patients, or only those at a given Facility if facilityId is supplied. Medical API: GET /medical/v1/patient.
| Name | Required | Description | Default |
|---|---|---|---|
| facilityId | No | Optional Facility ID to filter by. Omit to list all patients. |
metriport_start_consolidated_queryStart consolidated queryDestructiveInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The Metriport Patient ID. | |
| dateTo | No | Inclusive end date yyyy-mm-dd. | |
| dateFrom | No | Inclusive start date yyyy-mm-dd. | |
| metadata | No | Optional custom string key-value pairs returned in the webhook. | |
| resources | No | Comma-separated, case-sensitive list of FHIR resource types. Omit for all. | |
| conversionType | No | Output format: json, pdf, or html. |
metriport_start_document_queryStart document queryDestructiveInspect
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).
| Name | Required | Description | Default |
|---|---|---|---|
| metadata | No | Optional custom string key-value pairs returned in the webhook. | |
| patientId | Yes | REQUIRED. The Patient ID to query documents for. | |
| facilityId | Yes | REQUIRED. The Facility ID where the patient receives care. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!