clalit-mcp

Read your own Clalit Health Services records (lab results, prescriptions, lab orders, visit and hospital summaries) from an AI assistant over MCP, or from a CLI.

Unofficial. Not affiliated with Clalit. Not a substitute for the official portal or clinical advice.

Based on netanelavr/clalit-mcp by Netanel Avraham (MIT). This version adds the document readers and moves sign-in and session keep-alive into the MCP server itself, so it works as a plain local MCP server and can also run as one long-lived copy for several clients.

Everything runs on your machine. You sign in through your own browser, 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 account only. Never use this against someone else's record.

• Read-only. No booking, payments, profile writes, or prescription requests.

• No CAPTCHA, bot or Imperva bypass. You solve the CAPTCHA and enter the SMS code yourself.

• Residential connection. Clalit's Imperva turns most datacenter and cloud IPs away (Error 16). Run it at home.

• The session file is secret. It is saved with mode 0600 under ~/.config/clalit-mcp/. Never commit or paste it.

Related MCP server: halaxy-mcp

Install

git clone https://github.com/tadnir/clalit-mcp.git
cd clalit-mcp
npm install
npm test

Use it from an MCP client

Add the server to your client. For Claude Code, Cursor and most clients:

{
  "mcpServers": {
    "clalit": {
      "command": "npx",
      "args": ["tsx", "packages/cli/src/main.ts", "mcp"],
      "cwd": "/absolute/path/to/clalit-mcp"
    }
  }
}

Claude Desktop does not see your shell's PATH, so give it absolute paths (find node with which node):

{
  "mcpServers": {
    "clalit": {
      "command": "/absolute/path/to/node",
      "args": [
        "/absolute/path/to/clalit-mcp/node_modules/.bin/tsx",
        "/absolute/path/to/clalit-mcp/packages/cli/src/main.ts",
        "mcp"
      ]
    }
  }
}

Signing in

1. Ask your assistant for something, for example "list my lab results from this year".

2. While nobody is signed in, the tools answer with a link to a sign-in page this server serves on http://localhost:8765/. clalit_login returns the same link.

3. Open it, pick how long to stay signed in (1 hour to 1 week), and enter your ID, the CAPTCHA and the SMS code there.

4. Ask again. The server now keeps the session alive while it runs and signs out at the end of the length you picked.

Your ID and the codes are only ever typed on that page. The assistant only ever sees the link, and the tools tell it never to ask for them in the chat.

The keep-alive only runs while your client keeps the server running. If the client is closed for more than about ten minutes, Clalit ends the session and you sign in again next time. To keep one session alive across days, see docs/HOSTING.md.

Tools

Settings

CLI

The CLI shares the same session file, so signing in from either one works for both.

npx tsx packages/cli/src/main.ts login
npx tsx packages/cli/src/main.ts labs --json
npx tsx packages/cli/src/main.ts lab --ref <token-from-labs> --json
npx tsx packages/cli/src/main.ts lab-document --ref <token> --out result.pdf
npx tsx packages/cli/src/main.ts prescriptions --json
npx tsx packages/cli/src/main.ts lab-orders --json
npx tsx packages/cli/src/main.ts documents --source visit_summaries --json
npx tsx packages/cli/src/main.ts document --ref <token-from-documents> --out summary.pdf
npx tsx packages/cli/src/main.ts help

See docs/ for the sign-in flow, the portal pages used and a first live check.

License

MIT