OVOKby ACTIMI
Read the docsStart free

Set up your healthcare backend from your AI agent.

Ovok's MCP server connects Claude, ChatGPT, Cursor and other MCP clients to one Ovok project. A project admin signs in and consents once; the agent then works on the project through named tools, as that admin.

Start free Open the MCP setup
ovok.com/console/fhir/Patient
Lena HoffmannPatient
Observations
TemperatureDr. Weber°CNo alert
Blood glucoseDr. Webermmol/LNo alert
Heart rateSleep radarbpmNo alert
Respiratory rateSleep radar/minAlert sent
Sleep sessionSleep radarhNot evaluated
Blood pressureVitalivammHgNo alert
WeightVitalivakgNo alert
9:41
Home
Blood pressuremmHg
Oxygen saturation%
Weightkg
Blood glucosemmol/L
Temperature°C
Check-in
Send
Medication
Ramipril 5 mg08:00
Mark as takenTaken
Sleep radar
7.21458
23:4006:55
Lena Hoffmann
WDr. Weber
Blood glucosemmol/L
Temperature°C
Save

Connect a project in one step

Standard OAuth sign-in

The client registers itself and signs in with PKCE (S256). A project admin approves the connection in the Console, and it lasts 90 days after consent.

22 setup guides

The Console's MCP page has a guide for each listed client, including Claude, ChatGPT and Cursor, plus the raw MCP URL for any other MCP client.

Docs written for agents

The AI agents guide covers the Ovok agent skill, the MCP server and llms.txt, so an agent can read the platform docs while it works.

Read the documentation

27 tools, named for what they do

17 core tools and 10 CMS tools cover the setup work a project admin does in the Console.

Project and team

Read the project, read and change its settings, list members and send invitations, and list and create client apps.

Requests and usage

Inspect request logs, failed requests and their details, usage, and a Signals summary.

FHIR data

Search FHIR resources and create, update or delete them in the connected project.

CMS content

Read the CMS schema, create, change and delete documents, set UI translations, and manage CMS API keys.

Know what the agent can reach

The MCP connection

  • Works on the one project its admin consented for.
  • Acts as that admin, and ends 90 days after consent.

Your team

  • Connects each further project separately.
  • Reviews what the agent changes before production use.

Explore solutions for your team.

Compare startup validation, scaleup device workflows, enterprise architecture, and provider-led Hospital at Home, virtual-ward, or Spitex programmes.

Startup evaluation

Set up a Developer sandbox project from your AI client and test your first workflow.

Read about Startup evaluation

Connect your AI client to a sandbox project.

Start free, open the Console's MCP page and follow your client's setup guide.

Start free Open the MCP setup