Alberta Health MCP Server

An MCP (Model Context Protocol) server that provides Claude Desktop with passthrough access to Alberta's My Health Records portal and AHS MyChart (Connect Care). Ask Claude about your lab results, immunizations, medications, vitals, appointments, clinical documents, and more — all through natural language.

What It Does

You: "Show me my lab results from the last 6 months and explain anything unusual"
Claude: [calls get_lab_results] Here are your results...

The MCP server authenticates with Alberta's SSO (shared across both portals), fetches your health data from MHR and MyChart, and passes it to Claude for interpretation. It's a read-only passthrough — no health data is stored, cached, or analyzed by the server itself. Claude handles all interpretation.

Quick Start

Option 1: One-Click Install (Recommended)

1. [Request access](https://www.myaihealth.ca/#request-access) — we'll email you a download link
2. Double-click the downloaded file — Claude Desktop installs it automatically
3. Tell Claude: "Connect to My Health Records"
4. Chrome opens to Alberta's real login page — sign in with your MyAlberta credentials
5. Start asking: "Show me my lab results", "Am I up to date on immunizations?", etc.

No Node.js. No terminal. No configuration files. No API keys.

Requirements: Claude Desktop and Google Chrome. You need a MyAlberta account with My Health Records access.

Try It First — Demo Mode

Don't have an Alberta account? Want to see what the extension can do before signing in? Demo mode uses a realistic, multi-person sample family so you can explore all 48 tools without any credentials.

After installing the extension, try this conversation:

1. You: "Connect to health data in demo mode"
2. You: "Pull a comprehensive health report"
3. You: "What health concerns can you identify? What patterns do you see across my labs, medications, and vitals?"
4. You: "Can you put all this in a PDF I can take to the doctor?"

Claude will connect instantly (no browser, no login), pull sample health data, and demonstrate how AI can identify clinically meaningful patterns — like a worsening HbA1c trend, cardiovascular risk factors across multiple tests, or medication interactions worth discussing with a doctor. These are the kinds of insights that are easy to miss when browsing portal pages individually.

The demo now includes a four-person sandwich-generation scenario:

| Person | Profile | What it showcases |

|--------|---------|-------------------|

| Demo User (you, 39M) | Type 2 Diabetes, Hypertension, Hyperlipidemia, Vitamin D deficiency | Worsening HbA1c trend, statin titration, kidney function monitoring |

| Margaret User (mother, 72F) | T2D, AFib, HFpEF, mild Alzheimer-type dementia, CKD3a, polypharmacy (12+ meds) | Caregiver workflow, recent ED visit, polypharmacy review, advance care planning, drug interactions (donepezil+metoprolol, glipizide+CKD) |

| Sarah User (spouse, 41F) | Hashimoto hypothyroidism, GAD, migraine with aura, perimenopause, recent IUD | Women's preventive care (mammogram, Pap/HPV), mental-health continuity, migraine + perimenopause hormonal pattern |

| Liam User (son, 7M) | Mild persistent asthma (recent ED), ADHD on Concerta, peanut allergy + EpiPen | Pediatric care, stimulant monitoring, anaphylaxis preparedness, vaccine schedule, asthma action plan |

Switch between them with: "List the people I have access to" → "Switch to my mother's chart" → "Compare HbA1c trends between me and my mom"

More demo prompts to try:

| Prompt | What it showcases |

|--------|-------------------|

| "Show me my lab results and flag anything outside reference ranges" | AI identifies abnormal values (high LDL, low Vitamin D, elevated HbA1c) |

| "Are any of my mom's medications interacting with each other or her kidney function?" | Polypharmacy review across 12 meds with CKD3a (donepezil+metoprolol bradycardia, glipizide hypos) |

| "How has my diabetes control changed over the past year?" | Tracks HbA1c trend: 6.2% → 6.5% → 6.8% (Self) or 7.4% → 7.9% (Mother) |

| "What's my cardiovascular risk profile?" | Connects high cholesterol + diabetes + hypertension + blood pressure trends |

| "Am I overdue for any screenings or vaccinations?" | Checks immunization records and preventive care gaps |

| "What appointments does Liam have coming up, and is his asthma plan up to date?" | Pediatric scheduling + asthma action plan retrieval |

| "Summarize what I should discuss with each of my mom's specialists at the next visit" | Synthesizes all data into actionable talking points |

Note: Demo data is clearly fictional ("Demo User", "Margaret User", "Sarah User", "Liam User"). To access your real health records, use Option 1 above. In demo mode, every response is marked with [DEMO MODE — sample data, not a real patient].

Option 2: Developer Install

<details>

<summary>For contributors or users who prefer manual setup</summary>

Prerequisites

• Node.js 22+
• Claude Desktop
• Google Chrome
• A MyAlberta account with My Health Records access

Install

git clone https://github.com/JCrossman/ab-health-mcp.git
cd ab-health-mcp
npm install
npm run build

Configure Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS):

