Production-ready MCP server for healthcare workflow automation with n8n - HIPAA-compliant patient task management and care coordination
Careflow MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Careflow MCP directly instead of describing what you should do. Production-ready MCP server for healthcare workflow automation with n8n - HIPAA-compliant patient task management and care coordination.
Production-ready healthcare workflow automation powered by n8n and the Model Context Protocol. Enables Claude and other AI assistants to trigger HIPAA-compliant patient task management workflows through natural language.
Once Careflow MCP is connected, these are the calls the assistant has available:
trigger_workflow — Triggers an n8n workflow by name with JSON payloadlist_workflows — Lists all active workflows from n8nget_workflow_status — Checks execution status by IDcreate_patient_task — Sends structured patient task to workflowBuild — The Build tool exposed by this serverYou will need 3 environment variables: N8N_BASE_URL, N8N_API_KEY, N8N_WEBHOOK_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Careflow MCP's toolset — trigger_workflow, list_workflows, get_workflow_status and 2 more — is a fair guide to whether it matches your workflow. It is maintained by pratapsfdc22-dev; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| trigger_workflow | Triggers an n8n workflow by name with JSON payload |
| list_workflows | Lists all active workflows from n8n |
| get_workflow_status | Checks execution status by ID |
| create_patient_task | Sends structured patient task to workflow |
| Build | The Build tool exposed by this server. |
**Using npm global install:**
```json
{
"mcpServers": {
"n8n-workflow": {
"command": "careflow-mcp",
"env": {
"N8N_BASE_URL": "https://your-n8n-instance.com",
"N8N_API_KEY": "your_api_key_here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| N8N_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| N8N_API_KEY | Credential the server authenticates with. | Yes |
| N8N_WEBHOOK_SECRET | Credential the server authenticates with. | Yes |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.