Best for
- AI coding assistants that use MCP (e.g., Claude Code, Cursor)
- Developers who need to automate workflows around test suites
- Teams looking to reduce token usage while maintaining reliable parsing
P
Pare Test
Community
Test runner MCP server that auto-detects test frameworks (pytest, jest, vitest, mocha) and returns typed JSON.
GitHub source repository ↗
30FMRS · D
Pare Test is a focused MCP server for test runners, providing structured output to save tokens and improve agent reliability. It suits AI-driven development workflows but is limited to the listed frameworks. Setup is straightforward, but Node version and timeouts should be checked.
Pare Test is an MCP server in the Pare collection that wraps test runners. It auto-detects the test framework used in a project (supporting pytest, jest, vitest, mocha) and returns structured, typed JSON output instead of fragile terminal text. This eliminates the need to parse ANSI escape codes, progress bars, and locale-specific formatting, giving agents reliable data they can act on directly. This server is part of the Pare project, which provides multiple MCP servers for developer tools, but this profile focuses solely on the test server and does not cover sibling servers.
Tools
The tool list has not been reviewed yet.
Setup
This server is distributed via the npm package @paretools/test and uses stdio transport. A typical setup involves adding a server entry to your MCP client configuration, using a command like npx -y @paretools/test (or similar). Since no specific client config example is provided, users should refer to the client setup guides in the Pare repository (e.g., Claude Code, Cursor).
Fit and risk
Not for
- Scenarios requiring non-Node.js native integration or HTTP/SSE transport
- Users needing support for test frameworks not listed in this profile (e.g., Maven)
- Developers who prefer to parse terminal output directly without structured data
Required permissions
- File system access: to run test commands and read test output
- Subprocess execution: to run test runners (pytest, jest, etc.)
- Network access: potentially for installing packages via npm
Risks and side effects
- Test commands may execute arbitrary code; risk depends on project scripts
- Performance impact if test runners consume significant system resources
- Misconfiguration or failing tests may lead to partial output
Troubleshooting
- Ensure Node.js version >= 20
- Run npx -y @paretools/test once to cache the package and avoid timeouts
- Check MCP client timeout settings; increase MCP_TIMEOUT if needed
- Verify that the test framework is installed and configured correctly
Use cases
Running tests in AI coding agents and getting actionable structured results
Standardizing test output across different test frameworks (pytest, jest, vitest, mocha)
Reducing token consumption during test runs to save context window
Supported clients
Supported clients have not been confirmed yet.