Changelog
What changed on the Koma MCP server, newest first. A client that connected before a change keeps the tool list it fetched; refresh the connector and start a new conversation to see new tools.
2026-10-13
- Lists and items replace tasks, notes, projects and collections as separate shapes. A list is the one container: the Tasks list and the Notes list every account has, and any list the person keeps; a former project and a former collection are lists under their old ids. An item is the one thing on a list, a former task, note or row under its old id, with a title, a body as Markdown and a value per property of its list; a list made for tasks keeps a status and a due date on its items. Concepts.
- One tool family replaces the four:
list_lists,create_list,update_listanddelete_listover lists;list_items,get_item,query_items,create_items,update_items,move_itemsanddelete_itemsover items. Retired, with no alias:list_tasks,get_task,get_task_context,create_task,create_tasks,update_task,delete_task,list_notes,get_note,create_note,update_note,delete_note,list_projects,create_project,update_project,list_collections,create_collection,update_collection,delete_collection,get_collection_items,get_collection_item,add_collection_items,update_collection_itemsanddelete_collection_items.get_context,search,create_image_upload, the chat tools, the trash tools and the automation tools keep their names;get_contextnames lists and takesfocusListId,searchanswers items and lists, andlist_deletedandrestore_deletedtake the typesitemandlist. Tools. - A
listIdis a list's id, or the wordtasksfor the Tasks list andnotesfor the Notes list.projectIdis gone: an item's list is itslistId, and moving one ismove_items, which answers a preview of what a lossy move would drop before it moves anything.priorityis gone from every shape. - Bodies are edited by block handle on every item, whatever its list:
get_itemreturns the body with a handle in front of every block andupdate_itemstakeseditsper item. The olderbodyplusmodestill works. - On the REST API the routes follow:
/lists,/items,POST /items/query,POST /items/move,/items/{id}and/items/{id}/messagesreplace/tasks,/tasks/batch,/notes,/projects,/collectionsand their rows, with no redirects.POST /quick-addis gone:POST /itemswithlistId: "tasks"andenrich: truedoes what it did. REST API. - A standing order or paste-in prompt that names a retired tool needs the new name; a client that connected before this change keeps the tool list it fetched until the connector is refreshed.
- A changes feed for workers.
list_itemstakeschangedSince: every item of a list, or of the Tasks set, whose record moved after that instant, oldest change first, with the deleted ones asdeletedtombstones,hasMore, andnextChangedSinceto pass next time. A worker that polls makes one call per cycle instead of re-reading the list. On the REST API:GET /items?changedSince=…. Run a worker loop. - The tool descriptions, the server instructions and the skill say when to pass a cursor:
changedSinceonlist_items,updatedAfteronquery_items,sinceonread_chat_messages.
2026-10-02
create_tasksis new: up to 100 tasks in one call, the way to hand Koma a list of outstanding work. The tasks are stored as written and indexed for search; no AI pass runs unlessenrichis true. A row'sexternalIdmakes re-sending safe: the same id returns the task already made underexistinginstead of a duplicate, and one bad row never fails the batch. On the REST API it wasPOST /tasks/batch; its successor iscreate_items. Tools.- The overview and llms-full.txt open with one paragraph to paste into any agent: the address, the sign-in, the docs and the first call.
- After you approve an app whose callback is on your own computer, a Koma page confirms the connection before taking you back, with the link to copy if your agent runs in the cloud and the callback page does not load.
2026-09-30
- A REST API at
/api/v1: the MCP server's operations over plain HTTP for Zapier, Make, n8n and scripts, withPOST /quick-addand an OpenAPI document at/api/v1/openapi.json. REST API. - API keys beside OAuth: a person creates a
koma_key under Settings, then Connections, and an agent without a browser sends it as a bearer token. Creating a new key replaces the old one; revocable at any time. Authentication. - These developer docs. Every page is also Markdown (add
.mdto its address) and listed in llms.txt. - The tool reference is generated from the server's live registration.
2026-09-23
- Writes made through MCP are recorded in the person's event log as their own actions, marked as coming through the connection. Before this they read as system activity.
2026-09-18
get_contextreplacesget_hub. One call returns the person, today in their timezone, memory (read-only), projects, what is due, unsorted tasks, recent notes, collections with columns, automations with their last run and three days of activity.create_projectandupdate_projectare new.update_taskacceptsprojectIdto move a task;nullmoves it to unsorted.list_automations,get_automation_runsandrun_automationare new.- Every tool states all three of
readOnlyHint,destructiveHintandopenWorldHintexplicitly, and carries a title. update_taskretries once on a write conflict with a background pass, so an edit right after a create lands.
2026-09-04
list_tasksandlist_notesgain time windows (createdAfter,updatedAfter,completedAfterand their upper bounds) and asortparameter.
2026-08-14
create_image_uploadis new: pre-signed slots for raw image bytes, for rows whose images come from a source without a stable URL.- Row tools report every image that could not be ingested, per URL and with a reason.
2026-08-13
- Collections have full create, update and delete. The trash covers collections and rows.
list_deletedandrestore_deletedare new: every soft delete is now recoverable from a client.
2026-08-05
- Collections are on the server:
list_collections,get_collection_items,add_collection_items,update_collection_items.
2026-06-29
- Notes and search:
search,get_note,list_notes,create_note,update_note. - Soft deletes:
delete_task,delete_note. - Every tool carries annotations and an output schema; results return both text and structured content.
- Tokens are verified locally; a rate limit of 60 requests a minute per token.
2026-06
- First release: tasks and projects over OAuth 2.1 at
https://koma.ac/api-preview/mcp.