Repomix vs VHGENGINE

A side-by-side look at the Repomix and VHGENGINE MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Repomix logoRepomixDeveloper Tools · Local subprocess (stdio)Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search64GoodAuth: not declared
V
VHGENGINEDeveloper Tools
Agents-first viral-hook engine: generate, score, and remix short-form hooks over MCP.37FairAuth: not declared

Verdict: choose Repomix for developer tools work as a local process; choose VHGENGINE for developer tools. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Repomix logoChoose Repomix when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like pack_codebase, directory, compress.
Explore Repomix

V
Choose VHGENGINE when

  • You need dedicated capabilities in the Developer Tools domain.
Explore VHGENGINE

Feature & specification comparison

Rows where the two servers differ are marked.

SpecRepomix logoRepomix
V
VHGENGINE
CategoryDeveloper ToolsDeveloper Tools
Quality signal64/100 · Good37/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars29,007—
Directory activity 3 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools23Not listed

Tools & capabilities

Repomix tools 23

  • pack_codebasePackage a local code directory into a consolidated XML file for AI analysis
  • directoryAbsolute path to the directory to pack
  • compress(Optional, default: false) Enable Tree-sitter compression to extract essential code signatures and structure while removing implementation details. Reduces token usage by ~70% while preserving semantic meaning. Generally not needed since grep_repomix_output allows incremental content retrieval. Use…
  • includePatterns(Optional) Specify files to include using fast-glob patterns. Multiple patterns can be comma-separated (e.g., "**/*.{js,ts}", "src/**,docs/**"). Only matching files will be processed.
  • ignorePatterns(Optional) Specify additional files to exclude using fast-glob patterns. Multiple patterns can be comma-separated (e.g., "test/**,*.spec.js", "node_modules/**,dist/**"). These patterns supplement .gitignore, .ignore, and built-in exclusions.
  • outputPatterns(Optional) Per-file inclusion levels, mirroring the config-file `output.patterns` option. An array of `{ pattern, compress?, directoryStructureOnly? }` entries; the first matching pattern wins, `directoryStructureOnly` takes precedence over `compress`, and a match with neither flag forces full cont…
  • topFilesLength(Optional, default: 10) Number of largest files by size to display in the metrics summary for codebase analysis.
  • attach_packed_outputAttach an existing Repomix packed output file for AI analysis
  • pathPath to a directory containing repomix-output.xml or direct path to a packed repository XML file
  • pack_remote_repositoryFetch, clone, and package a GitHub repository into a consolidated XML file for AI analysis
  • remoteGitHub repository URL or user/repo format (e.g., "yamadashy/repomix", "https://github.com/user/repo", or "https://github.com/user/repo/tree/branch")
  • read_repomix_outputRead the contents of a Repomix-generated output file. Supports partial reading with line range specification for large files.
  • +11 more on the listing page

VHGENGINE tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Repomix

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "repomix": {
      "command": "npx",
      "args": [
        "-y",
        "repomix@latest"
      ]
    }
  }
}

VHGENGINE

No confirmed install command for VHGENGINE yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Repomix is categorized under Developer Tools and uses a local stdio subprocess. VHGENGINE belongs to Developer Tools and uses an install path we have not confirmed yet. Pick Repomix for developer tools work and VHGENGINE for developer tools.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. VHGENGINE has no confirmed install command yet — follow its own setup instructions.

Repomix has no declared pricing — check the project's own site. VHGENGINE has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add repomix and vhgengine as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Repomix has a quality signal of 64/100 (Good) with 3 views, 0 installs and 29,007 GitHub stars. VHGENGINE has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.