Side-by-Side Model Context Protocol Comparison
Amendor MCP vs Unfour
In-depth architectural comparison of the Amendor MCP and Unfour 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
Amendor MCP
Delivery · Local stdio
Quality: 57/100 (Good) | Auth: API Key required
Unfour
Delivery · Local stdio
Quality: 40/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Amendor MCP if you need specialized Delivery tools running via a local process. Choose Unfour if your workspace requires Delivery integration with local subprocess execution. Both servers can be configured concurrently in your client's
mcpServers manifest.Which MCP Server Should You Choose?
Choose Amendor MCP when:
- You need dedicated capabilities in the Delivery domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: API Key required (Freemium).
- You have access to required keys:
AMENDOR_API, AMENDOR_TOKEN. - Primary tools included: list_change_requests, get_change_request, set_preview_url.
Choose Unfour when:
- You need dedicated capabilities in the Delivery domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
Feature & Specification Comparison
Tools & Capabilities Breakdown
Amendor MCP Tools (7)
list_change_requests
List change requests submitted by end users on sites you ship. Optionally filter by status. Start here to see what people are asking for.
get_change_request
Get full detail for one change request so you can implement it: the user request, the exact element they pointed at (CSS selector + outerHTML), the page URL, and a screenshot URL. Call this before making the change.
set_preview_url
Attach a deploy-preview URL to a change request and mark it ready for the requester to review.
update_status
Update a change request status as it moves through the build and review flow.
start_build
LOCAL MODE ONLY (repo on this machine, no host). Cuts a branch + git worktree the local Amendor serves at /preview/<id>/. For the normal GitHub flow, do NOT call this: instead branch "relay/task-<id>" in your own repo clone, edit, commit, push, and open a PR tagged "relay-task:<id>" — the host builds the preview and the webhook captures it automatically.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Amendor MCP Configuration
Unfour Configuration