F
licenseNot graded
qualityB
maintenanceMCP serverr for Lastest to manage your tests, AI create them, run them, and speed up AI-development.
18
-
@testneo/mcp-server
Related Servers
Alternatives to @testneo/mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server that generates ISO/IEC/IEEE 29119-3 compliant test plan drafts from project information, providing a structured resource for the standard's test plan outline and a tool for draft creation.1242 npmMIT
- AlicenseAqualityDmaintenanceMCP server for comprehensive code analysis, navigation, and quality assessment across 25+ programming languages.988MIT
- FlicenseNot gradedqualityBmaintenanceMCP server that enables AI agents to programmatically run tests, query results, and receive intelligent recommendations about test execution strategy.-
- FlicenseBqualityBmaintenanceMCP server for AI-powered QA analysis. It enables analyzing test failures, identifying root causes, suggesting fixes, classifying defects, detecting flaky tests, and generating test cases and bug reports.10-
- AlicenseAqualityAmaintenanceAn MCP server that brings senior-QA discipline to AI coding assistants, enabling test planning, TDD, mutation testing, and code review.48506 PyPI7Apache 2.0
TDQS
C2.8/5.0
Scored across 48 tools
Disambiguation3/5
The tool set covers diverse areas, but several tools have overlapping purposes (e.g., multiple execution and batch-run tools). Descriptions help differentiate them, but an agent could still be confused when choosing between similar-sounding tools like testneo_execute_generated_test_case and testneo_run_generated_test_pipeline.
Naming Consistency3/5
All tools share the 'testneo_' prefix, but the naming pattern is inconsistent: some use verb_noun (testneo_create_web_project), others use noun_verb combinations (testneo_api_project_openapi_impact) or longer phrases (testneo_figma_to_tests_workflow). While readable, the lack of a strict convention reduces predictability.
Tool Count2/5
With 48 tools, the server is excessively large for typical use. Although the domain is broad, this count is likely overwhelming and indicates a lack of focus, potentially leading to agent confusion and performance issues.
Completeness2/5
The tool set covers creation, reading, and some updating across multiple entities, but critical delete operations are missing for projects, test cases, contexts, and environments. This gap means agents may need fallback strategies or fail when attempting to clean up resources.
Maintenance
ActivityStale
ResponsivenessNo issues