Skip to main content
Glama

Related Servers

Alternatives to bourne mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables agents to submit and manage persistent, dependency-aware task graphs with immutable artifacts, resource reservations, durable event streaming, and retryable process execution over MCP.
      12
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents and MCP clients to run research as an explicit scientific process: forming hypotheses, designing and executing sealed experiments, capturing observations and artifacts, linking claims to supporting evidence, and reviewing provenance. Exposes coordinated MCP services so users can inspect, reproduce, and audit every step from question to conclusion rather than trusting an opaque final answer.
      46
      21
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to run declarative agents and DAG workflows as plain tools, with parallel nodes, review loops, and per-run least-privilege sandboxing.
      5 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to schedule task graphs, compute critical paths and slack, lease lock-aware parallel cohorts to agents, version plan-as-code variants, and track earned value with resource leveling and Monte Carlo risk analysis.
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to control the local Open Science research application, including creating projects, starting or continuing research sessions, inspecting progress and plans, canceling runs, and reading generated artifacts.
      12
      Apache 2.0

    TDQS

    A3.9/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools have clearly separated lifecycle roles: schema/validate/plan/execute/get/wait/cancel/trace are distinct. A few phrases overlap, notably bourne_plan versus bourne_site_candidates/bourne_site_select and bourne_discover versus bourne_site_discover, but the descriptions actively explain when to use each.

    Naming Consistency3/5

    Every tool is prefixed with bourne, but the underlying pattern is inconsistent: validate_request and execute_plan are verb+object, site_list and execution_get are object+verb, while discover, inventory, and request_schema are bare or noun-only. Names remain readable, but the convention is not uniform.

    Tool Count3/5

    17 tools is just above the ideal range and feels somewhat heavy for a single server. The planning workflow is split across plan, site_candidates, and site_select, which inflates the tool count even though the overall domain is coherent.

    Completeness5/5

    The tool set covers the stated execution lifecycle well: schema validation, request normalization, discovery, inventory, site policy, candidate planning, selection, immutable plan creation, execution, monitoring, wait, cancellation, reconciliation, and artifact tracing. No obvious operation needed by the domain seems missing.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues