Skip to main content
Glama
halexzd686-cloud

SoloFlow

by halexzd686-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to SoloFlow

No user-submitted related servers found.

    Related Servers

    • AgentTasker MCP Server

      S3bRR
      A
      license
      B
      quality
      D
      maintenance
      A lightweight stdio-only MCP server that allows AI agents to run multiple tasks (e.g., Python code, HTTP requests, shell commands) in parallel or with dependencies, returning structured results in a single call.
      2
      20 PyPI
      MIT

    • moo-tasks

      shekarsiri
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for agentic task orchestration and management, enabling AI agents to create goals, plan tasks with acceptance criteria, track dependencies, request human input, and provide proof of completion.
      24 npm
      2
      MIT

    • hotwired-mcp

      hotwired-sh
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Hotwired multi-agent workflow orchestration, enabling AI agents to coordinate locally via Unix sockets with tools for protocol, messaging, and task management.
      1 npm
      MIT

    • local-mcp

      fan-67
      A
      license
      Not graded
      quality
      D
      maintenance
      A lightweight, stdio-based MCP server enabling AI assistants to perform local file system operations like reading, writing, searching, and executing commands.
      2,456 npm
      MIT
    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

    A4.1/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct combination of entity (Skill, Flow, Agent) and action (list, get, run, validate). There is no overlap between list, run, validate, or get operations, and the three entity types are clearly separated.

    Naming Consistency5/5

    All tool names follow the consistent pattern soloflow_<verb>_<entity>, with verbs limited to list, get, run, and validate. Snake_case is used uniformly, making the naming scheme highly predictable.

    Tool Count5/5

    Nine tools is well-scoped for a platform managing three entity types with core operations. Each tool serves a clear purpose without redundancy, and the count feels neither thin nor bloated.

    Completeness4/5

    The set covers list, get, run, and validate for skills; list, validate, and run for flows; and list and run for agents. Missing get_flow and get_agent are minor gaps, but the core workflow (discover, validate, execute) is fully covered.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources