Particle Health MCP by usefulapi

io.usefulapiPublished by usefulapi.ioOfficial publisherv1.39.2Updated Nov 14, 2026

Query Particle Health patient records across connected clinical networks.

The publisher's own server: Ably MCP by usefulapi

VerifiedStreamable HTTPWeb executableLocation & LifestyleData & Analytics

Overview

AI-generated overview

Hosted MCP server that lets an assistant look up Particle Health patient records and clinical data across connected health-data networks.

What you can do
  • Find and read patient records: search by demographics, fetch a patient by id, list uploaded documents
  • Retrieve clinical data: full FHIR bundles, single FHIR resource types, flattened records, C-CDA documents
  • Track record retrievals: check query status or the latest completed query
  • Explore the network: list health-data network participants, optionally filtered by state or zipcode
  • Register patients and start nationwide record retrievals (write operations)
  • Check usage, request features, and upgrade or cancel the paid plan
When to use it
Useful when you already work with Particle Health and want an assistant to pull patient demographics, conditions, medications, observations or documents, or to start and monitor clinical-record retrievals without writing API calls yourself.
Requirements
Remote streamable HTTP endpoint; no local install. Connect with the URL only and sign in through OAuth using your Particle Health credentials, which are validated and stored per user. A free plan allows 50 tool calls per month; paid plans raise the limit.
Before you install
Handles protected health information, so check your HIPAA and consent obligations before use. Two tools write data: registering a patient and initiating a nationwide record retrieval, which may incur costs with Particle Health. Paid plans are billed through Stripe Checkout, and upgrading from Pro to Pro+ charges the price difference immediately; cancellation has no refund for the current period.

Installation

In SourceWeft

  1. Open Particle Health MCP by usefulapi in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.usefulapi%2Fparticlehealth/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "particle-health-by-usefulapi": {
      "type": "http",
      "url": "https://particlehealth.usefulapi.io/mcp"
    }
  }
}

README

Particle Health MCP by usefulapi

Query Particle Health patient records across connected clinical networks. Hosted, no local install.

Live endpoint: https://particlehealth.usefulapi.io/mcp · Homepage: https://usefulapi.io

Connect

  • Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste https://particlehealth.usefulapi.io/mcp.
  • Claude Code: claude mcp add --transport http particlehealth https://particlehealth.usefulapi.io/mcp, then run /mcp to log in.
  • VS Code: Add to VS Code.
  • Cursor and other clients: add the URL as a remote MCP server:
json
{  "mcpServers": {    "particlehealth": {      "url": "https://particlehealth.usefulapi.io/mcp"    }  }}

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, and the login page asks for your Particle Health credentials.

Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/particlehealth/

On first connect you'll paste your Particle Health credentials. They are validated, stored per-user, and scoped to you — no keys in config files.

Tools

ToolTypeWhat it does
particle_get_patientreadGet patient record
particle_search_patientreadSearch for a patient
particle_get_query_statusreadGet query status
particle_get_fhirreadGet FHIR bundle
particle_get_fhir_by_typereadGet FHIR resources by type
particle_get_flatreadGet flattened clinical data
particle_get_ccdareadGet C-CDA document(s)
particle_search_network_participantsreadSearch network participants
particle_get_patient_documentsreadList patient documents
particle_submit_patientwriteSubmit (register) patient (WRITE)
particle_create_querywriteCreate clinical-record query (WRITE)
particlehealth_usage_statusmetaUsage status (free-tier meter)
particlehealth_request_featuremetaRequest a missing feature
particlehealth_upgrademetaUpgrade to Pro or Pro+
particlehealth_cancel_subscriptionmetaCancel the Pro subscription

read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.

Pricing

PlanPriceLimit
Free$050 tool calls / month
Pro$9/mo or $90/yr (2 months free)10,000 tool calls / month
Pro+$39/mo or $390/yr (2 months free)100,000 tool calls / month

Each paid plan covers this server only. Ask your AI to run particlehealth_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with particlehealth_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with particlehealth_upgrade before then undoes the cancel. Or write to [email protected].

License

MIT

Source: servers/particlehealth/README.md at commit f22f848

Tools

11

particle_get_patient

Get patient record

Fetch a single patient record by its Particle patient id. Endpoint: GET /api/v2/patients/{particle_patient_id}.

Parametersparticle_patient_idrequired

particle_search_patient

Search for a patient

Search for an existing patient by demographics (non-mutating). Returns an array of matching patient objects (or a 204 message when none match). Endpoint: POST /api/v2/patients/search.

Parametersssnemailgenderrequiredconsenttelephonegiven_namerequiredpatient_idrequiredfamily_namerequiredpostal_coderequiredaddress_cityrequiredaddress_linesaddress_staterequired+1 more

particle_get_query_status

Get query status

Get the status of a clinical-record retrieval query (state, timing, demographics, files). Omit query_id to get the latest COMPLETE query. Endpoint: GET /api/v2/patients/{particle_patient_id}/query.

Parametersquery_idparticle_patient_idrequired

particle_get_fhir

Get FHIR bundle

