Particle Health MCP server

Query Particle Health patient records across connected clinical networks. Hosted by usefulapi: connect it to Claude, ChatGPT, Cursor or any MCP client.

Connect Particle HealthFree 50 tool calls / monthPro $9/mo · $90/yr · pricing15 tools

What can I ask?

Turn on the Particle Health connector, then ask in plain words. The AI picks the tools.

How do I connect Particle Health?

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 Particle Health client secret and Particle Health client id.

Particle Health issues the client id and secret to partners. They are used only to mint an access token on your behalf.

Claude claude.ai · Desktop

  1. Open Customize → Connectors, then click + Add → Add custom connector.
  2. Enter the name Particle Health and this URL, then click Add:
    https://particlehealth.usefulapi.io/mcp
  3. Claude opens the login page: enter your Particle Health client secret and Particle Health client id.
  4. In a chat, click + → Connectors and turn on Particle Health.

Team and Enterprise: an Owner adds the connector for the organization first.

ChatGPT chatgpt.com

  1. Open Plugins, click +, then Add custom MCP server.
  2. Enter the name Particle Health and this URL, choose OAuth as the authentication, confirm the warning and create it:
    https://particlehealth.usefulapi.io/mcp
  3. ChatGPT opens the login page: enter your Particle Health client secret and Particle Health client id.
  4. In Plugins, install Particle Health, then choose it in a chat.

No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.

Claude Code

Run this command, then run /mcp in Claude Code to log in:

claude mcp add --transport http particlehealth https://particlehealth.usefulapi.io/mcp

Cursor

Add to Cursor or add this to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "particlehealth": {
      "url": "https://particlehealth.usefulapi.io/mcp"
    }
  }
}

VS Code

Add to VS Code or add this to .vscode/mcp.json:

{
  "servers": {
    "particlehealth": {
      "type": "http",
      "url": "https://particlehealth.usefulapi.io/mcp"
    }
  }
}

Codex

Run these commands. The second one opens the login page:

codex mcp add particlehealth --url https://particlehealth.usefulapi.io/mcp
codex mcp login particlehealth

Other clients

Windsurf, Cline, Zed and other MCP clients: add this URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser.

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: the login page asks for your Particle Health client secret and Particle Health client id. 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.

Pricing

PlanPriceLimit
Free$050 tool calls / month
Pro$9/mo · $90/yr10,000 tool calls / month
Pro+$39/mo · $390/yr100,000 tool calls / month

Each paid plan covers this Particle Health 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].

Tools 15

Show all 15 tools (the AI picks them for you)

Read only · 9

  • Get patient recordparticle_get_patient
    Fetch a single patient record by its Particle patient id.
  • Search for a patientparticle_search_patient
    Search for an existing patient by demographics (non-mutating). Returns an array of matching patient objects (or a 204 message when none match).
  • Get query statusparticle_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.
  • Get FHIR bundleparticle_get_fhir
    Retrieve the patient's complete clinical record as a FHIR searchset Bundle. Supports incremental sync and pagination.
  • Get FHIR resources by typeparticle_get_fhir_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.
  • Get flattened clinical dataparticle_get_flat
    Retrieve the patient's clinical data in Particle's flattened (de-nested) format, easier to read than raw FHIR. Optionally filter to one domain.
  • Get C-CDA document(s)particle_get_ccda
    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.
  • Search network participantsparticle_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).
  • List patient documentsparticle_get_patient_documents
    List the documents uploaded / available for a patient.

Changes data · 2

  • Submit (register) patient (WRITE)particle_submit_patient
    ⚠️ WRITE: register a new patient with Particle Health. Returns the patient with a system-generated particle_patient_id (use it for subsequent queries).
  • Create clinical-record query (WRITE)particle_create_query
    ⚠️ WRITE: initiate a nationwide clinical-record retrieval for a patient. Returns a query_id — poll particle_get_query_status for progress.

Your usefulapi plan · 4

  • Usage status (free-tier meter)particlehealth_usage_status
    Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter.
  • Request a missing featureparticlehealth_request_feature
    Tell usefulapi that the user needs something the Particle Health 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.
  • Upgrade to Pro or Pro+particlehealth_upgrade
    Get a paid plan for Particle Health (the free tier caps monthly usage). Pro: 10,000 tool calls a month, for normal use — plan "monthly" ($9/month) or "yearly" ($90/year, 2 months free). Pro+: 100,000 tool calls a month, for automations and heavy use — plan "plus" ($39/month) or "plus_yearly" ($390/year). Without a plan it returns both Pro and Pro+, each with a payment link, for the user to choose; with a plan, one link. An existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Cancel any time: the plan then runs to the end of the paid period, so it also suits a one-time job. A link opens Stripe Checkout in the browser; after payment the account upgrades automatically. Does not count against the meter.
  • Cancel the Pro subscriptionparticlehealth_cancel_subscription
    Cancel the caller's Particle Health Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run particlehealth_upgrade later to undo the cancel before the period ends. Does not count against the meter.

FAQ

Is this an official Particle Health product?

No. usefulapi is an independent service. It is not affiliated with or endorsed by Particle Health. The server calls the Particle Health API with your own Particle Health access, so it sees only the data that your account can see.

Can I use this server with patient data (PHI)?

No. Do not use this server with protected health information (PHI). We do not sign HIPAA Business Associate Agreements (BAAs). See Terms, Health data.

Can I connect Particle Health to Claude or ChatGPT?

Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.

What do I need to connect?

The login page asks for your Particle Health client secret and Particle Health client id. See Before you connect for where to find them.

Do I put my Particle Health key or an Authorization header in the client config?

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 Particle Health client secret and Particle Health client id. 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.

How do you keep my Particle Health credentials?

The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Particle Health 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 Particle Health.

Can the AI change my Particle Health data?

Yes, if you approve it. 2 of the 11 Particle Health 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.

What does it cost?

The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with 10,000 tool calls / month. Pro+ costs $39/mo or $390/yr, with 100,000 tool calls / month. Each subscription covers this Particle Health server only. Cancel any time: your paid plan then runs to the end of the paid period. Run particlehealth_usage_status to see how many calls you used.

How do I subscribe or cancel?

Ask the 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+. After you confirm, your existing subscription changes in place, keeps its billing interval and charges the price difference for the rest of the period immediately. To cancel, run particlehealth_cancel_subscription. Your paid plan continues to the end of the paid period.

What if a Particle Health tool that I need is missing?

Tell the AI what you wanted to do. It can send the request with particlehealth_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.

Which AI clients can I use?

Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, 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.

Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.

More Healthcare MCP servers

Akute HealthCanvas MedicalClinicalTrials.govClinikoDailyMedDrChronoElation HealthFeegowFitbitHalaxyHealth GorillaHealthieHint HealthInfermedicaIntakeQMetriportNexHealthNookalNPPES NPI RegistryOpen DentalopenFDAOuraPhoton HealthPractice BetterRxNormSemblesploseSpruce HealthVitalWHOOP

All Healthcare servers →