cool-test-mcp

cool-test-mcp

An automated testing MCP server that converts test cases into a fixed JSON format, runs them case-by-case, and provides a visual report with review support for cases that cannot be automatically judged.

Category
访问服务器

README

Cool Test MCP

<p align="center"> English · <a href="README.cn.md">简体中文</a> </p>

An automated testing MCP (Model Context Protocol) server. It is lightweight — no extra runtime dependencies, single entry point, instant to start — and plugs into any MCP-capable agent (Claude Desktop, Cursor, opencode, etc.) with a few lines of config.

Features

  • Lightweight & easy to adapt — no extra runtime deps, runnable via npx, one-line config to connect to your agent tools
  • Conversion — turn test cases in any format into a fixed JSON template (.cooltest/)
  • Case-by-case testing — read / test / write cases one by one through MCP tools, avoiding direct JSON file I/O that wastes tokens
  • Review flow — cases that cannot be tested or judged are automatically set to review, left for human review
  • Visual report — a local web page shows all case results and supports editing status and notes

Requirements

  • Node.js 18 or newer
  • Claude Desktop, Cursor, opencode, or any other MCP client

Getting started

No local install needed — the server runs directly via npx. Register it in your agent's MCP configuration.

Standard config works in most of the tools:

{
  "mcpServers": {
    "cool-test": {
      "command": "npx",
      "args": [
        "-y",
        "cool-test-mcp@latest"
      ],
      "cwd": "/absolute/path/to/your/project"
    }
  }
}

cwd points to your project root; .cooltest/ will be created there. For clients without a per-server cwd, the folder is created in the MCP process's working directory.

<details> <summary>Codex</summary>

Use the Codex CLI to add the server:

codex mcp add cool-test npx "-y cool-test-mcp@latest"

Alternatively, create or edit ~/.codex/config.toml:

[mcp_servers.cool-test]
command = "npx"
args = ["-y", "cool-test-mcp@latest"]

For more information, see the Codex MCP documentation.

</details>

<details> <summary>Claude Desktop</summary>

Follow the MCP install guide, and add to claude_desktop_config.json:

{
  "mcpServers": {
    "cool-test": {
      "command": "npx",
      "args": [
        "-y",
        "cool-test-mcp@latest"
      ],
      "cwd": "/absolute/path/to/your/project"
    }
  }
}

</details>

<details> <summary>Cursor</summary>

Go to Cursor Settings -> MCP -> Add new MCP Server. Name it to your liking, use command type with the command npx -y cool-test-mcp@latest. Alternatively, add to .cursor/mcp.json:

{
  "mcpServers": {
    "cool-test": {
      "command": "npx",
      "args": [
        "-y",
        "cool-test-mcp@latest"
      ]
    }
  }
}

</details>

<details> <summary>Trae</summary>

Create a .trae/mcp.json file in your project root (Cursor-compatible mcpServers schema):

{
  "mcpServers": {
    "cool-test": {
      "command": "npx",
      "args": ["-y", "cool-test-mcp@latest"]
    }
  }
}

For more information, see the Trae MCP documentation.

</details>

<details> <summary>Zed</summary>

Zed uses the context_servers key (not mcpServers). Add to ~/.config/zed/settings.json:

{
  "context_servers": {
    "cool-test": {
      "command": "npx",
      "args": ["-y", "cool-test-mcp@latest"]
    }
  }
}

For more information, see the Zed MCP documentation.

</details>

<details> <summary>opencode</summary>

Follow the MCP Servers documentation. For example in ~/.config/opencode/opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cool-test": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "cool-test-mcp@latest"
      ],
      "enabled": true
    }
  }
}

</details>

The MCP configs for each agent tool above have not all been individually verified. If you find any issues or missing configs, we welcome PRs to add or fix them.

Environment variables

Variable Description
COOLTEST_ROOT Absolute path to the project root where .cooltest/ is created and read. Defaults to the MCP process's working directory (process.cwd()) when unset. Set it when your client has no per-server cwd (e.g. opencode) or when you want to pin the root explicitly.
{
  "environment": {
    "COOLTEST_ROOT": "/absolute/path/to/your/project"
  }
}

Usage

Trigger the full test flow

Use Cool Test for <test case address>

The LLM will: check whether your agent has browser automation capability (Playwright MCP etc.) → convert the cases → test case by case → open the report.

View the report

Use Cool Test to view <address>

MCP Tools

Tool Purpose
cooltest_init_suite Generate a .cooltest JSON (does not overwrite by default; overwrite:true rebuilds)
cooltest_append_cases Append one or more new cases to a suite in a single batch
cooltest_list_suites List existing suites
cooltest_list_cases Case summary list (id/title/status/priority)
cooltest_get_case Read a single case's full content
cooltest_update_case Update an existing case's status/notes/evidence/lastRunAt after testing
cooltest_get_stats Suite status statistics
cooltest_open_report Start the local report server and open the page

Contributing

Contributions are welcome. To set up a local environment:

# Clone
git clone https://github.com/CoolTea001/cool-test-mcp.git
cd cool-test-mcp

# Install
npm install

# Build (compile TS + copy the report script to dist)
npm run build

# Test (end-to-end check, full tool flow via MCP client)
node test-e2e.mjs <temp dir>

Test the local build as an MCP server

To try your un-published changes in an actual MCP client, point the server at the local dist/index.js instead of the npm package. Rebuild first (npm run build) so dist/ is up to date, then register it.

Generic mcpServers config (Claude Desktop, Cursor, Trae, etc.):

{
  "mcpServers": {
    "cool-test": {
      "command": "node",
      "args": ["/absolute/path/to/cool-test-mcp/dist/index.js"],
      "cwd": "/absolute/path/to/your/project"
    }
  }
}

opencode (~/.config/opencode/opencode.json):

{
  "mcp": {
    "cool-test": {
      "type": "local",
      "command": ["node", "/absolute/path/to/cool-test-mcp/dist/index.js"],
      "environment": {
        "COOLTEST_ROOT": "/absolute/path/to/your/project"
      }
    }
  }
}

Notes for local testing:

  • Set the working directory (or COOLTEST_ROOT) to the project you want to test against — .cooltest/ is created there.
  • After rebuilding, restart the MCP client / reconnect the server for the new dist/ to take effect.
  • The published package runs the same code via npx -y cool-test-mcp@latest; only the entry point differs.

License

MIT

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选
mcp-server-qdrant

mcp-server-qdrant

这个仓库展示了如何为向量搜索引擎 Qdrant 创建一个 MCP (Managed Control Plane) 服务器的示例。

官方
精选
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选