trigger_workflowLABSCO 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.
Setup effort
Build from source — git clone https://github.com/pratapsfdc22-dev/careflow-mcp.git
USE CASES
01
Kicking off an automation without opening n8n
List the active workflows, then trigger the one you mean with the payload it expects.
02
Filing a patient task in a fixed shape
Send patient id and task type as structured fields, so the downstream steps receive the same format every time.
03
Finding out whether the run worked
Check the execution status by id, rather than going to read the n8n log.
04
Wiring a new workflow in and testing it
Import one of the example workflows, confirm it shows up in the list, trigger it once and read the execution status.
4 tools
Listed in project docs. Your client may show a different list.
list_workflowsget_workflow_statuscreate_patient_taskBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Requires
- Node.js >= 18.0.0
- N8N_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/pratapsfdc22-dev/careflow-mcp.git
cd careflow-mcp
npm install
npm run buildMCP Clients
Claude Desktop — local build
CLAUDE DESKTOP — LOCAL BUILD · JSON
{
"mcpServers": {
"n8n-workflow": {
"command": "node",
"args": [
"<YOUR_PATH_TO_CAREFLOW_MCP>/dist/index.js"
],
"env": {
"N8N_BASE_URL": "<YOUR_N8N_BASE_URL>",
"N8N_API_KEY": "<YOUR_N8N_API_KEY>",
"N8N_WEBHOOK_SECRET": "<YOUR_N8N_WEBHOOK_SECRET>"
}
}
}
}
