MCP Server Analyzer vs MCP Pandoc
A side-by-side look at the MCP Server Analyzer and MCP Pandoc MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Server Analyzer for developer tools work as a local process; choose MCP Pandoc 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 MCP Server Analyzer when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
ruff-check, ruff-format, ruff-check-ci.
Choose MCP Pandoc when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
convert-contents.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 57/100 · Good | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 11 | 583 |
| Directory activity | 1 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 5 | 1 |
| Full listing | View MCP Server Analyzer | View MCP Pandoc |
Tools & capabilities
MCP Server Analyzer tools 5
ruff-checkLint Python code using RUFF to identify style violations and potential errors.ruff-formatFormat Python code using RUFF's fast formatter.ruff-check-ciRun RUFF linter with CI/CD-specific output formats.vulture-scanDetect dead/unused code using VULTURE.analyze-codeComprehensive analysis combining RUFF linting and VULTURE dead code detection.
MCP Pandoc tools 1
convert-contentsConverts content between different formats. Transforms input content from any supported format into the specified output format. 🚨 CRITICAL REQUIREMENTS - PLEASE READ: 1. PDF Conversion: * You MUST install TeX Live BEFORE attempting PDF conversion: * Ubuntu/Debian: `sudo apt-get install texlive-xetex` * macOS: `brew install texlive` * Windows: Install MiKTeX or TeX Live from https://miktex.org/ or https://tug.org/texlive/ * PDF conversion will FAIL without this installation 2. File Paths - EXPLICIT REQUIREMENTS: * When asked to save or convert to a file, you MUST provide: - Complete directory path - Filename - File extension * Example request: 'Write a story and save as PDF' * You MUST specify: '/path/to/story.pdf' or 'C:\Documents\story.pdf' * The tool will NOT automatically generate filenames or extensions 3. File Location After Conversion: * After successful conversion, the tool will display the exact path where the file is saved * Look for message: 'Content successfully converted and saved to: [file_path]' * You can find your converted file at the specified location * If no path is specified, files may be saved in system temp directory (/tmp/ on Unix systems) * For better control, always provide explicit output file paths Supported formats: - Basic (returned inline): txt, html, markdown, ipynb - Advanced (REQUIRE complete file paths): pdf, docx, rst, latex, epub, odt, pptx - pptx is WRITE-ONLY: it can be produced, but not used as an input format ✅ CORRECT Usage Examples: 1. 'Convert this text to HTML' (basic conversion) - Tool will show converted content 2. 'Save this text as PDF at /documents/story.pdf' - Correct: specifies path + filename + extension - Tool will show: 'Content successfully converted and saved to: /documents/story.pdf' ❌ INCORRECT Usage Examples: 1. 'Save this as PDF in /documents/' - Missing filename and extension 2. 'Convert to PDF' - Missing complete file path When requesting conversion, ALWAYS specify: 1. The content or input file 2. The desired output format 3. For advanced formats: complete output path + filename + extension Example: 'Convert this markdown to PDF and save as /path/to/output.pdf' 🎨 DOCX, ODT & PPTX STYLING: 4. Custom Styling with Reference Documents: * Use reference_doc parameter to apply professional styling to DOCX, ODT and PPTX output * The reference document MUST match the output format: .docx for docx, .odt for odt, .pptx for pptx * Create custom templates with your branding, fonts, and formatting * Perfect for corporate reports, academic papers, and professional documents * Example: 'Convert this report to DOCX using /templates/corporate-style.docx as reference and save as /reports/Q4-report.docx' 🎯 PANDOC FILTERS (NEW FEATURE): 5. Pandoc Filter Support: * Use filters parameter to apply custom Pandoc filters during conversion * Filters are Python scripts that modify document content during processing * Perfect for Mermaid diagram conversion, custom styling, and content transformation * Example: 'Convert this markdown with mermaid diagrams to DOCX using filters=["./filters/mermaid-to-png-vibrant.py"] and save as /reports/diagram-report.docx' 📋 Creating Reference Documents: * Generate template: pandoc -o template.docx --print-default-data-file reference.docx * Customize in Word/LibreOffice: fonts, colors, headers, margins * Use for consistent branding across all documents 📋 Filter Requirements: * Filters must be executable Python scripts * Use absolute paths or paths relative to current working directory * Filters are applied in the order specified * Common filters: mermaid conversion, color processing, table formatting 📄 Defaults File Support (NEW FEATURE): 7. Pandoc Defaults File Support: * Use defaults_file parameter to specify a YAML configuration file * Similar to using pandoc -d option in the command line * Allows setting multiple options in a single file * Options in the defaults file can include filters, reference-doc, and other Pandoc options * Example: 'Convert this markdown to DOCX using defaults_file="/path/to/defaults.yaml" and save as /reports/report.docx' Note: After conversion, always check the success message for the exact file location.
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.
MCP Server Analyzer
{
"mcpServers": {
"mcp-server-analyzer": {
"command": "uvx",
"args": [
"mcp-server-analyzer"
]
}
}
}
MCP Pandoc
{
"mcpServers": {
"vivekvells-mcp-pandoc": {
"command": "uvx",
"args": [
"mcp-pandoc"
]
}
}
}
Frequently asked questions
MCP Server Analyzer is categorized under Developer Tools and uses a local stdio subprocess. MCP Pandoc belongs to Developer Tools and uses a local stdio subprocess. Pick MCP Server Analyzer for developer tools work and MCP Pandoc 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.
MCP Server Analyzer has no declared pricing — check the project's own site. MCP Pandoc is listed as free. Auth: no auth required. 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 mcp-server-analyzer and vivekvells-mcp-pandoc as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Server Analyzer has a quality signal of 57/100 (Good) with 1 views, 0 installs and 11 GitHub stars. MCP Pandoc has 64/100 (Good) with 5 views, 0 installs and 583 GitHub stars.