The TaskDeck MCP server

Identify the TaskDeck account this connection is acting as, and whether it acts as the person who authorized it (their full access) or as a restricted AI agent account.

List every TaskDeck project and board this account can see, with each board's columns (the Closed column marked system: "closed"), open card count and last activity.

The plan this account is on, its limits and how much of them is used.

What this account did on its cards on a day or over a range of days, grouped by board — the material for a standup or a daily summary.

The activity feed: who did what, when, across the projects this account is in.

This account's notifications, newest first, with whether each has been read, and how many are unread in all.

Mark one notification read, or all of them when no id is given.

Delete one notification, or every notification of this account when no id is given.

This account's notification settings: which events notify it.

Turn one of this account's notification settings on or off.

Change this account's display name or interface language.

List the AI agents this account owns: id, name, whether suspended, the projects each is a member of, and how many live connections act as it.

Create an AI agent account owned by this account, optionally making it a member of projects right away (project ids from workspace-overview; only projects where you are more than a viewer).

Make one of your AI agents a member of more projects, so act_as can use it there.

Turn on Autotrack for a repository: every task the assistant does there becomes a card on one board.

Start a piece of work on a tracked board; call it before changing anything.

Finish a piece of work on a tracked board once it is verified: ticks the criteria you name as verified, posts the verification notes and links as a comment, and moves the card to the review column when the board has one and to the done column otherwise.

Only for an AI routine session, Claude Code or Codex, that TaskDeck handed a card to, when its run ends without finish-work: blocked, out of time, or unable to do the work.

Create a new TaskDeck project; this account becomes its admin.

Rename a project or change its description.

Delete a project with every board, column, card, comment and attachment in it.

List who is in a project, with their user id and role.

Invite people to a project by email, all with the same role.

Change a member's role in a project (admin, member or viewer), which of its boards they open, or both.

Remove a member from a project.

List the invitations a project has sent that have not been accepted yet.

Send a pending project invitation again.

Withdraw a pending project invitation so it can no longer be accepted.

List the project invitations waiting for this account: which project, which role, who sent it.

Accept a project invitation addressed to this account and join the project with the offered role.

Decline a project invitation addressed to this account.

The GitHub repositories and GitLab projects connected to a project, and the ones that could be connected: what the project's own GitHub connection sees, and what its GitLab connection may add webhooks to.

Connect GitHub repositories or GitLab projects to a project, by the repository ids list-repositories shows as available, one provider per call.

Disconnect a GitHub repository or GitLab project from its project, removing the webhook TaskDeck added on GitLab.

Create a board in a project, ready to hold cards.

Rename a board, change its description or its icon, change the prefix its card keys use, or change its rules for how cards started by an assistant are filled in (tags, tag_names, estimate, deadline, assignee, reporter, observer).

Delete a board with all of its columns and cards.

Add a column to the end of a board.

Rename a column, recolour it, move it after another column on the same board, set how many days cards wait in it before being archived, or give it a role in the board's flow (todo, doing, review or done; a role held by another column moves to this one).

Delete a column and every card in it.

Add an automation to a board: when a card moves from one of the from columns to one of the to columns and every condition holds, its actions run on the card in order, with the board's authority.

Change a board automation: rename it, switch it off or on, or rewrite its trigger columns, conditions or actions.

Put a board's automations in the order they should run: name every one of them once, first to run first.

Delete a board automation.

Show a board to the person: its columns with their counts and cards, who holds what, and any card opened in full.

Show a board's insights to the person: cards created and finished per day, how many are open, sent back, overdue or due within seven days, and the median hours cards spend in each column, over the last 30 days.

List the cards on a board, or in one column, in board order.

Search cards by title and description across every board this account can see, best match first.

Read one card in full: title, description as Markdown, column, board, assignee, reporter, observer, estimate, dates, tags, checklist (each item with its id and who checked it), what it is waiting for and what is waiting for it, its parent, children and related cards, attachments, comment count, the AI routine sessions (Claude Code or Codex) it was handed to, and the lock one of them holds on it.

Create a card on a board.

Change a card: retitle it, rewrite its description (Markdown, replacing the whole text — read-card first to keep what is there), assign it, set reporter, observer, estimate or dates, move it to another column on the same board, or place it after another card.

Close a card: move it into the board's Closed column, the system column for cards dropped without being done.

Reopen a closed card: move it out of the board's Closed column back into the column it was closed from, or into the first column when that one no longer exists.

Delete a card permanently, with its comments, notes and attachments.

List the tags already in use in a project, so you can reuse existing names rather than invent near-duplicates.

Tag a card.

Record that a card is waiting for another card on the same board.

Drop a dependency between two cards: the first card stops waiting for the second.

Ask for information required to continue a card, naming the member who must answer.

Answer a required question as its named respondent, including while an agent session holds the card.

Redirect an unanswered required question to another board member, or withdraw it when no longer needed.

Acknowledge received answers when resuming a card.

Link two cards of the same project, on the same board or different ones: make the other card this card's parent, one of its children, or a related card.

Remove the link between two cards, whichever it is: parent, child or related.

Detach a commit or pull request from a card, for a link whose target is gone.

Remove an attachment from a card.

Add items to the end of a card's checklist, in the order given: acceptance criteria, steps, anything that gets checked off.

Change one checklist item: check it off (done=true), reopen it (done=false) or reword it.

Remove an item from a card's checklist.

Read the discussion on a card: every comment in order, with who wrote it and when.

Comment on a card.

Rewrite one of this account's own comments.

Delete a comment.

Read this account's private notes on a card.

Add a private note to a card for this account only.

Rewrite one of this account's private notes.

Delete one of this account's private notes.

The sprints on a board: how the board runs them, the one it is working in, the one planned next, and the ones already finished.

How the sprint a board is working in is going: what is finished, what is left, how much time remains, and which cards are at risk — overdue, waiting on another card, or unassigned with the week nearly gone.

Plan a sprint on a board.

Change a sprint's name, goal, dates or capacity.

Start a planned sprint, so the board is working in it and new cards join it.

Close a sprint.

Put cards in a sprint, or take them out of every sprint and back into the backlog.

Propose a set of changes for a person to approve before any of them happen.

Check whether a proposed plan has been approved yet, and what happened to each step once it was.

List the plans AI agents have proposed and that are waiting for a person's review in this account's projects.

Read one proposed plan in full, whatever its status, including what happened to each step once it ran.

Approve a proposed plan and carry out its steps now, on behalf of the person who authorized this connection.

Turn down a proposed plan, optionally saying why so the agent can revise it.

Propose a card instead of creating it.

The proposals on a board: the open ones waiting for a decision, most supported first, or with status "decided" the ones accepted, dismissed or expired in the last 30 days, with the card each accepted one became.

Accept a proposal: it becomes a card in the board's todo column, or in column_id, assigned to whoever proposed it unless assigned_to says otherwise, reporting to the person accepting, and gets its key now.

Dismiss one proposal or many at once, with an optional reason that anyone proposing something similar later is shown.