In-depth architectural comparison of the MCP Documentation Server and Refigure MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
MCP Documentation Server
Developer Tools · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Refigure
Developer Tools · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose MCP Documentation Server if you need specialized Developer Tools tools running via a local process. Choose Refigure if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
M
Choose MCP Documentation Server when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
MCP Documentation Server is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Refigure belongs to Developer Tools using local stdio subprocess. Select MCP Documentation Server when you need capabilities focused on developer tools and Refigure when you require tools for developer tools.
Local-first document management and semantic search for AI coding agents
Convert DOCX/XLSX to Markdown with native OOXML chart-data extraction (real numbers, no OCR or rasterization) and zero-loss composite-figure markers for images a chart parser cannot read. CLI, MCP server (stdio + Streamable HTTP), optional VLM fallback for figures with no native chart data.