{
  "mcpServers": {
    "ab-health-mcp": {
      "command": "node",
      "args": ["/path/to/ab-health-mcp/build/index.js"]
    }
  }
}

Restart Claude Desktop. You'll see the tools appear in the connectors panel.

</details>

Usage

1. Tell Claude: "Connect to My Health Records"
2. A browser window opens — log in with your MyAlberta credentials
3. Once logged in, your session is established (covers both MHR and MyChart)
4. Ask Claude anything: "Summarize my recent lab results", "Am I up to date on immunizations?", etc.

Example Prompts

Here are working examples that demonstrate core functionality:

| Prompt | Tools Used |

|--------|-----------|

| "Show me my lab results from the last year and flag anything outside reference ranges" | get_lab_results |

| "Am I up to date on all my vaccinations?" | get_immunizations, mc_get_immunizations |

| "Give me a complete health summary — profile, medications, allergies, and recent labs" | get_health_overview |

| "What medications am I currently on according to AHS Connect Care?" | mc_get_medications |

| "Show me my upcoming appointments and any messages from my doctors" | mc_get_visits, mc_get_messages |

| "Download my latest diagnostic imaging report and explain the findings" | get_diagnostic_imaging, download_attachment |

| "Show me my blood work trends over the last 3 years for CBC and lipids" | get_lab_results (with test_name filter) |

| "Do I have any active referrals or pending orders?" | mc_get_referrals, mc_get_upcoming_orders |

Architecture

The MCP server acts as a passthrough to Alberta's public health portals. There is no official API — the REST endpoints were reverse-engineered from the portal web applications. The server authenticates as the user (via browser-based SSO), then makes the same API calls the portals' own frontend JavaScript makes. All data accessed belongs to the authenticated user.

Claude Desktop ──MCP (stdio)──▶ MCP Server (local) ──REST──▶ myhealthrecords.alberta.ca
                                     │                  └──REST──▶ myahsconnect.albertahealthservices.ca (MyChart)
                                     │
                                     └──Puppeteer──▶ account.alberta.ca (SSO login)

Claude Desktop ──HTTPS──▶ MCP Server (Azure Canada Central) ──REST──▶ Same endpoints
                               │
                          OAuth 2.1/PKCE
                               │
                     SSO cookies encrypted INTO the access token
                     (zero server-side storage)

Local Mode (stdio)

• Transport: stdio (local Claude Desktop)
• Auth: Browser-based via Puppeteer — user logs in through the real Alberta SSO page
• Session: Encrypted cookie storage (AES-256-GCM) at ~/.mhr-records/session.enc

Remote Mode (OAuth)

• Transport: Streamable HTTP over HTTPS
• Auth: OAuth 2.1 with PKCE — Claude Desktop acts as an OAuth client
• Session: Zero server-side storage — SSO cookies are encrypted into the OAuth access token itself. The server is fully stateless.
• Infrastructure: Azure Container Apps (Canada Central) — HIA/POPA compliant

Both modes share the same 48 tools and session keepalive logic. Session timeout is ~10 minutes per system. Tools auto-keepalive both MHR and MyChart on each call.

Auth Flow

