Skip to main content
Glama
cldr-steven-matison

Edge Flow Manager MCP Server

Related Servers

Alternatives to Edge Flow Manager MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables Claude to inspect and operate Apache Airflow over its REST API, providing read tools and safe write operations (gated by read-only mode) for managing DAGs, runs, tasks, and pools.
      14
      MIT
    • 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
      -
    • F
      license
      A
      quality
      D
      maintenance
      Enables LLM agents to query and explore Cloudera Hive virtual warehouses through tools like list_databases, list_tables, describe_table, get_table_sample, and execute_query with read-only safety.
      5
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP server exposing Flowsery analytics and AI-detected issues via 17 GET tools, enabling natural language queries in compatible clients.
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      Enables read-only monitoring and diagnostics of Apache Flink clusters through a JobManager REST endpoint, including job, checkpoint, backpressure, TaskManager, and multi-cluster overviews with LLM-friendly summaries.
      21
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to query an F5 BIG-IP over read-only iControl REST, retrieving system/version and failover state, virtual server and pool member health, and any other readable /mgmt/tm/ object through natural-language questions. Every tool issues GET requests only, with paging for large object lists and both server-side path blocking and BIG-IP RBAC guarding against changes.
      1
      MIT

    TDQS

    A3.9/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: classes, agents, manifests, monitors, flows, resources. Even similar pairs (e.g. efm_get_manifest vs efm_get_manifest_by_id) are separated by query key, and efm_list_resources vs efm_list_class_resources differ by scope.

    Naming Consistency5/5

    All tools follow a consistent efm_<verb>_<noun> snake_case pattern. List/get are used predictably, and compound nouns like class_monitor and class_resources are clear. Minor suffix variations (by_id) are still systematic.

    Tool Count5/5

    12 tools is a well-scoped set for an edge flow manager: enough to cover the main entities (agent classes, agents, flows, manifests, resources) without bloat.

    Completeness3/5

    The read/query surface is thorough: classes, agents, manifests, flows, resources, health. Validation is included enough to test flows. However, there are no publish/update/delete operations, and resource assignment is only readable, so management actions are missing.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues