GodPrompt MCP Server vs Repomix

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

GodPrompt MCP Server logoGodPrompt MCP ServerDeveloper Tools · Local subprocess (stdio)GodPrompt workflows for TDD, debugging, verification, task routing, and progressive disclosure.63GoodAuth: not declaredRepomix 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 GodPrompt MCP Server for developer tools work as a local process; 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?

GodPrompt MCP Server logoChoose GodPrompt MCP Server when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like get_god_prompt, get_core_skill, get_protocols.
Explore GodPrompt MCP Server

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.

SpecGodPrompt MCP Server logoGodPrompt MCP ServerRepomix logoRepomix
CategoryDeveloper ToolsDeveloper Tools
Quality signal63/100 · Good64/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars128,979
Directory activity 1 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
Tools723

Tools & capabilities

GodPrompt MCP Server tools 7

  • get_god_promptReturns the complete GodPrompt.md — a single-file universal system prompt for AI software development (47KB, ~1145 lines). Use this when you want the full payload in one shot. For progressive disclosure (smaller context), use get_core_skill and the reference tools instead.
  • get_core_skillReturns SKILL.md — the lean core protocol (~16KB) covering the universal 6-phase protocol, Three Iron Laws, and task auto-classification. Load it at the start of a task or after a context reset, then reuse that context instead of reloading it on every message. Start here for progressive disclosure.
  • get_protocolsReturns references/01-PROTOCOLS.md — deep execution guides for each task type (BUILD, DEBUG, REFACTOR, CONTENT, DESIGN, SHIP, ANALYZE, AUTOMATE, PLAN). Load this when the task requires detailed protocol steps beyond the core skill. ~13KB.
  • get_gatesReturns references/02-GATES.md — verification checklists, THE GATE (pre-completion verification), and structured report templates for every deliverable type. Load when you need to verify work before claiming completion. ~9KB.
  • get_anti_patternsReturns references/03-ANTI-PATTERNS.md — red flags, rationalizations, and recovery patterns. Covers the 10 most dangerous anti-patterns that lead to broken code, scope creep, and false confidence. Load when you catch yourself rationalizing. ~9KB.
  • classify_taskClassify one concrete software-development task into one of GodPrompt's 9 task types (BUILD, DEBUG, REFACTOR, CONTENT, DESIGN, SHIP, ANALYZE, AUTOMATE, PLAN), or UNCLASSIFIED when no reliable route is detected. Returns JSON with task_type, deterministic confidence, protocol, matched_signals, alternative_task_types, ambiguous, and recommendation; use it for routing before loading detailed workflow text.
  • get_versionReturns JSON with the GodPrompt content version, MCP server version, repository, bundled file sizes and purposes, and task-type/protocol catalog. Use it to verify which GodPrompt content/server version a client is connected to; use the content retrieval tools when you need the actual workflow text.

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.

GodPrompt MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "godprompt-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "god-prompt-mcp"
      ]
    }
  }
}

Repomix

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

Frequently asked questions

GodPrompt MCP Server is categorized under Developer Tools and uses a local stdio subprocess. Repomix belongs to Developer Tools and uses a local stdio subprocess. Pick GodPrompt MCP Server 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.

GodPrompt MCP Server has no declared pricing — check the project's own site. 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 godprompt-mcp-server and repomix as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, GodPrompt MCP Server has a quality signal of 63/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Repomix has 64/100 (Good) with 3 views, 0 installs and 28,979 GitHub stars.