Pull change requests from your Amendor board into your coding agent to build and open PRs.
Connect Remote server
claude mcp add --transport http amendor-mcp https://amendor.site/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
{
"mcpServers": {
"amendor-mcp": {
"url": "https://amendor.site/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
{
"servers": {
"amendor-mcp": {
"type": "http",
"url": "https://amendor.site/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://amendor.site/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools 4 found in our last check
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.
Headers
| Name | Description |
|---|---|
AuthorizationRequired, secret | Bearer <connector token from amendor.site/settings> |
Details
| Endpoint | https://amendor.site/mcp (Streamable HTTP) |
| Package | [email protected] (NPM, stdio) |
| First published | 22 Jun 2026 |
| Last updated | 22 Jun 2026 |
| Registry name | io.github.deslay1/amendor-mcp |
More developer tools servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
