# Decknote (remote · decknote.app) Kanban boards your AI agent can use: add, complete, move and recall tasks with your team. - Trust score: 87/100 (high trust) - Change this week: +3 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - remote · `decknote.app`: 87/100 (this document), [markdown](https://verifymcp.io/servers/app-decknote-decknote/api-v1-mcp.md), [page](https://verifymcp.io/servers/app-decknote-decknote/api-v1-mcp) ## Channel facts - Endpoint: `https://decknote.app/api/v1/mcp` - Transports: `streamable-http` - Auth: `required (not validated)` - Version: `1.0.0` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-05. - **Endpoint Security**: 89/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. - HTTPS is enforced; there's no plaintext access path. - The HSTS (Strict-Transport-Security) header is present. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 78/100 - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name). - AI-judged instruction clarity (good). - Context-footprint check failed: tool/resource definitions use about 28095 tokens (~131/item across 213 items; 211 tools + 2 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 80/100 - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 89/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 67% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - All 38 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. - An AI judge read all 213 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 73/100 - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. - Supports UI / widget rendering. ## Install ### How do I install the Decknote MCP server? Decknote is a hosted endpoint at https://decknote.app/api/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add --transport http app-decknote-decknote 'https://decknote.app/api/v1/mcp' ``` ### Cursor ```json { "mcpServers": { "app-decknote-decknote": { "url": "https://decknote.app/api/v1/mcp" } } } ``` ### VS Code ```json { "servers": { "app-decknote-decknote": { "type": "http", "url": "https://decknote.app/api/v1/mcp" } } } ``` ### Codex ```toml [mcp_servers.app-decknote-decknote] url = "https://decknote.app/api/v1/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "app-decknote-decknote": { "type": "remote", "url": "https://decknote.app/api/v1/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add app-decknote-decknote --url 'https://decknote.app/api/v1/mcp' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: app-decknote-decknote: url: "https://decknote.app/api/v1/mcp" ``` ### Netclaw ```json { "McpServers": { "app-decknote-decknote": { "Transport": "http", "Url": "https://decknote.app/api/v1/mcp" } } } ``` ### Vellum ```bash assistant mcp add app-decknote-decknote -t streamable-http -u 'https://decknote.app/api/v1/mcp' ``` ### Other ```json { "mcpServers": { "app-decknote-decknote": { "type": "http", "url": "https://decknote.app/api/v1/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-05 (score 87, +1) - [security] Tool “share_board” rewrote its description, which is the text the model reads ### 2026-11-03 (score 86, +1) No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-31 (score 85, +1) No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-29 (score 84, +1) No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-28 (score 83, 0) - [security] Tool “email_invoice” rewrote its description, which is the text the model reads ### 2026-10-27 (score 83, +1) No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-25 (score 82, +1) No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-23 (score 81, +1) - [security] New tool “add_expense_receipt”, which the server declares destructive - [security] New tool “approve_time_off”, which the server declares destructive - [security] New tool “approve_timesheet”, which the server declares destructive - [security] New tool “convert_estimate_to_project”, which the server declares destructive - [security] New tool “create_webhook”, which the server declares destructive - [security] New tool “delete_expense_receipt”, which the server declares destructive - [security] New tool “delete_webhook”, which the server declares destructive - [security] New tool “reject_time_off”, which the server declares destructive - [security] New tool “reject_timesheet”, which the server declares destructive - [security] New tool “submit_timesheet”, which the server declares destructive - [security] New tool “test_webhook”, which the server declares destructive - [security] New tool “update_webhook”, which the server declares destructive - [security] New tool “withdraw_timesheet”, which the server declares destructive - [security] Tool “add_time_off” rewrote its description, which is the text the model reads - [security] Tool “get_profitability_report” rewrote its description, which is the text the model reads - [security] Tool “list_time_off” rewrote its description, which is the text the model reads - [security] Tool “update_time_off” rewrote its description, which is the text the model reads - [functional regression] Schema quality: 25131 → 28016 - [functional] New tool “get_assignments_report” - [functional] New tool “get_invoice_pdf” - [functional] New tool “list_timesheets” - [functional] New tool “list_webhooks” - [cosmetic] “list_time_off” added an optional parameter “status” ## MCP tools (211) ### `overview` (~71 tokens) Account overview Snapshot of the user's Decknote account: plan and limits, recent boards, what needs attention (overdue and due-today tasks, unread notifications, upcoming reminders), sharing (pending invitations, shared boards, public links, live embeds) and suggested next steps. Useful at the start of a conversation about the user's work. ### `list_boards` (~80 tokens) List boards Lists the boards the user can access, each with its lists (ids and titles), the user's role on it (OWNER, EDITOR or VIEWER), whether it is archived and whether it is a favorite. These board and list ids identify boards and lists everywhere else in this server. Input parameters: - `includeArchived` (boolean): Include archived boards. Default false. ### `create_board` (~121 tokens) Create board Creates a new board owned by the user. `template` sets the initial lists and labels, in the user's language: blank (To do / In progress / Done), kanban, content or personal; `lists` replaces the template's list titles. Returns the board with its list ids. The free plan allows 5 owned boards. Input parameters: - `lists` (array): List titles, in order; they replace the template's lists (its labels stay). - `template` (string): Initial lists/labels. Default 'blank'. - `title` (string, required) ### `create_list` (~79 tokens) Create list Adds a list (column) to a board, at the end or, with first: true, before the other lists. Returns the new list with its id. Needs edit access to the board. Input parameters: - `boardId` (string, required) - `first` (boolean): Put it before the other lists. Default false. - `title` (string, required) ### `search_tasks` (~180 tokens) Search tasks Searches the user's tasks (cards) across boards by free text in title and description, and by board, list, status (open, completed, all or archived) and due date. Answers questions like what is still open, what was noted about something, or what is due soon. Input parameters: - `boardId` (string) - `dueBefore` (string): ISO 8601; only tasks due before this instant. - `include` (array): Extra fields on each task. 'location' adds the names of its board (board) and list (list). - `limit` (number): Max results, 1–100. Default 20. - `listId` (string) - `query` (string): Free text; matches card title and description. - `status` (string): Default 'open'. 'archived' finds archived tasks. ### `get_task` (~121 tokens) Get task Reads one task in full: title, description, dates, completion, board and list, labels, assignees, checklists with their items, comments with reactions, attachments, links to other tasks, custom field values, whether the user watches it and the user's pending reminders, with the id of each part. Input parameters: - `cardId` (string, required) - `include` (array): Extra fields on the task. 'descriptionMarkdown' adds the description with its formatting (headings, lists, task lists, code) as Markdown, when the page has any. ### `create_task` (~213 tokens) Create task Adds a task (card) to a list, or to a board's first list when only boardId is given. The description becomes the card's page and accepts Markdown (headings, bullet and numbered lists, - [ ] task lists, bold, italic, code, links, fenced code). Optional due date, reminders, repeat (Pro) and a checklist. The board's rules for new cards run, as in the app. Input parameters: - `boardId` (string): Used if listId is omitted. - `checklist` (object): A checklist on the card: { title?, items: [{ text, done? }] }. - `description` (string) - `dueDate` (string): ISO 8601. - `listId` (string) - `recurrence` (string): Repeat: archiving the task creates the next one, dates and reminders moved (Pro; needs a due date). - `reminders` (array): Reminders for you (push and email). - `title` (string, required) ### `update_task` (~195 tokens) Update task Edits a task: title, description, due date, start date, repeat or cover (a color, or one of the task's image attachments). The description accepts Markdown and replaces the card's whole page. null clears a date, the repeat or the cover. Input parameters: - `cardId` (string, required) - `coverColor` (string|null): A color cover, or null to remove the cover. Replaces an image cover. - `coverImageAttachmentId` (string|null): Use one of the card's image attachments as its cover (null removes it). - `description` (string) - `dueDate` (string|null): ISO 8601, or null to clear. - `recurrence` (string|null): Repeat on archive (Pro), or null to stop repeating. - `startDate` (string|null): ISO 8601, or null to clear (shown on the timeline). - `title` (string) ### `complete_task` (~24 tokens) Complete task Marks a task as completed (done). Input parameters: - `cardId` (string, required) ### `reopen_task` (~25 tokens) Reopen task Marks a completed task as not done again. Input parameters: - `cardId` (string, required) ### `archive_task` (~55 tokens) Archive task Archives a task: it leaves the board but keeps all its data and can be restored from the board's archive. Archiving a dated repeating task creates its next occurrence, as in the app. Input parameters: - `cardId` (string, required) ### `move_task` (~116 tokens) Move task Moves a task to another list: on the same board, optionally to a position (index 0 = top), or on another board the user can edit (it lands at the end). Moving to another board drops the old board's labels and the assignees and watchers who can't see the new board, as in the app. Input parameters: - `cardId` (string, required) - `index` (integer): Position in the target list, 0 = top. Default: the end. - `listId` (string, required): Target list id. ### `add_comment` (~153 tokens) Add comment Adds a comment to a task as the user. By default nobody is notified. With notify: true it notifies @mentioned board members and the card's watchers by push and email, as commenting in the app does; that needs confirm: true, and without it the result is a preview of who would be notified. Input parameters: - `cardId` (string, required) - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `notify` (boolean): Notify mentioned people and watchers, as the app does. Default false. - `text` (string, required): Mention a board member by writing @ and their name. ### `add_reminder` (~117 tokens) Add reminder Adds a reminder for the user on a task: a push notification and an email at a chosen moment. Either `at` (an ISO 8601 instant), or relative to the due date (`daysBefore` + local `time` + IANA `timeZone`), which follows the due date when it moves and repeats with repeating tasks. Input parameters: - `at` (string) - `cardId` (string, required) - `daysBefore` (integer) - `time` (string) - `timeZone` (string) ### `list_reminders` (~55 tokens) List reminders Lists the user's pending reminders, soonest first, optionally on one board, with each task's title and due date. Input parameters: - `boardId` (string) - `limit` (integer): Default 50, max 200. ### `remove_reminder` (~24 tokens) Remove reminder Deletes one of the user's reminders. Input parameters: - `reminderId` (string, required) ### `search` (~51 tokens) Search cards Searches the open and completed cards of every board the user can access by text in title and description. Returns card ids, titles (with the board) and links. Input parameters: - `query` (string, required): What to look for. ### `fetch` (~44 tokens) Fetch card Reads one card by id as a document: title, board and list, due date, labels, description, checklists and comments. Input parameters: - `id` (string, required): The card id. ### `get_board` (~133 tokens) Get board Reads one board in full, like opening it in the app: lists with their cards (dates, labels, assignees, checklist progress, custom field values), labels, members and the user's role, custom fields, rules, card templates, the user's saved views, recently archived cards, the public link and pending invitations (owner only) and the plan limits that apply, with every id. Input parameters: - `boardId` (string, required) - `cardsPerList` (integer): Max cards per list, 1–500. Default 100. - `includeCards` (boolean): Default true. False returns only the structure. ### `list_activity` (~70 tokens) List board activity Lists a board's activity history, newest first: who did what, and when. How far back it goes follows the board owner's plan (Free: 40 entries, Pro: 200), as in the app. Input parameters: - `boardId` (string, required) - `limit` (integer): Default 50. ### `update_board` (~127 tokens) Update board Changes a board's title, icon (one emoji), cover color or background image (Pro; PNG, JPEG, WEBP or GIF up to 5 MB, base64-encoded), or removes the background. Needs edit access to the board. Input parameters: - `backgroundImageBase64` (string): A new background image, base64-encoded (Pro). - `boardId` (string, required) - `coverColor` (string|null) - `icon` (string|null): One emoji, or null to remove it. - `removeBackground` (boolean) - `title` (string) ### `set_board_preferences` (~59 tokens) Set board preferences Sets the user's own preferences for a board: favorite (starred) and muted (no notifications from it). Affects only the user. Input parameters: - `boardId` (string, required) - `favorite` (boolean) - `muted` (boolean) ### `duplicate_board` (~67 tokens) Duplicate board Copies a board the user can see into a new board the user owns: lists, cards (content, dates, checklists, labels) and look. Members, comments and attachments are not copied. Counts toward the free plan's 5 owned boards. Input parameters: - `boardId` (string, required) ### `archive_board` (~51 tokens) Archive board Archives a board the user owns: it leaves everyone's dashboard and keeps all its data until it is restored. Archived boards don't count toward the free plan's 5 owned boards. Input parameters: - `boardId` (string, required) ### `restore_board` (~28 tokens) Restore board Restores an archived board the user owns to everyone's dashboard. Input parameters: - `boardId` (string, required) ### `delete_board` (~105 tokens) Delete board Permanently deletes a board the user owns, with every list, card, comment and attachment on it, also for the people it is shared with. Irreversible. Without confirm: true nothing is deleted and the result is a preview of what would be lost. Input parameters: - `boardId` (string, required) - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. ### `import_trello_board` (~88 tokens) Import Trello board Creates a board from a Trello JSON export (in Trello: Menu → Print, export and share → Export as JSON): lists, cards with Markdown descriptions, dates, labels, checklists, comments and links. Counts toward the free plan's 5 owned boards. Input parameters: - `trelloJson` (string, required): The whole Trello export, as JSON text (max 20 MB). ### `share_board` (~149 tokens) Share board Shares a board the user owns with someone by email, as EDITOR or VIEWER. People with an account get access right away; others get an invitation link by email and join when they open it. Decknote emails them either way, so it needs confirm: true; without it the result is a preview. Sharing is a Pro feature on the web (one flat price, not per person). Input parameters: - `boardId` (string, required) - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `email` (string, required) - `role` (string): Default EDITOR. ### `update_member` (~57 tokens) Change member role Changes a member's role on a board the user owns: EDITOR (can change things) or VIEWER (read only). Input parameters: - `boardId` (string, required) - `role` (string, required) - `userId` (string, required) ### `remove_member` (~102 tokens) Remove member Removes someone from a board the user owns: they lose access, and their assignments, watches and reactions on it are removed (their comments stay). Needs confirm: true; without it the result is a preview. Input parameters: - `boardId` (string, required) - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `userId` (string, required) ### `leave_board` (~93 tokens) Leave board Removes the user from a board someone else shared with them; only the owner can add them back. The owner can't leave their own board. Needs confirm: true; without it the result is a preview. Input parameters: - `boardId` (string, required) - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. ### `transfer_board` (~110 tokens) Transfer board ownership Hands a board the user owns to one of its members: they become the owner (their plan then decides the board's Pro features) and the user stays on as an editor. Needs confirm: true; without it the result is a preview. Input parameters: - `boardId` (string, required) - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `newOwnerId` (string, required) ### `set_public_link` (~130 tokens) Set public link Turns a board's public read-only link on or off, or issues a new one so the old one stops working. Anyone with the link can view the board without an account. Owner only. Needs confirm: true; without it the result is a preview. Input parameters: - `boardId` (string, required) - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `enabled` (boolean, required) - `regenerate` (boolean): Issue a new link, so the old one stops working. ### `list_embeds` (~38 tokens) List embeds Lists the live embeds of a board the user owns (the board shown inside another app of the user's). Input parameters: - `boardId` (string, required) ### `create_embed` (~159 tokens) Create embed Lets another app of the user's show this board in an iframe (Pro, owner only): a name and up to 5 https origins allowed to frame it, read-only unless canEdit. That app's server then requests a session through the REST API. Needs confirm: true; without it the result is a preview. Input parameters: - `boardId` (string, required) - `canEdit` (boolean): Whether people in the embed can edit. Default false. - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `name` (string, required) - `origins` (array, required): Up to 5, like https://your-app.com ### `revoke_embed` (~85 tokens) Revoke embed Turns off one of a board's embeds: the app showing it loses access at its next request. Needs confirm: true; without it the result is a preview. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `embedId` (string, required) ### `update_list` (~103 tokens) Update list Renames a list, sets its WIP limit (Pro; null clears it) or moves it to another position among the board's lists (index 0 = first). Needs edit access to the board. Input parameters: - `index` (integer): New position among the lists, 0 = first. - `listId` (string, required) - `title` (string) - `wipLimit` (integer|null): Max cards before the list warns (Pro), or null. ### `duplicate_list` (~41 tokens) Duplicate list Copies a list with its open cards (content, dates, labels, checklists) to the end of the same board. Input parameters: - `listId` (string, required) ### `sort_list` (~56 tokens) Sort list Reorders a list's cards by due date (soonest first, undated last), by title (A to Z) or by creation (newest first). Input parameters: - `by` (string, required) - `listId` (string, required) ### `delete_list` (~93 tokens) Delete list Permanently deletes a list and every card in it, archived ones included. Irreversible. Needs confirm: true; without it the result is a preview with the number of cards that would be lost. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `listId` (string, required) ### `create_label` (~55 tokens) Create label Adds a label to a board. Colors: green, yellow, orange, red, purple, blue, sky, pink. Input parameters: - `boardId` (string, required) - `color` (string, required) - `name` (string, required) ### `update_label` (~48 tokens) Update label Renames or recolors a label; the change shows on every card that has it. Input parameters: - `color` (string) - `labelId` (string, required) - `name` (string) ### `delete_label` (~81 tokens) Delete label Deletes a label from a board and removes it from every card that has it. Needs confirm: true; without it the result is a preview. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `labelId` (string, required) ### `create_custom_field` (~84 tokens) Create custom field Adds a custom field to a board's cards: text, number, select (with up to 20 options), checkbox or date. The free plan allows 3 per board. Input parameters: - `boardId` (string, required) - `name` (string, required) - `options` (array): For select: the choices (up to 20). - `type` (string, required) ### `update_custom_field` (~105 tokens) Update custom field Renames a custom field or changes a select field's options. Removing an option that cards use clears it from them, which needs confirm: true; without it the result is a preview. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `fieldId` (string, required) - `name` (string) - `options` (array) ### `delete_custom_field` (~77 tokens) Delete custom field Deletes a custom field and its value on every card. Needs confirm: true; without it the result is a preview. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `fieldId` (string, required) ### `create_saved_view` (~104 tokens) Create saved view Saves a personal view of a board: how to show it (board, table, calendar or timeline) and a filter (due date, labels, assignees). Only the user sees it. The free plan allows 3 per board. Input parameters: - `assigneeIds` (array) - `boardId` (string, required) - `due` (string) - `labelIds` (array) - `name` (string, required) - `view` (string) ### `delete_saved_view` (~74 tokens) Delete saved view Deletes one of the user's saved views. Needs confirm: true; without it the result is a preview. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `viewId` (string, required) ### `create_automation` (~242 tokens) Create automation Adds a board rule: WHEN a card is added to a list / moved to a list / gets a label, THEN move it, add or remove a label, assign someone, set the due date N days ahead, archive it, or comment. Triggers: card_added, card_moved, label_added (card_added/card_moved need triggerListId, label_added needs triggerLabelId). Actions: move_to_list, add_label, remove_label, assign, set_due, archive, comment (move_to_list needs actionListId; add_label/remove_label need actionLabelId; assign needs actionUserId; set_due needs actionDays; comment needs actionText). Free plan: 1 per board. Input parameters: - `action` (string, required) - `actionDays` (integer) - `actionLabelId` (string) - `actionListId` (string) - `actionText` (string) - `actionUserId` (string) - `boardId` (string, required) - `name` (string, required) - `trigger` (string, required) - `triggerLabelId` (string) - `triggerListId` (string) ### `set_automation_enabled` (~36 tokens) Enable or disable automation Turns a board rule on or off without deleting it. Input parameters: - `automationId` (string, required) - `enabled` (boolean, required) ### `delete_automation` (~71 tokens) Delete automation Deletes a board rule. Needs confirm: true; without it the result is a preview. Input parameters: - `automationId` (string, required) - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. ### `duplicate_task` (~49 tokens) Duplicate task Copies a task right below the original: title, description, dates, labels, cover, field values and checklists (not comments, assignees or attachments). Input parameters: - `cardId` (string, required) ### `restore_task` (~26 tokens) Restore task Puts an archived task back on its list. Input parameters: - `cardId` (string, required) ### `delete_task` (~88 tokens) Delete task Permanently deletes a task with its comments, checklists and attachments. Irreversible. Needs confirm: true; without it the result is a preview of what would be lost. Input parameters: - `cardId` (string, required) - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. ### `set_task_labels` (~63 tokens) Set task labels Adds and/or removes labels of the task's board on a task. Adding a label runs the board's 'label added' rules, as in the app. Input parameters: - `add` (array) - `cardId` (string, required) - `remove` (array) ### `set_task_assignees` (~124 tokens) Set task assignees Assigns or unassigns board members on a task. Assigning someone other than the user sends them a push and an email, as in the app, so it needs confirm: true and returns a preview without it; self-assigning and unassigning don't. Input parameters: - `add` (array) - `cardId` (string, required) - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `remove` (array) ### `watch_task` (~46 tokens) Watch task Starts or stops watching a task (watchers are notified of new comments on it). Affects only the user. Input parameters: - `cardId` (string, required) - `watching` (boolean, required) ### `set_task_field` (~82 tokens) Set task custom field Sets a custom field's value on a task, or clears it with null. text: any text; number: a number; select: one of its options; checkbox: true or false; date: YYYY-MM-DD. Input parameters: - `cardId` (string, required) - `fieldId` (string, required) - `value` (string|number|boolean|null, required) ### `link_tasks` (~59 tokens) Link tasks Relates two tasks on the same board: 'blocks' (from blocks to) or 'relates' (both ways). Input parameters: - `fromCardId` (string, required) - `kind` (string, required) - `toCardId` (string, required) ### `unlink_tasks` (~23 tokens) Unlink tasks Removes a relation between two tasks. Input parameters: - `linkId` (string, required) ### `bulk_tasks` (~94 tokens) Bulk update tasks Acts on up to 100 tasks of one board at once, like multi-select in the app: moves them to a list, adds a label, or archives them (repeating ones create their next occurrence). Input parameters: - `action` (string, required) - `cardIds` (array, required) - `labelId` (string): For add_label. - `listId` (string): For move: the target list on the same board. ### `create_task_from_template` (~41 tokens) Create task from template Adds a task to a list from one of the board's card templates. Input parameters: - `listId` (string, required) - `templateId` (string, required) ### `save_task_as_template` (~41 tokens) Save task as template Saves a task's description and labels as a reusable card template on its board. Input parameters: - `cardId` (string, required) - `name` (string, required) ### `delete_card_template` (~77 tokens) Delete card template Deletes a card template; tasks made from it stay. Needs confirm: true; without it the result is a preview. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `templateId` (string, required) ### `edit_comment` (~48 tokens) Edit comment Edits a comment's text (the user's own, or any on a board the user owns). It shows as edited. Input parameters: - `commentId` (string, required) - `text` (string, required) ### `delete_comment` (~82 tokens) Delete comment Deletes a comment (the user's own, or any on a board the user owns). Needs confirm: true; without it the result is a preview. Input parameters: - `commentId` (string, required) - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. ### `react_to_comment` (~64 tokens) React to comment Adds or removes the user's emoji reaction on a comment. Emojis: 👍 ❤️ 🎉 😄 👀 🚀. Input parameters: - `commentId` (string, required) - `emoji` (string, required) - `on` (boolean): Default true (add). false removes it. ### `add_checklist` (~52 tokens) Add checklist Adds a checklist with its items to a task, in addition to its other checklists. Input parameters: - `cardId` (string, required) - `items` (array) - `title` (string): Default 'Checklist'. ### `update_checklist` (~51 tokens) Update checklist Renames a checklist or moves it among the task's checklists (index 0 = top). Input parameters: - `checklistId` (string, required) - `index` (integer) - `title` (string) ### `delete_checklist` (~74 tokens) Delete checklist Deletes a checklist with all its items. Needs confirm: true; without it the result is a preview. Input parameters: - `checklistId` (string, required) - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. ### `add_checklist_items` (~34 tokens) Add checklist items Adds items at the end of a checklist. Input parameters: - `checklistId` (string, required) - `items` (array, required) ### `update_checklist_item` (~45 tokens) Update checklist item Checks or unchecks a checklist item, or changes its text. Input parameters: - `done` (boolean) - `itemId` (string, required) - `text` (string) ### `delete_checklist_item` (~92 tokens) Delete checklist item Deletes one checklist item. A checklist keeps at least one item, so its last item only goes away with the whole checklist. Needs confirm: true; without it the result is a preview. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `itemId` (string, required) ### `add_attachment` (~145 tokens) Add attachment Attaches a link (url) or a file (contentBase64 + filename) to a task. Files follow the board owner's plan: 5 MB each and 100 MB per board on Free, 25 MB and 2 GB on Pro. Photos are optimized, as in the app. Input parameters: - `cardId` (string, required) - `contentBase64` (string): For a file: its bytes, base64-encoded. - `filename` (string): For a file: its name with extension. - `mimeType` (string) - `name` (string): The link's or file's name. - `url` (string): An http(s) link. ### `rename_attachment` (~34 tokens) Rename attachment Renames an attachment; a file keeps its extension. Input parameters: - `attachmentId` (string, required) - `name` (string, required) ### `delete_attachment` (~85 tokens) Delete attachment Deletes an attachment from a task (and the task's cover, if it was the cover image). Needs confirm: true; without it the result is a preview. Input parameters: - `attachmentId` (string, required) - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. ### `list_my_tasks` (~75 tokens) List my tasks Lists the user's tasks across every board, like the app's My tasks page: open cards assigned to the user plus dated cards on the user's own boards that nobody is assigned to, grouped as overdue, today, next 7 days, later and no date. Input parameters: - `limit` (integer): Default 100, max 500. ### `list_notifications` (~59 tokens) List notifications Lists the user's notifications (mentions, assignments, comments on watched cards, due-date digests), newest first, with the unread count. Input parameters: - `limit` (integer): Default 30, max 100. - `unreadOnly` (boolean): Default false. ### `mark_notifications_read` (~78 tokens) Mark notifications read Marks notifications as read: one (notificationId, which also marks the others about the same card, as opening it in the app does), every one about a card (cardId), or all of them (all: true). Input parameters: - `all` (boolean) - `cardId` (string) - `notificationId` (string) ### `get_account` (~53 tokens) Get account Reads the user's account and settings: name, email, language, time zone, notification preferences, plan with its limits and usage, upgrade prices, API tokens and connected apps (names and dates only; secrets are not included). ### `update_account` (~102 tokens) Update account settings Changes the user's settings: display name, language (en, es, fr), time zone (IANA, e.g. America/Argentina/Buenos_Aires; the daily digest goes out in the user's morning) and which notifications they get (mention, assigned, comment, due; email turns emails on or off). Input parameters: - `language` (string) - `name` (string) - `notifications` (object) - `timeZone` (string) ### `revoke_access` (~136 tokens) Revoke access Revokes one of the user's API tokens (apiTokenId) or disconnects a connected app (appClientId), as listed in the account. Whatever used it stops working at once, including this connection if it is the one in use. Needs confirm: true; without it the result is a preview. New tokens are only created by the user, in Settings. Input parameters: - `apiTokenId` (string) - `appClientId` (string) - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. ### `list_webhooks` (~95 tokens) List webhooks Lists the account's webhooks and Slack channels: kind (slack or json), a shortened address, the board it listens to (null: every board the user owns, plus invoices and estimates), the event types it sends, whether it is on, and how its last delivery went (lastStatus, lastError, lastSentAt; it turns itself off after 20 failures in a row). Signing secrets are not listed. ### `create_webhook` (~240 tokens) Create webhook Adds a webhook: from then on, each chosen event of the user's boards is sent outside Decknote. kind "slack" posts a line to a Slack channel through a Slack incoming-webhook URL (https://hooks.slack.com/…); kind "json" POSTs the event as JSON to any https URL (Zapier, Make, n8n, a server), signed in X-Decknote-Signature with a secret returned once, here. boardId limits it to one board the user owns; without it, every board they own and their invoices and estimates. events: the types to send (default: all). The free plan has 1 webhook, Pro 25. Needs confirm: true; without it the result is a preview. Input parameters: - `boardId` (string): One board the user owns. Omit for all of them. - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `events` (array) - `kind` (string, required) - `url` (string, required) ### `update_webhook` (~144 tokens) Update webhook Changes one of the account's webhooks: the event types it sends, turns it off or on (enabled), or replaces its signing secret (rotateSecret: the new one comes back once, and the old one stops verifying). Turning it on needs confirm: true, since events leave Decknote again; without it the result is a preview. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `enabled` (boolean) - `events` (array) - `rotateSecret` (boolean) - `webhookId` (string, required) ### `delete_webhook` (~83 tokens) Delete webhook Deletes one of the account's webhooks: nothing more is sent to its address. Needs confirm: true; without it the result is a preview. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `webhookId` (string, required) ### `test_webhook` (~128 tokens) Test webhook Sends a test to one of the account's webhooks now and returns how it went (ok, HTTP status, error): a sample of the first event type it sends, marked "test": true (a Slack channel gets a line saying it is connected). Needs confirm: true, since it sends to an address outside Decknote; without it the result is a preview. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `webhookId` (string, required) ### `export_data` (~53 tokens) Export data Exports everything the user can read in Decknote as one JSON document (boards, lists, cards, checklists, comments, attachment metadata), the same export as Settings → Your data. Up to 5 per hour. ### `start_pro_checkout` (~183 tokens) Start Pro checkout Starts an upgrade to Decknote Pro (14-day free trial, then US$9/month or US$90/year) by creating a Stripe Checkout link where the user pays; this tool charges nothing. Without confirm: true it returns the exact price and changes nothing; with confirm: true, amount has to equal that price. Accounts billed through Shopify are upgraded from the Shopify admin, not here. Input parameters: - `amount` (number|string): The price the user agreed to, in US$ (e.g. 9 or 90). - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `interval` (string): Default month. - `offer` (string): A founder-offer code from Decknote's email, if the user has one. ### `open_billing_portal` (~49 tokens) Open billing portal Creates a link to Stripe's billing portal, where the user manages their Pro subscription: payment card, invoices, monthly or yearly billing, cancellation. Changes happen there, made by the user. ### `api_read` (~274 tokens) Read from Decknote API Reads from Decknote's HTTP API (reference: https://decknote.app/api-docs#mcp-http-api) as the signed-in user, with GET; it doesn't change anything. Covers what no dedicated tool returns, such as the contents of an uploaded text file or a link preview. Reachable: GET /api/v1/me: the user (id, name, email); GET /api/v1/boards: the user's boards and their lists; GET /api/v1/boards/{boardId}/embeds: a board's live embeds (owner); GET /api/export: everything the user can read, as one JSON document; GET /api/link-preview?url=…: the title and description of a web page; GET /api/attachments/{attachmentId}: an uploaded file (text files come back as text; others as type and size). Takes a path on Decknote itself (not a full URL) and optional query parameters. Authentication, token, session, admin, payment and internal endpoints are not reachable, and secrets are removed from responses. Input parameters: - `path` (string, required): A path from the list, e.g. /api/v1/boards or /api/link-preview?url=https://example.com - `query` (object): Extra query parameters (string, number or boolean values). ### `api_create` (~259 tokens) Create via Decknote API Creates something through Decknote's HTTP API (reference: https://decknote.app/api-docs#mcp-http-api) as the signed-in user, with POST. Reachable: POST /api/v1/boards: a board: { title, template? }; POST /api/v1/cards: a card: { listId | boardId, title, description?, dueDate?, checklist?, reminders? }; POST /api/v1/boards/{boardId}/embeds: an embed of a board: { name, origins[], canEdit? } (owner, Pro). Takes a path on Decknote itself (not a full URL) and a JSON object body as documented there. Needs confirm: true; without it nothing is sent and the result is a preview of the request. Authentication, token, session, admin, payment and internal endpoints are not reachable, and secrets are removed from responses. Input parameters: - `body` (object): The JSON body the route documents. - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `path` (string, required): A path from the list, e.g. /api/v1/cards ### `show_board` (~102 tokens) Show board Shows a board as an interactive kanban that updates live while the conversation is open: lists and cards with labels, due dates, checklist progress and assignees, where the user can drag cards between lists, complete them and add new ones. Without boardId it shows the board the user changed most recently. Clients that can't display it get the same board as JSON. Input parameters: - `boardId` (string): The board to show. Default: the most recently changed one. ### `get_board_live_url` (~65 tokens) Get board live updates address Returns a short-lived address (2 minutes to connect) of a board's live event stream: a Server-Sent Events URL that announces every change to the board and who is viewing it. Used by the board view to update itself. Input parameters: - `boardId` (string, required) ### `start_timer` (~134 tokens) Start timer Starts the user's time tracker on a project, optionally on one of its tasks. There is one timer per person: a timer already running is stopped and its time kept first (a timer stopped within 30 seconds is dropped as an accidental click). The hours are the time elapsed when it stops, rounded to the minute and capped at 16 hours. Needs the editor role on the project. Input parameters: - `boardId` (string): The project. Optional when cardId is given. - `cardId` (string): The task to track time on. - `note` (string): What is being done, up to 500 characters. ### `stop_timer` (~45 tokens) Stop timer Stops the user's running timer and keeps the elapsed time as a time entry. A timer stopped within 30 seconds is dropped as an accidental click. Says so when no timer was running. ### `get_running_timer` (~37 tokens) Get running timer Returns the user's running timer, if any: the project, the task, the note, when it started and how long it has run. ### `log_time` (~209 tokens) Log time Adds hours by hand to a project, or to one of its tasks. The entry takes the project's hourly rate (or the client's) and is billable according to the task's setting, else the project's, unless billable is given. Needs the editor role on the project. Input parameters: - `billable` (boolean): Default: the task's setting, else the project's. - `boardId` (string): The project. Optional when cardId is given. - `cardId` (string): The task the time was spent on. - `day` (string): The day worked, YYYY-MM-DD. Default: today in the user's time zone. - `duration` (string, required): A duration the way a person writes it: 90, 90m, 1h, 1h30, 1:30 or 1.5h. A bare number is minutes. Up to 24 hours per entry. - `note` (string): What was done, up to 500 characters. ### `list_time_entries` (~157 tokens) List time entries Lists the time entries of a project, newest first, with who logged each, the task, the day, the minutes and whether it is billable. The project owner reads everyone's entries, with their hourly rates in cents; any other member reads only their own, without rates. Also returns the total minutes of everything the filters match. Input parameters: - `boardId` (string, required): The project. - `cardId` (string): Only this task. - `from` (string): Only entries from this day on, YYYY-MM-DD. - `limit` (integer): Default 100, max 500. - `to` (string): Only entries up to this day, YYYY-MM-DD. - `userId` (string): Only this person's entries. ### `update_time_entry` (~195 tokens) Update time entry Changes a finished time entry: its duration, day, note, whether it is billable, or the task it is on (null takes it off any task). A person edits their own entries and the project owner edits anyone's. Time already billed to a client, and a timer still running, cannot be edited. Input parameters: - `billable` (boolean) - `cardId` (string|null): Move the entry to this task of the same project; null removes the task. - `day` (string): The day worked, YYYY-MM-DD. - `duration` (string): A duration the way a person writes it: 90, 90m, 1h, 1h30, 1:30 or 1.5h. A bare number is minutes. Up to 24 hours per entry. - `entryId` (string, required) - `note` (string): Up to 500 characters. ### `delete_time_entry` (~107 tokens) Delete time entry Permanently deletes a time entry, or a running timer. A person deletes their own entries and the project owner deletes anyone's; time already billed to a client cannot be deleted. Needs confirm: true; without it the result is a preview of what would be lost. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `entryId` (string, required) ### `set_task_estimate` (~106 tokens) Set task estimate Sets how long a task is expected to take, or clears it with null. Written with a unit: 4h, 1h30, 90m, 1.5h (a bare number is minutes); up to 10,000 hours. Needs the editor role on the project. Input parameters: - `cardId` (string, required) - `estimate` (string|null, required): The estimate, e.g. 4h or 1h30; null clears it. ### `set_task_billable` (~83 tokens) Set task billable Sets whether time logged on a task is billable to the client (true or false), or makes it follow the project's default (null). Applies to time logged from then on; entries already logged keep their setting. Needs the editor role on the project. Input parameters: - `billable` (boolean|null, required): null follows the project's default. - `cardId` (string, required) ### `get_task_time` (~76 tokens) Get task time Reads the time of one task: its estimate, the time tracked so far, how close that is to the estimate (ok, warning from 80%, over), whether its time is billable, and its time entries. The project owner reads everyone's entries; any other member only their own. Input parameters: - `cardId` (string, required) ### `list_clients` (~60 tokens) List clients Lists the user's clients (the companies or people projects are done for) with their contact details, currency, default hourly rate in cents and how many projects use each. The free plan includes 2 active clients. Input parameters: - `includeArchived` (boolean): Default false. ### `create_client` (~163 tokens) Create client Adds a client. Projects are linked to a client in their settings; the client's currency and default hourly rate apply to their time. The free plan includes 2 active clients; Pro has no limit. Input parameters: - `address` (string) - `currency` (string): Three-letter code, e.g. USD or ARS. Default USD. - `email` (string): Contact email. - `hourlyRate` (number|string): Default hourly rate for this client's projects. An amount in the currency's main unit, e.g. 85 or "85.50" (not cents). - `name` (string, required): Up to 120 characters. - `notes` (string) - `phone` (string) - `taxId` (string): Tax or VAT number. ### `update_client` (~174 tokens) Update client Changes a client's name, contact details, currency, default hourly rate or notes; null clears an optional field. A new rate applies to time logged from then on: entries already logged keep the rate they were logged with. Input parameters: - `address` (string|null) - `clientId` (string, required) - `currency` (string): Three-letter code, e.g. USD or ARS. Default USD. - `email` (string|null) - `hourlyRate` (number|string|null): Default hourly rate for this client's projects. An amount in the currency's main unit, e.g. 85 or "85.50" (not cents). null clears it. - `name` (string) - `notes` (string|null) - `phone` (string|null) - `taxId` (string|null) ### `archive_client` (~95 tokens) Archive client Archives a client: it leaves the active list and stops counting toward the plan's client limit. Its projects keep the link and all the time stays. Needs confirm: true; without it the result is a preview. Input parameters: - `clientId` (string, required) - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. ### `restore_client` (~39 tokens) Restore client Brings an archived client back to the active list. The free plan's limit of 2 active clients applies. Input parameters: - `clientId` (string, required) ### `get_project_settings` (~87 tokens) Get project settings Reads a board's project settings: client, status (active, on hold, completed, cancelled), budget (none, hours or money), default hourly rate in cents, whether time is billable by default, and start and due dates. A board without settings is not a project yet. Only the project owner reads the rate and the money budget. Input parameters: - `boardId` (string, required) ### `update_project_settings` (~292 tokens) Update project settings Turns a board into a project or changes its settings: client (one of the user's own), status, budget type with its hours or amount, default hourly rate, billable by default, start and due dates. null clears a value. A new rate applies to time logged from then on. Only the board's owner can do this. Input parameters: - `billableByDefault` (boolean): Whether time is billable unless a task says otherwise. - `boardId` (string, required) - `budgetAmount` (number|string|null): Money budget. An amount in the currency's main unit, e.g. 85 or "85.50" (not cents). Used when budgetType is money. - `budgetHours` (number|string|null): Hours budget, e.g. 40 or "40h". Used when budgetType is hours. - `budgetType` (string): What the budget counts: tracked hours, or the billable amount. - `clientId` (string|null): One of the user's clients; null unlinks it. - `dueDate` (string|null): YYYY-MM-DD. - `hourlyRate` (number|string|null): Hourly rate for this project, over the client's. An amount in the currency's main unit, e.g. 85 or "85.50" (not cents). - `startDate` (string|null): YYYY-MM-DD. - `status` (string) ### `get_project_summary` (~84 tokens) Get project summary Summarizes a project: time tracked, billable time, the billable amount in cents, how much of the budget is used (ok, warning from 80%, over) and the hours of each person. The project owner reads all of it; any other member reads the project's totals and their own hours, without money. Input parameters: - `boardId` (string, required) ### `get_week_timesheet` (~72 tokens) Get week timesheet Returns the user's own timesheet for one week, Monday to Sunday: a row per project and task with the minutes of each day, the totals per day and the week's total. Input parameters: - `day` (string): Any day of the week wanted, YYYY-MM-DD. Default: today in the user's time zone. ### `get_time_report` (~234 tokens) Get time report Adds up the time logged in a date range, grouped by project, client, person, task or day: minutes, billable minutes and the billable amount in cents (hours times the rate each entry was logged with; clients in different currencies add up as plain numbers). The user's own projects count everyone's time and money; projects the user only belongs to count the user's own hours, with no amounts. Input parameters: - `billable` (boolean): true: only billable time. false: only non-billable time. - `boardId` (string): Only this project. - `by` (string): What to group the rows by. Default project. - `clientId` (string): Only the projects of this client (one of the user's own). - `from` (string): First day of the range, YYYY-MM-DD. Default: 29 days before `to`. - `to` (string): Last day of the range, YYYY-MM-DD. Default: today in the user's time zone. At most 400 days from `from`. - `userId` (string): Only the time logged by this person. ### `export_time_report` (~230 tokens) Export time report Exports the detail lines of a date range as CSV text (date, project, client, task, person, hours, billable, rate per hour), with the same filters and visibility as the time report. Cells that start with = + - or @ are escaped so a spreadsheet does not run them. A Pro feature; large exports are cut at 400,000 characters. Input parameters: - `billable` (boolean): true: only billable time. false: only non-billable time. - `boardId` (string): Only this project. - `by` (string): What to group the rows by. Default project. - `clientId` (string): Only the projects of this client (one of the user's own). - `from` (string): First day of the range, YYYY-MM-DD. Default: 29 days before `to`. - `to` (string): Last day of the range, YYYY-MM-DD. Default: today in the user's time zone. At most 400 days from `from`. - `userId` (string): Only the time logged by this person. ### `get_billing_profile` (~76 tokens) Get billing profile Reads the user's billing details that are copied onto every new invoice and estimate: business name, address, tax id, email, phone, currency, the invoice and estimate prefixes and next numbers, the default tax and its name, payment terms in days, payment instructions and default notes. Returns null when they are not set up yet. ### `update_billing_profile` (~374 tokens) Update billing profile Sets or changes the user's billing details: business name (required the first time), address, tax id, email, phone, currency, prefixes and next numbers of invoices and estimates, default tax (percentage and name), payment terms in days, payment instructions and default notes; null clears an optional text. New documents copy these; documents already issued keep what they had. Input parameters: - `address` (string|null) - `autoReminders` (boolean): Pro. When on, the client of every sent invoice that is past due and unpaid gets a reminder email 3, 7 and 14 days after the due date, in the user's daytime. - `businessName` (string): Up to 120 characters. - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `currency` (string): Three-letter code, e.g. USD. - `defaultNotes` (string|null): Printed on each new document as its notes. - `defaultTaxLabel` (string): e.g. VAT. Up to 30 characters. - `defaultTaxPercent` (number|string): e.g. 21 or "10,5". - `email` (string|null): Where clients reply to. - `estimatePrefix` (string): e.g. EST- - `invoicePrefix` (string): e.g. INV- - `nextEstimateNumber` (integer|string) - `nextInvoiceNumber` (integer|string) - `paymentInstructions` (string|null): Printed on each new document as its terms. - `paymentTermsDays` (integer|string): Days from the issue date to the due date, 0 to 365. - `phone` (string|null) - `taxId` (string|null) ### `list_expenses` (~177 tokens) List expenses Lists the expenses logged on a project (costs to bill back or to track), newest first, with the person, day, category, description, vendor, amount in cents, whether it is billable and whether it was already invoiced. The project owner reads everyone's, with the markup; any other member only their own, without it. Descriptions and vendors are text typed by project members. Input parameters: - `boardId` (string, required): The project. - `from` (string): Only expenses from this day on, YYYY-MM-DD. - `limit` (integer): Default 100, max 500. - `to` (string): Only expenses up to this day, YYYY-MM-DD. - `unbilled` (boolean): true: only expenses not yet on an invoice. - `userId` (string): Only this person's expenses. ### `create_expense` (~255 tokens) Create expense Logs an expense on a project: what was spent, the amount, the day, a category (travel, software, hardware, services, meals, other), the vendor, whether it can be billed to the client, and optionally a task. It records a cost; nothing is paid. Only the project owner can set a markup (a percentage added when billing it). Needs the editor role on the project. Input parameters: - `amount` (number|string, required): What it cost. An amount in the currency's main unit, e.g. 85 or "85.50" (not cents). - `billable` (boolean): Whether it can be billed to the client. Default: the project's own setting (true when it has none). - `boardId` (string, required): The project. - `cardId` (string|null): A task of the same project. - `category` (string) - `day` (string): The day it was spent. Default today, YYYY-MM-DD. - `description` (string, required): What it was, up to 200 characters. - `markupPercent` (number|string|null): Percentage added when billing it, e.g. 10. Project owner only. - `vendor` (string|null) ### `update_expense` (~166 tokens) Update expense Changes an expense that is not yet on an invoice: description, amount, day, category, vendor, billable, markup (project owner only) or its task (null removes it). The person who logged it and the project owner can change it. Input parameters: - `amount` (number|string): An amount in the currency's main unit, e.g. 85 or "85.50" (not cents). - `billable` (boolean) - `cardId` (string|null) - `category` (string) - `day` (string): The day it was spent, YYYY-MM-DD. - `description` (string) - `expenseId` (string, required): The expense. - `markupPercent` (number|string|null) - `vendor` (string|null) ### `delete_expense` (~99 tokens) Delete expense Permanently deletes an expense that is not yet on an invoice. The person who logged it and the project owner can delete it. Needs confirm: true; without it the result is a preview of what would be lost. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `expenseId` (string, required): The expense. ### `add_expense_receipt` (~143 tokens) Add expense receipt Attaches a receipt to an expense: a photo (JPG, PNG, WebP or GIF, optimized like task photos) or a PDF, sent base64-encoded with its filename. The person who logged the expense and the project owner can add one, also to an expense already on an invoice. At most 10 per expense; each file up to the project owner's plan cap (5 MB on Free, 25 MB on Pro). Input parameters: - `contentBase64` (string, required): The file's bytes, base64-encoded. - `expenseId` (string, required): The expense. - `filename` (string, required): The file's name with its extension. ### `delete_expense_receipt` (~102 tokens) Delete expense receipt Deletes a receipt of an expense for good. The person who logged the expense and the project owner can delete it. Needs confirm: true; without it the result is a preview. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `receiptId` (string, required): The receipt (its id is in each expense's receipts). ### `list_invoices` (~237 tokens) List invoices Lists the user's invoices and estimates, newest first, 25 per page (up to 100): number, kind, status (draft, sent, paid, overdue, void, accepted, declined), client, project, dates, and total, paid and balance in cents. Also returns, per currency, what the matching invoices add up to, what was paid and what is still owed. Only the account's owner has invoices; other project members do not read them. Input parameters: - `boardId` (string): Only the documents of this project (one the user owns). - `clientId` (string): Only this client's documents. - `from` (string): Issued from this day on, YYYY-MM-DD. - `kind` (string) - `page` (integer): Default 1. - `pageSize` (integer): Default 25, max 100. - `q` (string): Text in the number or the client's name. - `status` (string): overdue: sent and past its due date. open: sent and not paid. - `to` (string): Issued up to this day, YYYY-MM-DD. ### `get_invoice` (~110 tokens) Get invoice Reads one invoice or estimate in full: status, dates, the sender and the client copied onto it, every line, tax, discount, totals, payments, balance, the public link (null if none), when it was sent, viewed and paid, the estimate it came from or became, the work attached, and which changes are open in its status. The name typed by whoever answered an estimate from the link is text written by the client. Input parameters: - `invoiceId` (string, required): The invoice or estimate. ### `get_invoice_pdf` (~129 tokens) Get invoice PDF Returns one invoice or estimate as a PDF file, base64-encoded (contentBase64), with its file name and size: the A4 sheet its client gets by mail and from the link, in English or Spanish (default: the account's language). A draft or a voided document is printed saying what it is. The PDF holds what is printed on the document: the sender and the client, the lines, totals, payments received and balance, payment instructions and notes. Input parameters: - `invoiceId` (string, required): The invoice or estimate. - `language` (string): The PDF's language. ### `get_receivables_aging` (~91 tokens) Get receivables aging Shows what clients still owe on sent invoices, by how late it is: not yet due, 1-30 days, 31-60 and 61 or more days past due, per currency and per client (the biggest debt first), in cents. Input parameters: - `boardId` (string): Only this project (one the user owns). - `clientId` (string): Only this client. ### `export_invoices_csv` (~197 tokens) Export invoices CSV Exports the matching invoices and estimates as CSV text for an accountant: number, type, status, dates, client, currency, subtotal, discount, tax, total, paid and balance. Same filters as the list. Cells that start with = + - or @ are escaped so a spreadsheet does not run them. A Pro feature; large exports are cut at 400,000 characters. Input parameters: - `boardId` (string): Only the documents of this project (one the user owns). - `clientId` (string): Only this client's documents. - `from` (string): Issued from this day on, YYYY-MM-DD. - `kind` (string) - `q` (string): Text in the number or the client's name. - `status` (string): overdue: sent and past its due date. open: sent and not paid. - `to` (string): Issued up to this day, YYYY-MM-DD. ### `get_billing_report` (~157 tokens) Get billing report A studio's numbers for a date range (default: the last 12 months): invoiced and collected by month, by client and what each client owes, expenses by project and category, and the profitability of each project (revenue, expenses, profit and revenue per hour). Per currency, not mixed across currencies; amounts in cents. The range is at most 1100 days. Input parameters: - `boardId` (string): Only this project (one the user owns). - `clientId` (string): Only this client. - `from` (string): First day. Default 364 days before `to`, YYYY-MM-DD. - `to` (string): Last day. Default today in the user's time zone, YYYY-MM-DD. ### `create_invoice` (~415 tokens) Create invoice Creates a draft invoice or estimate, with its lines if given, copying the user's billing details and the chosen client onto it. The draft is private: nothing is sent or published. It has no number until it is sent; sending takes the next one from the profile's counter. The free plan includes 2 invoices or estimates per calendar month (voided ones count); Pro has no limit. Needs the billing details to be set up. Input parameters: - `boardId` (string|null): A project the user owns, to link the document to. - `clientId` (string|null): One of the user's clients; its name, email, address, tax id and currency are copied onto the document. - `currency` (string): Three-letter code. Default: the client's, else the profile's. - `discount` (number|string|null): A fixed amount off the whole document. An amount in the currency's main unit, e.g. 85 or "85.50" (not cents). null clears it. - `dueDate` (string|null): YYYY-MM-DD. Default: the profile's payment terms (invoice) or 30 days (estimate). - `issueDate` (string): The issue date. Default today, YYYY-MM-DD. - `kind` (string, required) - `lines` (array): At most 500. - `notes` (string|null): Up to 4000 characters. Default: the profile's default notes. - `taxLabel` (string): What the tax is called, up to 30 characters. - `taxPercent` (number|string): Tax as a percentage, e.g. 21 or "10,5". Default: the profile's. - `terms` (string|null): Up to 4000 characters. Default: the profile's payment instructions. - `toAddress` (string|null) - `toEmail` (string|null) - `toName` (string): Who it is for. Default: the client's name. - `toTaxId` (string|null) ### `list_unbilled_work` (~113 tokens) List unbilled work Lists what a project could still bill: its finished billable time entries (person, task, day, minutes and the rate each will be priced at, in cents) and its billable expenses not yet on an invoice. Only the project owner. Expense descriptions and task titles are text typed by project members. Input parameters: - `boardId` (string, required): The project. - `from` (string): From this day on, YYYY-MM-DD. - `to` (string): Up to this day, YYYY-MM-DD. ### `preview_invoice_from_work` (~517 tokens) Preview invoice from work Shows the lines and totals an invoice made from a project's unbilled work would have, without creating anything or taking any hours: finished billable time and billable expenses, grouped per task (default), person, day or one line in total, priced at the rate each entry was logged with (an entry with no rate at all is priced at zero and counted). Only the project owner. Input parameters: - `boardId` (string, required): The project. - `clientId` (string|null): One of the user's clients; its name, email, address, tax id and currency are copied onto the document. - `currency` (string): Three-letter code. Default: the client's, else the profile's. - `discount` (number|string|null): A fixed amount off the whole document. An amount in the currency's main unit, e.g. 85 or "85.50" (not cents). null clears it. - `dueDate` (string|null): YYYY-MM-DD. Default: the profile's payment terms (invoice) or 30 days (estimate). - `expenseIds` (array): Only these expenses. - `from` (string): Only work from this day on, YYYY-MM-DD. - `groupBy` (string): How the work becomes lines. Default task. - `includeExpenses` (boolean): Default true. - `includeTime` (boolean): Default true. - `issueDate` (string): The issue date. Default today, YYYY-MM-DD. - `notes` (string|null): Up to 4000 characters. Default: the profile's default notes. - `taxLabel` (string): What the tax is called, up to 30 characters. - `taxPercent` (number|string): Tax as a percentage, e.g. 21 or "10,5". Default: the profile's. - `taxableExpenses` (boolean): Whether tax applies to the expense lines. Default true. - `taxableTime` (boolean): Whether tax applies to the time lines. Default true. - `terms` (string|null): Up to 4000 characters. Default: the profile's payment instructions. - `timeEntryIds` (array): Only these time entries (from the unbilled list). - `to` (string): Only work up to this day, YYYY-MM-DD. - `toAddress` (string|null) - `toEmail` (string|null) - `toName` (string): Who it is for. Default: the client's name. - `toTaxId` (string|null) ### `create_invoice_from_work` (~578 tokens) Create invoice from work Creates a draft invoice from a project's unbilled work (same options as the preview): the finished billable hours and billable expenses become lines and are tied to the invoice, so they cannot be invoiced twice or edited until it is voided. The draft is private: nothing is sent. Counts toward the free plan's 2 documents per month. Only the project owner. Needs confirm: true and amount equal to the total of the preview; without them the result is that preview. Input parameters: - `amount` (number|string): The document's total in the currency's main unit, repeated from the preview (e.g. 220 or "220.00"). Must equal the total or nothing is done. - `boardId` (string, required): The project. - `clientId` (string|null): One of the user's clients; its name, email, address, tax id and currency are copied onto the document. - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `currency` (string): Three-letter code. Default: the client's, else the profile's. - `discount` (number|string|null): A fixed amount off the whole document. An amount in the currency's main unit, e.g. 85 or "85.50" (not cents). null clears it. - `dueDate` (string|null): YYYY-MM-DD. Default: the profile's payment terms (invoice) or 30 days (estimate). - `expenseIds` (array) - `from` (string): Only work from this day on, YYYY-MM-DD. - `groupBy` (string): How the work becomes lines. Default task. - `includeExpenses` (boolean) - `includeTime` (boolean) - `issueDate` (string): The issue date. Default today, YYYY-MM-DD. - `notes` (string|null): Up to 4000 characters. Default: the profile's default notes. - `taxLabel` (string): What the tax is called, up to 30 characters. - `taxPercent` (number|string): Tax as a percentage, e.g. 21 or "10,5". Default: the profile's. - `taxableExpenses` (boolean) - `taxableTime` (boolean) - `terms` (string|null): Up to 4000 characters. Default: the profile's payment instructions. - `timeEntryIds` (array) - `to` (string): Only work up to this day, YYYY-MM-DD. - `toAddress` (string|null) - `toEmail` (string|null) - `toName` (string): Who it is for. Default: the client's name. - `toTaxId` (string|null) ### `update_invoice` (~414 tokens) Update invoice Changes a document. A draft takes every field (client, dates, currency, tax, discount, notes, terms, who it is for, project and the whole list of lines, which replaces the current ones); once sent only the notes and the due date change; once paid or answered, only the notes. Totals are recomputed on the server. null clears an optional field. Input parameters: - `boardId` (string|null): A project the user owns. - `clientId` (string|null): One of the user's clients; its name, email, address, tax id and currency are copied onto the document. - `currency` (string): Three-letter code. Default: the client's, else the profile's. - `discount` (number|string|null): A fixed amount off the whole document. An amount in the currency's main unit, e.g. 85 or "85.50" (not cents). null clears it. - `dueDate` (string|null): YYYY-MM-DD. Default: the profile's payment terms (invoice) or 30 days (estimate). - `invoiceId` (string, required): The invoice or estimate. - `issueDate` (string): The issue date. Default today, YYYY-MM-DD. - `lines` (array): The whole list (replaces the current lines). At most 500. - `notes` (string|null): Up to 4000 characters. Default: the profile's default notes. - `taxLabel` (string): What the tax is called, up to 30 characters. - `taxPercent` (number|string): Tax as a percentage, e.g. 21 or "10,5". Default: the profile's. - `terms` (string|null): Up to 4000 characters. Default: the profile's payment instructions. - `toAddress` (string|null) - `toEmail` (string|null) - `toName` (string): Who it is for. Default: the client's name. - `toTaxId` (string|null) ### `send_invoice` (~192 tokens) Send invoice Marks a draft as sent, gives it the next number and publishes its link: anyone who has the link can read the document (lines, amounts, the user's business details), and for an estimate answer it. Nothing is emailed. After that only the notes and the due date change. The draft needs a client name, at least one line and a total above zero. Needs confirm: true and amount equal to the total; without them the result is a preview. Input parameters: - `amount` (number|string): The document's total in the currency's main unit, repeated from the preview (e.g. 220 or "220.00"). Must equal the total or nothing is done. - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `invoiceId` (string, required): The invoice or estimate. ### `get_invoice_email_draft` (~155 tokens) Get invoice email draft Shows the email that would go to the client for a draft or sent document: the address, the subject and the text, with the personal message and the language if given; a reminder reads differently for a sent invoice with a balance. Sends nothing and changes nothing; says whether this server can send email at all. Input parameters: - `invoiceId` (string, required): The invoice or estimate. - `locale` (string): Language of the email. Default: the user's. - `message` (string|null): A few personal lines at the top, up to 2000 characters. - `reminder` (boolean): A reminder for a sent invoice with a balance. - `to` (string): Another address than the one on the document. ### `email_invoice` (~323 tokens) Email invoice Emails the document to the client from Decknote on the user's behalf (replies go to the user), with a link to it; a draft takes the next number, becomes sent and its link is published. One plain address: the document's or `to`. Limited to 20 emails an hour per person and one email per document every 10 minutes. A new address beyond the plan's allowance (2 addresses in all on the free plan, 25 new ones a day on Pro) must first confirm that it wants the user's emails: it gets a link from Decknote and the call fails with code unconfirmed until it confirms. On the free plan the message cannot carry links or web addresses. Needs confirm: true and amount equal to the total; without them the result is a preview with the exact email. Input parameters: - `amount` (number|string): The document's total in the currency's main unit, repeated from the preview (e.g. 220 or "220.00"). Must equal the total or nothing is done. - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `invoiceId` (string, required): The invoice or estimate. - `locale` (string) - `message` (string|null): A few personal lines at the top, up to 2000 characters. - `reminder` (boolean): A reminder for a sent invoice with a balance. - `to` (string): Another address than the one on the document. ### `regenerate_invoice_link` (~116 tokens) Regenerate invoice link Replaces the public link of a document with a new one: the old link stops working at once for anyone who has it, and the new one lets anyone who holds it read the document. Not for a voided document. Needs confirm: true; without it the result is a preview. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `invoiceId` (string, required): The invoice or estimate. ### `revoke_invoice_link` (~99 tokens) Revoke invoice link Turns a document's public link off: the client can no longer open the document until a new link is made. The document itself is unchanged. Needs confirm: true; without it the result is a preview. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `invoiceId` (string, required): The invoice or estimate. ### `void_invoice` (~136 tokens) Void invoice Voids a sent invoice or estimate: it cannot change any more, its number is kept, and the hours and expenses it had taken go back to the project's unbilled work. A draft is not voided (it is deleted). An invoice with payments recorded, and an estimate whose invoice still stands, cannot be voided. Needs confirm: true; without it the result is a preview. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `invoiceId` (string, required): The invoice or estimate. ### `delete_invoice_draft` (~153 tokens) Delete invoice draft Deletes a draft invoice or estimate for good. Only a draft: it was not sent, so no client saw it, and it has no number, so no gap is left in the numbering. The hours and expenses it had taken go back to the project's unbilled work, and an estimate it was made from can become an invoice again. A deleted draft stops counting toward the free plan's monthly allowance. Needs confirm: true; without it the result is a preview. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `invoiceId` (string, required): The invoice or estimate. ### `record_invoice_payment` (~258 tokens) Record invoice payment Records that the client paid, fully or in part, on a sent invoice: the amount, the day (default today, not in the future), the method (bank, card, cash, paypal, other) and a note. It records that the client paid; it does not charge or move money. The invoice becomes paid when the payments cover the total. A payment above the balance needs confirmOverpay. Needs confirm: true; without it the result is a preview with the balance. Input parameters: - `amount` (number|string, required): What the client paid. An amount in the currency's main unit, e.g. 85 or "85.50" (not cents). - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `confirmOverpay` (boolean): Record it even though it is more than the balance. - `day` (string): The day it was received. Default today, YYYY-MM-DD. - `invoiceId` (string, required): The invoice or estimate. - `note` (string|null): Up to 500 characters. - `paymentMethod` (string): How it was received. Default other. ### `remove_invoice_payment` (~117 tokens) Remove invoice payment Deletes a recorded payment from an invoice, as if it had not been written down; a paid invoice that is no longer covered goes back to sent. It undoes a note in the books; no money moves. Needs confirm: true; without it the result is a preview. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `paymentId` (string, required): A payment of one of the user's invoices. ### `list_recurring_invoices` (~109 tokens) List recurring invoices Lists the user's recurring invoices: for each, the client, the total of each invoice, how often (every N weeks, months or years), the next date, how many are left (null = no end), what happens to each new invoice (draft, sent, or emailed to the client), whether it is paused, the last invoice it made and the reason its last run could not finish, if any. Client names and line descriptions are text typed by the user and their clients. ### `create_recurring_invoice` (~311 tokens) Create recurring invoice Pro. Makes an invoice repeat: a new invoice with the same client, lines, tax, notes and terms is made on each date (every N weeks, months or years from nextDate), until endAfter invoices are made or with no end. Each new invoice is left as a draft, marked as sent (its link is published), or emailed to the client, as action says. The lines are copied now: later changes to the original invoice do not reach the ones to come. Needs confirm: true; without it the result is a preview. Input parameters: - `action` (string): What happens to each new invoice. Default draft. email needs the client's email address on the invoice. - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `endAfter` (integer|string|null): How many invoices to make, 1 to 500; null or omitted = no end. - `every` (integer|string): Every how many weeks, months or years, 1 to 12. Default 1. - `interval` (string, required) - `invoiceId` (string, required): The invoice to repeat (not an estimate, not voided). - `nextDate` (string, required): The date of the next invoice, today or later, YYYY-MM-DD. - `paymentTermsDays` (integer|string): Days each new invoice gives to pay. Default: those of the original invoice. ### `update_recurring_invoice` (~252 tokens) Update recurring invoice Changes a recurring invoice: how often, the next date (a new cadence counts from it), endAfter (null = no end), what happens to each new invoice, the days to pay, or pauses it (active false) and resumes it (active true; dates missed while paused are skipped). The lines stay as they were copied. Pausing needs nothing more; a change after which new invoices are sent or emailed needs confirm: true, and without it the result is a preview. Input parameters: - `action` (string) - `active` (boolean): false pauses it, true resumes it. - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `endAfter` (integer|string|null): Invoices left to make, 1 to 500; null = no end. - `every` (integer|string): 1 to 12. - `interval` (string) - `nextDate` (string): The new next date, today or later, YYYY-MM-DD. - `paymentTermsDays` (integer|string) - `recurringId` (string, required): The recurring invoice. ### `delete_recurring_invoice` (~93 tokens) Delete recurring invoice Deletes a recurring invoice: no more invoices are made from it. The invoices it already made stay as they are. Needs confirm: true; without it the result is a preview. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `recurringId` (string, required): The recurring invoice. ### `duplicate_invoice` (~71 tokens) Duplicate invoice Creates a new draft with the same client, lines, tax, notes and terms as an invoice or estimate, dated today and without a number until it is sent; no work, no payments. Counts toward the free plan's 2 documents per month. Input parameters: - `invoiceId` (string, required): The invoice or estimate. ### `convert_estimate_to_invoice` (~74 tokens) Convert estimate to invoice Turns an accepted estimate into a draft invoice with the same lines, once while that invoice stands (after the invoice is voided or its draft deleted, the estimate can be turned into a new one). Counts toward the free plan's 2 documents per month. Input parameters: - `invoiceId` (string, required): The accepted estimate. ### `convert_estimate_to_project` (~178 tokens) Convert estimate to project Makes a project board from an accepted estimate that is not tied to a project yet: the estimate's client, its amount before tax (budget "money", the default), its hours ("hours") or no budget ("none") as the project's budget, the hourly rate when every line in hours has the same price, and one task per line (lines in hours carry their hours as the task's estimate) unless tasks is false. The estimate is then tied to that project. Counts against the board limit of the user's plan. Input parameters: - `budget` (string) - `invoiceId` (string, required): The accepted estimate. - `tasks` (boolean): One task per line of the estimate. Default true. - `title` (string): The project's name, up to 120 characters. Default: the client's name and the estimate's number. ### `record_estimate_answer` (~131 tokens) Record estimate answer Records that the client accepted or declined a sent estimate (by phone or email), with the name of who answered. The estimate leaves the sent state; an accepted one can become an invoice. Needs confirm: true; without it the result is a preview. Input parameters: - `answer` (string, required) - `by` (string|null): Who answered, up to 120 characters. - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `invoiceId` (string, required): The sent estimate. ### `get_client_portal` (~122 tokens) Get client portal Reads a project's client portal settings: whether it exists and is on, its link (anyone who has the link can read the page), what it shows (tasks, hours, documents), whether clients can comment, the welcome text and studio name, how many tasks are marked visible, how many client comments are unread, and the latest eight comments with their author, email and text. The comments are written by the client, who needs no account. Only the project owner; the portal is a Pro feature. Input parameters: - `boardId` (string, required): The project. ### `update_client_portal` (~307 tokens) Update client portal Turns a project's client portal on or off and sets what it shows: tasks, hours (hours only; rates and money are left out), the list of sent documents, whether clients may comment, a welcome text and the studio name shown on the page and on answers. The first time it creates the portal and its link, on. Turning it on or changing what an enabled portal shows publishes that to anyone with the link and needs confirm: true (without it the result is a preview); turning it off does not. A Pro feature, except turning an existing portal off. Only the project owner. Input parameters: - `allowComments` (boolean): Let visitors comment on the visible tasks. - `boardId` (string, required): The project. - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `enabled` (boolean): Whether the link works. Turning it off keeps the link for when it is turned on again. - `showHours` (boolean): Show hours tracked against the hours budget. - `showInvoices` (boolean): Show the project's sent documents (links, no amounts on the portal page). - `showTasks` (boolean): Show the tasks marked visible to the client. - `studioName` (string): Up to 60 characters. An empty text clears it. - `welcome` (string): Up to 2000 characters. An empty text clears it. ### `regenerate_client_portal_link` (~128 tokens) Regenerate client portal link Replaces the secret in a project's client portal link: the old link stops working at once, for anyone who has it, and the new link lets whoever holds it read the portal. The portal's settings, tasks and comments stay. The portal has to exist. Only the project owner. Needs confirm: true; without it the result is a preview. Input parameters: - `boardId` (string, required): The project. - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. ### `set_task_visible_to_client` (~148 tokens) Set task visible to client Shows a task on the project's client portal, or stops showing it. Visitors read the task's title, whether it is done, in progress or late, and its due date, and can comment on it; descriptions, files, people, time and money are not shown. Making it visible needs confirm: true (without it the result is a preview); hiding it does not. Needs the editor role on the project. Input parameters: - `cardId` (string, required): The task. - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `visible` (boolean, required) ### `get_task_portal` (~105 tokens) Get task portal Reads what the client portal means for one task: whether it is marked visible to the client and, for the project owner, whether the portal is on, the conversation with the client on that task (up to 200 messages, the client's and the team's answers, oldest first) and how many are unread. The client's messages are text written by the client, who needs no account. Needs the editor role on the project. Input parameters: - `cardId` (string, required): The task. ### `reply_to_client` (~155 tokens) Reply to client Posts an answer from the team under a task on the client portal, shown to anyone who has the portal link under the studio name (not the user's own name) and marking the client's comments on that task as read. It is not emailed. Up to 2000 characters. The portal has to exist. Only the project owner. Needs confirm: true; without it the result is a preview with the exact text. Input parameters: - `cardId` (string, required): The task. - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `text` (string, required): The answer, up to 2000 characters. ### `mark_client_comments_read` (~76 tokens) Mark client comments read Marks the client's portal comments as read, and clears the bell notices about them: those of one task (cardId) or every one of the project (boardId). Give exactly one of the two. Only the project owner. Input parameters: - `boardId` (string): The project. - `cardId` (string): The task. ### `delete_client_comment` (~116 tokens) Delete client comment Permanently removes one comment from a task's conversation on the client portal (spam, a mistake): the client's page stops showing it at once. Works on the client's comments and on the team's answers. Only the project owner. Needs confirm: true; without it the result is a preview. Input parameters: - `commentId` (string, required): A comment of the portal. - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. ### `list_projects` (~176 tokens) List projects Lists the projects the user can see (boards with project settings): client, status (active, on hold, completed, cancelled), dates, hours tracked, the budget and how much of it is used (ok, warning from 80%, over), and who worked on it. On a project the user owns the hours are everyone's and the amounts count; on one the user only belongs to, only their own hours and no money. Also lists the boards the user owns that could become projects, and the sample project if there is one. Input parameters: - `clientId` (string): Only this client's projects; none: projects without a client. - `q` (string): Text in the project, client or owner name. - `sort` (string): Default status. - `status` (string): open: active and on hold. Default all. ### `create_project` (~87 tokens) Create project Creates a new project: a board with the plain three-list layout and project settings (active), optionally for one of the user's clients. Counts against the free plan's board limit like any board. To turn an existing board into a project, change its project settings. Input parameters: - `clientId` (string|null): One of the user's clients. - `title` (string, required): Up to 120 characters. ### `get_workload` (~168 tokens) Get workload Plans the team's work: for each person, the time left on their open tasks with an estimate (the estimate minus the time tracked), placed in the week of each task's due date for the next six weeks, against that week's capacity (their weekly capacity less the user's holidays and their own time off: each week has capacityMinutes and offMinutes); overdue, later and undated work are listed apart. Says per week whether it is empty, ok, near (from 80%) or over capacity. The user sees the people on the projects they own and themselves. A Pro feature. Names and task titles are text typed by project members. Input parameters: - `includeTasks` (boolean): Add the tasks behind each week's number. Default false. - `personId` (string): Only this person's row. ### `set_my_weekly_capacity` (~94 tokens) Set my weekly capacity Sets how many hours a week the user can work, which the workload view compares their planned work with: 40, 37.5 or 37:30; 0 for someone who is away, at most 168. Only the user's own: there is no way to set another person's. Input parameters: - `hours` (number|string, required): Hours a week, e.g. 40 or "37:30". ### `list_project_templates` (~90 tokens) List project templates Lists the templates a new project can start from: the starters that come with Decknote (website project, marketing campaign, monthly retainer) and the ones the user saved, each with its lists, number of tasks, total estimate, whether its tasks carry relative due dates, and a note when a saved one cannot be used. The free plan keeps 1 saved template; the starters cost no place. ### `save_project_as_template` (~156 tokens) Save project as template Saves a project's shape as a template: its lists, open tasks (title, estimate, billable, labels, checklists with the items unticked, due dates as days from the start), labels and billable default. Its people, comments, logged time, descriptions, attachments and client are left out. The budget and the hourly rate are saved only with includeMoney. Only the project owner. The free plan keeps 1 saved template; Pro has no limit. Input parameters: - `boardId` (string, required): The project. - `description` (string): Up to 300 characters. - `includeMoney` (boolean): Keep the budget and the hourly rate. Default false. - `name` (string, required): Up to 100 characters. ### `create_project_from_template` (~154 tokens) Create project from template Creates a new project from a starter or saved template: its lists, labels, tasks with estimates and checklists, and settings, with due dates shifted onto the start date (default today). The template is untouched. Optionally for one of the user's clients. Counts against the free plan's board limit like any board. Input parameters: - `clientId` (string|null): One of the user's clients. - `startDate` (string|null): YYYY-MM-DD. The day the project starts. Default today. - `templateId` (string, required): The template's id: a starter's or a saved one's. - `templateKind` (string, required) - `title` (string, required): The new project's name, up to 120 characters. ### `rename_project_template` (~75 tokens) Rename project template Changes the name and description of a saved template (also one that is damaged and cannot be used). The description is cleared when not given. Input parameters: - `description` (string): Up to 300 characters. - `name` (string, required): Up to 100 characters. - `templateId` (string, required): A saved template of the user. ### `delete_project_template` (~96 tokens) Delete project template Permanently deletes a saved template of the user (projects already made from it are untouched; the starters cannot be deleted). Needs confirm: true; without it the result is a preview. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `templateId` (string, required): A saved template of the user. ### `list_pages` (~116 tokens) List pages Lists a project's notes or discussions, pinned first and then the most recently touched (a reply counts), up to 200: title, a snippet, who started it, comment count, pinned and archived. Searches titles and bodies. Titles and snippets are written by project members. Any role on the project reads. Input parameters: - `archived` (boolean): true: the archived ones. Default false. - `boardId` (string, required): The project. - `kind` (string, required) - `q` (string): Text in the title or the body. ### `get_page` (~121 tokens) Get page Reads one note or discussion in full: its title, its body as Markdown (up to 100,000 characters; bodyTruncated says it was cut), who started it, whether it is pinned or archived, its comments oldest first (the newest ones that fit, at most 500; commentsTruncated says some were left out), and the rev to send back when editing it. The title, body and comments are written by project members. Any role on the project reads. Input parameters: - `pageId` (string, required): The page (a note or a discussion). ### `create_page` (~121 tokens) Create page Starts a note (shared writing any editor can change) or a discussion (its text belongs to its author and the owner; editors answer with comments) in a project. The body is Markdown; links must be http, https, mailto, tel or of this site. Too much text is refused, not cut. Needs the editor role on the project. Input parameters: - `boardId` (string, required): The project. - `content` (string): The body, in Markdown. - `kind` (string, required) - `title` (string, required): Up to 200 characters. ### `update_page` (~173 tokens) Update page Changes a page's title and/or body (Markdown, replacing the whole body). It needs the rev from when the page was read: if somebody saved in between, the save is refused with the reason and nothing is overwritten. Pinning, archiving and comments do not change the rev. A discussion's text is edited by its author and the project owner; an archived page is read-only. A page with images, or with a body longer than 100,000 characters, keeps its body: only its title changes. Needs the editor role on the project. Input parameters: - `content` (string): The whole new body, in Markdown. - `pageId` (string, required): The page (a note or a discussion). - `rev` (string, required): The rev returned when the page was read. - `title` (string) ### `set_page_pinned` (~60 tokens) Set page pinned Pins a page to the top of its list, or unpins it. Only the project owner; an archived page cannot be pinned. Input parameters: - `pageId` (string, required): The page (a note or a discussion). - `pinned` (boolean, required) ### `set_page_archived` (~59 tokens) Set page archived Archives a page (it leaves the list, becomes read-only and loses its pin) or restores it. Only the project owner. Input parameters: - `archived` (boolean, required) - `pageId` (string, required): The page (a note or a discussion). ### `delete_page` (~93 tokens) Delete page Permanently deletes a note or discussion with all its comments. Its author and the project owner can. Needs confirm: true; without it the result is a preview. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `pageId` (string, required): The page (a note or a discussion). ### `add_page_comment` (~78 tokens) Add page comment Adds a comment to a note or discussion (plain text, up to 5000 characters); the page moves up its list. Not on an archived page. Needs the editor role on the project. Input parameters: - `pageId` (string, required): The page (a note or a discussion). - `text` (string, required): Up to 5000 characters. ### `edit_page_comment` (~59 tokens) Edit page comment Changes the text of one of the user's own page comments. Not on an archived page. Needs the editor role on the project. Input parameters: - `commentId` (string, required): A page comment. - `text` (string, required): Up to 5000 characters. ### `delete_page_comment` (~84 tokens) Delete page comment Permanently deletes a page comment. Its author and the project owner can. Needs confirm: true; without it the result is a preview. Input parameters: - `commentId` (string, required): A page comment. - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. ### `list_project_files` (~140 tokens) List project files Lists every file and link attached to a project's tasks, newest first (up to 200): name, type (image, pdf, document, sheet, archive, media, link, other), MIME type, size, the task and list it is on, and for a link its address. Narrow by type or by text in the file or task name; also returns how many there are of each type. Names and addresses are typed by project members. Any role on the project reads. Input parameters: - `boardId` (string, required): The project. - `q` (string): Text in the file name or the task title. - `type` (string) ### `list_team_rates` (~87 tokens) List team rates and costs Lists the user's team (themselves, the people on their projects and whoever logged time on them) with each person's default hourly rate, what an hour of theirs costs the user, their weekly capacity and on how many projects they are. Amounts in cents. The cost is only the user's: nobody else reads it. Names and emails are typed by other people. A Pro feature. ### `set_team_rate` (~212 tokens) Set a person's rate and cost Sets what a person is billed at by default on the user's projects (hourlyRate) and what an hour of theirs costs the user (hourlyCost), per hour. They apply to hours logged from then on: each hour keeps the rate and cost it had when it was logged, unless the user applies the new ones to the hours already logged. null clears a value. The rate is the last resort: the person's rate on a project, then the project's, then the client's come first. A Pro feature. Input parameters: - `hourlyCost` (number|string|null): What an hour costs the user (salary and overhead). In the currency's main unit: 85, "85.50", "1.250,50". null clears it. - `hourlyRate` (number|string|null): Default hourly rate. In the currency's main unit: 85, "85.50", "1.250,50". null clears it. - `userId` (string, required): A person on the user's team. ### `get_member_rates` (~100 tokens) Get the rates of a project's people For a project the user owns: the project's and the client's rates and, for each person who can log time there (the owner and the editors), the rate set for them on this project, what a new hour of theirs would be billed at and where that comes from (member, project, client, team or none). Amounts in cents. Names are typed by project members. A Pro feature. Input parameters: - `boardId` (string, required): The project. ### `set_member_rate` (~121 tokens) Set a person's rate on a project Sets what one person is billed at on one project the user owns, over the project's, the client's and their default. null goes back to those. It applies to hours logged from then on. The person must be able to log time there. A Pro feature. Input parameters: - `boardId` (string, required): The project. - `hourlyRate` (number|string|null, required): In the currency's main unit: 85, "85.50", "1.250,50". null clears it. - `userId` (string, required): A person on the user's team. ### `reprice_time` (~232 tokens) Apply today's rates and costs to logged hours A rate or a cost is frozen on each hour when it is logged, so one set today does not reach last month's hours. This gives the hours logged on or after `from` (not invoiced, not running, not on a closed day) the rate and cost a new hour would get now: only the empty ones unless overwrite is true, and it does not clear a value. It changes numbers in the user's reports, so it needs confirm: true; without it the result is a preview with the counts. Only the user's own projects and team. A Pro feature. Input parameters: - `boardId` (string): Only this project (one the user owns). - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `from` (string, required): The first day to re-price as YYYY-MM-DD. - `overwrite` (boolean): Also replace rates and costs that are already there. Default false: only fill the empty ones. - `userId` (string): Only this person's hours. ### `get_profitability_report` (~221 tokens) Get the profitability report What the hours were worth, what they cost and what is left, for a range of at most 400 days, by project (default), client, person or task (each task with its project; the hours of a project logged without a task are one row whose key is none: followed by the project id). value = billable minutes at the rate frozen on each entry; cost = all minutes at the cost frozen on each entry (hours logged before a cost was set are counted in minutesWithoutCost and have none); margin = value + billable expenses recovered with their markup - cost - expenses. Money is per currency and is not added across them; a project in a currency other than costCurrency (the user's billing currency) has marginCents null. Amounts in cents. Only the user's own projects. Names are typed by other people. A Pro feature. Input parameters: - `by` (string): Default project. - `from` (string, required): First day as YYYY-MM-DD. - `to` (string, required): Last day as YYYY-MM-DD. ### `get_utilization_report` (~127 tokens) Get the utilization report For each person on the user's team: what they could work in a range of at most 400 days (their weekly capacity over Monday to Friday, less the user's holidays and their own time off), their hours on the user's projects, their billable hours, and billable over capacity in percent (utilizationPct, null with no capacity). Only the hours on the user's own projects are counted. Names are typed by other people. A Pro feature. Input parameters: - `from` (string, required): First day as YYYY-MM-DD. - `to` (string, required): Last day as YYYY-MM-DD. ### `get_assignments_report` (~287 tokens) Get the assignments report Who is doing what: every open task (not completed, not archived) of the projects the user owns, grouped by the person it is assigned to, plus a group for the tasks nobody is assigned to (userId null); a task with two people is in both groups and the totals count it once. Each task has its project, client, list, labels, due day and where it falls (overdue, this_week, later or none, in the user's time zone), the estimate, the time logged on it by everyone, what is left of the estimate and what was logged past it. Filters: a project, a client, a person or the unassigned tasks, the due bucket and a label name. Up to 5,000 tasks. Names and titles are typed by other people. A Pro feature. Input parameters: - `boardId` (string): Only this project (one the user owns). - `clientId` (string): Only the projects of this client (one of the user's clients). - `due` (string): overdue (before today), this_week (today to Sunday), later, or none (no due date). - `label` (string): Only tasks with a label of this name (any project, any case). - `unassigned` (boolean): Only the tasks nobody is assigned to. - `userId` (string): Only this person's tasks. ### `preview_time_import` (~451 tokens) Preview time import Reads a CSV of hours (Toggl, Harvest, Clockify or any CSV with a date and a duration or start and end times) and says what importing it would do, without writing anything: the rows that can be imported and their total time, the clients, projects and tasks that would be created, duplicates of an earlier import that would be skipped, the rows that cannot be read with their row numbers, who the time would be logged as, and whether the free plan's limits block it. Also returns the settings it used (guessed from the headers unless given) and the file's columns. The CSV travels as text, up to 200,000 characters; the Import page of the app takes files up to 8 MB. Names and cells from the file are text written by others. Input parameters: - `createClients` (boolean): Create the clients named in the file and link the projects to them. Default true. - `csv` (string, required): The CSV file's text, up to 200,000 characters. A Toggl, Harvest or Clockify export or any CSV with a date column and a duration (or start and end times). - `dateOrder` (string): How 03/04/2026 reads when the file does not settle it. Default: month first in English, day first in Spanish. - `durationUnit` (string): What a bare number in the duration column means. Default auto: hours. - `excludeProjects` (array): Projects to leave out, by their key in the preview. - `fallbackProject` (string): The project for rows that name none. Default "Imported time". - `fileName` (string): The file's name, for the history. Default import.csv. - `mapping` (object): Which column holds each field, as the column's header text or its position (0 is the first). Fields: date, startTime, endDate, endTime, duration, project, client, task, person, firstName, lastName, e… - `source` (string): Which tool exported it. Default: guessed from the columns. ### `import_time_csv` (~458 tokens) Import time CSV Imports a CSV of hours: creates the clients and projects it names (when createClients is on), a task for each task name, and one time entry per row, logged as the user unless the file names a project member's email. Rows already imported before are skipped, and the whole import can be taken back. The plan is made again from the file and the account at that moment. Same arguments as the preview; the CSV travels as text, up to 200,000 characters (bigger files go through the Import page of the app). Names from the file are text written by others. Needs confirm: true; without it the result is the preview. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `createClients` (boolean): Create the clients named in the file and link the projects to them. Default true. - `csv` (string, required): The CSV file's text, up to 200,000 characters. A Toggl, Harvest or Clockify export or any CSV with a date column and a duration (or start and end times). - `dateOrder` (string): How 03/04/2026 reads when the file does not settle it. Default: month first in English, day first in Spanish. - `durationUnit` (string): What a bare number in the duration column means. Default auto: hours. - `excludeProjects` (array): Projects to leave out, by their key in the preview. - `fallbackProject` (string): The project for rows that name none. Default "Imported time". - `fileName` (string): The file's name, for the history. Default import.csv. - `mapping` (object): Which column holds each field, as the column's header text or its position (0 is the first). Fields: date, startTime, endDate, endTime, duration, project, client, task, person, firstName, lastName, e… - `source` (string): Which tool exported it. Default: guessed from the columns. ### `list_time_imports` (~79 tokens) List time imports Lists the user's time imports, newest first (the last 30): the source (toggl, harvest, clockify, generic), the file name, whether it is done or was undone, how many entries and how many minutes it brought, how many rows were skipped as duplicates or failed, and when. The sample project is not listed. ### `undo_time_import` (~132 tokens) Undo time import Takes an import back: deletes its time entries and the clients, projects and tasks it created that nobody has used since (those that were used are kept, and the result counts them). Refused when some of the time was already invoiced, when it was already undone, and for the sample project. Needs confirm: true; without it the result is a preview. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `importId` (string, required): An import of the user. ### `create_sample_project` (~83 tokens) Create sample project Creates a sample client, a sample project with a budget, six tasks with estimates and two weeks of hours, labelled as a sample in its name, so reports, the budget bar and the timesheet have something to show. One at a time. Uses a board of the free plan's limit (and the sample client is left out if the client limit is full). ### `delete_sample_project` (~99 tokens) Delete sample project Permanently deletes the sample project with everything on it (its tasks, hours and anything added to it since) and the sample client if nothing else uses it. The user's own projects and reports are untouched. Needs confirm: true; without it the result is a preview. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. ### `list_holidays` (~106 tokens) List holidays Lists the holidays on the user's calendar, oldest first (up to 1,000): day, name and whether it falls on a weekend (a weekend holiday takes nothing from anyone's capacity). A holiday takes the whole working day off the capacity of everybody in the user's Workload. A Pro feature. Input parameters: - `from` (string): Only holidays on or after this day, YYYY-MM-DD. - `to` (string): Only holidays on or before this day, YYYY-MM-DD. ### `add_holiday` (~102 tokens) Add holiday Adds a holiday to the user's calendar: one per day, with a name of up to 80 characters. That day holds no work for anybody in the user's Workload, so every person's capacity for that week is one working day lower; a holiday on a Saturday or a Sunday changes nothing. A Pro feature. Input parameters: - `day` (string, required): The day, YYYY-MM-DD. - `name` (string, required): Up to 80 characters, for example Independence Day. ### `remove_holiday` (~97 tokens) Remove holiday Removes a holiday from the user's calendar: that day counts as a working day again in everybody's capacity. Needs confirm: true; without it the result is a preview. A Pro feature. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `holidayId` (string, required): A holiday of the user's calendar. ### `list_time_off` (~253 tokens) List time off Lists time off (vacation, sick leave, other), soonest first (up to 500): the user's own and, on Pro, that of the editors of the projects the user owns. Each has the person, the kind, the first and last day, the minutes off each day (null is the whole working day), the number of days and its status: pending (asked for and waiting for an owner of the person's projects), approved (it lowers the capacity) or rejected, with who decided, when and their note, and whether the user can approve or reject it. The person's own note comes only with the user's own time off. Person names and notes are typed by people. Optionally one person's, one status, or what overlaps a range of days. Input parameters: - `from` (string): Only time off that reaches this day or later, YYYY-MM-DD. - `status` (string): Only time off in this status (pending: waiting for approval). - `to` (string): Only time off that starts on or before this day, YYYY-MM-DD. - `userId` (string): Only this person's time off: the user's own or an editor of one of the user's projects (Pro). ### `add_time_off` (~323 tokens) Add time off Records time off for the user or, on Pro, for an editor of a project the user owns: a vacation, sick leave or other, from a first day to a last day (a single day when no last day is given), for the whole working day or a number of minutes of each. Once approved it lowers that person's capacity in the Workload for the weeks it touches (Monday to Friday count). The user's own time off is a request (status pending, and those owners get a notification) when an owner of a project the user edits plans with the team calendar, and approved at once otherwise; time off recorded for an editor is approved. A span is at most 366 days. The note belongs to the person: only they can write it, so it is refused when the time off is for somebody else. Input parameters: - `endDay` (string): The last day off. Default: the first day, YYYY-MM-DD. - `kind` (string): vacation, sick or other. Default vacation. - `minutesPerDay` (integer|null): Minutes off each day (240 is half a working day), between 1 and the person's working day. null or missing: the whole working day. - `note` (string): Up to 300 characters. Only the person writes it and only they read it back. - `startDay` (string, required): The first day off, YYYY-MM-DD. - `userId` (string): Whose time off it is: the user (default) or an editor of one of the user's projects (Pro). ### `update_time_off` (~255 tokens) Update time off Changes the kind, the days, the minutes off each day or the note of a time off; what is not given stays as it was, and null minutes make it the whole working day again. A person changes their own (changing the kind, the days or the minutes of an approved or rejected one asks the owners for approval again); on Pro, the owner of a project changes the time off of its editors (the note stays the person's). The whole result is checked again: at most 366 days, ending on or after the first day. Input parameters: - `endDay` (string): The last day off, YYYY-MM-DD. - `kind` (string): vacation, sick or other. Default vacation. - `minutesPerDay` (integer|null): Minutes off each day (240 is half a working day), between 1 and the person's working day. null or missing: the whole working day. - `note` (string): Up to 300 characters. Only the person writes it and only they read it back. - `startDay` (string): The first day off, YYYY-MM-DD. - `timeOffId` (string, required): A time off of the user or of an editor of one of the user's projects. ### `remove_time_off` (~116 tokens) Remove time off Deletes a time off (the user's own, or on Pro one of an editor of the user's projects): those days count as working days again in the Workload. Needs confirm: true; without it the result is a preview. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `timeOffId` (string, required): A time off of the user or of an editor of one of the user's projects. ### `approve_time_off` (~155 tokens) Approve time off Approves a time off an editor of a project the user owns asked for: from then on it lowers that person's capacity in the Workload, and the person gets a notification. A Pro feature (the team calendar). Needs confirm: true; without it the result is a preview. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `note` (string): Up to 300 characters for the person (why it was rejected). The person and the owners read it. - `timeOffId` (string, required): A time off of the user or of an editor of one of the user's projects. ### `reject_time_off` (~161 tokens) Reject time off Rejects a time off an editor of a project the user owns asked for, or one approved before: it no longer lowers that person's capacity. The note is read by the person, who gets a notification. A Pro feature (the team calendar). Needs confirm: true; without it the result is a preview. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `note` (string): Up to 300 characters for the person (why it was rejected). The person and the owners read it. - `timeOffId` (string, required): A time off of the user or of an editor of one of the user's projects. ### `get_time_rules` (~199 tokens) Get time rules Reads the rules that close logged hours. Without boardId: the rules the user has set for the projects they own: lockedUntil (the last closed day: nobody, the owner included, can add, edit, move or delete hours dated on or before it, and a timer cannot start while it reaches today) and editWindowDays (how many days back people other than the owner can fix their own hours; 0 = only today; null = no limit), with today in the user's time zone and whether the plan lets them set rules. With boardId: the rules that govern that project, from where the user stands (any member can read them): whether the user owns it, the earliest day the window lets them change, and whether a timer can start there today. Closed days refuse writes with the code `closed`. Input parameters: - `boardId` (string): A project the user belongs to. Omit it for the user's own rules. ### `set_time_rules` (~268 tokens) Set time rules Sets the rules that close logged hours on all the projects the user owns, which change what every person on them can do: lockedUntil, a day (YYYY-MM-DD, up to today) closes every day on or before it for everybody, the user included, until the date is changed; editWindowDays, a whole number of days (0 to 366), limits how far back people other than the user can fix their own hours (0 = only today). null clears a rule; a field left out stays. Setting rules is a Pro feature; turning them off is allowed on every plan, and rules already set keep protecting the hours if the plan lapses. Needs confirm: true; without it the result is a preview that says how many hours get frozen. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `editWindowDays` (integer|null): Days back that people other than the owner can still change their hours (0 to 366; 0 = only today); null = no limit. - `lockedUntil` (string|null): The last day that is closed, YYYY-MM-DD, not later than today; null reopens everything. ### `get_timer_alert` (~63 tokens) Get timer alert Reads the user's alert for a timer left running: how many hours a timer may run before Decknote sends a notification (and a push to their devices), once per timer; 0 means off. The default is 8 hours. It does not stop the timer. ### `set_timer_alert` (~99 tokens) Set timer alert Sets after how many hours a running timer sends the user a notification (and a push to their devices), once per timer: 0 turns it off; otherwise between 0.5 and 24 hours (the Time page offers 4, 8, 10 and 12). It only tells the user: the timer keeps running. Available on every plan. Input parameters: - `hours` (number, required): Hours before the alert; 0 = off. ### `list_timesheets` (~224 tokens) List weeks under review Lists the weeks of hours handed in for approval, newest week first (up to 100 of each): toReview, the weeks the people on the user's projects submitted to the user, and mine, the weeks the user submitted to the owners of the projects they work on. Each week has its status (submitted: waiting; approved; rejected: open again), the hours when it was submitted and now, the owner's note, and the hours by project and task for each day from Monday to Sunday. While a week is submitted or approved its hours are closed to the person who submitted it; the project owner can still change them. Names, titles and notes are typed by other people. Input parameters: - `from` (string): Only weeks that start on or after the week of this day, YYYY-MM-DD. - `status` (string): Only weeks in this status. Default: all. - `to` (string): Only weeks that start on or before this day, YYYY-MM-DD. - `userId` (string): Only this person's weeks, among those handed to the user. ### `submit_timesheet` (~239 tokens) Submit a week for approval Hands in the user's week of hours (give any day of it; weeks run Monday to Sunday) for approval to each owner of the projects the user logged hours on that week, or only to ownerId. From then on the user cannot add, change or delete their hours of that week on those projects until the owner rejects it or the user withdraws it, and an approved week stays closed. A week can be submitted from its Monday on, a timer running in that week has to be stopped first, and a week already submitted or approved stays as it is. Each owner gets a notification. The owner's plan has to include it (Pro). Needs confirm: true; without it the result is a preview with the hours for each owner. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `ownerId` (string): Only to this owner (one of the owners of the projects the user logged hours on that week). - `week` (string, required): Any day of the week to submit, YYYY-MM-DD. ### `withdraw_timesheet` (~76 tokens) Withdraw a submitted week Takes back a week the user submitted that is still waiting for approval: its hours can be changed again and the week can be submitted again later. An approved week can only be reopened by the project owner. Input parameters: - `timesheetId` (string, required): A week handed in for approval (the user's own, or one handed to the user). ### `approve_timesheet` (~170 tokens) Approve a week of hours Approves a week of hours a person on the user's projects submitted for approval: its hours stay closed to that person (the user, as the project owner, can still change them) and the person gets a notification. A rejected week has to be submitted again first. A Pro feature. Needs confirm: true; without it the result is a preview with the week's hours by project and task. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `note` (string): Up to 500 characters, sent to the person with the notification. - `timesheetId` (string, required): A week handed in for approval (the user's own, or one handed to the user). ### `reject_timesheet` (~158 tokens) Reject a week of hours Sends back a week of hours a person submitted to the user, or reopens one the user approved: its hours open again for that person, who can change them and submit the week again. The note goes to the person with the notification. Available on every plan. Needs confirm: true; without it the result is a preview. Input parameters: - `confirm` (boolean): true performs the action. Without it (or with any value other than the boolean true) nothing changes and the result is a preview of the effects. - `note` (string): Up to 500 characters, sent to the person with the notification. - `timesheetId` (string, required): A week handed in for approval (the user's own, or one handed to the user). ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-decknote-decknote/api-v1-mcp#diagnostics ## Score history - 2026-11-05: 87 - 2026-11-04: 86 - 2026-11-03: 86 - 2026-11-02: 85 - 2026-11-01: 85 - 2026-10-31: 85 - 2026-10-30: 84 - 2026-10-29: 84 - 2026-10-28: 83 - 2026-10-27: 83 - 2026-10-26: 82 - 2026-10-25: 82 - 2026-10-24: 81 - 2026-10-23: 81 - 2026-10-22: 80 - 2026-10-21: 80 - 2026-10-20: 79 - 2026-10-19: 78 - 2026-10-18: 77 - 2026-10-17: 77 - 2026-10-16: 76 - 2026-10-15: 76 - 2026-10-14: 75 - 2026-10-13: 71 - 2026-10-12: 72 ## Common questions ### What is the Decknote MCP server? Decknote is an MCP server listed in the public MCP registry as app.decknote/decknote. Kanban boards your AI agent can use: add, complete, move and recall tasks with your team. This page covers its hosted endpoint (https://decknote.app/api/v1/mcp). ### Is the Decknote MCP server safe to use? Decknote scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm. ### What tools does the Decknote MCP server expose? Decknote exposes 211 tools: overview, list_boards, create_board, create_list, search_tasks, and 206 more. Their descriptions and schemas cost roughly 27,349 tokens of context every time the server is loaded. ### Does the Decknote MCP server require authentication? Yes. Decknote asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything. ### Is the Decknote MCP server still maintained? Decknote is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ## Links - Remote endpoint: https://decknote.app/api/v1/mcp - Authorisation metadata: https://decknote.app/.well-known/oauth-protected-resource/api/v1/mcp - Website: https://decknote.app/for-ai-agents - Changelog RSS feed: https://verifymcp.io/servers/app-decknote-decknote/api-v1-mcp.xml - Changelog JSON feed: https://verifymcp.io/servers/app-decknote-decknote/api-v1-mcp.json - HTML version of this page: https://verifymcp.io/servers/app-decknote-decknote/api-v1-mcp