Choose your AI assistant and follow the setup instructions.
Claude Desktop connects directly to inou via OAuth — no tokens to copy, no extensions to install.
Download and install from claude.ai/download
In Claude Desktop:
| Name | Inou Health |
| Remote MCP server URL | https://inou.com/mcp |
Click Add, then Connect.
Your browser will open to sign in to inou. After signing in, click Open Claude to complete the connection.
To avoid being asked 11 times for permission:
This grants Claude permission to read your health data without asking each time.
To automatically load your family's health data context in every conversation:
At the start of health-related conversations, use the family_health_context tracker from the Inou Health connector to understand what health data is available.
This tells Claude to check what health data is available for your family members at the beginning of each conversation, without filling up the context window with actual medical data.
Open Claude Desktop and try:
List my available dossiers.
You should see your dossier(s). You're all set!
Connect Grok so it can look at your family’s health data in inou — scans, labs, and the rest — and answer in your own words. You only need to connect once.
You’re using Grok on a laptop or desktop that has a normal web browser. This is the usual case.
Someone set Grok up on a server, or you’re remote. You approve the connection on your phone instead.
On your own computer
In Grok, add a connection (sometimes called a connector or MCP server) and use this address:
https://inou.com/mcp
You can name it anything — “Inou” or “Health data” is fine.
Grok will open your browser. Sign in to inou the same way you always do, then click Allow so Grok may read your health data.
If nothing opens, look in Grok for a button like Connect, Sign in, or Authenticate next to the inou connection.
Back in Grok, type something simple:
Show me who is in my family’s health records.
You should see names you recognize. After that you can ask about labs, scans, or anything else you’ve uploaded.
Grok is on another machine
Use this only if the person who set things up says the computer can’t open a browser by itself.
Grok (or the person helping you) will show a short code like ABCD-EFGH, or a link that already includes the code.
On your phone or any computer:
Do this soon — the code only works for a short time. If it says the code expired, ask for a new one and try again. Don’t reuse an old code.
After you tap Allow, Grok should finish connecting on its own. Then ask the same test question as above. If it still can’t see your data, the person who set up Grok needs a new code from the start — not something you fix by guessing.
Once it’s working, try questions in everyday language, for example:
Grok only sees data you’ve put in inou, for people you’re allowed to see. It can’t invent medical files that aren’t there.
Kimi (and similar chat UIs) can access your health data through our API using HTTP requests. No installation needed.
Once connected, ask it to:
See the API guide for the full data model and every endpoint. Prefer the Grok tab when you can connect Grok properly.
Not recommended for medical imaging due to elevated hallucination risk in our testing.
Medical imaging requires absolute accuracy. In our testing, ChatGPT fabricated information even when correct data was clearly provided. We cannot recommend it for analyzing health data where errors have real consequences.
Use Claude Desktop or Grok for native tool access, or Kimi for a paste-token web API flow.
Any AI that can fetch a URL can read your data through our web API. The same instructions work for any model — give it your token and point it at the guide.
Tell the model to read https://inou.com/api/v1/guide first — it's a plain-text guide to the data model and every endpoint (navigation, imaging, genome, labs, documents) — then fetch your dossiers with your token. The Kimi tab has a ready-to-paste prompt you can reuse. For Grok, use the Grok tab instead.
Capabilities vary by model. Some (e.g. Gemini) have restricted web browsing and may not fetch inou.com URLs directly — copy responses in manually, or use a model with a working fetch tool. Whatever the model, never accept conclusions it can't tie to data the API actually returned.