# Healthie MCP connector

The Healthie connector brings your practice's announcements, allergy records, accepted insurance plans, alert templates and appointment pricing into Claude, ChatGPT, Cursor and Microsoft Copilot, with every request running as the person who signed in and logged.

Source: https://elaichi.ai/connectors/healthie/

## Facts

| | |
| --- | --- |
| Application | Healthie |
| Category | CRM |
| AI tools | 787 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Healthie is connected

- Draft an announcement about the new front desk hours
- Which insurance plans do we currently accept?
- Add a penicillin allergy to Maria Lopez's chart

## Connect Healthie in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Healthie.
2. Optionally set Share with, then press Connect.
3. Paste a Healthie API key. One person generates a token in Healthie and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Healthie tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Healthie MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Healthie MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Healthie MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Healthie MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Healthie MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Healthie to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Healthie tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Healthie through Elaichi

### Post a practice-wide announcement in seconds

Front desk. Tell the agent what changed, holiday hours or a new location, and it publishes the announcement in Healthie so every provider sees it the same day.

### Record a new allergy after intake

Clinical. After a visit, say which allergy or sensitivity the client reported and the agent adds it to their Healthie chart, so the next provider sees it before prescribing.

### Keep accepted insurance plans current

Billing. When your practice starts or stops taking a payer, ask the agent to add or remove the plan in Healthie, so the front desk quotes the right answer to every caller.

### Add an addendum to a signed note

Clinical. Forgot a detail after signing? Dictate the correction and the agent attaches it to the Healthie record as an addendum, leaving the original note untouched.

### Tune alert templates without opening settings

Operations. Ask the agent to list your Healthie alert templates, reword the one that confuses staff, and retire the one nobody uses, all from one conversation.

### Check appointment pricing before quoting a client

Practice admin. Ask what a given appointment type costs and the agent pulls the advance price from Healthie, so nobody quotes a figure from an outdated spreadsheet.

## Elaichi vs Zapier MCP vs Composio for Healthie

All three can connect Healthie to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Healthie tools | Allow or restrict single Healthie tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Healthie call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Healthie to Claude?

Open Elaichi, choose Healthie, and paste the API key from your Healthie account settings. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in as yourself and Healthie is ready to use.

### Does Healthie work with ChatGPT and Cursor as well as Claude?

Yes. Once Healthie is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Healthie once and every client picks it up.

### What can an AI agent actually do with my Healthie data?

With Healthie connected, an agent can publish and update practice announcements, add allergies and sensitivities to a client's chart, attach an addendum to a signed note, manage your accepted insurance plans and alert templates, and look up appointment prices. Short, concrete asks work best, such as adding one allergy or posting one announcement at a time.

### Does connecting Healthie give the AI access to every client chart?

No. Every request to Healthie runs as the person who signed in, so an agent sees only the charts, announcements and settings that person already has in Healthie. Elaichi can narrow that further with roles and restrictions, and it can never widen it beyond what Healthie itself allows.

### Can my team share one Healthie connection?

Yes. One practice admin connects Healthie with the API key and shares the connection with a team in Elaichi, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every Healthie action.

### Can I stop an agent from deleting or changing things in Healthie?

Yes. Restrictions in Elaichi apply per action, so you can allow reading Healthie announcements while restricting deletion of insurance plans or alert templates, for a role or for one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Healthie connection when someone leaves the practice?

Offboarding that person in Elaichi ends their Healthie access at once, across Claude, ChatGPT, Cursor and every other client. A shared Healthie connection keeps working for everyone else on the team. If you disconnect Healthie once in Elaichi, it is removed from every client at the same time.

### Does the Healthie MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Healthie is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Healthie?

Yes. Both let Claude, ChatGPT or Cursor use Healthie. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Healthie call.

### How is Elaichi different from Composio for Healthie?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Healthie: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 787 Healthie tools

