WellSky MCP Server
The WellSky MCP server lets AI agents read and write patient, scheduling, care-plan, and authorization data in WellSky. Connect WellSky to Claude, ChatGPT, and Cursor. Built and maintained by Supergood, since WellSky doesn't ship an MCP server.
What is the WellSky MCP server?
The WellSky MCP server is a connector that lets AI agents (Claude, ChatGPT, Cursor, and other MCP clients) read and write patient, scheduling, care-plan, and authorization data in WellSky through a standard protocol.
In short: WellSky builds enterprise EHR and care-management software for post-acute and community-based care: home health and hospice (formerly Kinnser), personal care and EVV, rehabilitation, behavioral health, HME/DME, and social care coordination.
WellSky doesn't ship an official MCP server, and WellSky's FHIR coverage varies by module and configuration, many interfaces are read-first, and write access or API connectivity can require specific roles, entitlements, or paid options. Supergood builds and maintains the connector by reverse-engineering WellSky's authenticated web and batch flows and exposing them as MCP tools an agent can call directly, plus a normalized REST API underneath.
What you can do with WellSky via MCP
Once connected, an agent can:
- Look up patients and clients (demographics, identifiers, coverage).
- Pull practitioner rosters (NPI, roles, specialties).
- Retrieve and create appointments and schedules.
- Get encounters and visit notes (diagnoses, procedures, documentation).
- Pull care plans (goals, activities, outcomes).
- Retrieve referrals and transitions of care, and payer coverage and authorizations.
- Export visit data and billing artifacts for claims and remittances.
How to connect WellSky to Claude, ChatGPT & Cursor
Connecting works like any other MCP server. The short version:
- Claude (Desktop or claude.ai): add the WellSky MCP server under Settings → Connectors (or your MCP config), authorize the WellSky account Supergood provisions, and the tools show up in any chat, including agent runs.
- ChatGPT: add it as a connector under Settings → Connectors, authorize, and ChatGPT can call the WellSky tools in conversations and in agent mode.
- Cursor: add the server to your MCP config (mcp.json or Settings → MCP), reload, and the tools are available to the agent.
Supergood owns the auth piece (credentials, MFA, session refresh), so the connection doesn't drop. New to MCP? Our explainer covers what an MCP server is and how clients connect to one.
How Supergood builds the WellSky MCP server
Supergood doesn't wait for WellSky to ship an API. We reverse-engineer the authenticated web and batch flows behind WellSky, normalize the responses, and wrap them as MCP tools, plus the underlying REST API if you'd rather call it from code.
- Auth and MFA, handled. Supergood provisions a dedicated WellSky account (email and phone managed by us) and keeps the session alive through MFA, token expiry, and re-auth.
- Normalized data. Responses come back in consistent JSON shapes across modules, not the raw shape WellSky's front-end happens to return.
- Monitored and adapted. When WellSky changes its web and batch UI or internal API, monitoring catches it and the connector gets patched, usually before it reaches you.
- Past read-first limits. Where WellSky exposes only read access or partial FHIR, Supergood works the authenticated web flows and batch feeds so writes (appointments, care plans) are on the table where your role permits.
Getting Started
- Schedule Integration Assessment
Book a 30-minute call to confirm which WellSky modules and workflows you need and how authentication should work.
- Supergood Builds and Validates Your MCP Server
We deliver a hardened WellSky connector (MCP tools plus the underlying API) scoped to your workflows and entitlements.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as WellSky changes.
Use Cases
Intake and scheduling
- Pull the referral and create the patient record - Build the visit schedule against the authorization - Surface coverage gaps before the first visit
Care management
- Pull the care plan and what's due - Surface recent encounters and notes - Flag authorizations running low on units
Roster and operations
- Keep practitioner rosters in sync with another system - Surface schedule conflicts and unstaffed visits - Pull encounter exports for reporting
Billing support
- Export visit data for claim generation - Reconcile authorizations against billed units - Pull remittance artifacts for posting
Technical Specifications
MCP transport
Remote MCP server over HTTPS; works with hosted MCP clients and with local MCP configs.
Authentication
Supergood provisions a dedicated WellSky account (managed email and phone) and handles MFA; you can also bring your own credentials. Session refresh is automatic.
Supported clients
Claude (Desktop, claude.ai, Claude Code), ChatGPT connectors, Cursor, and other MCP-compatible clients.
Tools exposed
8 tools covering the workflows listed above; the set is scoped to the modules you license.
Data freshness
Near real-time for scheduling and clinical reads; HL7/SFTP feeds and nightly exports are orchestrated by Supergood with retry.
Rate limits
Tuned to WellSky's tolerances; Supergood paces requests to avoid tripping security throttles.
Latency
Sub-second for most reads under normal load; writes reflect the underlying platform timing.
Session management
Automatic re-auth plus cookie/token rotation, with health checks.
Security
Encrypted transport, scoped access, and audit logging; respects WellSky role-based permissions.
Webhooks
Optional asynchronous delivery for long-running operations; polling otherwise.
Reliability
Retry logic, backoff, and idempotency keys to avoid duplicates.
Adaptation
Continuous monitoring for WellSky web and batch surfaces changes, with rapid connector updates.
Frequently asked questions
No. WellSky doesn't publish an MCP server. Supergood builds and maintains one by reverse-engineering WellSky's authenticated flows and exposing them as MCP tools, plus the underlying REST API.
All of them, plus any MCP-compatible client. The same connector shows up in Claude (Desktop, claude.ai, Claude Code), ChatGPT connectors, and Cursor.
Supergood provisions a dedicated WellSky account with managed MFA, or uses credentials you supply. We keep the session alive through MFA prompts, token expiry, and re-auth, so the connection stays live.
Yes. Reads and writes hit WellSky's live system, not a nightly export. WellSky's FHIR coverage varies by module and configuration, many interfaces are read-first, and write access or API connectivity can require specific roles, entitlements, or paid options.
Both. The MCP tools are a layer on top of a normalized REST API for WellSky; you can call either, from an agent or from your own code.