Skip to main content
Glama

Standup MCP Server

An MCP server that connects AI coding agents (Claude Code, etc.) to Standup — a kanban board app. Once connected, the agent can list boards, read and create cards, move cards between columns, manage assignees, and post comments, all through natural conversation.

Prerequisites

  • A Standup account with a Pro or Enterprise membership (required for API keys)

  • Node.js 18+

  • An MCP-compatible client (e.g. Claude Code)

Related MCP server: ClickDown

Setup

1. Create an API key in Standup

  1. Go to thestandup.app and log in

  2. Click the user menu (top-right) → API Keys

  3. Give your key a name (e.g. "Claude Code") and click Create

  4. Copy the key — it starts with sk- and is only shown once

2. Configure your MCP client

Claude Code

Run the following command, replacing sk-your-api-key-here with your API key from step 1:

claude mcp add standup \
  -e STANDUP_URL=https://www.thestandup.app \
  -e STANDUP_API_KEY=sk-your-api-key-here \
  -- npx -y thestandup-mcp

Then restart Claude Code for the server to connect.

Other MCP clients

The server uses stdio transport — any MCP client that can launch a subprocess will work. Set the STANDUP_URL and STANDUP_API_KEY environment variables and run:

npx -y thestandup-mcp

3. Verify the connection

Start a new Claude Code session and ask it to list your boards:

"List my standup boards"

You should see your boards returned. If you get an authentication error, double-check your API key.

Available tools

Tool

Description

list_boards

List all boards with name and column summary

create_board

Create a board from a template (blank or ai-software-development), with optional context and repository

get_board

Get a full board with columns, cards, context, and agents

get_board_summary

Compact board: columns with agents and one row per card (first line, assignees, stickers, work, comment count, last comment author and time), no comment bodies

create_card

Create a new card in a column

update_card

Update card text

delete_card

Delete a card

move_card

Move a card to a different column

assign_card

Assign a user, or a column agent as agent:<identifier>, to a card

unassign_card

Remove a user or column agent from a card

search_cards

Search for cards across all boards by text content

get_comments

Get all comments on a card

add_comment

Post a comment on a card (supports markdown, @mentions, clickable option buttons, and attribution to a column agent via agentId)

update_board_context

Set a board's project context and/or repository URL

update_column_agents

Replace a column's agents (send the full list)

set_card_work

Record where a card's work lives (repo path, branch, commits, pushed, PR link); merges with what's already recorded

Example usage

Once connected, you can interact with your boards in natural language:

  • "What's on my standup board?"

  • "Create a card in the To Do column: Refactor the auth middleware"

  • "Move the auth refactor card to In Progress"

  • "Add a comment to that card: Started work, estimating 2 hours"

  • "Assign me to the top card in In Progress"

Workflow conventions

The server includes built-in instructions that guide the AI agent to follow these conventions:

  • Assignment: each column agent assigns itself as agent:<identifier>; agents in the same column work in parallel

  • Priorities: resume cards handed back after a person replied, then take unfinished cards nobody is assigned to

  • Progress updates: add a comment (attributed with agentId) summarising what you did before unassigning, and record where code changes live with set_card_work (shown on the card)

  • Blockers: post a comment with clickable options, @mention the user and assign the card to them in place. Standup hands it back to the agent when they answer

  • Handed-back note: tool responses include a "Handed back to you" note while a card is waiting to be resumed

  • Pipeline flow: advance cards left-to-right through columns; reject by moving back with a comment

  • Running the pipeline: when asked to process a board, carry each card on through every agent column rather than stopping after one stage; board context is optional

  • Instruction length: Claude Code truncates server instructions at 4,096 characters, so a test keeps them under that limit

Keeping agents running

Agents only act while a session is running; Standup cannot start one. A card you hand back by replying or reassigning waits until a session next looks at the board. To have it picked up without asking, keep a session polling:

  • Claude Code: /loop 15m process the <board name> board

  • Other agents: a scheduler or cron job that starts the agent with the same prompt

Development

npm install
npm run build       # compile TypeScript
npm test            # run tests
npm run test:watch  # run tests in watch mode
npm run all         # type-check + test

License

MIT

Available Tools

23 tools
add_columnB

Add an empty column to a board

Inputs: name (required), boardId (required), index.

add_commentB

Add a comment to a card, with optional @mentions and clickable option buttons

Inputs: text (required), cardId (required), boardId (required), agentId, +2 more.

add_stickerB

Add a sticker (an emoji) to a card. Automatically finds the column containing the card.

