Skip to main content
Glama
gvasile29

qai-consultant-mcp

by gvasile29
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to qai-consultant-mcp

No user-submitted related servers found.

    Related Servers

    • Testers AI CARBON Test Harness

      jarbon
      A
      license
      Not graded
      quality
      A
      maintenance
      A local, MIT-licensed AI test harness with 10 MCP tools and 11 prompts for risk-based testing, accessibility checks, quality maps, evidence, and interactive reports. Runs over stdio against an explicitly configured project folder; uses the host AI coding agent, with no hosted backend or runtime telemetry.
      1
      MIT

    • mk-spec-master

      kao273183
      A
      license
      A
      quality
      D
      maintenance
      AI 規格大師 — MCP server bridging specs (Linear / JIRA / GitHub Issues / Notion / Markdown / Figma) to tests, with bidirectional traceability and a spec-quality coach. Sibling to mk-qa-master.
      18
      2
      MIT

    • McpApp

      krok1029
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a local-first MCP server for AI-native software delivery, enabling structured specifications, human approval gates, controlled repository operations, verification evidence, review, and traceability.
      Apache 2.0
    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.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: knowledge retrieval, source listing, effort estimation, document review, maturity assessment, and test results analysis. No two tools overlap in functionality; an agent can unambiguously select the correct tool for a task.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (retrieve_qa_knowledge, list_kb_sources, estimate_qa_effort, review_qa_document, assess_qa_maturity, analyze_test_results). The naming is uniform, predictable, and clearly indicates the action and object.

    Tool Count5/5

    Six tools is well within the typical 3-15 range and each tool serves a distinct, non-redundant function in the QA consulting domain. The scope is tight without being sparse or overwhelming.

    Completeness4/5

    The tool set covers the core lifecycle: knowledge retrieval, source enumeration, effort estimation, document review, maturity assessment, and test result analysis. Minor gaps exist (e.g., no tool for generating a QA plan or updating knowledge), but these are not essential to the server's stated consultative purpose and agents can work around them.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources