Standup MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STANDUP_URL | Yes | The Standup server URL, for example https://thestandup.app. | |
| STANDUP_API_KEY | Yes | Your Standup API key. It starts with sk- and is created from the Standup API Keys page. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_boardsB | List all boards with name and column summary |
| 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. |
| get_boardB | Get a full board with columns, cards, context, and agents |
| 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. |
| create_cardC | Create a new card in a column |
| update_cardB | Update card text. Automatically finds the column containing the card. |
| delete_cardB | Delete a card. Automatically finds the column containing the card. |
| move_cardB | Move a card to a different column. Automatically finds the source column. |
| assign_cardA | Assign a user or agent to a card. Adds to existing assignees without duplicates. Column agents are assigned as agent:. |
| unassign_cardB | Remove a user or agent from a card. |
| search_cardsB | Search for cards across all boards by text content |
| get_commentsC | Get all comments on a card |
| add_commentB | Add a comment to a card, with optional @mentions and clickable option buttons |
| update_board_contextA | Set a board's project context (markdown) and/or repository URL. Omitted fields are left unchanged. |
| 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. |
| 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. |
| add_columnB | Add an empty column to a board |
| rename_columnC | Rename a column |
| reorder_columnB | Move a column to a new position on its board, keeping its cards |
| delete_columnA | Delete a column. Refused while it has cards, unless deleteCards is true, which permanently deletes them too. |
| add_stickerB | Add a sticker (an emoji) to a card. Automatically finds the column containing the card. |
| remove_stickerB | Remove a sticker from a card. If the card has the same sticker more than once, one is removed. |
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 23 tools
Each tool targets a distinct resource and action (board, column, card, comment, sticker, attachment, work, agents) with no overlapping purposes. Descriptions clearly differentiate similar-sounding tools like get_board vs get_board_summary and update_card vs set_card_work.
All names follow a snake_case verb_noun pattern, but verb choices are slightly inconsistent: create_board/create_card use 'create' while add_column/add_sticker/add_comment use 'add', and set_card_work uses 'set' while other metadata updates use 'update'.
23 tools is on the heavy side for a board management server; while the domain is complex, several tools could potentially be consolidated (e.g., sticker add/remove into a single update). It sits in the borderline 16–25 range.
Core board, column, and card CRUD is largely covered, but there are notable gaps: comments support create+get but no update/delete, boards lack delete/rename, and attachments only support get with no way to add or remove them.