Skip to main content
Glama

Related Servers

Alternatives to Flow

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables external MCP clients like Claude Desktop, Claude Code, Cursor and Zed to hand work to a local crew of AI agents that plan, write, check and fix code in a folder, while also acting as an MCP client that can use their tools. Runs locally with user-supplied keys, approval-gated commands, diffable and undoable runs.
      AGPL 3.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Autonomous spec-to-product coding-agent CLI. Its MCP server exposes 34 tools over stdio: project state and task-queue ops, memory retrieve/store, code search, quality and verification reports, repo hotspots/co-changes, and structured findings/learnings.
      9,984 npm
      1,118
      Business Source 1.1
    • A
      license
      A
      quality
      F
      maintenance
      An autonomous, extensible LLM build orchestrator. Give it a repo and a goal; it decomposes the goal into tasks, edits code, and gates every change on build/tests/lint, reverting regressions. Polygot, cost-aware model selection, pluggable via entry points. Ships as an MCP server so any client can drive it in plain English.
      15
      99 PyPI
      5
      AGPL 3.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enforces a git-tracked, code-checked finite state machine that hands control between a planning director and a local Ollama implementor, exposing tools to check phase status, transition states, and run the implementor to execute plan step files one at a time. It enables a project to be planned, implemented step by step with per-step test gating, and validated before completion.
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Equips AI assistants and MCP-compatible clients with software development tools for deep research, requirements and PRD generation, user stories, task lists, codebase mapping, context curation, and full-stack project scaffolding. It also runs multi-step workflows and AI-native task management over stdio or SSE transports.
      69 npm
      MIT

    TDQS

    C2.8/5.0

    Scored across 3 tools

    Disambiguation4/5

    flow_run (planner/coder/reviewer pipeline) and flow_check (named operator checks) are distinguished by their descriptions, though both perform 'verification-like' work and could be confused in edge cases. flow_status is clearly separate as a read-only info tool.

    Naming Consistency4/5

    All three tools share a clean flow_ prefix with snake_case, which is predictable. Minor quibble: run and check are verbs while status is a noun, but the pattern remains easy to read.

    Tool Count3/5

    Three tools is on the thin side for a workflow orchestrator; run/status/check covers the basics but feels like a minimal surface. It is borderline rather than mismatched, given the focused purpose.

    Completeness3/5

    Core lifecycle (execute a run, inspect status, run checks) is present, but there is no way to discover available check names, cancel an in-flight run, or retrieve prior run results/logs. These are notable gaps that could cause agent dead ends.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues