Klaxoon

Create a new blank Klaxoon whiteboard, or one from an existing Board template. For a blank whiteboard, provide a title and optionally a description. To start from a template, provide its Klaxoon link or access code in the "template" field and optionally override its title in the "title" field. The template argument MUST point to a Board template: a regular whiteboard link is rejected and no whiteboard is created. The source template is left untouched. Template duplication runs server-side and may take several seconds. Before adding any content, you MUST plan the structural layout and how you will use categories, extra-fields, and colors as per the instruction "Plan briefly before acting".

create_whiteboard

Create items (stickies, shapes, text, connectors) on a whiteboard. Input: "items" is an array of objects (not strings), max 50 per call. JSON convention: omit any optional field you do not want to set — never send it as null. Each object must have "type" and "payload". Supported type values only: "IDEA", "TEXT", "SHAPE", "CONNECTOR". Other Board objects (questions, comments, tables, formal zones, sticky files/images, board images, icons, brush/drawing) are not creatable via MCP; see the instructions not-managed list. Always set explicit x/y coordinates and position.z (low z = background, high z = foreground). Required fields: "shapeType" for SHAPE, a non-empty "content" for TEXT. Use "tmpId" to reference new items within the same request (e.g. to attach a connector to two shapes being created in the same call). Examples per type (illustrative only — combine fields freely based on the use case): IDEA (sticky note): {"type":"IDEA","tmpId":"idea-1","payload":{"position":{"x":0,"y":0,"z":1},"geometry":{"width":160},"data":{"content":"<p>My idea</p>","format":"square","color":{"id":"<color-uuid>"},"category":{"id":"<category-uuid>"},"extraFields":[{"id":"<extra-field-uuid>","value":"High"}]}}} TEXT: {"type":"TEXT","payload":{"position":{"x":200,"y":0,"z":2},"data":{"content":"<h1>Title</h1><p>Details</p>","fontSize":24,"maxLineWidth":400}}} SHAPE: {"type":"SHAPE","tmpId":"box-1","payload":{"position":{"x":400,"y":0,"z":1},"geometry":{"width":200,"height":150},"data":{"shapeType":"rectangle","content":"<h2>Label</h2><p>Details</p>","fontSize":20,"style":{"fillColor":"#e0f0ff","fillOpacity":1,"strokeColor":"#0066cc","strokeStyle":"solid","strokeThickness":2}}}} CONNECTOR (linking box-1 → idea-1 via tmpId, with an optional "content" label on the line): {"type":"CONNECTOR","payload":{"data":{"content":"<h3>Dependency</h3><p>depends on</p>","fontSize":16,"startItem":{"id":"box-1","anchor":"right"},"endItem":{"id":"idea-1","anchor":"left","shape":"arrow"},"pathType":"curve","style":{"strokeColor":"#333333","strokeStyle":"solid","strokeThickness":2}}}} WRIKE ITEM (sticky note with a Wrike task URL — content must contain ONLY the URL, no extra text): {"type":"IDEA","payload":{"position":{"x":0,"y":400,"z":1},"geometry":{"width":160},"data":{"content":"https://www.wrike.com/open.htm?id=123456789","format":"square"}}}

create_whiteboard_items

Add one hex color to the board's palette for sticky notes. JSON convention: omit any optional field you do not want to set — never send it as null. Rule: Only create new colors if the existing palette cannot support a necessary semantic distinction.

create_whiteboard_sticky_color

Delete specific items from a whiteboard using their IDs. Strict Limits: Max 50 items per call. Only managed item ids (from list_whiteboard_items) can be deleted. Safe Editing Rule: Avoid deleting content or moving many existing elements unless explicitly requested. You must prioritize "Preservation" and "Fact Integrity"—never delete data that could be essential to the user's context without confirmation.

delete_whiteboard_items

Remove one color from the board's palette for sticky notes. Safe Editing: Before deleting, ensure the color is not currently used to encode critical meaning.

delete_whiteboard_sticky_color

Retrieve the full Klaxoon board assistant instructions. Mandatory First Step: You MUST call this at the very beginning of every session to establish your operating framework. It provides the essential rules for planning, visual structuring, and quality standards required to assist the user effectively.

get_mcp_server_instructions

Retrieve information for a specific whiteboard, including categories, extra-fields, and colors. Mandatory Audit: Use this to get basic information of an existing board based on its ID or accessCode, and to resolve category / extra-field / color ids before assigning them on sticky notes. Returns core metadata (title, id, accessCode, shareLink, state, createdAt, updatedAt, author) plus optional `categories`, `extraFields`, and `colors` when present on the board. REQUIRED: you must provide either "boardId" (UUID) or "accessCode".

get_whiteboard_info

Retrieve managed items only (sticky notes, text, shapes, connectors) from a whiteboard with their properties. Does not return questions, comments, tables, formal zones, board images, icons, or brush/drawing; their absence from the response does not mean they are absent from the board. See the instructions not-managed list. JSON convention: omit any optional filter you do not want to apply — never send it as null. Mandatory Audit: Always call this tool before modifying a board to perform a "Context Analysis" in order to understand spatial organization of the current layout.

list_whiteboard_items

List all available sticky note colors on a board. Mandatory Step: Use this to perform "Context Analysis" and identify the board's existing colors. You must reuse these existing colors for any new sticky note content to ensure visual consistency and avoid creating redundant or "one-off" colors.

list_whiteboard_sticky_colors

Retrieve a list of available whiteboards. Context Analysis: Use this to search for existing boards based on title, author, and/or date. Returns total count and core metadata: title, id, accessCode, shareLink, state, createdAt, updatedAt, author.

list_whiteboards