Repomix MCP (official)
Score = points from 5 automated checks. Not a quality or security rating. Methodology
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs15/15
- License10/10
Tested npm repomix 1.18.1 started as `repomix --mcp` (repo yamadashy/repomix). Its 6 tools listed without credentials. Real tool calls (no LLM, no credentials): pack_codebase packed a 2-file local folder and grep_repomix_output searched the packed output. pack_remote_repository (clones from GitHub), generate_skill, attach_packed_output and read_repomix_output were not called.
Tool-call test (2026-11-02, direct MCP stdio client, no LLM): pass. 2 of 2 calls passed: pack_codebase packed a local folder and grep_repomix_output searched the result. No credentials; remote-repo packing not tested. Evidence: local test run, Nov 2, 2026.
Transport (tested 2026-11-02): stdio
Score 100/100 · Tools 6 · Token cost ~2,516 · Compare · Last tested 2026-11-02 · Version tested 1.18.1 · Package repomix · Repo yamadashy/repomix
Summary: Repomix MCP (official) completed an MCP handshake without credentials and exposed 6 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 6
- Context cost
- 2,516 model-visible tokens (name, description, inputSchema; tiktoken cl100k_base)
Extra payload (sent by the server, usually not read by the model): 1,192 tokens; raw tools/list total 3,708. Clients differ in what they forward. ranking · add up your servers' context cost - API key
- No key needed for the tools we called
- Tested
- 2026-11-02
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install repomix (Node 20, Linux) succeeded in 3s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 6 tools listed in 7.4s. |
| maintenance | pass | 25 | Repo pushed 0 days before test; 29,112 GitHub stars. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Automated check of the package's own README (README shipped in npm package). |
| license | pass | 10 | MIT (OSI-approved). |
Local-model readiness
Schema context cost: ~2,516 tokens for 6 tools (11,914 bytes) · about 31% of an 8k context. Method: tiktoken cl100k_base over compact JSON of name+description+inputSchema (approximate).
Small-model friendly (schema heuristic, not a model result): unknown.
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-02
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 6 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Tool-schema token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that it is safe to give it access to your data.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-02 test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
2a58088542cf: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "repomix",
"version": "1.18.1",
"registry": "npm",
"status": "working",
"tested": "2026-11-02",
"tools_count": 6,
"tools_schema_tokens_est": 2516,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`npm install repomix` (Node 20, Linux) succeeded in 3s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 6 tools listed in 7.4s."
],
"maintenance": [
"pass",
25,
"Repo pushed 0 days before test; 29,112 GitHub stars."
],
"docs": [
"pass",
15,
"README over 3,000 chars; install instructions present; `mcpServers` config example present. Automated check of the package's own README (README shipped in npm package)."
],
"license": [
"pass",
10,
"MIT (OSI-approved)."
]
}
}Install
npx -y repomix --mcp
Tools listed
pack_codebase, read_repomix_output, grep_repomix_output, pack_remote_repository, generate_skill, attach_packed_output
Quick config
{
"mcpServers": {
"repomix-mcp": {
"command": "npx",
"args": [
"-y",
"repomix",
"--mcp"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
npm install repomix(Node 20). This is the exact command we ran on 2026-11-02. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (6 in our test).
{
"mcpServers": {
"repomix-mcp": {
"command": "npx",
"args": [
"-y",
"repomix",
"--mcp"
]
}
}
}Test history
No dated events yet.
FAQ
Is Repomix MCP (official) deprecated?
No. repomix was not deprecated or archived when we last tested it on 2026-11-02.
What replaces Repomix MCP (official)?
Nothing; Repomix MCP (official) is not deprecated as of 2026-11-02.
Does Repomix MCP (official) need an API key?
No. It completed an MCP handshake with no credentials and listed 6 tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.