Skip to main content
Glama
sazanami-lab

ariadne mcp-server

by sazanami-lab

Related Servers

Alternatives to ariadne mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for test impact analysis and code intelligence. Maps tests to code and git history to determine impacted tests, risk scores, and ownership for AI coding agents.
      58 PyPI
      3
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server that analyzes TypeScript/JavaScript codebases via AST parsing and dependency graph tracing to identify affected tests, detect dead code, circular dependencies, and trace import chains, enabling AI agents to run only relevant tests.
      15
      37 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Local MCP server providing project cognition capabilities for AI coding agents, including context packs, impact analysis, and git diff review through stdio communication.
      10
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A universal AI-powered testing server built on the Model Context Protocol (MCP). Allows AI agents to inspect, execute, test, monitor, debug, and report on software projects.
      3
      GNU Lesser General Public v2.1 only
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for local-first code intelligence, providing structural code graph, semantic search, and impact analysis to AI agents.
      2
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Model Context Protocol (MCP) server for Octopilot — enables AI agents to detect, generate, build, and wire up new repositories end-to-end using the Octopilot CI/CD toolchain.
      7
      -

    TDQS

    A4.3/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no ambiguity. The tool's name and description clearly define its single purpose.

    Naming Consistency5/5

    The tool name follows a descriptive verb_noun pattern ('get_affected_tests'), which is consistent with typical MCP naming conventions.

    Tool Count3/5

    A single tool is borderline for most servers; while it serves a narrow purpose, additional tools for related operations (e.g., running tests) would be expected.

    Completeness2/5

    The tool only covers detection of affected tests, but lacks complementary operations like listing all tests, running tests, or configuring the analysis, leaving significant gaps.

    Maintenance

    ActivityStale
    ResponsivenessUnresponsive