mcp-server-repomix

Provides a Zed editor MCP server extension that exposes Repomix functionality (packing repositories and querying packed output) to AI assistants via MCP tools.

Evaluated Apr 04, 2026 (16d ago)
Repo ↗ DevTools zed mcp repomix codebase-packing repository-analysis developer-tools rust nodejs
⚙ Agent Friendliness
53
/ 100
Can an agent use this?
🔒 Security
34
/ 100
Is it safe for agents?
⚡ Reliability
26
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
55
Documentation
65
Error Messages
0
Auth Simplicity
95
Rate Limits
10

🔒 Security

TLS Enforcement
70
Auth Strength
20
Scope Granularity
0
Dep. Hygiene
45
Secret Handling
40

This extension shells out to Repomix (Node-based) and can pack remote repositories by URL. The README does not describe authentication, sandboxing, or secret-handling/logging behavior. Agents should assume repository contents may be read and processed locally and possibly transmitted to remote hosts when fetching remote URLs.

⚡ Reliability

Uptime/SLA
0
Version Stability
35
Breaking Changes
40
Error Recovery
30
AF Security Reliability

Best When

You want an editor-integrated workflow (Zed MCP) to convert repositories into compact context for LLM analysis.

Avoid When

You require formal REST/SDK contracts, OAuth-style auth, or clearly documented rate limiting/error recovery semantics.

Use Cases

  • Pack a local repository into an AI-friendly single output
  • Pack and analyze a remote repository by URL
  • Search within packed repository output for specific patterns
  • Extract/read specific files or sections from packed output
  • Generate shareable codebase snapshots for AI analysis

Not For

  • Use as a general-purpose code search/indexing service
  • Handling secrets or sensitive repositories without explicit data-governance review
  • Production-grade integrations needing documented stability/SLA guarantees

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

OAuth: No Scopes: No

No authentication mechanism is described for the MCP server/extension itself. The workflow appears local/editor-mediated; access control is likely delegated to the host environment (Zed) and the user’s filesystem permissions.

Pricing

Free tier: No
Requires CC: No

Pricing is not described; this is an editor extension using local tools (Repomix via Node).

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Packing remote repositories may require network access and can be slow; no explicit timeout/retry guidance is provided in the README.
  • Behavior and output size constraints are not documented; agents should manage large repositories carefully to avoid oversized context outputs.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-server-repomix.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered