Amendary for coding agents (MCP)
An agent can ask whether a repo's docs are behind, read the fixes waiting for review, and, with a scoped key, ask for a preview of a GitHub change. It sees your team's state. It cannot get around review.
What it is
One remote MCP endpoint at https://api.amendary.com/mcp. Each tool matches one REST endpoint, so an agent and a CI script see the same data: four read tools, plus check_change and get_change_check for keys with the checks:run scope.
Setup and the full tool list are in API and MCP and the REST API reference.
An agent can
- List pending and recent fixes, each with its evidence: the source, the changed paths, the old quote and the planned edit.
- Read freshness per repo: when it was last checked, against which commit, the last outcome, and how many fixes still wait.
- Read the team's usage summary, the same numbers Settings shows.
- List the pages and articles mapped to a repo, with freshness. Each one includes its link when the destination gives one.
- With a checks:run key, point at a GitHub pull request or commit range and poll a preview of its docs impact.
An agent cannot
- Approve, apply or dismiss a fix.
- Edit, comment on or create a page or article in Notion, GitHub, Zendesk or Intercom.
- Change a setting, a mapping or the review mode.
- Supply its own text as evidence. An optional note is hashed, never stored or sent to a model.
- Use model tokens, unless the key has the checks:run scope (capped per key per day).
Listings return titles and links, not page text. A preview drafts fixes for review and never applies them, whatever the review mode.
Keys
A workspace owner creates a key under Settings, API keys. It starts with amk_ and is shown once. Amendary stores only its hash and a short prefix, so a lost key cannot be recovered: make a new one and revoke the old.
Each key belongs to one team. The same key works for REST and MCP, sent as a bearer token. Keys are rate limited and can be revoked at once. Keep the key in your client’s secret settings, never in a repo.
Good uses
- An agent asks whether a repo’s docs are behind before it opens a pull request.
- An agent sums up the pending fixes for a page for the person reviewing.
- A CI step reads pending fixes over REST and warns on a pull request.
- A scheduled job posts the usage summary to a channel.
This is the supported remote MCP subset today. Wider client support and OAuth are on the roadmap.
Why agents cannot publish
Review rules are what make an automatic fix safe to trust. A write path for agents would skip them. So agents can point at a change, but people decide what gets published.
Next steps
- API and MCP guide: connect a client
- Daily checks: the same check a preview runs
- Security: keys, isolation and access control
See what an agent would read
Connect your help center and docs. Once the first check runs, create a key in Settings and point your agent at the MCP endpoint.
Free for 14 days with no card, and every edit waits for your review. Or free forever with your own Anthropic API key. Code is never touched.