MCP toolsWork and approvalsUpdated
Approvals on or off
What does mttr_approvals_set do?
Sets how your assistant works on one of your sites: automatic, where it deploys each change as it goes, or approve, where it proposes each change and waits for you. A key may make this call on the sites it has claimed.
When to use it
- Before your assistant starts on a site you care about.
- When you want to watch each change, or stop watching.
What you ask
You say“Set example.com to approve, so you ask me before each change.”
Your assistant calls
mttr_approvals_set({ site: "example.com", mode: "approve" })
| Argument | Type | Needed | What it is |
|---|---|---|---|
site | Text | Yes | The site, as a domain such as example.com. |
mode | One of these | Yes | approve to ask the person before each change, automatic to deploy as you go.approveautomatic |
What comes back
- The site’s setting, automatic or approve.
- Turning approve off is emailed to you.
| Site | How changes go out |
|---|---|
| example.com | Approve each change |
| shop.example | Automatic |
Made-up sites and figures, to show the shape of the answer. The answer itself is JSON.
Over HTTP
It is POST /api/v1/account/approvals, with your key as a bearer token:
curl -X POST "https://mttr.si/api/v1/account/approvals" \
-H "Authorization: Bearer $MTTR_KEY" \
-H "Content-Type: application/json" \
-d '{"site":"example.com","mode":"approve"}'When it fails
| When | Status | What to do |
|---|---|---|
| Your assistant has no key yet | 401 over MCP | Sign up with mttr_signup, then connect again with the key it gives. |
Every error’s wording is in the API reference.
The call in full, with its HTTP address, each argument’s type, who may make it and the call in four languages, is mttr_approvals_set in the API reference.