Skip to main content
Glama
Sign In
qai-consultant-mcp

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
      B
      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.
      2
      MIT

    • mk-spec-master

      kao273183
      A
      license
      A
      quality
      C
      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.3/5.0

    Scored across 6 tools

    Disambiguation4/5

    The four analytical tools (estimate_qa_effort, review_qa_document, analyze_test_results, assess_qa_maturity) each target a clearly different input and output, so misselection is unlikely. The only mild overlap is the knowledge-base pair — list_kb_sources (catalog of shipped documents) vs retrieve_qa_knowledge (semantic chunk retrieval) — but the descriptions make the catalog-vs-search split explicit.

    Naming Consistency5/5

    Every name follows a strict snake_case verb_noun pattern: list_kb_sources, retrieve_qa_knowledge, estimate_qa_effort, review_qa_document, analyze_test_results, assess_qa_maturity. Verbs are distinct (list/retrieve/estimate/review/analyze/assess) and nouns name the resource acted on.

    Tool Count5/5

    Six tools sit comfortably in the well-scoped range, and each covers a separate consulting activity: KB discovery, KB retrieval, effort estimation, document review, test-result analysis, and maturity assessment. No tool looks redundant or bolted on.

    Completeness4/5

    The surface covers the advisory lifecycle well — ground knowledge, estimate, review artifacts, analyze execution data, assess maturity — with no dead-end workflows for a read-only consultant role. Gaps remain: no tool to generate or draft QA artifacts (test plans, cases, risk registers), and list_kb_sources is a thin companion to retrieval.

    Maintenance

    ActivityActive
    ResponsivenessLimited data

    Resources