PrimeCare MCP
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., "@PrimeCare MCPRun the clinic flow brief for today."
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.
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: Business Operations Agent Kit
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.
Read-only senior-care exit routes, duplicate-referral deadlines, and templates; no PII or sending.
DEA registration & controlled-substance authority tracking for prescribers — read-only demo.
Read-only MVR preflight for trust, permission, evidence gaps, and African market-entry readiness.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceRead-only health and storage diagnostics for an enrolled CMDOP machine fleet.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceMCP server that provides read-only business operations tools: list businesses, get status, identify missing inputs, and prepare email drafts/attachment manifests from synthetic evidence, with strict no-send/no-write safeguards.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
- AlicenseNot gradedqualityCmaintenanceEnables warehouse operations agents to inspect tasks, deliveries, stock, and KPIs, and to attempt write operations in shadow mode with human approval and segregation of duties enforced as code.MIT