@blackwell-systems/jest-mcp-assert

@blackwell-systems/jest-mcp-assert

Jest integration for mcp-assert. Run MCP server assertion YAML files as Jest tests.

Same YAML files work across Jest, Vitest, pytest, and the CLI.

Install

npm install -D @blackwell-systems/jest-mcp-assert @blackwell-systems/mcp-assert

Usage

Suite mode (auto-discover YAML files)

// mcp.test.ts
import { describeMcpSuite } from '@blackwell-systems/jest-mcp-assert'

describeMcpSuite('my mcp server', 'evals/')

Each YAML file in evals/ becomes a Jest test case.

Single assertion mode

import { runMcpAssert } from '@blackwell-systems/jest-mcp-assert'

test('echo tool returns message', () => {
  runMcpAssert('evals/echo.yaml')
})

test('greet tool with timeout', () => {
  runMcpAssert('evals/greet.yaml', { timeout: '60s' })
})

Options

runMcpAssert('evals/echo.yaml', {
  timeout: '30s',           // per-assertion timeout
  fixture: 'test/fixtures', // {{fixture}} substitution
  server: 'node server.js', // server override
  binary: '/path/to/mcp-assert', // explicit binary path
})

How it works

@blackwell-systems/jest-mcp-assert is a thin bridge (~100 lines). It shells out to the mcp-assert Go binary with --json, parses the result, and maps it to Jest pass/fail outcomes. The Go binary handles all MCP protocol logic.

Binary resolution (in order):

• Explicit binary option
• mcp-assert on PATH (brew, go install, curl install)
• @blackwell-systems/mcp-assert npm package

Writing assertions

Assertions are YAML files. See the mcp-assert docs for the full reference.

name: echo returns the input message
server:
  command: node
  args: ["server.js"]
assert:
  tool: echo
  args:
    message: "hello"
  expect:
    not_error: true
    contains: ["hello"]

License

MIT