PrimeCare MCP
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
PrimeCare MCP Hackathon Demo
DEMO ENVIRONMENT — SYNTHETIC DATA ONLY. This clone refuses non-local database URLs. It must never be configured with production credentials, patient data, or external messaging or storage services.
PrimeCare MCP is an agentic clinic-operations dashboard built for the Amazon Developer Hackathon 2026. It combines a React (Vite) frontend, a Node/Express backend, and a self-hosted MCP server.
What it demonstrates
Material 3 queue cards with alternating blue row surfaces.
A PrimeCare Agent page that simulates an Alexa+ interaction in the browser.
A self-hosted MCP server at
http://127.0.0.1:4102/mcp, using MCP Streamable HTTP.A read-only
primecare_clinic_flow_briefMCP workflow that coordinates four aggregate checks: queue flow, rule-based BP follow-up review, outreach workload, and access-review workload. It never returns patient identity, contact, or clinical-note data and never makes clinical, eligibility, or security decisions.
Related MCP server: clearon-ops-audit-mcp
Requirements
Node.js 22 or later
npm
Run the synthetic demo
npm run install:all
npm run demo:bootstrap --prefix backend
npm run devOpen the URL printed by Vite. If another local project is already using the default ports, run the frontend with a different port and set VITE_API_PROXY_TARGET and VITE_MYKAD_AGENT_BASE to the matching local services.
Demo sign-in: demo.admin@invalid.test / DemoPass2026!. These credentials are intentionally public and work only with synthetic local data.
Local services
npm run dev starts the backend, frontend, MyKad demo agent, and MCP HTTP server together. The MCP endpoint is http://127.0.0.1:4102/mcp by default.
To run components separately:
npm run dev:backend
npm run dev:frontend
npm run dev:mykad-agent
npm run dev:mcp-httpDemo data and safety
npm run demo:bootstrap --prefix backend creates backend/hackathon-demo.sqlite locally and seeds it with synthetic data. The database is ignored by Git. Do not use production data, production credentials, or external messaging, storage, import, reconciliation, or deployment scripts in this demo clone.
To reset the demo, stop the backend and delete backend/hackathon-demo.sqlite plus any adjacent -wal and -shm files, then run the bootstrap command again.
License
This project is released under the MIT License.
This server cannot be deployed
Maintenance
Related MCP Connectors
Read-only dental practice aggregates: patients seen, procedure mix, and letter activity.
Aggregate compliance, held billing and administrative work insights for veterinary practices.
Read-only senior-care exit routes, duplicate-referral deadlines, and templates; no PII or sending.
Read clinic appointments, patients and finances; manage bookings and patient registration.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceRead-only health and storage diagnostics for an enrolled CMDOP machine fleet.Apache 2.0
- AlicenseBqualityCmaintenanceEnables read-only operational audits of schedulers, recurring job health, delivery failures, overdue runs, gateway/MCP health, and lock-file inventory without modifying inspected systems.11MIT
- AlicenseAqualityCmaintenanceExposes read-only account-health tools for scores, trends, claims checks, risks, pipeline, and next actions, with audience-scoped output for internal or customer views.6MIT
- AlicenseBqualityBmaintenanceProvides read-only access to multiple production services with unified status and timeline tools for cross-service monitoring and diagnostics.131MIT