Repomix vs Xmcp Docs

A side-by-side look at the Repomix and Xmcp Docs 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
X
Xmcp DocsDeveloper Tools · Remote HTTP/SSE
Search and retrieve the official xmcp documentation from AI coding agents. This free, read-only remote MCP server helps developers build MCP servers with TypeScript. Connect over Streamable HTTP at https://xmcp.dev/mcp with no authentication. Documentation: https://xmcp.dev/docs/guides/xmcp-mcp-server. Source: https://github.com/basementstudio/xmcp/tree/main/apps/website.54GoodAuth: no auth required

Verdict: choose Repomix for developer tools work as a local process; choose Xmcp Docs 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

X
Choose Xmcp Docs when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: No auth required.
  • You want tools like search.
Explore Xmcp Docs

Feature & specification comparison

Rows where the two servers differ are marked.

SpecRepomix logoRepomix
X
Xmcp Docs
CategoryDeveloper ToolsDeveloper Tools
Quality signal64/100 · Good54/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars28,979—
Directory activity 3 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools231

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

Xmcp Docs tools 1

  • searchSearch xmcp documentation.

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"
      ]
    }
  }
}

Xmcp Docs

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "xmcp-docs": {
      "url": "https://xmcp.dev/mcp"
    }
  }
}

Frequently asked questions

Repomix is categorized under Developer Tools and uses a local stdio subprocess. Xmcp Docs belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Repomix for developer tools work and Xmcp Docs 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. Xmcp Docs is listed as free. Auth: no auth required. 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 xmcp-docs 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 28,979 GitHub stars. Xmcp Docs has 54/100 (Good) with 1 views, 0 installs and 0 GitHub stars.