Changelog

Settings by API: manage your workspace from your own tools and AI agents

More teams run Quackback from scripts and AI agents, not just the browser. This release gives those tools the same reach as the admin, and makes sure you can always see who, or what, changed something.

Change settings from the API and MCP

Your workspace settings can now be read and changed through the REST API and through MCP, with the same permissions a teammate would need.

You can now:

  • Read and update settings with the API or the get_settings and update_settings MCP tools
  • Preview a change with a dry run before saving it
  • Undo any change using the receipt it returns
  • Sign in from command-line tools and MCP clients by entering a short code, with no browser needed

See where every change came from

The audit log now tells you how each change arrived.

You can now:

  • See whether a change came from the app, the API, MCP, the AI, a workflow or the system
  • See which key or app made it

Other improvements

  • New webhook events for mentions, post owners, and status page incidents, maintenance and components
  • The API reference now covers every public route
  • Self-hosted teams can set up a new install without a browser, using a setup token
  • On a new install, only the first account can finish setup

Where to find it: API keys and MCP are in Settings > Developers. The audit log is in Settings > Access & Security.

Live on Quackback Cloud now, and in Quackback 0.15 for self-hosted teams.