← Back to all docs

Netsmart MCP Server

The Netsmart MCP server lets AI agents run EVV, authorization, scheduling, claims, and remittance workflows through Netsmart. Connect Netsmart to Claude, ChatGPT, and Cursor. Built and maintained by Supergood, since Netsmart doesn't ship an MCP server.

By Alex KlarfeldMay 12, 2026
Netsmart API

What is the Netsmart MCP server?

The Netsmart MCP server is a connector that lets AI agents (Claude, ChatGPT, Cursor, and other MCP clients) run EVV, authorization, scheduling, claims, and remittance workflows through Netsmart using a standard protocol.

In short: Netsmart builds healthcare IT for behavioral health, home care, hospice, and social services, with Electronic Visit Verification delivered through Tellus to meet 21st Century Cures Act requirements: scheduling and visit management, member and caregiver rosters, payer authorizations, exception handling, and Medicaid/MCO billing support.

Netsmart doesn't ship an official MCP server, and Netsmart's EVV and exception handling (delivered via Tellus) lives in web apps and batch exports, with state- and payer-specific service codes and validation logic rather than a unified public API. Supergood builds and maintains the connector by reverse-engineering Netsmart's authenticated web and EVV flows and exposing them as MCP tools an agent can call directly, plus a normalized REST API underneath.

What you can do with Netsmart via MCP

Once connected, an agent can:

  • Look up members and clients, caregivers and providers.
  • Pull and submit EVV visits: check-in/out, service codes, tasks, GPS and verification metadata.
  • Manage authorizations (payer, service code, units, validity dates) and check remaining units.
  • Pull and update schedules and assignments.
  • Surface EVV exceptions: late or missing events, GPS mismatch, overlapping visits.
  • Submit Medicaid/MCO claims (837P/I) referencing verified visits.
  • Retrieve remittances (835) for reconciliation.

How to connect Netsmart to Claude, ChatGPT & Cursor

Connecting works like any other MCP server. The short version:

  • Claude (Desktop or claude.ai): add the Netsmart MCP server under Settings → Connectors (or your MCP config), authorize the Netsmart 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 Netsmart 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 Netsmart MCP server

Supergood doesn't wait for Netsmart to ship an API. We reverse-engineer the authenticated web and EVV flows behind Netsmart, 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 Netsmart 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 Netsmart's front-end happens to return.
  • Monitored and adapted. When Netsmart changes its web and EVV UI or internal API, monitoring catches it and the connector gets patched, usually before it reaches you.
  • State-aware logic. EVV validation rules and service codes vary by state Medicaid program (Florida, Georgia, Kentucky, and more); Supergood normalizes them into one consistent surface.

Getting Started

  • Schedule Integration Assessment

Book a 30-minute call to confirm which Netsmart modules and workflows you need and how authentication should work.

  • Supergood Builds and Validates Your MCP Server

We deliver a hardened Netsmart 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 Netsmart changes.

netsmart

Use Cases

EVV compliance

- Pull the day's visits and verification metadata - Flag GPS mismatches and overlapping shifts before billing - Submit corrected visit events with compliant reason codes

Authorization-aware scheduling

- Check remaining units before assigning a visit - Block scheduling that would exceed the auth - Flag authorizations expiring soon

Claims and reconciliation

- Submit Medicaid/MCO claims referencing verified visits - Pull remittances and post payments - Reconcile billed units against authorizations

Roster sync

- Keep caregiver and member rosters in sync with another system - Surface unstaffed visits - Pull exports for compliance reporting

Technical Specifications

MCP transport

Remote MCP server over HTTPS; works with hosted MCP clients and with local MCP configs.

Authentication

Supergood provisions a dedicated Netsmart 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 EVV and scheduling reads; SFTP/EDI feeds follow daily submission windows that Supergood orchestrates with retry.

Rate limits

Tuned to Netsmart'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 Netsmart 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 Netsmart web and EVV surfaces changes, with rapid connector updates.

Frequently asked questions

No. Netsmart doesn't publish an MCP server. Supergood builds and maintains one by reverse-engineering Netsmart'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 Netsmart 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 Netsmart's live system, not a nightly export. Netsmart's EVV and exception handling (delivered via Tellus) lives in web apps and batch exports, with state- and payer-specific service codes and validation logic rather than a unified public API.

Both. The MCP tools are a layer on top of a normalized REST API for Netsmart; you can call either, from an agent or from your own code.

Ready to get a real API?