Skip to main content
Glama
Particle-Academy

fancy-flow-mcp-js

by Particle-Academy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to fancy-flow-mcp-js

No user-submitted related servers found.

    Related Servers

    • Flow Weaver MCP Server

      synergenius-fw
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants and MCP-compatible editors to scaffold, edit, validate, compile, run, debug, and diff durable TypeScript workflows directly through conversation.
      25 npm
      1
      Apache 2.0

    • Orchestration MCP

      dufangshi
      F
      license
      A
      quality
      D
      maintenance
      A TypeScript MCP server for launching, tracking, and managing external coding-agent runs across local and remote backends like Codex and Claude Code. It allows top-level agents to orchestrate subagents through tools for spawning tasks, polling events, and handling interactive sessions.
      7
      2
      -

    • MCP-TS-DEMO

      pjqdyd
      A
      license
      D
      quality
      D
      maintenance
      A TypeScript MCP server demo supporting local Stdio and remote Streamable HTTP, demonstrating tool invocation for AI agents.
      2
      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.3/5.0

    Scored across 15 tools

    Disambiguation5/5

    Every tool maps to one distinct operation: workflow-level CRUD, node editing, edge editing, node-kind introspection, validation, import/export, and smoke-test running. The close pairs like get_workflow/export_workflow and list_node_kinds/describe_node_kind are explicitly differentiated. No two tools appear to do the same job.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern: list_, create_, get_, delete_, add_, remove_, configure_, connect_, describe_, validate_, export_, import_, and run_. The object nouns are predictable and consistent. There is no mixed casing or vague verb usage.

    Tool Count5/5

    Fifteen tools sits at the upper boundary of ideal, but each tool earns its place in the workflow-authoring lifecycle. There are no duplicate or filler tools, and the count matches the apparent domain richness. It feels intentionally scoped rather than bloated.

    Completeness5/5

    The server covers workflow CRUD, node editing, edge editing, node-kind introspection, validation, portable import/export, and a run smoke test. Every editing operation has a corresponding read or delete path, and get_workflow/export_workflow provide both authoring and portable views. The declared out-of-scope production execution is a deliberate boundary, not a gap.

    Resources