Hosting

Self-hosted local process scanning only the paths passed to the command.

Transport

stdio

Endpoint

Local process; no hosted endpoint documented

Authentication

No external credentials are required for local analysis.

Requirements

• jscpd 5.0.16 or newer, when the MCP server was added; use the current v5 release.
• A supported installation path: npm/npm npx, PyPI, Cargo, Homebrew, Nix, Docker, or official release binary.
• Read access to the project files being scanned.

Setup steps

1. Install jscpd using an official method from https://jscpd.dev/start/installation/. The official project documents `npm install -g jscpd` and `npx jscpd .`; v5 is a self-contained Rust binary and does not need Node.js at runtime, though npx itself needs Node.js.
2. Configure a stdio MCP process with command `jscpd` and args `--mcp`, `<absolute-project-path>`. Use an absolute path to the repository that the agent should scan; the MCP server scans the selected paths on startup.
3. For example, after installing the current jscpd package with npm, configure `{ command: "jscpd", args: ["--mcp", "C:/path/to/project"] }` using the actual absolute project path.
4. Reconnect the MCP client and inspect tools/list. A harmless initial check is `get_statistics`. After edits, call `check_current_directory` to refresh the scan before querying results.

The official MCP guide documents the named read-only tools below. The inventory is documentation-based, not a live tools/list response; some options require embeddings or specific server configuration.

• check_duplication

  Compare a code snippet with the scanned project for duplicate or similar code.

  01
• get_file_clones

  List clones involving a selected scanned file.

  02
• get_statistics

  Return duplication statistics from the latest scan.

  03
• check_current_directory

  Rescan configured paths and refresh duplication results.

  04
• compare_folders

  Compare two scanned code folders for function-level porting parity; requires supported embedding setup.

  05

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

• The MCP server is read-only and answers from its last scan; refresh after edits with check_current_directory.
• The server scans the paths given on startup, so restrict the configured path and avoid scanning sensitive directories unintentionally.
• The `compare_folders` capability requires an embedding model or embeddings API; semantic detection has additional model requirements.
• The official source-owner avatar is used as fallback tier D because a suitable standalone product mark was not found in the reviewed official docs.
• Documentation and logo were reviewed; server initialization, tools/list, and tool calls were not tested.

• official mcp documentation

  Documents the built-in v5 stdio MCP server, installation version floor, absolute-path setup, read-only semantics, five tool names and arguments, and scan limitations.

• official installation documentation

  Documents official npm, PyPI, Cargo, Homebrew, Nix, Docker, and platform binary installation methods.

• official repository documentation

  The official repository links to jscpd.dev and documents the v5 self-contained binary and project functionality.

• verified repository owner avatar

  GitHub avatar for the verified owner of the official jscpd repository; downloaded, decoded, and visually reviewed on light and dark backgrounds after no suitable standalone project icon was found. Selection tier D.

• discovery directory

  jscpd appeared in the directory's developer-tools search; used only for discovery.

• official or maintainer tool reference

  Official agent guide documents exactly five read-only tools; catalog rows match.

Documentation checked 2026-10-28T00:00:00Z. Connection has not been runtime tested.