Amendor

Official4 toolsLive

by deslay1 · JavaScript

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

Amendor MCP Server (io.github.deslay1/amendor-mcp)

This MCP server connects a coding agent to Amendor to pull change requests from an Amendor board into the agent, enabling the agent to build and open PRs. It is described as a connector for integrating request-handling workflows from a live site into development tooling.

🛠️ Key Features

Pull change requests from an Amendor board into a coding agent
Build and open PRs from pulled requests
4 tools in the server

🚀 Use Cases

Integrate Amendor “request changes” workflow on a live site with a coding agent
Convert board-based change requests into pull requests

⚡ Developer Benefits

Supports coding agents including Claude Code, Cursor, Cline, Codex (as referenced)

⚠️ Limitations

Description does not specify authentication, supported hosting, or exact PR-creation details beyond “build and open PRs.”

Captured live from the server via tools/list.

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.

Parameters1

status

string

optional

Optional status filter: new, accepted, building, preview, approved, shipped, or rejected. Omit to list every open request.

Raw schema

{
  "type": "object",
  "properties": {
    "status": {
      "type": "string",
      "description": "Optional status filter: new, accepted, building, preview, approved, shipped, or rejected. Omit to list every open request."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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.

Parameters1

string

required

Ticket code like "RB-3" from list_change_requests (raw ids also work).

Raw schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Ticket code like \"RB-3\" from list_change_requests (raw ids also work)."
    }
  },
  "required": [
    "id"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

set_preview_url

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

Parameters2

id	string	required	Ticket code like "RB-3" (raw ids also work).
url	string	required	Deploy-preview URL (from your host) that the requester will review.

Raw schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Ticket code like \"RB-3\" (raw ids also work)."
    },
    "url": {
      "type": "string",
      "description": "Deploy-preview URL (from your host) that the requester will review."
    }
  },
  "required": [
    "id",
    "url"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

update_status

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

Parameters2

id	string	required	Ticket code like "RB-3" (raw ids also work).
status	string	required	New status: new, accepted, building, preview, approved, shipped, or rejected.

Raw schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Ticket code like \"RB-3\" (raw ids also work)."
    },
    "status": {
      "type": "string",
      "description": "New status: new, accepted, building, preview, approved, shipped, or rejected."
    }
  },
  "required": [
    "id",
    "status"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

README.md2 KBView on GitHub

amendor-mcp

Featured on Product Hunt

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

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

code

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

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.

Install

Tools (4)

list_change_requestsget_change_requestset_preview_urlupdate_status

Configuration

Environment variables

AMENDOR_APIrequireddefault https://amendor.site

Your Amendor URL

AMENDOR_TOKENrequiredsecret

Connector token from amendor.site/settings (generated per account)

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "amendor-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "amendor-mcp@1.0.0"
      ],
      "env": {
        "AMENDOR_API": "https://amendor.site",
        "AMENDOR_TOKEN": "<YOUR_AMENDOR_TOKEN>"
      }
    }
  }
}

Amendor MCP Server (io.github.deslay1/amendor-mcp)

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

list_change_requests

get_change_request

set_preview_url

update_status

amendor-mcp

Setup

Use it

Install

Configuration

Related servers