Getting Things Done (GTD) board for AI agents: capture to Inbox, next actions by context, projects, waiting-for, someday/maybe. Remote Streamable HTTP server with OAuth 2.1 login (passwordless email code). 16 tools + 4 prompts. Setup guide: https://gtdbrain.com/connect?source=glama
Scored across 19 tools
Every tool has explicit use/do-not-use boundaries; capture vs create_card, archive_card vs move_card, get_card vs search_cards, and generic vs specialized list tools are all clearly distinguished. Overlaps are handled by descriptions directing agents to the preferred tool for each situation.
Names are all snake_case and mostly follow a verb_noun pattern such as create_card, update_context, list_projects, and move_card. Minor deviations exist: capture is verb-only and mark_card_reviewed uses a participle, but the overall convention remains predictable.
19 tools is slightly heavy for a GTD board but is justified by three resource families (cards, columns, contexts) plus specialized GTD list views and the full card lifecycle. No tool appears redundant, though some generic/specialized list tools could theoretically be consolidated.
Core card lifecycle is complete: capture, create, read, search, update, move, archive/restore, review, plus context CRUD and specialized lists. The notable gap is column management: list_columns and update_column exist, but there is no create_column or delete_column, so custom column lifecycle is only partially exposed.
Use this when the user says a card is done, finished, or no longer needed and the board has no Done (or Completed) column — check list_columns first: if there is one, move_card the card there instead. Archiving hides the card from the board; restore_card brings it back, and there is no delete. Tell the user the card was archived. Do not use to clear the board in bulk — archive only the cards the user named. Do not use when they just want the card somewhere else or changed (move_card, update_card), and never archive a card because you made a replacement for it. Returns the archived card.
Inputs: cardId (required).
Use this when the user mentions something they need to do, remember, buy, or follow up on and does not say which list it belongs to: it goes straight to the Inbox in one step, no column lookup (capture first, clarify later). Examples: 'remind me to renew my passport', 'add call the dentist', 'note: look into solar panels'. Do not use when the user names a destination list (Next Actions, Projects, Waiting For, Someday/Maybe, a custom column) or a card kind — use create_card. Do not use to change, move, or finish an existing card, and do not use for something the user says they already did ('Added the invoice', 'called Sam') — that completes an existing card: find it with search_cards and finish it. Returns the created card.
Inputs: title (required), notes, context.
Use this when the user says where a card belongs or what it is: a next action ('add a next action: email Sam the quote'), a project's next step (pass projectId), a project ('new project: plan the offsite'), something they are waiting on someone for, a Someday/Maybe idea, something to keep for reference that needs no action (the Reference column), or a card for a named custom column. Needs the destination columnId from list_columns; kind 'action' only in Next Actions, 'project' only in Projects, 'card' anywhere else. Do not use for a bare 'add / remind me / note' with no list named — use capture (Inbox, no lookup). Do not use for a card that is already on the board ('put the blog post under my launch project', 'make the passport card a next action') — find it with search_cards and move_card or update_card it; a new card plus archive_card on the old one loses its history. Returns the created card.
Inputs: title (required), columnId (required), who, kind, +4 more.
Use this when the user wants a new GTD context — a place, tool, or situation to tag actions with, e.g. '@boat', 'errands', 'deep work'. The id is derived from the label and must not already exist; color is optional (hex like #4f9466, auto-picked otherwise). Do not use when a matching context already exists (check list_contexts), and do not use to tag a card — use update_card with the existing id.
Inputs: label (required), color.
Use this when the user explicitly wants a context removed from their set. Every card tagged with it (archived included) has its context cleared, so confirm before calling. Do not use to take a context off one card — use update_card with an empty context.
Inputs: contextId (required).
Use this when you already have a card id (from a list, a search, or an earlier result) and the user wants that card's full details — notes, context, who it is waiting on and since when — or asks what happened to it: its history lists, oldest first, when it was created, moved between lists, edited, reviewed, archived or restored. Do not use to find a card by text — use search_cards.
Inputs: cardId (required).
Use this when you need cards as plain data to reason over — every card in one column, all cards of one kind, all actions in one context, or a project's actions. Filters combine; archived cards only with includeArchived. For the three main lists prefer list_next_actions, list_projects, and list_waiting_for. Do not use to find a card by words in its title — use search_cards.
Inputs: kind, context, columnId, projectId, +1 more.
Use this when you need a column id — for create_card, move_card, or list_cards — when the user asks which lists their board has, or how many cards a list holds ('how many are in my inbox?'). Returns every column (Inbox, Next Actions, Projects, Waiting For, Someday/Maybe, Reference, and any custom ones) with id, label, kind, order, and cardCount, the number of cards on the board in it (archived cards not included). Do not use to tell the user what is on the board: it carries no cards — use list_cards or the list tools.
Inputs: no named parameters.
Use this when you need the user's context ids — before passing a context to list_next_actions, list_cards, create_card, or update_card — or when the user asks which contexts they have. Returns id, label, color, and order. Do not guess a context id: the set is user-defined and an unknown id is rejected.
Inputs: no named parameters.
Use this when the user asks what to do now, what they can work on, or for their next actions or to-do list — optionally narrowed to a GTD context when they say where they are or what they have ('I'm at my desk', 'what can I do on the phone?'). Lists the Next Actions column (each card with context and project), in board order. Do not use for projects (list_projects), things delegated to others (list_waiting_for), the Inbox or other columns (list_cards), or to find one specific card (search_cards).
Inputs: context.
Use this when the user asks about their projects, their open outcomes, or which projects have no next action yet. Lists the Projects column in board order; a project is any outcome that needs more than one step. Do not use for single tasks (list_next_actions) or to add a project (create_card).
Inputs: no named parameters.
Use this when the user asks who they are waiting on, what they have delegated, or what to follow up on with other people. Lists the Waiting For column in board order, each card with who it is delegated to and since when. Do not use for the user's own tasks (list_next_actions).
Inputs: no named parameters.
Use this during a weekly review when the user keeps a card as it is ('keep', 'still relevant', 'reviewed, leave it'): it stays in its list and counts as reviewed now. Do not use when the card should change — move_card, update_card, or archive_card it instead. Returns the card.
Inputs: cardId (required).
Use this when the user wants a card in a different column — clarifying an Inbox item into Next Actions, Projects, Waiting For, Someday/Maybe, or Reference (worth keeping, no action), or into one of their own columns (a Done or Completed column, say) — or reordered within its column. 'Move it to done' means move_card into the user's column with that label (find it with list_columns), never archive_card. The card's kind follows the destination (Next Actions → action, Projects → project, normal columns → note, flexible columns keep it). Set the card's context, project, or who/since in the same call: clarifying or re-filing a card is one move_card on that card, never a new card plus archive_card on the old one. Do not use to only edit a card's text or tags — use update_card. Rejected for an archived card — use restore_card. Returns the moved card.
Inputs: cardId (required), toColumnId (required), who, since, +3 more.
Use this when the user wants an archived card back on the board: 'unarchive', 'restore', 'bring back', 'undo the archive'. Find the card with search_cards and includeArchived=true. By default it returns to the column it was archived from (Inbox if that column is gone); pass toColumnId to put it somewhere else, e.g. Next Actions. Do not use move_card on an archived card — it is rejected. Returns the restored card.
Inputs: cardId (required), toColumnId.
Use this when the user refers to a card by words from its title or notes ('the passport thing', 'my note about solar') and you need its id or details, or asks whether something is already on the board. Case-insensitive match over title and notes: every word of the query must appear, in any order, so leave out words you are unsure of ('testing agent' finds 'testing from the agent'); archived cards only with includeArchived. Do not use to list a whole column — use the list tools or list_cards.
Inputs: query (required), includeArchived.
Use this when the user wants to change what a card says or how it is tagged: retitle it, edit its notes, set or clear its context, link an action to a project or unlink it, or change who it is waiting on and since when. Only the fields passed change; an empty string clears a field. Do not use to put a card in another column or reorder it — use move_card, which takes these same fields. Do not use to finish or remove a card — use archive_card. Returns the updated card.
Inputs: cardId (required), who, notes, since, +3 more.
Use this when the user wants to rename one of their own columns or put a column in a different position on the board ('move Done to the end', 'rename my Errands column to Shopping'). Only columns the user added can be renamed — Inbox, Next Actions, Projects, Waiting For, Someday/Maybe, and Reference keep their names — and no plain column can move ahead of the Inbox. Do not use to move cards — use move_card. Returns the column.
Inputs: columnId (required), label, toIndex.
Use this when the user wants to rename or recolor one of their contexts. The id never changes, so cards keep their assignment. Do not use to change which context a card carries — use update_card.
Inputs: contextId (required), color, label.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Task & board management for AI agents + humans. Kanban, comments, digests via MCP.
One board for you and your AI: hand tasks to ChatGPT, Claude, Cursor or Codex and get a report back.
Kanban boards your AI agent can use: add, complete, move and recall tasks with your team.
Shared to-do memory for AI assistants: flows, tasks, inbox, meeting notes. Claim and hand off tasks.
Add one secure layer between your agents and this server.
