Repomix
NPM · REPOMIX · SCANNED SEP 24
Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 57 of 171 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to yamadashy/repomix). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2026 tokens (~337/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the Repomix MCP server?
Repomix runs locally as an npm package, launched with npx -y repomix. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · repomix
claude mcp add yamadashy-repomix -- npx -y repomix
{
"mcpServers": {
"yamadashy-repomix": {
"command": "npx",
"args": [
"-y",
"repomix"
]
}
}
} {
"servers": {
"yamadashy-repomix": {
"command": "npx",
"args": [
"-y",
"repomix"
]
}
}
} codex mcp add yamadashy-repomix -- npx -y repomix
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"yamadashy-repomix": {
"type": "local",
"command": [
"npx",
"-y",
"repomix"
],
"enabled": true
}
}
} openclaw mcp add yamadashy-repomix --command npx --arg -y --arg repomix
mcp_servers:
yamadashy-repomix:
command: "npx"
args: ["-y", "repomix"] {
"McpServers": {
"yamadashy-repomix": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"repomix"
]
}
}
} assistant mcp add yamadashy-repomix -t stdio -c npx -a -y repomix
{
"mcpServers": {
"yamadashy-repomix": {
"command": "npx",
"args": [
"-y",
"repomix"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 81
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Analysed npm/repomix@1.18.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | yamadashy/repomix |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/yamadashy/repomix/.github/workflows/npm-publish.yml@refs/heads/main |
| Rekor log index | 2905194443 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:5ed575a83e9a9094a2810ddf0517b1e6ffab59c19ae22f5c9b614bfccfcf12dccedeed6e0e2b28dc2b4d6e195988c22a26cb40772f268f69b5ca73b33 |
Background: How many MCP packages publish verified provenance →
Dependencies 171 packages
| Packages resolved | 171 |
|---|---|
| Deprecated | 1 |
| Stale | 56 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
attach_packed_output Attach Packed Output ~190
Attach an existing Repomix packed output file for AI analysis. This tool accepts either a directory containing a repomix output file or a direct path to a packed repository file. Supports multiple formats: XML (structured with <file> tags), Markdown (human-readable with ## headers and code blocks), JSON (machine-readable with files as key-value pairs), and Plain text (simple format with separators). Calling the tool again with the same file path will refresh the content if the file has been updated. It will return in that case a new output ID and the updated content.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Path to a directory containing repomix output file or direct path to a packed repository file (supports .xml, .md, .txt, .json formats) |
| topFilesLength | integer | – | Number of largest files by size to display in the metrics summary (default: 10) |
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | Human-readable description of the attached output |
| directoryStructure | string | yes | Tree structure extracted from the packed output |
| outputFilePath | string | yes | File path to the attached output file |
| outputId | string | yes | Unique identifier for accessing the packed content |
| result | string | yes | JSON string containing detailed metrics and file information |
| totalFiles | number | yes | Total number of files in the packed output |
| totalTokens | number | yes | Total token count of the content |
No examples provided.
generate_skill Generate Claude Agent Skill ~382
Generate a Claude Agent Skill from a local code directory. Creates a skill package containing SKILL.md (entry point with metadata) and references/ folder with summary.md, project-structure.md, files.md, and optionally tech-stacks.md. This tool creates Project Skills in <project>/.claude/skills/<name>/, which are shared with the team via version control. Output Structure: .claude/skills/<skill-name>/ ├── SKILL.md # Entry point with usage guide └── references/ ├── summary.md # Purpose, format, and statistics ├── project-structure.md # Directory tree with line counts ├── files.md # All file contents └── tech-stacks.md # Languages, frameworks, dependencies (if detected) Example Path: /path/to/project/.claude/skills/repomix-reference-myproject/
| Name | Type | Req | Description |
|---|---|---|---|
| compress | boolean | – | Enable Tree-sitter compression to extract essential code signatures and structure while removing implementation details (default: false). |
| directory | string | yes | Directory to pack (Absolute path) |
| ignorePatterns | string | – | Specify additional files to exclude using fast-glob patterns. Multiple patterns can be comma-separated (e.g., "test/**,*.spec.js"). |
| includePatterns | string | – | Specify files to include using fast-glob patterns. Multiple patterns can be comma-separated (e.g., "**/*.{js,ts}", "src/**,docs/**"). |
| skillName | string | – | Name of the skill to generate (kebab-case, max 64 chars). Will be normalized if not in kebab-case. Used for the skill directory name and SKILL.md metadata. If omitted, auto-generates as "repomix-refe… |
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | Human-readable description of the skill generation results |
| skillName | string | yes | Normalized name of the generated skill |
| skillPath | string | yes | Path to the generated skill directory |
| totalFiles | number | yes | Total number of files processed |
| totalTokens | number | yes | Total token count of the content |
No examples provided.
grep_repomix_output Grep Repomix Output ~185
Search for patterns in a Repomix output file using grep-like functionality with JavaScript RegExp syntax. Returns matching lines with optional context lines around matches.
| Name | Type | Req | Description |
|---|---|---|---|
| afterLines | number | – | Number of context lines to show after each match (like grep -A). Takes precedence over contextLines. |
| beforeLines | number | – | Number of context lines to show before each match (like grep -B). Takes precedence over contextLines. |
| contextLines | number | – | Number of context lines to show before and after each match (default: 0). Overridden by beforeLines/afterLines if specified. |
| ignoreCase | boolean | – | Perform case-insensitive matching (default: false) |
| outputId | string | yes | ID of the Repomix output file to search |
| pattern | string | yes | Search pattern (JavaScript RegExp regular expression syntax) |
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | Human-readable description of the search results |
| formattedOutput | array | yes | Formatted grep-style output with context lines |
| matches | array | yes | Array of search matches found |
| pattern | string | yes | The search pattern that was used |
| totalMatches | number | yes | Total number of matches found |
No examples provided.
pack_codebase Pack Local Codebase ~493
Package a local code directory into a consolidated file for AI analysis. This tool analyzes the codebase structure, extracts relevant code content, and generates a comprehensive report including metrics, file tree, and formatted code content. Supports multiple output formats: XML (structured with <file> tags), Markdown (human-readable with ## headers and code blocks), JSON (machine-readable with files as key-value pairs), and Plain text (simple format with separators). Also supports Tree-sitter compression for efficient token usage.
| Name | Type | Req | Description |
|---|---|---|---|
| compress | boolean | – | 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 n… |
| directory | string | yes | Directory to pack (Absolute path). Any directory readable by this process can be packed. |
| ignorePatterns | string | – | 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 and… |
| includePatterns | string | – | 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. Useful for focusing on spe… |
| outputPatterns | array | – | Per-file inclusion levels. Patterns are evaluated in order and the first match wins; directoryStructureOnly takes precedence over compress, and a match with neither flag forces FULL content (use this… |
| style | string | – | Output format style: xml (structured tags, default), markdown (human-readable with code blocks), json (machine-readable key-value), or plain (simple text with separators) |
| topFilesLength | integer | – | Number of largest files by size to display in the metrics summary for codebase analysis (default: 10) |
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | Human-readable description of the packing results |
| directoryStructure | string | yes | Tree structure of the processed directory |
| outputFilePath | string | yes | File path to the generated output file |
| outputId | string | yes | Unique identifier for accessing the packed content |
| result | string | yes | JSON string containing detailed metrics and file information |
| totalFiles | number | yes | Total number of files processed |
| totalTokens | number | yes | Total token count of the content |
No examples provided.
pack_remote_repository Pack Remote Repository ~531
Fetch, clone, and package a GitHub repository into a consolidated file for AI analysis. This tool automatically clones the remote repository, analyzes its structure, and generates a comprehensive report. Supports multiple output formats: XML (structured with <file> tags), Markdown (human-readable with ## headers and code blocks), JSON (machine-readable with files as key-value pairs), and Plain text (simple format with separators). Also supports various GitHub URL formats. Files matching known secret formats are excluded, but that scan is a heuristic, not an access boundary.
| Name | Type | Req | Description |
|---|---|---|---|
| compress | boolean | – | 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 n… |
| ignorePatterns | string | – | 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 and… |
| includePatterns | string | – | 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. Useful for focusing on spe… |
| outputPatterns | array | – | Per-file inclusion levels. Patterns are evaluated in order and the first match wins; directoryStructureOnly takes precedence over compress, and a match with neither flag forces FULL content (use this… |
| remote | string | yes | GitHub repository URL or user/repo format (e.g., "yamadashy/repomix", "https://github.com/user/repo", or "https://github.com/user/repo/tree/branch") |
| style | string | – | Output format style: xml (structured tags, default), markdown (human-readable with code blocks), json (machine-readable key-value), or plain (simple text with separators) |
| topFilesLength | integer | – | Number of largest files by size to display in the metrics summary for codebase analysis (default: 10) |
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | Human-readable description of the packing results |
| directoryStructure | string | yes | Tree structure of the processed repository |
| outputFilePath | string | yes | File path to the generated output file |
| outputId | string | yes | Unique identifier for accessing the packed content |
| result | string | yes | JSON string containing detailed metrics and file information |
| totalFiles | number | yes | Total number of files processed |
| totalTokens | number | yes | Total token count of the content |
No examples provided.
read_repomix_output Read Repomix Output ~136
Read the contents of a Repomix-generated output file. Supports partial reading with line range specification for large files. This tool is designed for environments where direct file system access is limited (e.g., web-based environments, sandboxed applications). For direct file system access, use standard file operations.
| Name | Type | Req | Description |
|---|---|---|---|
| endLine | number | – | Ending line number (1-based, inclusive). If not specified, reads to end. |
| outputId | string | yes | ID of the Repomix output file to read |
| startLine | number | – | Starting line number (1-based, inclusive). If not specified, reads from beginning. |
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The file content or specified line range |
| endLine | number | – | Ending line number used |
| linesRead | number | yes | Number of lines actually read |
| startLine | number | – | Starting line number used |
| totalLines | number | yes | Total number of lines in the file |
No examples provided.
What is the Repomix MCP server?
Repomix is an MCP server listed in the public MCP registry as io.github.yamadashy/repomix. Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search. This page covers its npm package (repomix).
Is the Repomix MCP server safe to use?
Repomix scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Repomix MCP server expose?
Repomix exposes 6 tools: pack_codebase, read_repomix_output, grep_repomix_output, pack_remote_repository, generate_skill, attach_packed_output. Their descriptions and schemas cost roughly 1,917 tokens of context every time the server is loaded.
Is the Repomix MCP server still maintained?
Repomix is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Repomix MCP server under?
Repomix declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.