test-inventory-mcp
MCP server for test-inventory: AI agents ask which Playwright, Vitest, Jest, Mocha, Jasmine, Cypress, WebdriverIO, node:test and Bun tests a project has, which are skipped and why, and which a change can affect, without running them.
Install / Use
claude mcp add Huldoser -- npx -y github:Huldoser/test-inventory-mcpIf the server publishes to npm under a different name, use that package instead — check the repo README.
MCP Server
Model Context Protocol server
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of test-inventory-mcp
test-inventory-mcp scores 83/100 on our quality scale, 2988th of 4,698 Development & Engineering skills we index.
Its MCP Server is 14 KB long, well organised into 10 sections with 5 code examples: a thorough specification that gives an agent plenty to work with.
It has 3 GitHub stars, so there is little community track record yet; judge it on its content.
Maintenance, license and trust
- The repository was last updated yesterday, so test-inventory-mcp is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 92/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-15. Automated pattern scan on 2026-11-15. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
test-inventory-mcp compared with similar skills
All 4 of these similar skills score higher than test-inventory-mcp; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| test-inventory-mcp (this skill)by Huldoser | 83 | 3 | 1d ago | MCP Server |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
Frequently asked questions
- How do I install test-inventory-mcp?
- Run
claude mcp add Huldoser -- npx -y github:Huldoser/test-inventory-mcp. The install tabs above show the steps for each supported agent. - Which AI agents does test-inventory-mcp work with?
- It is written for Claude Code and Claude Desktop, as a MCP Server file. Other agents that read the same format can often use it too.
- Is test-inventory-mcp safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 92/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is test-inventory-mcp still maintained?
- The repository was last updated yesterday, so test-inventory-mcp is actively maintained.
Skill content
View source on GitHubtest-inventory-mcp
An MCP server for test-inventory: AI agents ask which tests a project has, which are skipped and why, and which tests a change can affect, without running them.
It reads Playwright, Vitest, Jest, Mocha, Jasmine, Cypress, WebdriverIO, node:test and Bun test files with
test-inventory and answers from their source code. The running server executes no project code, writes no files and
opens no network connections. Installation through npx may download packages. Answers are passed to the MCP
client; its model provider and privacy settings determine what happens to that text next.
Setup
The server requires test-inventory 0.10.4 or a later 0.10 patch, including its reading of configs that package.json scripts pass to the runner.
Node.js 22.12 or newer. The client starts the server with npx and talks to it over standard input and output. The
server scans the test files your test runner's config runs, with the runner --framework names or, without
it, the one the project uses. Globs pick the files instead, as on test-inventory's command line.
Claude Code, in the project folder. --scope project writes .mcp.json, for everyone who works on the project:
claude mcp add --scope project test-inventory -- npx -y test-inventory-mcp@0.9 --framework playwright
Cursor, in .cursor/mcp.json:
{
"mcpServers": {
"test-inventory": {
"command": "npx",
"args": ["-y", "test-inventory-mcp@0.9", "--framework", "playwright"]
}
}
}
VS Code, in .vscode/mcp.json:
{
"servers": {
"test-inventory": {
"type": "stdio",
"command": "npx",
"args": ["-y", "test-inventory-mcp@0.9", "--framework", "playwright"]
}
}
}
Without --framework, as in a configuration shared by every project, each call scans with the runner the project
uses. In a project with several runners the agent passes framework, as the tools tell it, and patterns when it
wants other files than the configs run.
The project is the folder given with --root, otherwise the one Claude Code names in CLAUDE_PROJECT_DIR, otherwise
the folder the client starts the server in.
Verify the setup
- Open your client's MCP server list and confirm that
test-inventoryis connected. In Claude Code use/mcp; in VS Code run MCP: List Servers from the Command Palette; in Cursor open its MCP settings. - Confirm the five tools below are available, then ask: "Use test-inventory to summarize this project's tests."
- Check that
test_summaryreports the expected framework and file counts. If it reportsscanErrors, ask the agent to callscan_diagnosticsbefore trusting the counts.
Try "List tests marked fixme, with their conditions and reasons" or "Which tests may be affected by a change to pages/orders-blotter.ts?" A conditional skip is not proof a test was skipped in a run. Expected-to-fail tests run; their non-active state does not mean they are disabled. See key concepts.
Command line
test-inventory-mcp [--framework <name>] [<glob...>] [--root <dir>]
| Option | Meaning |
| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| --framework <name> | playwright, vitest, jest, mocha, jasmine, cypress, webdriverio, node or bun. Without it, the runner the project uses. A tool call can pass another. |
| <glob...> | The test files, relative to the project, in place of those the configs run. A tool call can pass others. |
| --root <dir> | The project. Tool calls can scan folders inside it, never outside. |
| -h, --help | Print the help. |
| -v, --version | Print the version. |
Tools
The generated tool reference lists each argument's type, default and bounds, response fields, complete request/response examples, pagination and errors. It is checked against the running server in tests.
| Tool | Answers |
| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------- |
| test_summary | Counts by state, tag and annotation, and the configs with their projects; with groupBy, the counts of each file, tag or project. |
| find_tests | The tests that match states, tags, grep, related, projects, only or withoutReason, with the fields you pick. |
| get_tests | Every key of up to 20 tests by ids, with the scan's diagnostics about them; ids it can't find come back in notFound. |
| scan_diagnostics | The problems the scan found, such as a file that failed to parse, by levels, codes or path. |
| diff_inventories | Changes between saved scans named by before and after, including renames, moves and newly declared skip states. |
A typical call sequence is test_summary, find_tests, then get_tests for a few returned ids. For example, the
arguments to find_tests can be:
{
"states": ["skip", "fixme"],
"fields": ["fullName", "state", "condition", "reason"],
"limit": 10
}
The answer contains matching tests, their total, scanErrors, nextCursor and hint, plus the framework and its
version. The records have selected keys and their id. Pass a non-null nextCursor as cursor with the same other
arguments to read another page; a narrow filter returning zero tests is a valid result.
related takes the files a change touches, from the project root as git diff --name-only writes them, and keeps
the tests whose dependencies include one of them, and those that reach code the scan can't follow, as
test-inventory's --related does.
The filter uses the actual scanned folder when directory names an internal link or an absolute path inside the project.
It also keeps tests that import a changed helper elsewhere in the project, outside that scanned folder.
dependencies can list hundreds of files, so it isn't among the default fields, and get_tests returns as many
tests as fit in one answer, with the other ids in remaining. An id stays the same when a test moves to another
line, and changes when its title, describes or file change.
Every scan tool also takes directory, a folder inside the project to scan, and framework and patterns, relative to
directory, to override the command line, and expandCases, which lists each case of a .each or .for table and
each pass of a loop as its own test, with the name the runner gives it, as test-inventory's
--expand-cases does. Ids differ with it, so get_tests takes
the same expandCases as the find_tests call the ids came from. Records have the keys of test-inventory's
output format.
Unknown tool arguments are refused with an error naming the unrecognized key, so misspelled filters are not silently ignored.
Answers are JSON, sent both as structured content and as text. Lists come 50 items at a time (limit takes up to
200), and an answer stays under about 30,000 characters; passing nextCursor back as cursor gets the next page.
A single oversized record is returned alone. A final page can fit more records because it needs no next-page cursor or hint.
scanErrors counts the problems that may leave tests out, and hint says what to do next when there is something to
say.
Compare saved inventories
diff_inventories takes before and after, paths to complete saved JSON inventories inside the project, plus
limit and cursor. It returns paged changes with original records and matching evidence, the full summary,
total, nextCursor, hashesComparable, warnings and hint. It does not scan or write files. Use the same
framework, root, patterns, filters and expandCases setting for both scans. Hash comparisons and rename matching
need the exact same core version. Incomplete scans produce warnings. Zero changes returns an empty page and a hint.
Each saved file must be a regular file of at most 128 MiB. Save scans with the core CLI, without --fields or
--format jsonl; see inventory diffs. If a saved file disappears or becomes unreadable while opening it, the error names the supplied file and suggests checking its existence and readability, without exposing the resolved host path. Cancellation during these operations retains the request's cancellation reason.
Troubleshooting
| Symptom | Next step |
| ----------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The server is disconnected or tools are missing | Open the client's server logs. Check that the client can find Node.js 22.12 or newer and npx, then restart the server through the client. A client launched by a desktop app may use a different PATH from your terminal. |
| No files or tests were found | Check --root, directory, the framework and the config's selected files. Try explicit patterns, such as ["tests/**/*.spec.ts"]. Call scan_diagnostics for details. |
| Several runners were detected | Pass framework on the call, or set --framework in the server configuration. Scan each runner separately. |
| The answer has scanErrors | Call scan_diagnostics and resolve the errors before treating the inventory as complete. |
| A path is refused | Keep the scanned files and dependencies inside the configured project. For an intended shared dependency, start the server at the shared parent and use directory to select a package. |
| A cursor is refused | Start the query again without cursor; keep filters, directory and case expansion unchanged when requesting later pages. Files may have changed between calls. |
| `get_te
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