Every tool below is callable through https://api.elaichi.ai/mcp once Healthie is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a Healthie accepted insurance plan** (Create). Create Accepted Insurance Plans. GraphQL mutation createAcceptedInsurancePlan.
- **Delete a Healthie accepted insurance plan by ID** (Delete). Destroy Accepted Insurance Plan. GraphQL mutation deleteAcceptedInsurancePlan. Required: id.
- **Create a Healthie addendum** (Create). Create a new addendum for the selected charting note. GraphQL mutation createAddendum.
- **List all Healthie advance appointment prices** (List). Fetch advance appointment prices. GraphQL query advanceAppointmentPrices.
- **Create a Healthie alert template** (Create). Creates a new AlertTemplate for the current organization. GraphQL mutation createAlertTemplate. Required: description, content.
- **Delete a Healthie alert template by ID** (Delete). Soft-deletes an AlertTemplate. GraphQL mutation deleteAlertTemplate. Required: id.
- **List all Healthie alert templates** (List). Paginated list of Alert Templates for the current organization. GraphQL query alertTemplates. The connector pages through all results (first / after; limit sets first, default 100).
- **Update a Healthie alert template by ID** (Update). Updates an existing AlertTemplate. GraphQL mutation updateAlertTemplate. Required: id.
- **Healthie all announcements archive** (Archive). Dismiss All Announcements For A User. GraphQL mutation dismissAllAnnouncements.
- **Create a Healthie allergy sensitivity** (Create). Create AllergySensitivity. GraphQL mutation createAllergySensitivity.
- **Delete a Healthie allergy sensitivity by ID** (Delete). Destroy AllergySensitivity. GraphQL mutation deleteAllergySensitivity. Required: id.
- **Update a Healthie allergy sensitivity by ID** (Update). Update AllergySensitivity. GraphQL mutation updateAllergySensitivity. Required: id.
- **List all Healthie allergy suggestions** (List). Search results for allergies, allergens, and reactions. GraphQL query allergySuggestions.
- **Healthie announcements archive** (Archive). Dismiss Announcement. GraphQL mutation dismissAnnouncement.
- **Create a Healthie announcement** (Create). Create Announcement. GraphQL mutation createAnnouncement.
- **Delete a Healthie announcement by ID** (Delete). Destroy Announcement. GraphQL mutation deleteAnnouncement. Required: id.
- **Get single Healthie announcement by ID** (Get). Fetch an announcement. GraphQL query announcement. Required: id.
- **List all Healthie announcements** (List). Fetch an array of announcements for a provider. GraphQL query announcements. The connector pages through all results (after the last record's cursor; limit sets page_size).
- **Healthie announcements lookup count** (Action). Number of announcements for a provider. GraphQL query announcementsCount.
- **Update a Healthie announcement by ID** (Update). Update Announcement. GraphQL mutation updateAnnouncement. Required: id.
- **Healthie answers as documents send** (Send). Add form answer group answers as document viewable by client. GraphQL mutation shareAnswersAsDocument.
- **Create a Healthie API key** (Create). create API Key. This capability needs to be turned on for your account first. GraphQL mutation createApiKey.
- **Delete a Healthie API key by ID** (Delete). Destroy API Key. GraphQL mutation deleteApiKey. Required: id.
- **List all Healthie API keys** (List). Fetch paginated API Keys collection. GraphQL query apiKeys. The connector pages through all results (after the last record's cursor; limit sets page_size).
- **Healthie API keys lookup count** (Action). Number of API Keys. GraphQL query apiKeysCount.
- **Create a Healthie apple health** (Create). Create AppleHealth. GraphQL mutation createAppleHealth.
- **Delete a Healthie apple health by ID** (Delete). Destroy AppleHealth. GraphQL mutation deleteAppleHealth. Required: id.
- **Update a Healthie apple health by ID** (Update). Update AppleHealth. GraphQL mutation updateAppleHealth.
- **Delete a Healthie applied tag by ID** (Delete). Remove applied tag on a specific user. GraphQL mutation removeAppliedTag. Required: id.
- **Get single Healthie applied tag by ID** (Get). An applied tag to a user. GraphQL query appliedTag. Required: id.
- **List all Healthie applied tags** (List). Applied tags to a users. GraphQL query appliedTags.
- **Healthie applies bulk apply** (Action). Apply selected tags on a specific user. GraphQL mutation bulkApply.
- **List all Healthie appointment booking warnings** (List). Return potential booking issues for an appointment, date, time, repeats, attendees, and provider. GraphQL query appointmentBookingWarnings.
- **Create a Healthie appointment form answer group connection** (Create). Create a connection between a form answer group and an appointment. GraphQL mutation createAppointmentFormAnswerGroupConnection. Not selected (each costs hundreds of points of Healthie's 2000-point complexity cap): zoom_appointment, zoom_cloud_recording_files, zoom_cloud_recording_urls, zoom_dial_in_info, zoom_dial_in_info_html, zoom_dial_in_numbers_json.
- **Delete a Healthie appointment form answer group connection by ID** (Delete). Remove a form_answer_groups connection to an appointment. GraphQL mutation deleteAppointmentFormAnswerGroupConnection.
- **Update a Healthie appointment form answer group connection by ID** (Update). Update the appointment linked to a form answer group. GraphQL mutation updateAppointmentFormAnswerGroupConnection. Required: form_answer_group_id, appointment_id. Not selected (each costs hundreds of points of Healthie's 2000-point complexity cap): zoom_appointment, zoom_cloud_recording_files, zoom_cloud_recording_urls, zoom_dial_in_info, zoom_dial_in_info_html, zoom_dial_in_numbers_json.
- **List all Healthie appointment frequency data** (List). Returns metadata about appointments for provider dashboard. GraphQL query appointmentFrequencyData.
- **Get single Healthie appointment inclusion by ID** (Get). Fetch an appointment inclusion by ID; group appointments are considered public. GraphQL query appointmentInclusion. Required: id.
- **Update a Healthie appointment inclusion by ID** (Update). Update AppointmentInclusion. GraphQL mutation updateAppointmentInclusion. Required: id.
- **Get single Healthie appointment location by ID** (Get). Fetch an appointment location by ID (considered public). GraphQL query appointmentLocation. Required: id.
- **List all Healthie appointment locations** (List). get appointment locations that the current user can use. (considered public). GraphQL query appointmentLocations.
- **List all Healthie appointment number per day of months** (List). Returns a JSON object of the number of appointments in each day of the month. The month is the month that the passed day is in. GraphQL query appointmentNumberPerDayOfMonth. Returns one value, not a list.
- **Update appointment realtime transcription status by ID** (Update). Start, stop, pause, or resume realtime transcription for a Zoom appointment. GraphQL mutation updateAppointmentRealtimeTranscriptionStatus. Required: id, action. Not selected (each costs hundreds of points of Healthie's 2000-point complexity cap): zoom_appointment, zoom_cloud_recording_files, zoom_cloud_recording_urls, zoom_dial_in_info, zoom_dial_in_info_html, zoom_dial_in_numbers_json.
- **Create a Healthie appointment request** (Create). Create a new appointment request as a part of the booking flow. GraphQL mutation createAppointmentRequest. Required: timezone, reason.
- **Delete a Healthie appointment request by ID** (Delete). Delete an existing appointment request. GraphQL mutation deleteAppointmentRequest. Required: id.
- **Get single Healthie appointment request by ID** (Get). Fetch a single appointment requests for a provider or organization. GraphQL query appointmentRequest. Required: id.
- **List all Healthie appointment requests** (List). Fetch a collection of appointment requests for a provider or organization. GraphQL query appointmentRequests. The connector pages through all results (first / after; limit sets first, default 50).
- **Update a Healthie appointment request by ID** (Update). Update an existing appointment request. GraphQL mutation updateAppointmentRequest. Required: id.
- **Create a Healthie appointment setting** (Create). create an Appointment Setting. GraphQL mutation createAppointmentSetting.
- **Get single Healthie appointment setting by ID** (Get). Fetch an appointment setting by ID (considered public). GraphQL query appointmentSetting. Required: id.
- ...and 737 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
