Use an InSync (Qualifacts) patient portal: reads, file transfer, messages and care requests
Insync-mcp is an MCP integration. Use an InSync (Qualifacts) patient portal: reads, file transfer, messages and care requests.
The published npm package is @chrischall/insync-mcp, version 0.5.0. Its declared MCP transport is stdio.
The package declares INSYNC_PORTAL (required): Your practice's portal, scheme and host only, e.g. https:// intouch.insynchcs.com.; INSYNC_USERNAME: Portal username. Set with INSYNC_PASSWORD to sign in server-side. Leave both empty to relay through your signed-in browser tab.; INSYNC_PASSWORD: Portal password. A rejected sign-in is never retried automatically, because the portal counts failures toward a lockout.; INSYNC_TRANSPORT: server or fetchproxy. Default: server when both credentials are set, otherwise fetchproxy.; INSYNC_WS_PORT: Override the fetchproxy WebSocket port (default 37149).; INSYNC_OUTPUT_DIR: Where downloaded files are written locally (a path-delimiter list; ~ expands). Default ~/Downloads and ~/Documents. A per-call dest must resolve inside one of these.; INSYNC_INLINE_DOWNLOADS: Local installs: true returns a downloaded file inline (up to 10 MiB) instead of writing it to disk; larger files are still saved. Ignored when hosted, which always delivers inline or by signed link. Default false.; 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/)..
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.
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.
| Variable | Description | Required |
|---|---|---|
| INSYNC_PORTAL | Your practice's portal, scheme and host only, e.g. https:// intouch.insynchcs.com. | Yes |
| INSYNC_USERNAME | Portal username. Set with INSYNC_PASSWORD to sign in server-side. Leave both empty to relay through your signed-in browser tab. | Check documentation |
| INSYNC_PASSWORD | Portal password. A rejected sign-in is never retried automatically, because the portal counts failures toward a lockout. | Check documentation |
| INSYNC_TRANSPORT | server or fetchproxy. Default: server when both credentials are set, otherwise fetchproxy. | Check documentation |
| INSYNC_WS_PORT | Override the fetchproxy WebSocket port (default 37149). | Check documentation |
| INSYNC_OUTPUT_DIR | Where downloaded files are written locally (a path-delimiter list; ~ expands). Default ~/Downloads and ~/Documents. A per-call dest must resolve inside one of these. | Check documentation |
| INSYNC_INLINE_DOWNLOADS | Local installs: true returns a downloaded file inline (up to 10 MiB) instead of writing it to disk; larger files are still saved. Ignored when hosted, which always delivers inline or by signed link. Default false. | Check documentation |
| 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. | Check documentation |
| FETCHPROXY_IDENTITY_DIR | Absolute path where the fetchproxy long-term identity keypair is stored (default ~/.fetchproxy/identity/). | Check documentation |
Read, search and edit files inside allowed directories with the Model Context Protocol reference Filesystem server.
Retrieve version-aware library documentation and code examples with Context7 MCP, using resolve-library-id and query-docs.
MCP server for SSH connections to Cisco network devices
MCP server with UI for NASA images
MCP server for Suppr API - AI-powered document translation and literature search
Backup Ai automation via MCP. Includes create backup plan, verify backup, list backups. By M...