{
  "markdown": "# amendor-mcp\n\n[![Featured on Product Hunt](https://img.shields.io/badge/Product%20Hunt-Featured-da552f?logo=producthunt&logoColor=white)](https://www.producthunt.com/products/amendor/amendor/launch-day)\n[![amendor-mcp MCP server](https://glama.ai/mcp/servers/deslay1/amendor-mcp/badges/score.svg)](https://glama.ai/mcp/servers/deslay1/amendor-mcp)\n\nConnect your coding agent to [Amendor](https://amendor.site).\n\nAmendor 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.\n\n## Setup\n\n1. Sign in at [amendor.site](https://amendor.site) and create a project.\n2. Go to Settings and copy the connector command. It already has your token filled in and looks like this:\n\n   ```\n   claude mcp add amendor --env AMENDOR_API=https://amendor.site --env AMENDOR_TOKEN=your-token -- npx -y amendor-mcp\n   ```\n\n3. Run it in your repo.\n\n`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.\n\n## Use it\n\nAsk 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.\n\nTools: `list_change_requests`, `get_change_request`, `start_build`, `set_preview_url`, `publish_preview`, `update_status`, `ship_change`.\n\nMIT license. More at [amendor.site](https://amendor.site).\n",
  "bytes": 1639,
  "sha": "5a0021f752584ff7e39fb790f40d8107d0f81f46e580adf9299820ec19e5271e",
  "repo_slug": "deslay1/amendor-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_deslay1_amendor_mcp_b3240147/readme"
}