Skip to main content
Glama
Sign In
nifi-mcp

nifi-mcp

by newen-systems
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to nifi-mcp

No user-submitted related servers found.

    Related Servers

    • Rosetta NiFi MCP

      gaojie197710-tech
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables an AI assistant to turn a plain-language description into a working Apache NiFi 2.x flow, validate and layout the canvas, run test data, golden-file replays and diagnostics, and commit only verified versions to the NiFi Registry. It exposes 44 read-or-write tools for exploring, building, testing, debugging and releasing flows, staying read-only unless writes are explicitly enabled.
      2
      Elastic 2.0

    • nifi-mcp

      alexxonline
      F
      license
      B
      quality
      C
      maintenance
      Enables AI agents to manage and interact with Apache NiFi through its REST API, covering process groups, processors, connections, queues, provenance, and version control via natural language tool calls.
      28
      -

    • agent-workflow

      GallonShih
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients such as Claude Desktop, Claude Code, and Cursor to discover node types, author and validate typed multi-agent workflow files, launch runs against a workspace, and retrieve run status, node outputs, and workspace change details.
      MIT

    • NiFiMCP

      nifimcp
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to understand Apache NiFi flows, investigate failures with cited evidence, and draft reviewable flow files while keeping live NiFi access read-only.
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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 recent community issues

    Resources