MCP server that syncs live site UI change requests into coding agents to build branches and open pull requests.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent โ or use 1-click editor setup below.
๐ก Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Amendor MCP.
list_change_requestsList 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_requestGet 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_urlAttach a deploy-preview URL to a change request and mark it ready for the requester to review.
update_statusUpdate a change request status as it moves through the build and review flow.
start_buildLOCAL 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_previewMark 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.
Connect your coding agent to Amendor.
Amendor lets the people you build for request changes right on your live site. Requests land on a board. This connector pulls them into your agent (Claude Code, Cursor, Cline, Codex, any MCP client) so it can build each one on a branch and open a pull request.
Sign in at amendor.site and create a project.
Go to Settings and copy the connector command. It already has your token filled in and looks like this:
Run it in your repo.
AMENDOR_TOKEN is the key that ties the connector to your Amendor account. You do not make it up. Amendor generates it and shows it inside the ready-made command on the Settings page, so create a project first, then copy the whole command.
Ask your agent: "show me the change requests," pick one, "build that one." It opens a pull request, your host builds a preview, the requester approves, you merge.
Tools: list_change_requests, get_change_request, start_build, set_preview_url, publish_preview, update_status, ship_change.
MIT license. More at amendor.site.
Factual signals from GitHub, npm, and our automated checks โ not a rating.
No reviews yet โ be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/deslay1-amendor-mcp)<a href="https://allmcps.com/mcp/deslay1-amendor-mcp"><img src="https://allmcps.com/api/badge/deslay1-amendor-mcp?style=directory" alt="Amendor MCP on AllMCPs" /></a>