Inputs: cardId (required), boardId (required), sticker (required).

assign_cardA

Assign a user or agent to a card. Adds to existing assignees without duplicates. Column agents are assigned as agent:.

Inputs: cardId (required), boardId (required), assignee (required).

create_boardA

Create a board you own from a template: blank (Todo, In Progress, Done) or ai-software-development (Inbox, Triage, In Progress, Code Review, Testing, Done, with the default agents). Returns the new board with its column and agent identifiers.

Inputs: name (required), context, template, repository.

create_cardC

Create a new card in a column

Inputs: text (required), boardId (required), columnId (required).

delete_cardB

Delete a card. Automatically finds the column containing the card.

Inputs: cardId (required), boardId (required).

delete_columnA

Delete a column. Refused while it has cards, unless deleteCards is true, which permanently deletes them too.

Inputs: boardId (required), columnId (required), deleteCards.

get_attachmentA

Get a file attached to a card, using the fileId from the card's attachments in get_board. Images are returned so you can see them.

Inputs: cardId (required), fileId (required), boardId (required).

get_boardB

Get a full board with columns, cards, context, and agents

Inputs: boardId (required).

get_board_summaryA

Get a compact board: name, context, repository, columns with agents, and one row per card in every column with its first line, assignees, stickers, work, comment count and last comment author, agentId and time. No comment bodies: use get_comments or get_board for full content.

Inputs: boardId (required).

get_commentsB

Get all comments on a card. A deleted comment keeps its place, author and time, with empty text and a deletedAt time.

Inputs: cardId (required), boardId (required).

list_boardsB

List all boards with name and column summary

Inputs: no named parameters.

move_cardB

Move a card to a different column. Automatically finds the source column.

Inputs: cardId (required), boardId (required), toColumnId (required), index.

remove_stickerB

Remove a sticker from a card. If the card has the same sticker more than once, one is removed.

Inputs: cardId (required), boardId (required), sticker (required).

rename_columnC

Rename a column

Inputs: name (required), boardId (required), columnId (required).

reorder_columnB

Move a column to a new position on its board, keeping its cards

Inputs: index (required), boardId (required), columnId (required).

search_cardsB

Search for cards across all boards by text content

Inputs: query (required).

set_card_workA

Record where the work for a card lives: repository path, branch, commits, whether it was pushed and the pull request link. Merges with what is already recorded: new commits are added and fields you leave out are kept.

Inputs: cardId (required), boardId (required), branch, pushed, +3 more.

unassign_cardB

Remove a user or agent from a card.

Inputs: cardId (required), boardId (required), assignee (required).

update_board_contextA

Set a board's project context (markdown) and/or repository URL. Omitted fields are left unchanged.

Inputs: boardId (required), context, repository.

update_cardB

Update card text. Automatically finds the column containing the card.

Inputs: text (required), cardId (required), boardId (required).

update_column_agentsA

Set the agents for a column. The list replaces the column's existing agents, so to change one agent send the full list from get_board with that agent edited. Keep each existing agent's identifier so its assignments and comments stay linked.

Inputs: agents (required), boardId (required), columnId (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 23 tools

    Disambiguation5/5

    Each tool targets a clearly distinct resource/action across boards, columns, cards, comments, stickers, attachments, assignments, and work metadata. Overlapping-looking tools like get_board vs get_board_summary and assign_card vs update_column_agents are clearly differentiated by target scope.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern, including compound nouns such as get_board_summary, update_board_context, update_column_agents, and set_card_work. There is no mixing of camelCase or vague standalone verbs.

    Tool Count4/5

    23 tools is on the high side, but the domain is broad and most operations correspond to a real board-management need. A few retrieval or sticker/comment operations could potentially be consolidated, but the set remains reasonably scoped rather than bloated.

    Completeness3/5

    Core card and column lifecycle operations are well covered, including move, assign, reorder, and work tracking. However, board deletion/rename, comment editing/deletion, and attachment creation/deletion are missing, and get_attachment implies attachments can exist without a corresponding tool to add them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to manage kanban boards with tasks, including creating boards, items, moving between columns, and searching.
      8
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to read and write a local kanban board, adding and editing cards, moving them between columns, managing projects, and writing update entries so their work is visible in real time.
      6 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to operate a Kanban board through MCP tools: taking and moving cards, updating statuses, splitting subtasks, linking pull requests, and pausing for human approval that only people can grant.
      126 npm
      PolyForm Noncommercial 1.0.0