TestAtlas
Related Servers
Alternatives to TestAtlas
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA semantic map of your .NET solution for AI coding agents. Analyzes a solution with Roslyn into a queryable code graph exposing 11 read-only tools (find_symbol, impact_analysis, find_implementations, etc.) over MCP. 100% local, no telemetry, MIT licensed.25MIT
- FlicenseNot gradedqualityBmaintenanceCodeMap is a Roslyn-powered MCP server that lets AI agents navigate C# codebases by symbol, call graph, and architectural fact, instead of brute-force reading thousands of lines of source code. One tool call. Precise answer. No context flood.22-
- AlicenseNot gradedqualityAmaintenanceGives AI coding agents real .NET tooling: Roslyn code navigation and refactoring, build/test with affected-test selection, git, and parallel orchestration as a dependency graph.MIT
- AlicenseAqualityCmaintenanceExtracts deterministic architecture maps from codebases for AI agents, enabling queries about blast radius, routes, security findings, and production readiness without sending code anywhere.627 PyPIMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to explore and visualize a .NET codebase's architecture, generating dependency diagrams, Entity Relationship Diagrams from EF Core contexts or model snapshots, class hierarchy diagrams, and solution health metrics through natural language.1MIT
- AlicenseAqualityCmaintenanceAutomated QA for .NET microservice backends and React frontends, enabling API contract testing, UI crawling, YAML flows, and run diffing against a stage environment.73 npmMIT
TDQS
Scored across 11 tools
Most tools have clearly distinct targets (endpoints, tags, scenarios, dependencies), and descriptions explicitly differentiate the step-related tools. However, four tools touch step definitions (search_steps, get_step_definition, step_catalog, resolve_step), and an agent could plausibly confuse search_steps with step_catalog or get_step_definition without reading carefully.
Most names follow a verb_noun pattern (list_endpoints, list_tags, search_steps, get_scenario, resolve_step), but several are bare nouns (stats, impact, step_catalog, project_dependencies). The convention is readable but not uniform across the set.
11 tools is well within the sweet spot and each tool maps to a distinct query type over the test suite. No tool feels redundant or padded for the scope of analyzing a BDD test map.
The surface covers discovery (endpoints, tags, stats), search (steps, scenarios), inspection (scenario, step definition, catalog), and analysis (impact, dependencies) — strong coverage for a read-only analysis server. Minor gaps exist, e.g. no direct feature/file listing or bulk export, but core workflows are reachable.