Hub MCP vs Repomix

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

Hub MCP logoHub MCPDeveloper Tools · Remote HTTP/SSEOfficial MCP server to interact with Docker Hub, providing access to repositories, hub search and Docker Hardened Images77GreatAuth: api key requiredRepomix 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

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

Which MCP server should you choose?

Hub MCP logoChoose Hub MCP when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: HUB_PAT_TOKEN, MCP_AUTH_TOKEN.
  • You want tools like search, query, architectures.
Explore Hub MCP

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecHub MCP logoHub MCPRepomix logoRepomix
CategoryDeveloper ToolsDeveloper Tools
Quality signal77/100 · Great64/100 · Good
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthAPI key requiredNot declared
PricingFreeNot declared
Required env varsHUB_PAT_TOKENMCP_AUTH_TOKENNone listed
Verified owner VerifiedCommunity listing
GitHub stars16929,001
Directory activity 49 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
Tools3523

Tools & capabilities

Hub MCP tools 35

  • searchSearch repositories and content using Search V4 API
  • querySearch query parameter (string, required)
  • architecturesFilter on architectures (string, optional)
  • badgesFilter by image content type badges (string, optional)
  • categoriesFilter on categories (string, optional)
  • extension_reviewedFilter on reviewed extensions (boolean, optional)
  • fromNumber of documents to skip for pagination (number, optional)
  • imagesFilter on image names (string, optional)
  • operating_systemsFilter on operating systems (string, optional)
  • orderChange the ordering of results (string, optional)
  • sizeMaximum number of results to return (number, optional)
  • sortSort results by search field (string, optional)
  • +23 more on the listing page

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

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.

Hub MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "docker-hub-mcp": {
      "url": "https://docs.docker.com/ai/gordon/mcp/yaml/"
    }
  }
}

Repomix

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

Frequently asked questions

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

Hub MCP is listed as free. Auth: api key required. Repomix 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 docker-hub-mcp and repomix as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Hub MCP has a quality signal of 77/100 (Great) with 49 views, 0 installs and 169 GitHub stars. Repomix has 64/100 (Good) with 3 views, 0 installs and 29,001 GitHub stars.