Nahook MCP vs Amendor MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Nahook MCP vs Amendor MCP
In-depth architectural comparison of the Nahook MCP and Amendor MCP 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
Nahook MCP
Delivery · Local stdio
Quality: 48/100 (Fair) | Auth: other
Amendor MCP
Delivery · Local stdio
Quality: 57/100 (Good) | Auth: API Key required
Verdict Summary: Choose Nahook MCP if you need specialized Delivery tools running via a local process. Choose Amendor MCP 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 Nahook MCP when:
You need dedicated capabilities in the Delivery domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
"The official MCP server for the Nahook webhook platform — trigger webhooks, inspect deliveries, retry failures, and manage endpoints from your AI assistant."
Lets the non-technical people you build for request UI changes directly on your live site, then pulls each request (with the exact element and page) into your coding agent so it builds it on a branch and opens a pull request. Works with Claude Code, Cursor, Cline, Codex, and remote agents over HTTP. npx -y amendor-mcp
Category & Scope
Tools & Capabilities Breakdown
Nahook MCP Tools (12)
whoami
Local config sanity check — workspace, region, token id, expiry.
list_endpoints
List every endpoint in the current workspace.
get_endpoint
Fetch one endpoint by `ep_xxx`.
create_endpoint
Create a new endpoint. Defaults to the workspace's default environment; also accepts slugs like `production`.
Nahook MCP is categorized under Delivery and uses a local stdio subprocess. In contrast, Amendor MCP belongs to Delivery using local stdio subprocess. Select Nahook MCP when you need capabilities focused on delivery and Amendor MCP when you require tools for delivery.
Page through an endpoint's deliveries, newest-first.
get_delivery
Fetch one delivery by `del_xxx`. Pass `include_payload: true` to also fetch the original webhook body — critical for debugging.
list_attempts
List every attempt against a delivery (useful for debugging failures).
retry_delivery
Re-enqueue a failed or dead-lettered delivery.
trigger_event
Fire an event by type — the backend fans it out to every subscriber.
send_to_endpoint
Send a webhook directly to one endpoint.
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.
publish_preview
Mark a change request ready for the requester to review. The preview is already live from the worktree; this flips status to "in preview" and surfaces the link.
ship_change
Ship an approved change: merge the task branch into the project base, remove the worktree, and mark it shipped. Production (the live site) now reflects the change.