Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Coverage analysis, untested function detection and complexity scoring for TS and JS.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"test-intel": {
"command": "npx",
"args": [
"-y",
"@barissozudogru/test-intel-mcp"
]
}
}
}在终端中运行这条命令
claude mcp add test-intel -- npx -y @barissozudogru/test-intel-mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"test-intel": {
"command": "npx",
"args": [
"-y",
"@barissozudogru/test-intel-mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"test-intel": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@barissozudogru/test-intel-mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 barissozudogru 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.8.1)于2个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Excaliself
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Find, read, create, edit, and organize Excalidraw drawings in your self-hosted Excaliself instance.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Turn JavaScript and TypeScript coverage artifacts into practical test priorities. The server reads local coverage and source files, identifies gaps, scores function complexity, and suggests focused test cases without sending code to an external service.
Tool page · npm · Listed in the official MCP Registry
Add one local server entry to any stdio-compatible MCP client:
{
"mcpServers": { "test-intel": { "command": "npx", "args": ["-y", "@barissozudogru/test-intel-mcp"] } } }
Then ask the client to inspect an existing coverage file:
Use test-intel to analyze coverage/lcov.info, identify the highest-impact gaps,
and suggest tests for the most complex uncovered function.
No account, API key, or hosted service is required. File access is restricted to the directory where the server starts.
Running the complexity tool against the real src/paths.ts file produces:
Function complexity analysis for: src/paths.ts
Total functions analyzed: 1
Priority | Function | Line | Cyclomatic | Branches | Loops ---------|-----------------|------|------------|----------|------ low | deriveTestPaths | 11 | 3 | 1 | 1
Summary: 0 critical, 0 high, 0 medium, 1 low priority
The same server reads lcov, Istanbul JSON, and Cobertura files to surface uncovered functions, lines, and branches.
A pinned p-limit 7.3.1 case study reproduces coverage from the upstream project's 22 passing tests. test-intel-report reduces its lcov artifact to two uncovered lines and one uncovered branch while preserving the original coverage file for inspection.
If this saves you time, consider starring the repository. It helps other developers find it.
| Tool | What it answers |
|---|---|
analyze_test_coverage | Which files, functions, lines, and branches remain uncovered? |
find_untested_functions | Which source functions have no corresponding test file? |
get_function_complexity | Which functions deserve testing attention first? |
suggest_test_cases | Which happy path, boundary, error, async, and type cases should be reviewed? |
Supported coverage formats:
| Format | Common producers |
|---|---|
| lcov | Jest, Vitest, nyc, Istanbul |
| Istanbul JSON | Jest, nyc, Istanbul |
| Cobertura XML | Jest, pytest-cov, JaCoCo |
Heuristic source-to-test matching and complexity scores are prioritization signals. Native coverage data and human review remain the source of truth.
The package also includes a non-MCP command for CI and terminal use:
npx -y -p @barissozudogru/test-intel-mcp test-intel-report coverage/lcov.info
An explicit format can be supplied when the filename is ambiguous:
test-intel-report coverage/result.xml cobertura
Generate coverage with the project's own test runner, then pass the resulting artifact to the action:
name: Test priorities
on: [pull_request]
jobs: test-intel: runs-on: ubuntu-latest permissions: contents: read steps:
The report is written to the workflow summary. The action analyzes an artifact that already exists and does not upload source or coverage data.
Claude Desktop, Cursor, Windsurf, Cline, and similar clients
Use the stdio configuration from the quickstart. Config file locations differ by client, but the server entry is the same:
{
"mcpServers": { "test-intel": { "command": "npx", "args": ["-y", "@barissozudogru/test-intel-mcp"] } } }
VS Code with Copilot
Create .vscode/mcp.json:
{
"servers": { "test-intel": { "type": "stdio", "command": "npx", "args": ["-y", "@barissozudogru/test-intel-mcp"] } } }
Streamable HTTP
Start the local endpoint:
npx @barissozudogru/test-intel-mcp --http
The MCP endpoint is http://localhost:3000/mcp and the health endpoint is http://localhost:3000/health. Set PORT to use another port.
Docker
docker build -t test-intel-mcp .
docker run -p 3000:3000 -v "$(pwd):/project" -w /project test-intel-mcp
Connect an HTTP client to http://localhost:3000/mcp.
npm install
npm test npm run build node dist/index.js
Requirements: Node.js 18 or newer.
See CONTRIBUTING.md for the development workflow.
MIT