The auth flow navigates to the Alberta SSO login page directly. After login, sessions for both MHR and MyChart are established using the shared SSO cookies. Puppeteer includes stealth measures to avoid WAF bot detection.

account.alberta.ca/ui/sign-in/signin
  → User enters MyAlberta credentials (or auto-login via persistent browser profile)
  → SSO session cookies established

myahsconnect.albertahealthservices.ca/MyChartPRD/
  → SAML auto-authenticates via shared SSO (no re-prompt)
  → MyChart session cookies + CSRF token established

myhealthrecords.alberta.ca
  → Auto-authenticates via shared SSO cookies
  → MHR session cookies established

Puppeteer handles this automatically. The persistent browser profile at ~/.mhr-records/browser-profile preserves SSO cookies across sessions, enabling auto-login without re-entering credentials.

Tools (48)

Session Management

| Tool | Description |

|------|-------------|

| connect_account | Opens Chrome for MyAlberta SSO login. Captures and encrypts session cookies for both MHR and MyChart. |

| check_connection | Verifies session is active, returns time remaining. Also serves as keepalive. |

| disconnect_account | Clears stored encrypted session data. |

Health Data (MHR)

Note: As of March 2026, Alberta removed the Control-Mapping-Id header requirement from most MHR endpoints. Only medications still requires it (CMID 8050).

| Tool | Description | API Endpoint |

|------|-------------|-------------|

| get_health_overview | Comprehensive health overview from both MHR and MyChart in a single call | Multiple |

| get_user_profile | User profile and authorized records (MHR) | /api/phr/v1/user |

| get_lab_results | Lab test results with date/name filtering (MHR) | /api/phr/v1/labresult/getData |

| get_diagnostic_imaging | X-rays, ultrasounds, echocardiograms, CT/MRI (MHR) | /api/phr/v1/labresult/getData |

| get_immunizations | Vaccine records — dates, names, sources (MHR) | /api/phr/v1/myhealth/immunization-data-manager |

| get_medications | Current and past prescriptions (MHR) | /api/phr/v1/medication (CMID: 8050) |

| get_referrals | Specialist referral records (MHR) | /api/phr/v1/referral |

| get_vitals | Clinical vitals — pulse, temp, respiratory rate (MHR) | /api/phr/v1/VitalSigns |

| get_blood_oxygen | SpO2 saturation readings (MHR) | /api/phr/v1/myhealth/blood-oxygensaturation-data-manager |

| get_blood_pressure | Blood pressure readings (MHR) | /api/phr/v1/myhealth/blood-pressure-data-manager |

| get_height_weight | Height, weight, and BMI trends (MHR) | height, weight, BMI endpoints |

| get_exercise | Exercise and physical activity records (MHR) | /api/phr/v1/exercise |

| get_procedures | Medical procedure records — surgeries, biopsies (MHR) | /api/phr/v1/procedure |

| get_blood_glucose | Blood glucose monitoring for diabetes management (MHR) | /api/phr/v1/myhealth/blood-glucose-data-manager |

| get_sleep | Sleep session records — duration and quality (MHR) | /api/phr/v1/myhealth/sleep-session-data-manager-v2 |

| get_dietary_intake | Food and nutrition tracking data (MHR) | /api/phr/v1/myhealth/dietary-intake-data-manager |

| get_insulin | Insulin injection and usage records (MHR) | insulin-injection + insulin-injection-use endpoints |

| get_peak_flow | Peak expiratory flow for asthma monitoring (MHR) | /api/phr/v1/myhealth/peak-flow-data-manager |

| get_waist_circumference | Waist circumference measurements (MHR) | /api/phr/v1/myhealth/extendable-data-manager/waist-circumference |

| get_symptom_journal | Logged symptoms and health concerns (MHR) | /api/phr/v1/myhealth/extendable-data-manager/concern |

| download_attachment | Downloads PDF reports from lab/imaging results (MHR) | /api/phr/v1/attachment/{id}/download |

Health Data (MyChart / AHS Connect)

