Skip to main content
Glama
853046310

Qingflow MCP (CRUD)

by 853046310
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Qingflow MCP (CRUD)

No user-submitted related servers found.

    Related Servers

    • ragic-mcp

      EthanH9977
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to interact with Ragic databases via MCP protocol, supporting form exploration, data CRUD, approval, and locking operations.
      11
      MIT

    • Filly Forms MCP Server

      eneopt
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes the Filly Forms REST API as MCP tools for AI agents, enabling form type listing, record CRUD, data preview, and document upload with AI extraction.
      MIT

    • FileMaker Data API MCP Server

      fsans
      A
      license
      B
      quality
      D
      maintenance
      Provides AI agents with direct access to FileMaker databases through the FileMaker Data API, enabling natural language interactions for querying, managing records, and database introspection.
      28
      18 npm
      3
      MIT

    • DB Gateway MCP Server

      sijunkim
      A
      license
      A
      quality
      A
      maintenance
      Gives AI agents direct access to databases across 8 engines with 145+ tools, enabling schema-aware query execution and management through natural language.
      17
      57 npm
      MIT

    • mcp-dynamics-365

      dave-palt
      A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to perform CRUD operations, query data, fetch schemas, and execute custom operations on Microsoft Dynamics 365 CRM entities.
      10
      26 npm
      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

    B3.1/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose. Query tools (aggregate, export, plan, record, rows) are separated from non-query tools (field resolve, form get, mutate, spec get, value probe), and even within queries, each serves a unique function.

    Naming Consistency2/5

    Naming convention is inconsistent: some tools use underscores (qf_field_resolve, qf_form_get, qf_tool_spec_get, qf_value_probe) while others use dot notation (qf.query.aggregate, qf.query.export, etc.). This mixed pattern can confuse an agent.

    Tool Count5/5

    10 tools is appropriate for a CRUD server with advanced query capabilities. Each tool serves a well-defined purpose without excessive overlap.

    Completeness2/5

    Significant gaps exist: no explicit delete operation (qf.records.mutate only mentions create/update), no listing tools for forms or apps, and no field management beyond resolving. This will cause agent failures when delete or listing is needed.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources