Skip to main content
Glama
mcp-testing-tools

mcp-testing-tools

by rog0x

@rog0x/mcp-testing-tools

Testing and quality assurance tools for AI agents, exposed via the Model Context Protocol (MCP).

Tools

generate_tests

Generate test cases from a function signature. Produces four categories of tests as ready-to-run Jest or Vitest code:

  • Happy path -- valid inputs, expected outputs

  • Edge cases -- empty strings, zero values, null parameters

  • Error cases -- missing arguments, wrong types

  • Boundary values -- extreme numbers, large arrays, NaN

Parameters:

Name

Type

Required

Description

signature

string

Yes

Function signature, e.g. async function fetchUser(id: number): Promise<User>

framework

string

No

jest or vitest (default: vitest)

module_path

string

No

Import path for the module under test (default: ./module)

generate_mock_data

Generate realistic mock data for testing. Supported types:

name, email, address, date, uuid, phone, company, credit_card, ip

Parameters:

Name

Type

Required

Description

type

string

Yes

Data type to generate

count

number

No

Number of items (default: 10, max: 1000)

locale

string

No

en or es (default: en)

types

string[]

No

Generate mixed records with multiple field types

generate_api_mock

Generate mock API responses from a schema definition. Creates realistic JSON payloads for REST endpoints by inferring values from field names and types.

Parameters:

Name

Type

Required

Description

endpoint

string

Yes

API endpoint path

method

string

No

HTTP method (default: GET)

fields

object[]

Yes

Field schemas with name, type, optional items, fields, nullable, enum

count

number

No

Number of records (default: 1, max: 100)

status_code

number

No

HTTP status code (default: 200)

wrap_in_envelope

boolean

No

Wrap in { success, data, meta } (default: true)

analyze_test_coverage

Analyze source code and test code to find untested functions. Prioritizes suggestions by:

  • Export status (public API surface)

  • Cyclomatic complexity estimate

  • Parameter count

  • Async functions (more error paths)

Parameters:

Name

Type

Required

Description

source_code

string

Yes

Source code to analyze

test_code

string

Yes

Existing test code

source_file_name

string

No

Filename label (default: source.ts)

generate_assertions

Generate detailed assertion code by comparing expected and actual values. Performs deep diff and produces per-field assertions with descriptive comments.

Parameters:

Name

Type

Required

Description

expected

string

Yes

Expected value as JSON string

actual

string

Yes

Actual value as JSON string

label

string

No

Description for the comparison

framework

string

No

jest, vitest, or chai (default: jest)

deep

boolean

No

Deep equality for objects/arrays (default: true)

Related MCP server: EvalView

Setup

npm install
npm run build

Usage with Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "testing-tools": {
      "command": "node",
      "args": ["path/to/mcp-testing-tools/dist/index.js"]
    }
  }
}

License

MIT

Available Tools

5 tools
analyze_test_coverageA

Parse source code and test code to identify untested functions. Suggests which functions need tests most based on complexity, export status, and parameter count.

Inputs: test_code (required), source_code (required), source_file_name.

generate_api_mockB

Generate mock API responses from a schema. Creates realistic JSON responses for REST endpoints based on field names and types.

Inputs: fields (required), endpoint (required), count, method, +2 more.

generate_assertionsA

Given expected and actual values (as JSON strings), generate detailed assertion code with descriptive messages. Supports deep object comparison, array comparison, and type checking.

Inputs: actual (required), expected (required), deep, label, +1 more.

generate_mock_dataA

Generate realistic mock data: names, emails, addresses, dates, UUIDs, phone numbers, company names, credit cards (fake), IP addresses. Configurable count and locale.

Inputs: type (required), count, types, locale.

generate_testsB

Generate test cases from a function signature. Produces happy path, edge cases, error cases, and boundary value tests as Jest/Vitest test code.

Inputs: signature (required), framework, module_path.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but generate_tests and generate_assertions overlap slightly since generated test cases often include assertions. generate_mock_data and generate_api_mock are similarly related, though the former is general-purpose data and the latter is schema-driven API responses.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: generate_tests, generate_mock_data, generate_api_mock, generate_assertions, and analyze_test_coverage. The naming convention is uniform and predictable.

    Tool Count5/5

    Five tools is a well-scoped set for a testing-focused server. Each tool covers a distinct aspect of test generation, mocking, assertions, or coverage analysis without unnecessary redundancy.

    Completeness4/5

    The tool surface covers test generation, mock data, API mocking, assertions, and coverage analysis well. Minor gaps exist, such as no direct test execution or test file management, but the core testing workflow is addressed.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      A specialized testing harness that enables AI assistants to thoroughly test other MCP servers by connecting to them, discovering their tools/resources/prompts, executing test calls, and performing end-to-end validation with LLM integration.
      14
      4
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      MCP server that lets coding agents test AI agents. Create YAML test cases, snapshot golden baselines, check for regressions, and generate visual reports all from inside Claude Code or any MCP-compatible tool. Works with LangGraph, CrewAI, OpenAI, Claude, Mistral, and any HTTP API.
      10
      1,798 PyPI
      142
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to programmatically inspect, test, and validate other MCP servers by exposing MCP Workbench capabilities as structured tools. It supports automated test spec generation, execution, and detailed failure analysis to ensure server reliability.
      4
      7 npm
      Apache 2.0