Skip to main content
Glama
maksdizzy

FlowAPI MCP Server

by maksdizzy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to FlowAPI MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-server

      gwanghun-choi
      A
      license
      Not graded
      quality
      C
      maintenance
      A universal MCP server for registering internal, external, and OpenAPI-based APIs as MCP tools. It exposes them to MCP clients via Streamable HTTP and provides admin portal, RBAC/session auth, credential injection, and audit logging.
      Academic Free v1.1

    • fallpharm-mcp

      sjgant80-hub
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides a sovereign, MIT-licensed MCP server for professional-service workflows, running entirely on your infrastructure with Ed25519 cryptographic signing for every action.
      MIT
    • score-studio-mcp by score-technologies

      score-studio-mcpofficial

      score-technologies
      A
      license
      A
      quality
      A
      maintenance
      This server enables agents to identify users and organizations, inspect versioned datasets and model lineage, start training jobs, run and read evaluations, verify deployments, and execute typed workflows through authenticated MCP endpoints.
      12
      Apache 2.0

    • n8n MCP Server

      allanbchancery
      A
      license
      B
      quality
      D
      maintenance
      MCP server for managing n8n workflows and executions. Enables listing, activating, deactivating, and executing workflows, as well as monitoring executions and instance health.
      9
      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

    B3/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools have distinct purposes, but there is slight overlap between health_check and system_info (both check system status) and between get_invited_wallets and get_invited_wallets_by_token (similar but differentiated by token parameter). Overall, descriptions are clear enough to avoid major confusion.

    Naming Consistency3/5

    Tool names are inconsistent in prefix usage: some start with 'flowapi_' (e.g., flowapi_health_check), others do not (e.g., search_users). The pattern is mostly verb_noun but varies between 'search' and 'list' for similar operations. This mix reduces consistency.

    Tool Count4/5

    With 19 tools covering multiple domains (users, workers, arts, collections, wallets), the count is appropriate for the server's scope. It is slightly on the higher side but still well-scoped without feeling bloated.

    Completeness3/5

    The tool set provides full CRUD for external workers but lacks update for users and delete for arts and collections. Also, arts and art collections are limited to read-only operations. There are notable gaps that agents may need to work around.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources