Summary
n8n runs, started and checked from where the request arrives.
The three general calls make any n8n workflow callable in conversation, and the fourth gives patient tasks a fixed shape - so the same request does not arrive formatted differently every time.
What it is
A bridge between an MCP client and an n8n instance, shaped for healthcare work. Three of its calls are general - list the active workflows, trigger one with a payload, check an execution's status - and one is purpose-built for sending a structured patient task into a workflow.
What you get
- The active workflows on your n8n instance, listed
- A workflow triggered by name over its webhook, with a JSON payload you supply
- The status of a run, by execution id
- A patient task sent into a named workflow as structured fields - patient id and task type - rather than free-form JSON
- Payloads validated before they are sent
Requirements
A recent Node, an n8n instance - cloud or self-hosted - with API access, and an n8n API key. Importable example workflows and a HIPAA compliance guide ship with the repository; the guide is documentation, and the controls themselves remain on your n8n instance.