π¦
jest
An MCP server enabling LLMs to write integration tests through live test environment interaction
0 installs
Trust: 42 β Fair
Devtools
Installation
npx @astro-forge/mcp-jestAsk AI about jest
Powered by Claude Β· Grounded in docs
I know everything about jest. Ask me about installation, configuration, usage, or troubleshooting.
0/500
Loading tools...
Reviews
Documentation
mcp-testing
MCP (Model Context Protocol) servers for running tests from AI assistants like Claude.
Packages
| Package | Description | Status |
|---|---|---|
| mcp-jest | Jest test runner MCP server | β Available |
| mcp-vitest | Vitest test runner MCP server | π§ Coming soon |
Why MCP for Testing?
Traditional test output is designed for humans reading terminals. MCP test servers provide:
- Structured results - Detailed pass/fail information with test names, file paths, and full context
- AI-optimized output - Information organized for LLM comprehension
- Context for debugging - Expected vs received values, file locations, error messages
Development
# Install dependencies
npm install
# Build all packages
npm run build
# Run unit tests
npm test
# Run integration tests
npm run test:integration
# Run E2E tests (MCP protocol level)
npm run test:e2e --workspace=jest
# Run agent tests (requires ANTHROPIC_API_KEY in .env)
npm run test:agent --workspace=jest
Architecture
mcp-testing/
βββ jest/ # mcp-jest package
β βββ src/
β βββ server.ts # MCP server with tool registrations
β βββ core/ # Core modules
β β βββ testRunner.ts # Jest execution orchestration
β β βββ resultParser.ts # JSON output parsing
β β βββ jestConfig.ts # Config/monorepo detection
β β βββ packageManager.ts # npm/pnpm/yarn/bun detection
β β βββ __tests__/ # Unit tests
β βββ schemas/ # Zod schemas for tool I/O
β βββ testing/ # Test infrastructure
β βββ fixtures/ # Test project fixtures
β βββ integration/ # Integration tests
β βββ e2e/ # E2E and agent tests
β βββ configs/ # Vitest configurations
βββ vitest/ # mcp-vitest (future)
License
MIT
