A
licenseNot graded
qualityA
maintenanceEnables reading, querying, and editing Node-RED flows.json files through MCP, providing tools for node management, layout validation, and deployment.
MIT
nifi-mcp
Related Servers
Alternatives to nifi-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables management of multiple N8N workflow automation instances through MCP. Supports listing, creating, updating, deleting, executing workflows and monitoring their executions across different N8N environments.114 npmMIT
- AlicenseAqualityCmaintenanceMCP server for Dataiku DSS REST APIs, enabling flow analysis and day-to-day operations on projects, datasets, recipes, jobs, scenarios, folders, variables, connections, and code environments.948 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables DAG management, monitoring, debugging, and connection testing for Apache Airflow through the MCP protocol.-
- AlicenseNot gradedqualityCmaintenanceProvides a runtime-only MCP server and REST API for datasets, connections, flows, pipelines, and cron scheduling, without server-side LLM execution or entity-authoring admin UI, enabling clients to operate and manage these resources programmatically.Apache 2.0
- AlicenseCqualityDmaintenanceProvides a standardized way for MCP clients to interact with Apache Airflow's REST API, supporting operations like DAG management and monitoring Airflow system health.68822 PyPI178MIT
TDQS
B3.2/5.0
Scored across 35 tools
Disambiguation4/5
Most tools have distinct resource/action pairs, and descriptions clarify overlaps such as apply_flow_spec versus granular create_* calls. However, create/import/replace/apply_flow_spec and schedule_process_group versus set_run_status could still create confusion in edge cases.
Naming Consistency4/5
All tools share the nifi_ prefix and snake_case, and the vast majority follow a verb_noun pattern. Minor deviations like nifi_about and nifi_current_user keep it from being perfectly uniform, but the convention is highly predictable.
Tool Count2/5
35 tools is heavy for this surface, with many granular list/get/create/update tools that could be consolidated through apply_flow_spec or grouped by resource. While NiFi is genuinely complex, the count exceeds a comfortable selection range for an agent.
Completeness4/5
The surface covers most core flow lifecycle operations: process groups, processors, connections, controller services, parameter contexts, health, queues, and import/export/apply. Notable gaps remain around dedicated create/update port tools (though apply_flow_spec can create ports) and user/group policy management.
Maintenance
ActivityMaintained
ResponsivenessNo issues