Back to Browse

Test Intel MCP Server

Developer ToolsLow Risk10.0MCP RegistryLocal
Free

Server data from the Official MCP Registry

Coverage analysis, untested function detection and complexity scoring for TS and JS.

About

Coverage analysis, untested function detection and complexity scoring for TS and JS.

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (2 strong, 3 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry.

3 files analyzed · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-barissozudogru-test-intel": {
      "args": [
        "-y",
        "@barissozudogru/test-intel-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

test-intel-mcp

Test coverage intelligence MCP server for TypeScript and JavaScript projects. Analyzes coverage reports, detects untested functions, and scores cyclomatic complexity locally, with no external services and no authentication required.


Tools

ToolDescription
analyze_test_coverageParse lcov, istanbul JSON, or cobertura XML reports and surface uncovered files, functions, lines, and branches
find_untested_functionsScan a source directory for functions with no corresponding test file
get_function_complexityCompute cyclomatic complexity per function to prioritize what to test first
suggest_test_casesAnalyze a specific function and generate categorized test case suggestions

Setup

Option A: stdio (local)

Claude Desktop

Config file: ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "test-intel": {
      "command": "npx",
      "args": ["-y", "@barissozudogru/test-intel-mcp"]
    }
  }
}
Claude Code
claude mcp add test-intel -- npx -y @barissozudogru/test-intel-mcp
Cursor

Config file: ~/.cursor/mcp.json

{
  "mcpServers": {
    "test-intel": {
      "command": "npx",
      "args": ["-y", "@barissozudogru/test-intel-mcp"]
    }
  }
}
Windsurf

Config file: ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "test-intel": {
      "command": "npx",
      "args": ["-y", "@barissozudogru/test-intel-mcp"]
    }
  }
}
VS Code + Copilot

Config file: .vscode/mcp.json

{
  "servers": {
    "test-intel": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@barissozudogru/test-intel-mcp"]
    }
  }
}
Cline
{
  "mcpServers": {
    "test-intel": {
      "command": "npx",
      "args": ["-y", "@barissozudogru/test-intel-mcp"]
    }
  }
}
Continue.dev

Config file: ~/.continue/config.yaml

mcpServers:
  - name: test-intel
    command: npx
    args:
      - -y
      - "@barissozudogru/test-intel-mcp"
Zed

Config file: ~/.config/zed/settings.json

{
  "context_servers": {
    "test-intel": {
      "command": {
        "path": "npx",
        "args": ["-y", "@barissozudogru/test-intel-mcp"]
      }
    }
  }
}
JetBrains (IntelliJ, WebStorm, etc.)
{
  "mcpServers": {
    "test-intel": {
      "command": "npx",
      "args": ["-y", "@barissozudogru/test-intel-mcp"]
    }
  }
}

Option B: HTTP (remote clients)

Start the server:

npx @barissozudogru/test-intel-mcp --http
# or
PORT=3000 TRANSPORT=http npx @barissozudogru/test-intel-mcp

The server listens on http://0.0.0.0:3000/mcp. A health check is available at /health.

Cursor (HTTP)
{
  "mcpServers": {
    "test-intel": {
      "url": "http://localhost:3000/mcp"
    }
  }
}
VS Code + Copilot (HTTP)
{
  "servers": {
    "test-intel": {
      "type": "http",
      "url": "http://localhost:3000/mcp"
    }
  }
}
Windsurf (HTTP)
{
  "mcpServers": {
    "test-intel": {
      "serverUrl": "http://localhost:3000/mcp"
    }
  }
}
Continue.dev (HTTP)
mcpServers:
  - name: test-intel
    url: http://localhost:3000/mcp

Option C: Docker

docker build -t test-intel-mcp .
docker run -p 3000:3000 -v $(pwd):/project -w /project test-intel-mcp

Then configure any HTTP client to point at http://localhost:3000/mcp.


Supported Coverage Formats

FormatExtensionGenerator
lcov.infoJest, Vitest, nyc, Istanbul
istanbul.jsonJest, nyc, Istanbul
cobertura.xmlJest, pytest-cov, JaCoCo

Format is auto-detected from file extension when format is omitted.


Requirements

  • Node.js >= 18
  • No authentication or network access required
  • All file analysis runs locally

License

MIT

Reviews

No reviews yet

Be the first to review this server!

Test Intel MCP Server - Coverage analysis, untested function detection and | MCP Marketplace