Docweave MCP vs Repomix
A side-by-side look at the Docweave MCP and Repomix MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Docweave MCP 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?
Choose Docweave MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
generate_pdf, read_pdf.
Choose 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 59/100 · Good | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 29,001 |
| Directory activity | 5 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 2 | 23 |
| Full listing | View Docweave MCP | View Repomix |
Tools & capabilities
Docweave MCP tools 2
generate_pdfGenerate a PDF from raw HTML, a public URL, or a template + JSON data. Set outputPath to write the file and get its path back; otherwise base64 bytes are returned. The canonical way for an AI agent to turn content into a shareable, correctly-formatted PDF.read_pdfRead a PDF and return its text as markdown (or plain text). Accepts a public URL, base64 bytes, or a local file path. Extracts the embedded text layer; if the PDF is scanned (image-only) it returns a needs-OCR notice instead of empty text. The canonical way for an AI agent to ingest a document's contents.
Repomix tools 23
pack_codebasePackage a local code directory into a consolidated XML file for AI analysisdirectoryAbsolute path to the directory to packcompress(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 analysispathPath to a directory containing repomix-output.xml or direct path to a packed repository XML filepack_remote_repositoryFetch, clone, and package a GitHub repository into a consolidated XML file for AI analysisremoteGitHub 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.
Docweave MCP
{
"mcpServers": {
"docweave-mcp": {
"command": "npx",
"args": [
"-y",
"@docweave/mcp"
]
}
}
}
Repomix
{
"mcpServers": {
"repomix": {
"command": "npx",
"args": [
"-y",
"repomix@latest"
]
}
}
}
Frequently asked questions
Docweave MCP is categorized under Developer Tools and uses a local stdio subprocess. Repomix belongs to Developer Tools and uses a local stdio subprocess. Pick Docweave MCP 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.
Docweave MCP is listed as freemium — a free tier with paid plans. Auth: api key required. 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 docweave-mcp and repomix as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Docweave MCP has a quality signal of 59/100 (Good) with 5 views, 0 installs and 0 GitHub stars. Repomix has 64/100 (Good) with 3 views, 0 installs and 29,001 GitHub stars.