MyChart tools access data from AHS Connect Care (myahsconnect.albertahealthservices.ca/MyChartPRD/). All MyChart tools are prefixed with mc_ and require a __RequestVerificationToken CSRF header.

| Tool | Description |

|------|-------------|

| mc_get_visits | Past and upcoming appointments (MyChart) |

| mc_get_health_summary | Health summary overview (MyChart) |

| mc_get_allergies | Allergy list (MyChart) |

| mc_get_health_issues | Active diagnoses and conditions (MyChart) |

| mc_get_care_team | Care team providers (MyChart) |

| mc_get_messages | Patient messages and conversations (MyChart) |

| mc_get_medical_history | Medical and family history (MyChart) |

| mc_get_documents | Clinical documents (MyChart) |

| mc_get_upcoming_orders | Upcoming tests and procedures (MyChart) |

| mc_get_test_results | Test results from AHS labs, including scan images (MyChart) |

| mc_get_historical_results | Historical trend data for specific test result components (MyChart) |

| mc_get_family_tree | Family tree and pedigree (MyChart) |

| mc_get_goals | Patient and care team goals (MyChart) |

| mc_get_referrals | Referral details from AHS (MyChart) |

| mc_get_medications | Medications from AHS (MyChart) |

| mc_get_immunizations | Immunization records from AHS (MyChart) |

| mc_get_appointment_requests | Pending appointment requests awaiting scheduling (MyChart) |

| mc_download_document | Download scan images or documents from test results (MyChart) |

| mc_list_proxy_access | List available patient records — own and shared/proxy (MyChart) |

| mc_switch_context | Switch to viewing a different patient's records via proxy access (MyChart) |

Find a Provider (Public — No Login Required)

Search Alberta's public provider directory at albertafindaprovider.ca. These tools work without an Alberta account and return public information only — no PHI is involved.

| Tool | Description |

|------|-------------|

| find_provider | Find clinics by location (postal code, address, or lat/lng) with filters for radius, accepting-new-patients, gender preference, language, PCN, and services |

| search_provider_by_name | Look up doctors and nurse practitioners by name (partial OK) |

| find_provider_by_language | Find clinics with at least one provider who speaks a specific language (Mandarin, Punjabi, Arabic, Spanish, French, etc.) near a location |

| get_provider_details | Full details for a specific clinic, physician, or nurse practitioner by ID |

Example Queries

• "Give me a complete health summary — profile, immunizations, medications, and recent labs"
• "Show me how my blood work has changed over the past year"
• "Am I up to date on my vaccinations?"
• "Download my latest ECG report"
• "Explain my most recent lab results in plain language"
• "Show me my upcoming appointments from MyChart"
• "What medications am I on according to AHS Connect Care?"
• "Do I have any active referrals in MyChart?"
• "Show me my care team and any messages from my doctors"
• "Show me my procedure history"
• "Do I have access to any shared or family health records?"
• "Find me a family doctor accepting new patients near T6G 1L7"
• "Find a clinic with virtual appointments and online booking within 5 km"
• "Find a doctor who speaks Mandarin near downtown Calgary"
• "Look up Dr. Mahdavi's clinic"

Project Structure

