Repomix vs Xmp4 — Semantic Code Intelligence

A side-by-side look at the Repomix and Xmp4 — Semantic Code Intelligence 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 declaredXmp4 — Semantic Code Intelligence logoXmp4 — Semantic Code IntelligenceDeveloper Tools · Remote HTTP/SSESCIP-backed semantic code intelligence over 800+ pre-indexed OSS libraries. Hosted, free.53GoodAuth: not declared

Verdict: choose Repomix for developer tools work as a local process; choose Xmp4 — Semantic Code Intelligence for developer tools over a hosted endpoint. 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

Xmp4 — Semantic Code Intelligence logoChoose Xmp4 — Semantic Code Intelligence when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a remote HTTP/SSE transport.
  • You want tools like xmp4_callees, xmp4_callers, xmp4_deps.
Explore Xmp4 — Semantic Code Intelligence

Feature & specification comparison

Rows where the two servers differ are marked.

SpecRepomix logoRepomixXmp4 — Semantic Code Intelligence logoXmp4 — Semantic Code Intelligence
CategoryDeveloper ToolsDeveloper Tools
Quality signal64/100 · Good53/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars29,0071
Directory activity 3 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools2316

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

Xmp4 — Semantic Code Intelligence tools 16

  • xmp4_calleesFind direct callees (methods called by) a symbol in a project. Navigate step-by-step by calling xmp4_callees again on interesting results.
  • xmp4_callersFind direct callers of a symbol in a project. Navigate step-by-step by calling xmp4_callers again on interesting results.
  • xmp4_depsList external dependencies of a project.
  • xmp4_grepServer-side regex text search over indexed project source files. Free tier: requires file_path (single file). Premium tier (XMP4_PREMIUM_GREP_WALK=true): allows file_glob multi-file walk. Prefer xmp4_tests_for/xmp4_usages for SCIP symbols — grep is for text not indexed (comments, literals, config keys).
  • xmp4_guideUsage guide for xmp4 tools — read this first to learn the correct workflow
  • xmp4_hierarchyGet type hierarchy (base, interfaces, derived) for a symbol in a project.
  • xmp4_infoGet detailed information about a symbol in a project.
  • xmp4_outlineGet outline (all symbols) for a file in a project.
  • xmp4_projectsSearch and browse projects by language and name. Use this first to discover projects, then use other tools with the repo name.
  • xmp4_searchSearch symbols in a project. Use xmp4_projects first to find the project identifier.
  • xmp4_serverGet server information, version, and capabilities
  • xmp4_sourceExtract source code for a symbol in a project.
  • +4 more on 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"
      ]
    }
  }
}

Xmp4 — Semantic Code Intelligence

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "xmp4-semantic-code-intelligence": {
      "url": "https://mcp.example4.ai/mcp"
    }
  }
}

Frequently asked questions

Repomix is categorized under Developer Tools and uses a local stdio subprocess. Xmp4 — Semantic Code Intelligence belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Repomix for developer tools work and Xmp4 — Semantic Code Intelligence 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.

Repomix has no declared pricing — check the project's own site. Xmp4 — Semantic Code Intelligence 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 xmp4-semantic-code-intelligence 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. Xmp4 — Semantic Code Intelligence has 53/100 (Good) with 1 views, 0 installs and 1 GitHub stars.