Skip to main content
Glama
Ctrl1CandV

Atlas

by Ctrl1CandV
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Atlas

No user-submitted related servers found.

    Related Servers

    • Heym by heymrun

      Heymofficial

      heymrun
      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,328
      -

    • DAGSentinel

      WantedChip
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables autonomous multi-agent orchestration using directed acyclic graph workflows to interact with external developer infrastructure such as Git, Postgres, and Docker through safety-gated MCP servers.
      Apache 2.0

    • MultiAgent-MCP-Workflow

      Sakiko236
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables enterprise multi-agent decision workflows that expose 8+ MCP tools such as SQL query, web search, Python sandbox, RAG, file access, data cleaning, chart generation, and HTTP calls, orchestrated with LangGraph, streaming output, and human-in-the-loop approvals.
      MIT

    • MEMGRAPH-MCP

      MikeB317
      F
      license
      A
      quality
      D
      maintenance
      A durable multi-agent orchestrator for software development with explicit run graphs, checkpoint/resume capabilities, and project memory exposed through MCP resources and tools. It enables coordinated agent workflows for coding, review, repair, CI, and approval with SQLite-backed memory retrieval and pluggable research backends.
      10
      -
    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

    A3.8/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool has a clear, distinct purpose in the workflow lifecycle: get run status, resume interrupted runs, validate/save workflows, run/list/cancel runs, list workflows. No two tools are easily confused. The only slight overlap is between atlas_run_workflow and atlas_save_workflow regarding persistence semantics, but they are clearly differentiated.

    Naming Consistency5/5

    All tool names follow a consistent 'atlas_verb_noun' pattern (get_run, resume_run, validate_workflow, save_workflow, run_workflow, list_runs, list_workflows, cancel_run). This is highly predictable and readable.

    Tool Count5/5

    8 tools is well-scoped for a workflow orchestration server. Each tool fills a specific role in the workflow lifecycle (validation, persistence, execution, monitoring, cancellation), and there are no redundant tools.

    Completeness4/5

    The surface covers the full workflow lifecycle: validation, saving, running, listing runs/workflows, getting run details, resuming, and canceling. One notable gap is the absence of a delete/remove operation for workflows, which would be expected for full lifecycle management. However, core operations are complete and agents can work around this.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources