Careflow-MCP

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.

🏥Healthcare-Ready: Includes comprehensive HIPAA compliance documentation and patient task management workflows.

- 🚀Trigger Workflows- Execute n8n workflows via webhook with custom payloads
- 📋List Workflows- Query all active workflows from your n8n instance
- 📊Check Status- Monitor workflow execution status in real-time
- 🏥Healthcare-Ready- Built-in support for patient task workflows
- 🔒Type-Safe- Full TypeScript support with Zod validation
- ⚡Production-Ready- Comprehensive error handling and logging
- 🛠️MCP Standard- Compatible with Claude Desktop and other MCP clients

- [Case Studies](.[/case-studies/README.md)]- 5 real-world implementation examples with ROI metrics
- HEALTHCARE.md- Comprehensive HIPAA compliance guide (our differentiator!)
- Example Workflows- Importable n8n workflow JSON files

# 1. Import workflow to n8n examples/healthcare-patient-task-workflow.json # 2. Configure credentials in n8n # 3. Ask Claude: "Create a patient task for ID P12345 in the Patient Care workflow"

Install directly frommcp.sousing Smithery:

# Clone the repository git clone https://github.com/pratapsfdc22-dev/careflow-mcp.git cd careflow-mcp # Install dependencies npm install # Build the project npm run build # Link globally (optional) npm link

# Base URL of your n8n instance N8N_BASE_URL=https://your-n8n-instance.com # n8n API Key (Settings > API > Create API Key) N8N_API_KEY=n8n_api_xxxxxxxxxxxxxxxxxxxxxxxx # Optional: Webhook Secret N8N_WEBHOOK_SECRET=your_webhook_secret

{ "mcpServers": { "n8n-workflow": { "command": "node", "args": [ "/path/to/careflow-mcp/dist/index.js" ], "env": { "N8N_BASE_URL": "https://your-n8n-instance.com", "N8N_API_KEY": "your_api_key_here", "N8N_WEBHOOK_SECRET": "your_webhook_secret" } } } }

{ "mcpServers": { "n8n-workflow": { "command": "careflow-mcp", "env": { "N8N_BASE_URL": "https://your-n8n-instance.com", "N8N_API_KEY": "your_api_key_here" } } } }

// Ask Claude: "Trigger the 'Customer Onboarding' workflow with this data: { email: 'user@example.com', name: 'John Doe' }"

// Ask Claude: "Show me all active n8n workflows"

// Ask Claude: "Check the status of execution ID: abc123"

// Ask Claude: "Create a high-priority follow-up task for patient ID P12345 in the 'Patient Care' workflow, due tomorrow"

careflow-mcp/ ├── src/ │ ├── index.ts # Main MCP server implementation │ └── types.ts # TypeScript types and Zod schemas ├── dist/ # Compiled JavaScript (generated) ├── .env.example # Environment variable template ├── .gitignore # Git ignore rules ├── package.json # NPM package configuration ├── tsconfig.json # TypeScript configuration └── README.md # This file

Triggers an n8n workflow by name with optional JSON payload.

{ workflowName: string; // Name of the workflow payload?: object; // Optional JSON data }

{ "success": true, "workflowId": "abc123", "workflowName": "Customer Onboarding", "response": { ... } }

Lists all active workflows from n8n instance.

{ "success": true, "count": 5, "workflows": [ { "id": "abc123", "name": "Customer Onboarding", "active": true, "createdAt": "2024-01-01T00:00:00.000Z", "updatedAt": "2024-01-15T12:00:00.000Z" } ] }

Checks the execution status of a workflow run.

{ executionId: string; // Execution ID from trigger response }

{ "success": true, "execution": { "id": "exec123", "workflowId": "abc123", "finished": true, "status": "success", "startedAt": "2024-01-15T12:00:00.000Z", "stoppedAt": "2024-01-15T12:00:05.000Z" } }

Sends a structured patient task to an n8n workflow.

{ workflowName: string; // Target workflow patientId: string; // Patient identifier taskType: string; // Task type priority?: "low" | "medium" | "high" | "urgent"; description?: string; dueDate?: string; // ISO 8601 format assignedTo?: string; metadata?: object; }

{ "success": true, "workflowId": "abc123", "workflowName": "Patient Care", "task": { ... }, "response": { ... } }

The server implements comprehensive error handling with proper MCP error codes:

- Invalid Parameters-ErrorCode.InvalidParams
- Method Not Found-ErrorCode.MethodNotFound
- Internal Error-ErrorCode.InternalError

All errors include descriptive messages for debugging.
- Never commit.env- Always use.env.examplefor templates
- Rotate API keys- Regularly update your n8n API keys
- Use webhook secrets- Add authentication to webhook triggers
- Restrict API access- Use n8n's API key permissions
- Monitor logs- Check server logs for suspicious activity

# Check Node.js version node --version # Should be >= 18.0.0 # Verify environment variables cat .env # Check TypeScript compilation npm run build

- Verify the workflow name matches exactly (case-sensitive)
- Ensure the workflow is active in n8n
- Check API key has permission to access workflows

- VerifyN8N_API_KEYis correct
- CheckN8N_BASE_URLincludes protocol (https://)
- Ensure API key hasn't expired

- Verify webhook node exists in workflow
- Check webhook path matches workflow ID
- ConfirmN8N_WEBHOOK_SECRETif required
- Fork the repository
- Create a feature branch (git checkout -b feature/amazing-feature)
- Commit your changes (git commit -m 'Add amazing feature')
- Push to the branch (git push origin feature/amazing-feature)
- Open a Pull Request

MIT License - seeLICENSEfile for details.

- Built withModel Context Protocol SDK
- Powered byn8n workflow automation
- Type validation byZod

- 🐛 Issues:GitHub Issues
- 💬 Discussions:GitHub Discussions
- 📖 Documentation:Full API Reference

The AhaSlides MCP server lets AI assistants like Claude work inside AhaSlides for you. Just describe what you want in plain language — no app-switching, no coding.