Royalmail MCP vs Amendor MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Royalmail MCP vs Amendor MCP
In-depth architectural comparison of the Royalmail 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
Royalmail MCP
Delivery · Local stdio
Quality: 59/100 (Good) | Auth: API Key required
Amendor MCP
Delivery · Local stdio
Quality: 57/100 (Good) | Auth: API Key required
Verdict Summary: Choose Royalmail 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 Royalmail MCP when:
You need dedicated capabilities in the Delivery domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: RM_API_KEY, RM_BASE_URL.
Book, label, track and cancel Royal Mail and Parcelforce shipments. 33 UK and international services via friendly keys or raw Service Register codes. npx royalmail-mcp.
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
Royalmail MCP Tools (6)
book_order
Book a Royal Mail shipment via Click & Drop. Returns an orderIdentifier used to retrieve the label.
get_label
Get the shipping label for a Royal Mail Click & Drop order and save it to disk. Works for any order you have previously booked — pass its orderIdentifier. Default save location is ~/Downloads/parcel-toolkit/, overridable via the PARCEL_TOOLKIT_LABELS_DIR env var.
book_batch_and_label
Book multiple Royal Mail orders at once and return a single merged PDF containing every label, ready to print. Use this when the user pastes a list of orders/addresses. All orders share the same service, package format and sender. Saves the merged PDF to ~/Downloads/parcel-toolkit/ (overridable via PARCEL_TOOLKIT_LABELS_DIR).
track_order
Get the current status and tracking details for a Royal Mail Click & Drop order.
cancel_order
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).
Royalmail MCP is categorized under Delivery and uses a local stdio subprocess. In contrast, Amendor MCP belongs to Delivery using local stdio subprocess. Select Royalmail MCP when you need capabilities focused on delivery and Amendor MCP when you require tools for delivery.
Cancel a Royal Mail Click & Drop order. Must be done before the order is manifested/despatched.
list_services
List supported Royal Mail and Parcelforce services with their Service Register codes. Availability depends on your Click & Drop account.
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.