Retrieve the patient's complete clinical record as a FHIR searchset Bundle. Supports incremental sync and pagination. Endpoint: GET /api/v2/patients/{particle_patient_id}/fhir.

Parameters_count_since_page_tokenparticle_patient_idrequired

particle_get_fhir_by_type

Get FHIR resources by type

Retrieve only one FHIR resource type for a patient (e.g. Condition, MedicationRequest, Observation) as a Bundle. Supports the same pagination as particle_get_fhir. Endpoint: GET /api/v2/patients/{particle_patient_id}/fhir/{type}.

Parameters_count_since_page_tokenresource_typerequiredparticle_patient_idrequired

particle_get_flat

Get flattened clinical data

Retrieve the patient's clinical data in Particle's flattened (de-nested) format, easier to read than raw FHIR. Optionally filter to one domain. Endpoint: GET /api/v2/patients/{particle_patient_id}/flat.

Parameters_sincedomainparticle_patient_idrequired

particle_get_ccda

Get C-CDA document(s)

Retrieve the patient's C-CDA clinical document(s). May be large and returned as XML/text — parsed if JSON, otherwise passed through as-is. Endpoint: GET /api/v2/patients/{particle_patient_id}/ccda.

Parametersparticle_patient_idrequired

particle_search_network_participants

Search network participants

List the health-data network participants (organizations Particle can query). Optionally filter by state or zipcode, and page with continuation_token. Endpoint: GET /api/v1/networkparticipants (with /state/{state} and /zipcode/{zip} variants).

Parametersstatezipcodecontinuation_token

particle_get_patient_documents

List patient documents

List the documents uploaded / available for a patient. Endpoint: GET /api/v1/documents/{patient_id}.

Parameterspatient_idrequired

particle_submit_patient

Submit (register) patient (WRITE)

⚠️ WRITE: register a new patient with Particle Health. Returns the patient with a system-generated particle_patient_id (use it for subsequent queries). Endpoint: POST /api/v2/patients.

Parametersssnemailgenderrequiredconsenttelephonegiven_namerequiredpatient_idrequiredfamily_namerequiredpostal_coderequiredaddress_cityrequiredaddress_linesaddress_staterequired+1 more

particle_create_query

Create clinical-record query (WRITE)

⚠️ WRITE: initiate a nationwide clinical-record retrieval for a patient. Returns a query_id — poll particle_get_query_status for progress. Endpoint: POST /api/v2/patients/{particle_patient_id}/query.

Parametershintsspecialtiespurpose_of_userequiredparticle_patient_idrequired

Version history

26
  1. v1.39.2LatestNov 14, 2026
  2. v1.39.1Nov 13, 2026
  3. v1.38.0Nov 12, 2026
  4. v1.37.3Nov 11, 2026
  5. v1.36.5Nov 8, 2026
  6. v1.36.4Nov 7, 2026
  7. v1.35.3Nov 5, 2026
  8. v1.35.2Nov 5, 2026
  9. v1.35.1Nov 4, 2026
  10. v1.35.0Nov 3, 2026
  11. v1.34.1Nov 3, 2026
  12. v1.33.0Nov 1, 2026
  13. v1.31.0Oct 31, 2026
  14. v1.30.0Oct 31, 2026
  15. v1.29.2Oct 30, 2026
  16. v1.29.0Oct 30, 2026
  17. v1.24.0Oct 26, 2026
  18. v1.21.3Oct 25, 2026
  19. v1.21.0Oct 25, 2026
  20. v1.20.0Oct 24, 2026
  21. v1.17.0Oct 23, 2026
  22. v1.16.4Oct 22, 2026
  23. v1.16.3Oct 21, 2026
  24. v1.11.1Oct 9, 2026
  25. v1.10.0Oct 9, 2026
  26. v1.0.0Sep 29, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Usefulapi integrations

Ably MCP by usefulapi

io.usefulapiOfficial publisher

Hosted MCP server for Ably that lets an assistant inspect realtime channels, presence and usage stats, publish messages, and review app configuration.

Streamable HTTPWeb executable
Communication & Collaboration15 toolsNov 14, 2026

ROLLER MCP by usefulapi

io.usefulapiOfficial publisher

Read-only access to ROLLER venue data: search bookings, check product availability, and look up guests, waivers, gift cards and daily reports.

Streamable HTTPWeb executable
Data & Analytics42 toolsNov 14, 2026

Planerio MCP by usefulapi

io.usefulapiOfficial publisher

Hosted Planerio connector that lets an assistant read shifts, staffing requirements, staff, employees, absences and vacation days.

Streamable HTTPWeb executable
Productivity & Workflow6 toolsNov 14, 2026

Marmin MCP by usefulapi

io.usefulapiOfficial publisher

Read-only access to Marmin UAE e-invoicing data: invoices, credit notes, UBL XML, Peppol status and business profiles.

Streamable HTTPWeb executable
Finance10 toolsNov 14, 2026

Oyster MCP by usefulapi

io.usefulapiOfficial publisher

Remote MCP server for Oyster that lets an assistant read team, time off, expense, contract and invoice data and approve or decline requests.

Streamable HTTPWeb executable
Productivity & Workflow20 toolsNov 14, 2026