Create a kanban column in a project #6

New issue

Closed

opened 2026-08-09 19:52:39 -05:00 by mcp-gateway · 0 comments

mcp-gateway commented

2026-08-09 19:52:39 -05:00

Member

Filed from halfst/mpx-engine #120.

What's needed

A tool to create a column in a project. ticktick-list-columns exists for reading; there is no create.

Why

Sync Operating Spec §3 handles a missing column by degrading and flagging, explicitly because the MCP can't create one:

If the section has no column, use the default column and flag it (Ethan adds columns; MCP can't).

The People mirror's columns are its sections, and section: is Obsidian-owned — so the vault is the source of truth for a set that the engine cannot bring into existence. Adding a person in a new section means the card silently lands in the default column and waits for a manual fix.

There are currently eleven People columns against eight group notes in the vault, so the two sets already drift.

Acceptance

Create a column in a given project, with a name and optionally a position.
Returns the new column id, so the caller can place cards into it in the same run without a second lookup.
Creating a column whose name already exists in that project is rejected or returns the existing one — quietly creating a duplicate would split a section in two.

Priority

Lower than #1 and #4. The degrade-and-flag path is genuinely acceptable; this removes a manual step rather than unblocking anything.

Unblocks

Retires the §3 caveat and lets person-sync place a card in a brand-new section without human intervention.

Filed from `halfst/mpx-engine` #120. ## What's needed A tool to create a column in a project. `ticktick-list-columns` exists for reading; there is no create. ## Why `Sync Operating Spec` §3 handles a missing column by degrading and flagging, explicitly because the MCP can't create one: > If the section has no column, use the default column and flag it (**Ethan adds columns; MCP can't**). The People mirror's columns *are* its sections, and `section:` is Obsidian-owned — so the vault is the source of truth for a set that the engine cannot bring into existence. Adding a person in a new section means the card silently lands in the default column and waits for a manual fix. There are currently eleven People columns against eight group notes in the vault, so the two sets already drift. ## Acceptance - [ ] Create a column in a given project, with a name and optionally a position. - [ ] Returns the new column id, so the caller can place cards into it in the same run without a second lookup. - [ ] Creating a column whose name already exists in that project is rejected or returns the existing one — quietly creating a duplicate would split a section in two. ## Priority Lower than #1 and #4. The degrade-and-flag path is genuinely acceptable; this removes a manual step rather than unblocking anything. ## Unblocks Retires the §3 caveat and lets person-sync place a card in a brand-new section without human intervention.