Refigure vs AgentPhone — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Refigure vs AgentPhone
In-depth architectural comparison of the Refigure and AgentPhone 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
Refigure
Developer Tools · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
AgentPhone
Developer Tools · Local stdio
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Refigure if you need specialized Developer Tools tools running via a local process. Choose AgentPhone 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?
R
Choose Refigure 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).
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.
Give AI agents real phone numbers, messages, and voice calls via MCP.
Refigure is categorized under Developer Tools and uses a local stdio subprocess. In contrast, AgentPhone belongs to Developer Tools using local stdio subprocess. Select Refigure when you need capabilities focused on developer tools and AgentPhone when you require tools for developer tools.