Skip to main content
Glama

Related Servers

Alternatives to ReadyAgents

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      A local, auditable multi-model workflow engine that lets you define YAML graphs for orchestrating LLM agents across vendors, with MCP tools for validation, dry-runs, execution, and human approval, all fully observable in a local web interface.
      8
      3
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables local-first LLM orchestration with persistent memory, knowledge management, routing, swarm patterns, API probing, tests, automation planning, and plugin discovery via a stdio MCP server, using SQLite for offline storage.
      255 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      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.
      879 npm
      1,072
      Business Source 1.1
    • F
      license
      C
      quality
      A
      maintenance
      Self-hosted, source-available AI workflow automation platform. Build multi-agent, RAG, and tool-using pipelines on a visual canvas and publish any workflow as an MCP server (stdio/SSE/Streamable HTTP). Also an MCP client via the agent node.
      2
      1,284
      -

    TDQS

    A3.7/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: time, arithmetic, JSON path operations, HTTP GET, file directory listing/read/write, and workflow execution. There is no meaningful overlap that would cause an agent to misselect.

    Naming Consistency3/5

    Most tools follow a noun_verb or verb_noun underscore pattern like json_get and read_file, but now and calc are single-word exceptions. The mixed conventions are still readable and predictable enough, though not fully uniform.

    Tool Count5/5

    Ten tools is a well-scoped size for a general-purpose workflow utility server. Each tool serves a distinct functional area without unnecessary bloat or redundancy.

    Completeness4/5

    The toolset covers core utility operations: time, arithmetic, JSON manipulation, HTTP retrieval, file access, and workflow execution. Minor gaps exist such as no JSON delete or file delete, but these are workable for most workflow automation scenarios.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive