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 |
| get_boardB | Get a full board with columns, cards, context, and agents |
| 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. |
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 14 tools
Each tool targets a distinct resource+action: card CRUD (create/update/move/delete), assignment pair (assign/unassign), comment pair (add/get), board reads (get/list), and specialized setters (set_card_work, update_board_context, update_column_agents). Descriptions clarify boundaries where concepts could touch, e.g. update_card only edits text while move_card changes columns. No two tools appear to do the same thing.
Every tool follows a clean verb_noun snake_case pattern: get_board, list_boards, create_card, update_card, delete_card, move_card, add_comment, get_comments, assign_card, unassign_card, search_cards, set_card_work, update_board_context, update_column_agents. No convention mixing.
14 tools is well within the sweet spot for a kanban/standup server and each tool earns its place across card, comment, assignment, board, and work-tracking concerns. Nothing feels padded or redundant.
Card lifecycle is fully covered (create, update, move, delete, assign, unassign, comment, search) plus board context and work tracking. Minor gaps exist: no create_board/delete_board and no edit/delete for comments, but these are workable around and the core standup workflow is intact.