Practice data, reachable from outside the app
HyperCRM is built on a real REST API and a real MCP server, not just a UI. The same endpoints the app uses are documented and callable with a bearer token, and an MCP server lets AI agents read and write practice data under the same auth model.
Where to go next
REST API
Patients, appointments, billing, forms, files, tags, reporting and more, authenticated with a bearer token and scoped to your practice.
MCP server
A Model Context Protocol server so an AI agent can list, read, create and update patient records under OAuth 2.1 authorization.
Documentation
Getting started, task guides and the API reference — authentication, patients, appointments and the error envelope.
No separate developer product
There is no second, cut-down version of HyperCRM for developers. The REST API is the same layer the web app calls, scoped to your practice and authenticated the same way. If a feature exists in the app, its data is reachable through the API in the same shape.
Two ways in
The REST API covers patients, appointments, billing, forms, files, tags, reporting and more, authenticated with a bearer token. The MCP server exposes a smaller, patient-record-focused slice of that same surface over the Model Context Protocol, so an AI agent or assistant can read and write practice data directly, with OAuth 2.1 and PKCE for authorization.
What is on which plan
The REST API and the MCP server are included on the Complete plan and are not available on Essential. They are what the product itself runs on, but there is no official SDK and no webhook system yet — the docs page explains where the reference actually lives.
Common questions
HyperCRM is paid software. Every practice starts with a 30-day free trial of the full Complete plan, with no card required. After that, plans start at €19 and €29 a month excluding VAT, banded by how many practitioners you have. Every price is printed on the pricing page rather than quoted on a call.
Patient records are encrypted in transit and at rest, files are stored privately and served through short-lived signed links, and every change is written to an audit log. Staff accounts sign in with passkeys rather than shared passwords.
Not yet. The API is a plain JSON REST interface over HTTP, callable with any HTTP client and a bearer token, but there is no first-party SDK in any language today.
No. There is no separate developer signup or API-key dashboard. Authentication uses the same Firebase-based sign-in as the app, and once you're signed in you can call the API with a bearer token scoped to your own practice.
Start building against real data
The API and MCP server are on Complete, which the trial runs on. No card to start.
Start the free trial