Log inSubmit server

Repomix vs Roast My Design System

A side-by-side look at the Repomix and Roast My Design System 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 declaredRoast My Design System logoRoast My Design SystemDeveloper Tools · Local subprocess (stdio)Audit your Design System and serve your Agent the rules that keep AI-written UI on-system.51GoodAuth: no auth required

Verdict: choose Repomix for developer tools work as a local process; choose Roast My Design System 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?

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

Roast My Design System logoChoose Roast My Design System when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore Roast My Design System

Feature & specification comparison

Rows where the two servers differ are marked.

SpecRepomix logoRepomixRoast My Design System logoRoast My Design System
CategoryDeveloper ToolsDeveloper Tools
Quality signal64/100 · Good51/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars28,93027
Directory activity 3 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
Tools23Not listed
Full listingView Repomix View Roast My Design System

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

Roast My Design System 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"
      ]
    }
  }
}

Roast My Design System

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "roast-my-design-system-2": {
      "command": "npx",
      "args": [
        "-y",
        "roast-my-design-system@latest"
      ]
    }
  }
}

Frequently asked questions

Repomix is categorized under Developer Tools and uses a local stdio subprocess. Roast My Design System belongs to Developer Tools and uses a local stdio subprocess. Pick Repomix for developer tools work and Roast My Design System 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. Roast My Design System 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 roast-my-design-system-2 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,930 GitHub stars. Roast My Design System has 51/100 (Good) with 5 views, 0 installs and 27 GitHub stars.

Popular comparisons with Repomix

Popular comparisons with Roast My Design System