Skip to content

Amendor

by deslay1 · remote · local (npm) · no sign-in to list tools · v1.0.0 · published by GitHub user deslay1

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

Changes · 2
CompareRegistry entry

4 tools: 2 change things and 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http amendor https://amendor.site/mcp --header 'Authorization: <your-authorization>'

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Changes things 2Claude Code: ask
  • set_preview_urlAttach a deploy-preview URL to a change request and mark it ready for the requester to review.No findings

    Why it is in this group

    • The name "set_preview_url" says "set": a word for a change.
    Description, as the server wrote it
    Attach a deploy-preview URL to a change request and mark it ready for the requester to review.

    Annotations the server declares

    • readOnlyHint: false
    • idempotentHint: true
    • openWorldHint: true
    • destructiveHint: false
  • update_statusUpdate a change request status as it moves through the build and review flow.No findings

    Why it is in this group

    • The name "update_status" says "update": a word for a change.
    Description, as the server wrote it
    Update a change request status as it moves through the build and review flow.

    Annotations the server declares

    • readOnlyHint: false
    • idempotentHint: true
    • openWorldHint: true
    • destructiveHint: false
Only reads 2Claude Code: allow
  • 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.No findings

    Why it is in this group

    • The name "get_change_request" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
    • destructiveHint: false
  • list_change_requestsList change requests submitted by end users on sites you ship.No findings

    Why it is in this group

    • The name "list_change_requests" says "list": a word for reading.
    Description, as the server wrote it
    List change requests submitted by end users on sites you ship. Optionally filter by status. Start here to see what people are asking for.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
    • destructiveHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http amendor https://amendor.site/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__amendor__list_change_requests",
      "mcp__amendor__get_change_request"
    ],
    "ask": [
      "mcp__amendor__set_preview_url",
      "mcp__amendor__update_status"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as amendor. Review it before you use it.