ab-health-mcp/
├── src/
│   ├── index.ts                    # MCP server entry point (stdio transport, 48 tools)
│   ├── types.ts                    # TypeScript interfaces for API responses
│   ├── api/
│   │   ├── auth-client.ts          # Puppeteer SSO auth with stealth measures
│   │   ├── programmatic-auth.ts    # Server-side Puppeteer auth (for OAuth flow)
│   │   ├── mhr-client.ts           # MHR REST API client with cookie jar + retry-on-401
│   │   └── mychart-client.ts       # MyChart REST API client with cookie jar + CSRF + retry
│   ├── auth/
│   │   └── session-manager.ts      # AES-256-GCM encrypted session storage (v2)
│   ├── helpers/
│   │   ├── session-helpers.ts      # Session validation, cross-keepalive
│   │   └── content-helpers.ts      # PDF text extraction + image rendering (mupdf WASM)
│   ├── server/
│   │   ├── http-index.ts           # HTTP entry point with OAuth 2.1 + portal modes
│   │   ├── create-server.ts        # MCP server factory (registers all 48 tools with schemas)
│   │   ├── oauth-provider.ts       # OAuth 2.1 provider (zero-storage token architecture)
│   │   ├── token-crypto.ts         # AES-256-GCM token encryption/decryption
│   │   └── session-context.ts      # AsyncLocalStorage for per-request sessions
│   ├── tools/
│   │   ├── tool-factory.ts         # Factory functions with pagination (offset/max_results)
│   │   ├── simple-mhr-tools.ts     # 14 simple MHR tools via factory
│   │   ├── simple-mychart-tools.ts # 11 simple MyChart tools via factory
│   │   └── ...                     # Individual tool files (see Tools section)
│   └── utils/
│       ├── errors.ts               # Typed errors (SessionExpired, AuthRequired, etc.)
│       ├── logger.ts               # Stderr logger (no PII)
│       └── formatters.ts           # Date format conversion utilities
├── static/                         # Landing page (myaihealth.ca)
│   ├── index.html                  # Single-page site (Tailwind CSS)
│   ├── hero.png                    # Hero illustration
│   ├── og-image.png                # Open Graph preview image (1200×630)
│   ├── flatIcons.png               # Icon set
│   └── favicon.png                 # Site favicon
├── api/                            # Azure Functions for landing page
│   └── request-access/             # Access request form handler (ACS email + SAS URL)
├── portal/                         # Next.js web portal (chat UI)
├── Dockerfile                      # Multi-stage build for Azure Container Apps
├── staticwebapp.config.json        # Azure Static Web Apps config
├── scripts/
│   └── test-auth.ts                # Standalone auth flow test script
├── package.json
└── tsconfig.json

Build & Test

npm install          # Install dependencies
npm run build        # TypeScript compilation
npm run lint         # Type checking (tsc --noEmit)
npm test             # Run tests (vitest)

Build .mcpb Bundle

The .mcpb file is the one-click installer for Claude Desktop. Use the `mcpb` CLI — never raw zip.

npm run build                          # compile TypeScript first
mcpb validate manifest.json            # check manifest
mcpb pack . ab-health-mcp.mcpb         # build bundle (~16MB)

Upload to Azure Blob Storage for distribution:

az storage blob upload \
  --account-name myaihealthdownloads --container-name downloads \
  --name ab-health-mcp.mcpb --file ab-health-mcp.mcpb \
  --overwrite --auth-mode key

Note: .mcpbignore excludes dev dependencies, source code, docs, and non-runtime directories. Never use raw zip — it will include everything and produce a 1GB+ file instead of 16MB.

⚠️ Critical: All directory patterns in .mcpbignore MUST be root-relative (e.g., /src/ not src/). Bare patterns match inside node_modules/ and silently strip critical runtime code. See COPILOT.md for full build documentation.

Test Auth Flow

npx tsx scripts/test-auth.ts

Opens a browser, you log in, and it verifies session + API calls work.

Accessibility Benefits

Conversational AI removes the barriers that make health portals difficult to use — complex navigation, medical jargon, visually dense layouts, and multiple systems to learn.

| Benefit | Description |

|---------|-------------|

| 🎤 Voice interaction | Speak naturally to access health data — no typing required. Claude Desktop supports voice input, helping people with motor disabilities, vision impairments, or repetitive strain injuries. |

| 📖 Plain language explanations | AI translates medical jargon into language you understand. Research complex conditions and arrive at appointments informed and prepared. |

| 🧭 No complex navigation | One conversation replaces dozens of clicks across two separate portals. No menus, tabs, or page loads — especially helpful for elderly users or anyone overwhelmed by complex interfaces. |

| 🔊 Screen reader friendly | Text-based responses work naturally with screen readers, unlike visually dense portal layouts with charts, tables, and multi-column designs. |

| 📋 Doctor visit preparation | Generate PDF summaries, organize health concerns, and prepare questions before appointments. |

| 🌍 Multilingual support | Claude can explain health data in languages other than English — important for Alberta's diverse communities. |

