Skip to main content
Glama
swl-informatica

meloqa-mcp

by swl-informatica
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to meloqa-mcp

No user-submitted related servers found.

    Related Servers

    • connectsecure-mcp

      Decian-Inc
      A
      license
      C
      quality
      C
      maintenance
      Exposes every operation in the ConnectSecure OpenAPI specification as an MCP tool, enabling vulnerability management, assets, assessments, integrations, and reporting.
      359
      MIT

    • Panaya MCP Server

      engineersonal
      F
      license
      C
      quality
      C
      maintenance
      Exposes Panaya REST APIs as MCP tools for managing entities like projects, requirements, tests, defects, releases, cycles, and business processes. Enables Claude or any MCP client to perform CRUD operations on Panaya data via natural language.
      9
      -

    • Autonomous QA Engineer MCP

      GolffyCoding
      F
      license
      Not graded
      quality
      B
      maintenance
      Provides MCP tools that give LLM agents a full QA engineer workflow: scanning projects, generating deterministic test suites, executing them across browser/API/mobile, diagnosing failures, and proposing fixes that require human approval.
      -

    • kiwi-tcms-mcp

      ShahjahanAliTaimoor
      A
      license
      B
      quality
      B
      maintenance
      Enables MCP clients to interact with Kiwi TCMS test-management data, allowing users to browse and create test cases, build plans and runs, and record execution results through natural-language prompts. It exposes 49 read/write tools over the Kiwi JSON-RPC API.
      49
      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

    C2.9/5.0

    Scored across 83 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action, with clear grouping by tags. No overlapping or ambiguous tool semantics.

    Naming Consistency5/5

    All tools follow a consistent resource_action naming pattern using snake_case. Verbs are uniform (list, create, delete, get, update) with few deviations like 'unarchive' and 'batch_create'.

    Tool Count2/5

    With 83 tools, the count far exceeds the typical well-scoped range (3-15). While the domain is complex, the sheer number may overwhelm agents.

    Completeness4/5

    The tool set covers CRUD and lifecycle operations for all main entities (bugs, cycles, executions, test cases, projects, etc.). Minor gaps like missing direct test case status management are present but not critical.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources