Skip to main content
Glama
MaojieXu

astro-flow-mcp

by MaojieXu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to astro-flow-mcp

No user-submitted related servers found.

    Related Servers

    • Hermes n8n MCP

      csenguttuvan
      A
      license
      Not graded
      quality
      B
      maintenance
      A local stdio MCP bridge for managing n8n from Hermes Agent, exposing tools to check health, list/inspect workflows, view executions, and activate/deactivate workflows securely without exposing n8n over the network.
      MIT

    • sdlc-workflow-mcp

      Tingsum26
      F
      license
      C
      quality
      C
      maintenance
      Enables local Copilot use to interact with SDLC workflow tools (workflow tasks, internal-readiness, epic/ticket/repo-task, change-request, and journey) via a stdio MCP server that proxies to a local Workflow Service.
      42
      -

    • Git RAG MCP Server

      vamsi-desu
      F
      license
      B
      quality
      C
      maintenance
      Connects an LLM to specialized MCP servers via stdio, enabling authenticated GitHub repository, issue, file, and code operations alongside TF-IDF retrieval over employee PDF records and QA test-case generation and result validation. It exposes tools, a read-only resource, and reusable prompt templates so a client can discover and orchestrate multiple capabilities in one workflow.
      3
      -

    • PacedLoop MCP Server

      gvfullstack
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with the hosted PacedLoop API to manage workflows and monitor process runs. It provides tools for workflow CRUD operations, run execution management, and access to detailed performance analytics within MCP-capable clients.
      -
    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 7 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: workflow submission, run status, capability search/describe, canvas listing/reading/editing. There is no overlap in purpose, and descriptions further clarify boundaries.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with lowercase and underscores (submit_, get_, search_, describe_, list_, edit_). The naming is uniform and predictable.

    Tool Count5/5

    Seven tools is well-scoped for an Astro Flow workflow server, covering execution, monitoring, capability discovery, and canvas editing without unnecessary bloat or thinning.

    Completeness4/5

    The core lifecycle is covered: reading/editing canvases, submitting workflows, retrieving run status, and exploring capabilities. A minor gap exists—there is no run listing or cancellation—but it does not break the primary workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources