manual_test_validateLABSCO SUMMARY
Shipping self-documenting tools is the pattern more servers should copy.
A tool list tells an agent what it can call, not what order to call things in or what a valid record looks like — so it guesses, and the first three attempts fail. Exposing the workflow, the examples and the schema as callable tools means the agent can orient itself without you writing that into every prompt. It costs three tool definitions and saves the failures they prevent.
What it is
A server for managing manual test cases in YAML, built around the idea that the agent should learn the workflow before attempting it.
What you get
- Test cases stored and manipulated as YAML
- Discovery tools the README tells agents to run first — one explaining the workflow patterns, one giving usage examples, one describing the data structures
- The management operations underneath them
Requirements
Node, run straight from the repository with npx.
Setup effort
One command — npx github:70-10/manual-tests-mcp
USE CASES
01
Letting the agent orient itself
Workflow, examples and schema as callable tools.
02
Keeping test cases in version control
YAML files rather than a database.
11 tools
Listed in project docs. Your client may show a different list.
manual_test_parsemanual_test_listmanual_test_createmanual_test_initmanual_test_results_listmanual_test_results_reportmanual_test_results_cleanmanual_test_helpmanual_test_workflowmanual_test_schemaBEFORE YOU INSTALL
What to know first
Tools you get
11 tools named in the project's documentation.
Requires
npx on PATH
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx github:70-10/manual-tests-mcpMCP Clients
Claude Code
CLAUDE CODE · JSON
{
"mcpServers": {
"manual-tests": {
"command": "npx",
"args": [
"github:70-10/manual-tests-mcp"
]
}
}
}