| 👨‍👩‍👧 Caregiver empowerment | Family members managing health for elderly parents or dependents can quickly pull comprehensive views across all data sources without learning two portal systems. |

⚕️ Important: Not medical advice.

This tool provides information retrieval, not professional medical advice. It is not a medical device or health service. Always discuss findings, concerns, and health decisions with your doctor. AI can identify patterns but cannot diagnose or treat conditions. If you are experiencing a medical emergency, call 911 immediately.

Security

This project handles protected health information under Alberta's Health Information Act (HIA) and Protection of Privacy Act (POPA).

Non-Negotiable Rules

1. No PII in logs. No names, health data, cookie values, or identifiers in log output.
2. No health data stored by the extension. Only encrypted session cookies are persisted (local mode) or encrypted into tokens (remote mode). All health data is returned to Claude and discarded by the extension. See Anthropic's privacy policy for how Claude handles conversation data.
3. Credentials never touch the server. In local mode, users enter credentials in the browser via Puppeteer. In remote mode, credentials are entered on the Alberta SSO page in the user's own browser.
4. Encryption at rest. Local: AES-256-GCM at ~/.mhr-records/session.enc. Remote: AES-256-GCM in the OAuth access token (held on user's machine by Claude Desktop).
5. Zero server-side storage (remote mode). The server stores nothing — no database, no user data. Session cookies are encrypted into the OAuth token. If the server is compromised, there is no stored user data to leak.
6. Canadian data residency (our infrastructure). Azure Canada Central for HIA/POPA compliance. Note: Claude (Anthropic) processes conversations on US-based servers.
7. No clinical action suggestions. The MCP server never flags lab values, suggests calling healthcare providers, recommends medication changes, or cross-references clinical data to surface concerns. All clinical interpretation is Claude's responsibility.

Passthrough Principle

The MCP server is a pipe. It does NOT:

• Interpret or analyze health data (that's Claude's job)
• Cache health data beyond the session
• Calculate trends or averages
• Make medical assessments
• Store any health information
• Suggest clinical actions (calling doctors, 911, changing medications, etc.)

Dependencies

| Package | Purpose |

|---------|---------|

| @modelcontextprotocol/sdk | MCP server framework |

| puppeteer-core | Browser automation for SSO login (requires system Chrome) |

| tough-cookie | Cookie jar management and serialization |

| undici | HTTP client |

| express | HTTP server for remote/OAuth mode |

| express-rate-limit | Rate limiting for OAuth endpoints |

| mupdf | PDF text extraction and image rendering (WASM) |

Landing Page

The project has a landing page at www.myaihealth.ca for explaining the extension and distributing downloads. Includes Open Graph meta tags for rich link previews in chat apps and a section recommending the free PubMed connector for medical research.

• Hosting: Azure Static Web Apps (Free tier)
• API function: /api/request-access — accepts form submissions, generates a 3-month SAS download link for the .mcpb file, and emails the link via Azure Communication Services. Email includes privacy messaging that pre-frames the Claude Desktop security warning.
• API function: /api/check-update — called by the extension to check for updates. Returns a 30-minute SAS download URL when a newer version is available.
• Email: noreply@myaihealth.ca via Azure Communication Services (custom domain, verified SPF/DKIM/DMARC)
• Download storage: Azure Blob Storage (myaihealthdownloads account, downloads container)
• Analytics: Azure Application Insights (myaihealth-insights) — anonymous visitor tracking (pageviews, sessions, geography, referrers). No cookies used (disableCookiesUsage: true). JS SDK loaded on all pages (index, demo, terms, 404).
• Privacy messaging: Landing page and email explain that the Claude Desktop "grant access" warning applies to all extensions and that the local architecture is an intentional privacy feature (data flows directly between user and Alberta Health, no middleman)

Deployment

# Deploy static site + API function
swa deploy ./static \
  --api-location ./api \
  --api-language node --api-version 18 \
  --deployment-token <TOKEN> \
  --env production

Required App Settings

| Setting | Description |

|---------|-------------|

| STORAGE_CONNECTION_STRING | Azure Blob Storage connection string |

| STORAGE_CONTAINER | Container name (default: downloads) |

| MCPB_BLOB_NAME | Blob name (default: ab-health-mcp.mcpb) |

| NOTIFY_EMAIL | Email to receive access request notifications |

| ACS_CONNECTION_STRING | Azure Communication Services connection string |

| ACS_FROM_EMAIL | Verified sender email (default: noreply@myaihealth.ca) |

Roadmap

• [x] Phase 1 + 2: MHR Tools — 24 tools for My Health Records (lab results, immunizations, medications, vitals, procedures, imaging, and more)
• [x] MyChart Integration — 20 tools for AHS Connect Care (visits, allergies, care team, messages, documents, scan downloads, proxy access, etc.)
• [x] Session auto-refresh — Cross-keepalive between MHR and MyChart, retry-once-with-keepalive on 401/403
• [x] Desktop Extension — One-click .mcpb install for Claude Desktop
• [x] Landing Page — myaihealth.ca with gated download access via Azure Communication Services email
• [x] Open Source — Public repository with security-audited codebase
• [x] Phase 3: Remote Mode — OAuth 2.1 remote connector, Azure Container Apps deployment, zero-storage architecture (implemented, not yet productized)
• [x] Update notifications — In-app update check via /api/check-update with direct download link (30-minute SAS URL)
• [ ] MFA support — Relay MFA challenges for Alberta accounts with multi-factor enabled

Privacy Policy

This project accesses personal health information on your behalf. There are two delivery paths with different data flows:

Data flow

| | .mcpb (Claude Desktop extension) | Portal beta (web chat) |

|---|---|---|

| Health data route | Your machine → Alberta Health (direct, no middleman) | Your browser → Our server (Azure Canada Central) → Alberta Health |

| AI provider | Anthropic Claude (US-based servers) | Azure OpenAI (Microsoft, Canada East) |

| Conversation data leaves Canada? | Yes — sent to Anthropic (US) | No — processed within Canada |

| Health data stored by us? | No | No — in memory only during session |

| AI training on your data? | Opt-in via Anthropic settings | No (Azure OpenAI API data is never used for training) |

Details

• No health data is stored by the extension. Data fetched from Alberta Health portals is returned to the AI and immediately discarded. Nothing is written to disk or any server by this extension.
• Session cookies only. The only data persisted is an encrypted session cookie (AES-256-GCM) stored locally at ~/.mhr-records/session.enc (local mode) or in the browser (portal mode). It contains authentication state only — no health data.
• Credentials never transmitted to us. You log in through the real Alberta SSO page. Credentials are entered on Alberta's own page and never touch this extension's server.
• Canadian data residency (portal path). The portal uses Azure Canada Central (server) and Azure OpenAI Canada East (AI inference). All portal-path processing stays within Canada (HIA/POPA compliant).
• Claude Desktop path exception. When using the .mcpb extension with Claude Desktop, conversations are processed by Anthropic (US-based servers). See Anthropic's privacy policy for details.
• First-run privacy consent. On first connection via Claude Desktop, a notice explains that health data will be sent to Anthropic's US servers. You must acknowledge before proceeding.
• Azure OpenAI data handling. Microsoft Azure OpenAI may retain prompts for up to 30 days for abuse monitoring unless an opt-out is approved. Data is never used for model training. See Azure OpenAI data, privacy, and security.
• Data completeness. Health records may not reflect your complete medical history. Results may take 24–72 hours to appear after testing. Records from out-of-province providers may not be included.
• Anonymous website analytics only. The landing page (myaihealth.ca) uses Azure Application Insights to collect anonymous visitor statistics — page views, session counts, country, browser, and referral source. No cookies are used, no personally identifiable information is collected, and no health data is involved. The MCP extension itself collects no analytics or telemetry.

Full privacy policy: https://www.myaihealth.ca/terms.html

For privacy concerns, email support@myaihealth.ca or open an issue at https://github.com/JCrossman/ab-health-mcp/issues.

License

MIT