Amendor

io.github.deslay1Published by GitHub account deslay1v1.0.0Updated Oct 24, 2026

Pull change requests from your Amendor board into your coding agent to build and open PRs.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Amendor connects a coding agent to an Amendor board so it can list, inspect and update end-user change requests for sites you ship.

What you can do
  • List change requests submitted by end users, optionally filtered by status
  • Read one request in full: the user's text, the targeted element's CSS selector and outerHTML, page URL and screenshot URL
  • Attach a deploy-preview URL to a request and mark it ready for the requester to review
  • Update a request's status as it moves through the build and review flow
When to use it
Useful when you collect change requests from the people you build for on an Amendor board and want a coding agent to pick them up, implement them on a branch and open a pull request without copying details by hand.
Requirements
An Amendor account with a project created at amendor.site. A connector token generated per account on the Settings page, supplied as AMENDOR_TOKEN (or as an Authorization bearer header for the remote endpoint), plus the Amendor URL in AMENDOR_API. Runs as a remote endpoint or locally via the npm package amendor-mcp (npx).
Before you install
The connector token is an account credential; keep it out of shared configs and repositories. The server can change request status and attach preview URLs, which are visible to requesters. Request details include page URLs, element markup and screenshot links from your sites.

Installation

In SourceWeft

  1. Open Amendor in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.deslay1%2Famendor-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "amendor": {
      "type": "http",
      "url": "https://amendor.site/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

amendor-mcp

[Featured on Product Hunt] [amendor-mcp MCP server]

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.

Setup

  1. Sign in at amendor.site and create a project.

  2. Go to Settings and copy the connector command. It already has your token filled in and looks like this:

    claude mcp add amendor --env AMENDOR_API=https://amendor.site --env AMENDOR_TOKEN=your-token -- npx -y amendor-mcp

  3. 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.

Use it

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.

Source: README.md at commit 4868048

Tools

4

list_change_requests

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.

Parametersstatus

get_change_request

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.

Parametersidrequired

set_preview_url

Attach preview URL

Attach a deploy-preview URL to a change request and mark it ready for the requester to review.

Parametersidrequiredurlrequired

update_status

Update status

Update a change request status as it moves through the build and review flow.

Parametersidrequiredstatusrequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.