Skip to main content
Glama
JuliDir

flowise-mcp

by JuliDir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to flowise-mcp

No user-submitted related servers found.

    Related Servers

    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 18 tools

    Disambiguation5/5

    Every tool targets a distinct resource and action (e.g., flows, assistants, document stores, chat history, variables, tools, vector stores). There is no overlap in purpose, making it easy for an agent to select the correct tool.

    Naming Consistency5/5

    All tools follow a consistent 'flowise_verb_noun' pattern using snake_case. Even simple verbs like 'ping' and 'predict' fit naturally. No mixing of conventions.

    Tool Count5/5

    18 tools cover the major features of Flowise (flows, assistants, document stores, etc.) without being overwhelming. Each tool serves a clear function, and the count is appropriate for the domain's complexity.

    Completeness2/5

    While flows have full CRUD plus analysis and prediction, other resources like assistants, document stores, variables, and tools lack create/update/delete operations. This leaves significant gaps for managing those resources, causing potential agent failures.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources