SSyncDev

Therapyportal-mcp Server

TherapyNotes client portal: appointments, documents, billing, messages; confirm-gated sends, uploads

Local serverstdio

What is the Therapyportal-mcp Server?

Therapyportal-mcp is an MCP integration. TherapyNotes client portal: appointments, documents, billing, messages; confirm-gated sends, uploads.

Packages and local setup

The published npm package is @chrischall/therapyportal-mcp, version 0.5.0. Its declared MCP transport is stdio.

The package declares THERAPYPORTAL_PRACTICE (required): Your practice's portal code: the part after /p/ in its TherapyPortal URL (www.therapyportal.com/p/ /).; THERAPYPORTAL_EMAIL: The email you sign in to TherapyPortal with. Set with the password to sign in server-side; leave both empty to relay through your signed-in browser tab.; THERAPYPORTAL_PASSWORD: Your TherapyPortal password. A rejected sign-in is never retried automatically.; THERAPYPORTAL_DOB: Only if the portal asks for a date of birth at sign-in: that date, as MM/DD/YYYY. Tried once; never retried, because the portal limits attempts.; THERAPYPORTAL_TRANSPORT: server or fetchproxy. Default: server when email and password are both set, otherwise fetchproxy.; THERAPYPORTAL_WS_PORT: fetchproxy concentrator port (fetchproxy transport only, default 37149). The whole fleet shares this one port; override only when hosting.; THERAPYPORTAL_OUTPUT_DIR: Where downloaded files are written on the server transport (a path-delimiter list; ~ expands). Default ~/Downloads and ~/Documents. A per-call dest must resolve inside one of these.; THERAPYPORTAL_INLINE_DOWNLOADS: true returns downloaded bytes inline (base64) instead of writing to disk, for a hosted runner whose disk you cannot reach. Default false.; THERAPYPORTAL_UPLOAD_DIR: Folders an upload's file_path must be inside (a path-delimiter list; ~ expands). Default ~/Downloads, ~/Documents and ~/Desktop. Local installs only: a hosted server refuses file_path and takes uploads by upload slot or inline base64.; MCP_CONFIRM_MODE: Confirm-gate mode for every write (secure messages, document uploads). ask-user (default) returns a preview + confirmToken and needs a second call with that token; auto lets a capable host confirm in one step; an unrecognised value fails closed (refuse).; MCP_CONFIRM_ELICITATION: on (default) lets the host confirm a write interactively; off forces the confirmToken round-trip.; FETCHPROXY_WS_HOST: Bind interface for the fetchproxy concentrator, a literal IP only (default 127.0.0.1). Keep on loopback; it exists for hosted deployments that run each MCP in its own network namespace.; FETCHPROXY_IDENTITY_DIR: Absolute path where the fetchproxy long-term identity keypair is stored (default ~/.fetchproxy/identity/)..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.5.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
THERAPYPORTAL_PRACTICEYour practice's portal code: the part after /p/ in its TherapyPortal URL (www.therapyportal.com/p/ /).Yes
THERAPYPORTAL_EMAILThe email you sign in to TherapyPortal with. Set with the password to sign in server-side; leave both empty to relay through your signed-in browser tab.Check documentation
THERAPYPORTAL_PASSWORDYour TherapyPortal password. A rejected sign-in is never retried automatically.Check documentation
THERAPYPORTAL_DOBOnly if the portal asks for a date of birth at sign-in: that date, as MM/DD/YYYY. Tried once; never retried, because the portal limits attempts.Check documentation
THERAPYPORTAL_TRANSPORTserver or fetchproxy. Default: server when email and password are both set, otherwise fetchproxy.Check documentation
THERAPYPORTAL_WS_PORTfetchproxy concentrator port (fetchproxy transport only, default 37149). The whole fleet shares this one port; override only when hosting.Check documentation
THERAPYPORTAL_OUTPUT_DIRWhere downloaded files are written on the server transport (a path-delimiter list; ~ expands). Default ~/Downloads and ~/Documents. A per-call dest must resolve inside one of these.Check documentation
THERAPYPORTAL_INLINE_DOWNLOADStrue returns downloaded bytes inline (base64) instead of writing to disk, for a hosted runner whose disk you cannot reach. Default false.Check documentation
THERAPYPORTAL_UPLOAD_DIRFolders an upload's file_path must be inside (a path-delimiter list; ~ expands). Default ~/Downloads, ~/Documents and ~/Desktop. Local installs only: a hosted server refuses file_path and takes uploads by upload slot or inline base64.Check documentation
MCP_CONFIRM_MODEConfirm-gate mode for every write (secure messages, document uploads). ask-user (default) returns a preview + confirmToken and needs a second call with that token; auto lets a capable host confirm in one step; an unrecognised value fails closed (refuse).Check documentation
MCP_CONFIRM_ELICITATIONon (default) lets the host confirm a write interactively; off forces the confirmToken round-trip.Check documentation
FETCHPROXY_WS_HOSTBind interface for the fetchproxy concentrator, a literal IP only (default 127.0.0.1). Keep on loopback; it exists for hosted deployments that run each MCP in its own network namespace.Check documentation
FETCHPROXY_IDENTITY_DIRAbsolute path where the fetchproxy long-term identity keypair is stored (default ~/.fetchproxy/identity/).Check documentation