Developers

Appearance

MCP server changelog ​

The MCP server is versioned by Semantic Versioning — MAJOR.MINOR.PATCH — unlike the REST API's date-based versions. Format follows Keep a Changelog.

Subscribe to this page: RSS feed.

[Unreleased] ​

Nothing yet. Changes land here as they are merged, and move into a versioned section on release.

[1.2.0] - 2026-10-07 ​

Added ​

  • Search designs the way you describe them. search_designs takes query: its words are matched in any order, each in the design name or the project name, so "black friday story" finds "Black-Friday – Story" or a design in your Black Friday project.
  • Pick an exact project. search_designs and list_designs take project_id. When a project name matches several projects, your assistant is told so.
  • Find your latest design. Designs are listed most recently edited first. Use sort (last edited, created, name) and order to change it.
  • Find designs by format and date. The design tools take orientation (portrait, landscape, square), size, format, updated_since and created_since, and type takes several values — so "our story versions" or "what changed this week" is one call.
  • Find fonts by style and weight. list_fonts takes category, weight and style (italic), and name searches ignore spaces, accents and case, with exact names first.

Changed ​

  • Unsupported options are refused, not ignored. The listing tools answer an error naming an option they don't support, instead of returning an unfiltered list.
  • Honest paging. A page past the end says how many items exist instead of "nothing matched", and your assistant is only told to ask for a next page when there is one. Every listing result carries a one-line summary.

Fixed ​

  • Searching for a design with an emoji in its name no longer fails.

[1.1.1] - 2026-10-01 ​

Changed ​

  • Clearer confirmations in your AI client. Every tool now tells your client whether it only reads your workspace or changes it. Clients such as Claude can run read-only tools (listing designs, checking credits, …) without asking you each time, and always ask before a tool that deletes, moves or overwrites something. See Permissions.
  • move_design is now flagged as a destructive action, because moving a design resets its review/approval status. Your client will ask for confirmation before moving a design.
  • Better guidance on which generation tool to use. Tool descriptions now say which tool generates each design type: static images, animated (video, GIF, HTML5), print, and multi-page PDF. See get_design.
  • Image imports: if your assistant has to shrink an image so it fits in an import, it now tells you what it changed. It no longer looks for other ways to host the image by itself; it asks you for an image link instead.

Fixed ​

  • import_design_from_json's strict option was described the wrong way round. With strict: true, a text that can't fit its box makes the import fail instead of importing with a warning. The default (false) is unchanged.
  • callback_url (on generate_banners_async and generate_multipage_pdf) is now documented for what it is: Abyssale sends the job result to the address you give, which can be outside Abyssale.

[1.1.0] - 2026-09-29 ​

Added ​

  • Design editing — change or remove designs that already exist. You need a role that can manage designs (Admin, Manager, or Designer) and access to the design's project.
    • rename_design: rename a design.
    • move_design: move a design to another project in the same workspace. It keeps its content and generated banners; its review/approval status is reset.
    • delete_design: delete a design. Banners already generated from it are kept.
  • Scopes — write:design (rename, move) and delete:design (delete). Deleting has its own scope, so you can let a client change your designs without letting it delete them. See Authentication. Clients that were already connected need to reconnect to be granted them.

[1.0.0] - 2026-09-01 ​

First public release.

Added ​