karate-graph-mcp
Related Servers
Alternatives to karate-graph-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceTurn any .NET test-automation solution into a queryable map in one SQLite file — features, steps, API clients, page objects, and their dependencies. Zero config, no AI, no network, 100% deterministic.4113MIT
- AlicenseNot gradedqualityDmaintenanceAnalyzes GitHub and local repositories to automatically generate visual architectural diagrams such as dependency graphs, class diagrams, and data flow diagrams.2MIT
- FlicenseNot gradedqualityBmaintenanceEnables querying a Neo4j-based code graph for Python projects, providing tools for code structure, call graph, and test coverage analysis.1-
- AlicenseAqualityDmaintenanceAnalyzes codebases to generate dependency graphs and architectural insights across multiple programming languages, helping developers understand code structure and validate against architectural rules.64020MIT
- AlicenseAqualityCmaintenanceProvides a graph-based code analysis to coding agents, enabling tools to trace call dependencies, assess change impact, and identify hotspots using tree-sitter and Neo4j.104MIT
- AlicenseAqualityDmaintenanceEnables AI to analyze, query, and manage a graph-based representation of software architecture for impact analysis, dependency tracking, and design.2091AGPL 3.0
TDQS
Scored across 61 tools
Despite the large number of tools, each has a clearly distinct purpose and description, with specific targets like search_api vs search_test_case, and impact_analysis vs change_impact_preview. Overlaps are minimal and descriptions clarify differences.
All tool names follow a consistent verb_noun pattern with underscores, using lowercase throughout. No mixing of styles such as camelCase or different conventions, making the naming predictable and readable.
With 61 tools, the count is extremely high for an MCP server. Even though the domain is broad, the tool surface is overly large and would benefit from consolidation or modularization, as most servers in this ecosystem have fewer than 20 tools.
The tool set covers the full lifecycle of Karate testing analysis: project registration, dependency graph construction, impact analysis, failure debugging, search, presets, and visualization. There are no obvious gaps in the analytical capabilities offered.