ichilov-mcp
ichilov-mcp lets an AI assistant read your own Ichilov (beWell) medical records — documents, their PDFs, and upcoming appointments — after you sign in on a page it serves locally.
Sign in (
ichilov_login): returns a localhost link where you enter your ID, mobile number and SMS/voice one-time code — never in the chat.Check the session (
ichilov_session_status): whether you're signed in, since when, until when, or the sign-in link if not.Sign out (
ichilov_logout): ends and forgets the beWell session.List documents (
list_documents): lab results, imaging reports, visit/hospitalization summaries, newest first; filter by kind (lab,imaging,other), date range, or text search.Fetch a document (
get_document_pdf): one document as a base64 PDF, using the type/number/version/part from the listing — lab values appear only inside the PDFs.List appointments (
list_appointments): your upcoming hospital appointments.Boundaries: read-only, your own records only; no bookings, cancellations or changes, and beWell has no prescriptions.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ichilov-mcp what were my last blood test results at Ichilov?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ichilov-mcp
Read your own records from beWell, the patient portal of Tel Aviv Sourasky Medical Center (Ichilov, איכילוב), from an AI assistant over MCP: lab results, imaging reports and visit summaries as PDFs, and upcoming appointments.
Unofficial. Not affiliated with the hospital. It uses the same API as the beWell website, which can change without notice.
Everything runs on your machine. You sign in on a page this server serves, the session is saved only on your computer, and this project has no hosted backend and collects nothing. Whatever your AI client requests is passed to that client and handled under its provider's privacy terms.
Terms of use
Own records only.
Read-only. No bookings, cancellations or changes at the hospital.
The session file is secret. It holds beWell's session cookies, is saved with mode
0600under~/.config/ichilov-mcp/, and must never be committed or pasted.
Related MCP server: SundhedMCP
Install
git clone https://github.com/tadnir/ichilov-mcp.git
cd ichilov-mcp
npm install
npx playwright install chromium
npm testUse it from an MCP client
{
"mcpServers": {
"ichilov": {
"command": "npx",
"args": ["tsx", "src/main.ts"],
"cwd": "/absolute/path/to/ichilov-mcp"
}
}
}For Claude Desktop, use absolute paths: "command": "/absolute/path/to/node" with "args": ["/absolute/path/to/ichilov-mcp/node_modules/.bin/tsx", "/absolute/path/to/ichilov-mcp/src/main.ts"].
Signing in
Ask your assistant something, for example "what were my last blood test results at Ichilov?".
While nobody is signed in, the tools answer with a link to a sign-in page this server serves on
http://localhost:8767/.ichilov_loginreturns the same link.Open it, enter your ID number (or passport) and the mobile number the hospital has on file, and pick how long to stay signed in (1 hour to 30 days). The hospital sends a one-time code by SMS, or by a voice call to a landline; enter it on the page.
Ask again.
Your ID, phone number and the code are only ever typed on that page and sent to the hospital. The assistant only ever sees the link.
beWell protects its sign-in with an invisible reCAPTCHA that only its own page can run, so the server does each step inside a Chromium browser open on the hospital's sign-in page. When reCAPTCHA wants a picture puzzle, the sign-in page shows it, and you solve it there by clicking the picture; nothing is solved automatically. The browser keeps its profile (Google's cookies included) in ICHILOV_CONFIG_DIR/browser, so reCAPTCHA asks fewer puzzles after the first sign-in.
beWell has no refresh token, and ends a sign-in about 20 minutes after it starts, however active it is: neither its own session check nor data calls extend it. So sign in just before you want your assistant to read your records. While the MCP server runs it checks the session every 2 minutes with a small data call (beWell's session check keeps answering "OK" after the sign-in has ended), saves the session's cookies, and shows the session as ended as soon as beWell refuses it. A restart picks the saved session back up if it hasn't ended in between.
Tools
Tool | What it reads |
| Lab results, imaging reports, visit and hospitalization summaries, newest first; filter by kind, date or text |
| One of those documents as a PDF (lab values are only in the PDFs) |
| Upcoming appointments |
| The sign-in link, whether a session is live and until when, and sign-out |
beWell has no prescriptions.
Settings
Variable | Default | Meaning |
|
| Where the session and the sign-in browser's profile are saved |
|
| Address the sign-in page listens on |
|
| Its port; a free one is used if another copy holds it |
|
| The link handed out, when the page sits behind a reverse proxy. When set, the page starts with the server. |
|
|
|
|
| |
| Playwright's Chromium | Another Chromium to sign in with |
Hosting one long-lived copy
To share one session between several clients, run a single copy on an always-on machine at home and put a stdio-to-HTTP MCP proxy in front of it, such as TBXark/mcp-proxy, with a bearer token per client. Keep it on your own network or a private VPN, never on the internet. Put the sign-in page behind your own authentication and set ICHILOV_LOGIN_URL to its address (and ICHILOV_LOGIN_HOST=0.0.0.0 inside a container). Its links and forms are relative, so it can sit at the root of a host or under a path whose prefix the reverse proxy strips (ICHILOV_LOGIN_URL=https://mcp.example.com/ichilov/login/, with the trailing slash).
Every token holder reads the records of whoever signed in on the page; the proxy's tokens and the beWell session are unrelated. For a second person, run a second copy with its own ICHILOV_CONFIG_DIR, tokens and sign-in page.
The Dockerfile builds an image of the stdio server with Chromium, published as ghcr.io/tadnir/ichilov-mcp from master, with the session in /data and the page on port 8767. Run it with docker run -i, or use it as a base for an image that adds your MCP proxy.
The sign-in page answers only to localhost, 127.0.0.1 and the host in ICHILOV_LOGIN_URL, and each form carries a per-process token. Anyone who can open the page can sign in or out, so keep it on loopback or behind your own authentication.
License
Available Tools
6 toolsget_document_pdfA
Download one document from list_documents as a PDF (base64).
Inputs: part (required), type (required), number (required), version (required).
ichilov_loginA
Get the link where the user signs in to beWell (ID, mobile number and one-time code are typed on that page, never in the chat). Returns the status when already signed in.
Inputs: no named parameters.
ichilov_logoutA
Sign out of beWell here: end the session and forget it.
Inputs: no named parameters.
ichilov_session_statusA
Whether this server is signed in to beWell, since when, until when, and the sign-in link when it is not.
Inputs: no named parameters.
list_appointmentsB
The patient's upcoming appointments at the hospital.
Inputs: no named parameters.
list_documentsB
The documents in the patient's file (lab results, imaging, visit and hospitalization summaries), newest first, with the type, number, version and part get_document_pdf takes.
Inputs: to, from, kind, search.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Auth tools (login, session_status, logout) and data tools (list_documents, list_appointments, get_document_pdf) are clearly separated. The only mild overlap is ichilov_login and ichilov_session_status both returning the sign-in link, but their purposes differ.
Half the tools use an ichilov_ prefix (auth) while the other half use bare verb_noun names (data), with no clear rule. Mixed verb styles and prefixes across the set reduce predictability.
Six tools is a tight, reasonable surface for an authenticated document/appointment reader. Nothing feels extraneous, though it is on the leaner side.
Read path is well covered (list then fetch PDF), and auth lifecycle is complete. However, there is no tool to view appointment details, cancel/reschedule, or fetch documents by filter—notable gaps for an agent working in this domain.
Related MCP Connectors
Your MedNode health vault in your AI assistant — records, summaries, labs, appointments.
Your labs, wearables, DNA and notes as one health record your AI agent can read (OAuth 2.1).
Your own health records from Vora, Still, Stackwell and Joiva in your AI assistant (OAuth).
Read patient-authorized EHR records: medications, labs, conditions, allergies. Consent-bounded.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to securely read and organize a patient's own health records from Epic MyChart via the FHIR API, including labs, documents, appointments, and attachments, using OAuth-based authorization.-
- AlicenseAqualityBmaintenanceEnables AI assistants to securely read a user's own sundhed.dk health record data, including medications, lab results, vaccinations, and referrals, after MitID login via a local browser session.1223 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables users to read their own Clalit Health Services records—including lab results, prescriptions, lab orders, visit and hospital summaries, and source PDFs—through an AI assistant over MCP or a CLI, with local browser-based sign-in and session keep-alive.MIT
- AlicenseAqualityCmaintenanceGives AI agents read-only access to patient context on any FHIR R4 server, including journey timelines of encounters and appointments, open booking slots, and discharged patients whose follow-ups were never booked. Search, appointment, and follow-up tools return compact summaries, so agents can answer front-desk and outreach questions without write access.5MIT