Skip to main content
Glama
johannschiffer

PipelineFlow

by johannschiffer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to PipelineFlow

No user-submitted related servers found.

    Related Servers

    • mmc-mcp by modelmycontext

      mmc-mcpofficial

      modelmycontext
      F
      license
      Not graded
      quality
      F
      maintenance
      MCP server that lets AI agents execute structured business processes by exposing process steps as tools with a sequenced event bus to prevent skipping steps.
      1
      -

    • graph-engineering

      sciencemj
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that turns coding workflows into explicit execution graphs (DAG) with deterministic command execution, human-in-the-loop gates, and tamper-proof run history for Claude Code.
      5 npm
      MIT

    • gentleman

      madebyman
      A
      license
      Not graded
      quality
      B
      maintenance
      A declarative AI agent server that provides MCP for tools, A2A for agents, and AG-UI for humans, enabling interactive chat and agent orchestration.
      1
      MIT

    • super-plumber

      LUKAWI
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for managing workflow topology graphs as pure YAML files, enabling AI agents to read, create, claim, and update task nodes with a strict state machine.
      15 npm
      3
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.5/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool targets a distinct pipeline-building action: create_pipeline, add_node, connect_nodes, run_pipeline, get_node_output, export, and list are largely separable. The only mild overlap is between run_pipeline (executes and collects outputs) and get_node_output (fetches cached output), but the descriptions clarify execution vs. retrieval.

    Naming Consistency5/5

    All seven tools use a consistent snake_case verb_noun pattern (create_pipeline, add_node, connect_nodes, run_pipeline, get_node_output, list_pipelines). export_pipeline_mermaid is slightly longer but still follows the same verb_noun convention.

    Tool Count5/5

    Seven tools is well-scoped for a pipeline DAG builder/runner, covering construction, execution, inspection, and export without redundancy. Every tool earns its place.

    Completeness3/5

    The surface covers creation, node/edge building, execution, output retrieval, listing, and export, but has notable gaps: no delete_pipeline, no update/rename, and no remove_node or disconnect_nodes, so agents cannot clean up or modify an existing DAG. These missing lifecycle operations will force workarounds.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources