← Back to all docs

TheraNest MCP Server

The TheraNest MCP server lets AI agents read and write client, scheduling, documentation, and billing data in TheraNest. Connect TheraNest to Claude, ChatGPT, and Cursor. Built and maintained by Supergood, since TheraNest doesn't ship an MCP server.

By Alex KlarfeldMay 12, 2026
TheraNest API

What is the TheraNest MCP server?

The TheraNest MCP server is a connector that lets AI agents (Claude, ChatGPT, Cursor, and other MCP clients) read and write client, scheduling, documentation, and billing data in TheraNest through a standard protocol.

In short: TheraNest is a cloud practice-management and EHR platform for behavioral and mental health practices: scheduling, reminders, telehealth, a client portal, clinical documentation, insurance billing and ERA posting, and outcomes tracking with measures like PHQ-9 and GAD-7.

TheraNest doesn't ship an official MCP server, and TheraNest has limited public APIs. Many scheduling, documentation, and billing features are reachable only through the web app or CSV exports, and clearinghouse behavior varies by partner. Supergood builds and maintains the connector by reverse-engineering TheraNest's authenticated web and portal flows and exposing them as MCP tools an agent can call directly, plus a normalized REST API underneath.

What you can do with TheraNest via MCP

Once connected, an agent can:

  • Look up clients: demographics, contacts, portal status.
  • Pull and create appointments: service codes, place of service, status, telehealth links.
  • Retrieve clinical notes and treatment plans, with signatures.
  • Get diagnoses (ICD-10), problem lists, and goals/objectives.
  • Pull invoices, payments, and write-offs.
  • Submit insurance claims (CMS-1500 / 837P) and reconcile ERA remittances (835).
  • Pull outcomes measures (PHQ-9, GAD-7) and progress data.

How to connect TheraNest to Claude, ChatGPT & Cursor

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

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

Supergood doesn't wait for TheraNest to ship an API. We reverse-engineer the authenticated web and portal flows behind TheraNest, 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 TheraNest 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 TheraNest's front-end happens to return.
  • Monitored and adapted. When TheraNest changes its web and portal UI or internal API, monitoring catches it and the connector gets patched, usually before it reaches you.
  • Past the export limits. Where TheraNest only offers CSV downloads on a timer, Supergood works the authenticated web flows directly so the agent gets live data, not a queued report.

Getting Started

  • Schedule Integration Assessment

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

  • Supergood Builds and Validates Your MCP Server

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

theranest

Use Cases

Practice-ops agent

- Answer "who's on my schedule and which intakes are outstanding" - Send and chase intake forms - Confirm contact and insurance details

Documentation

- Pull the open session note and treatment plan - Surface notes that still need a signature - Keep records consistent with another tool

Billing and RCM

- Submit claims and reconcile ERAs - Surface denials and rejections - Reconcile payments against invoices

Outcomes tracking

- Pull PHQ-9 / GAD-7 trends for a client - Flag clients due for a reassessment - Feed reporting without manual exports

Technical Specifications

MCP transport

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

Authentication

Supergood provisions a dedicated TheraNest 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 reads and writes against TheraNest's live web app and client portal; export-driven artifacts are orchestrated by Supergood.

Rate limits

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

Frequently asked questions

No. TheraNest doesn't publish an MCP server. Supergood builds and maintains one by reverse-engineering TheraNest'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 TheraNest 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 TheraNest's live system, not a nightly export. TheraNest has limited public APIs. Many scheduling, documentation, and billing features are reachable only through the web app or CSV exports, and clearinghouse behavior varies by partner.

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

Ready to get a real API?