scrumdo-mcp
OfficialThe scrumdo-mcp server provides an MCP interface connecting AI tools to ScrumDo project management boards, enabling comprehensive management through the following capabilities:
Board & Project Management
List boards, get board details (columns, custom fields, statistics), list iterations/sprints, labels, and epics
Card Operations
List, search, retrieve, create, update, move, archive cards
Move cards between columns or iterations, assign/unassign members, add/remove labels, set custom fields
Blockers
List active blockers, block cards with a reason (optionally as show-stopper or external dependency), unblock/resolve blockers
Tasks (Checklists)
List, create, update, complete, reopen, and delete tasks on cards
Comments
List, add (with Markdown support), and delete comments on cards
Custom Fields
List field definitions, get/set individual or all custom field values on cards
Members
List organization/project members, find by name, username, or email
Search
Full-text search across card summaries, descriptions, and comments; search by custom field value
Activity Logging
Log structured activity entries to cards; retrieve per-card or workspace-wide activity logs
Webhooks
List, create, and delete project webhooks
Time Tracking
List time entries (per card or project-wide), log time spent on a card
Spec Management
Get, set, and patch card specs; view spec history; check spec drift
GitHub Integration
List repos, link PRs/commits/issues to cards
Agent Runs & Loops
Start, get, list, approve, report progress on, and cancel agent runs
Start/pause/resume/cancel loops, manage verification loops, log loop steps, attach evidence
Intelligence Features
Velocity forecasts, spec complexity analysis, behavior contract verification
Provides tools for linking GitHub PRs, commits, and issues to ScrumDo cards, as well as listing GitHub repositories connected to the project.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@scrumdo-mcp What's the status of ENG-42?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
scrumdo-mcp
Connect any MCP-compatible AI tool (Claude Code, Cursor, Windsurf, and others) directly to your ScrumDo boards.
Once installed, your AI assistant can read cards, move them, create tasks, post comments, and search across your board — without you copy-pasting anything.
Installation
pip install scrumdo-mcpRelated MCP server: kanban-mcp
Cursor quick-start
1 — Install
# To run the server only:
pip install scrumdo-mcp
# To run tests too:
git clone https://github.com/ScrumDoLLC/scrumdo-mcp.git
cd scrumdo-mcp
pip install -e ".[dev]"
pytest tests/ -v2 — Get your token
Log in to ScrumDo → your org → Settings → API Tokens → Create Token. Copy it — shown once only.
3 — Add to ~/.cursor/mcp.json
{
"mcpServers": {
"scrumdo": {
"command": "scrumdo-mcp",
"env": {
"SCRUMDO_TOKEN": "your-token-here",
"SCRUMDO_ORG": "your-org-slug",
"SCRUMDO_PROJECT": "your-default-project-slug"
}
}
}
}Your org and project slugs are the short names in your board URL:
app.scrumdo.com/my-company/engineering
4 — Restart Cursor
Done. In any Cursor chat you can now ask:
"What cards are in the current sprint?"
"Move ENG-42 to In Review"
"Add a comment to ENG-42: PR is up for review"
"List all cards assigned to me"
Setup
Step 1 — Get your token
Log in to ScrumDo → your organization → Settings → API Tokens → Create Token.
Copy the token — it is only shown once. This is your personal key; keep it private.
Step 2 — Configure your AI tool
Find your tool's MCP config file and add the scrumdo server entry:
Tool | Config file |
Claude Code |
|
Claude Desktop |
|
Cursor |
|
Windsurf |
|
Claude Code — the reliable way. Rather than hand-editing the JSON (it's easy to edit the wrong
~/.claude/claude.jsonby mistake), let the CLI write it:claude mcp add scrumdo \ -e SCRUMDO_TOKEN=your-token-here \ -e SCRUMDO_ORG=your-org-slug \ -e SCRUMDO_PROJECT=your-project-slug \ -- scrumdo-mcp
{
"mcpServers": {
"scrumdo": {
"command": "scrumdo-mcp",
"env": {
"SCRUMDO_TOKEN": "your-token-here",
"SCRUMDO_ORG": "your-org-slug",
"SCRUMDO_PROJECT": "your-default-project-slug"
}
}
}
}Your org slug and project slug are the short names in your board URL:
app.scrumdo.com/my-company/engineering
Step 3 — Restart your AI tool
Done. Your AI assistant now has direct access to your board.
What you can do
Once connected, just talk to your AI tool naturally:
"What's the status of ENG-42?"
"Move ENG-42 to In Review and add a comment saying the PR is up"
"List all cards assigned to me in the current sprint"
"Create a sub-task on ENG-42: write release notes"
"Search for cards about the login bug"
"What did the team work on this week?"
"Block ENG-42 — waiting on design approval"
"Move ENG-42 to the Sprint 14 iteration"
"Set the due date on ENG-42 to 2026-04-30"
"Assign ENG-42 to Sarah"Available tools (132 total)
Group | Tools |
Boards |
|
Cards |
|
Blockers |
|
Tasks |
|
Comments |
|
Attachments |
|
Fields |
|
Members |
|
Search |
|
Activity |
|
Webhooks |
|
Time |
|
Spec |
|
Spec proposals |
|
GitHub |
|
Cockpit commands |
|
Cockpit |
|
Agents |
|
Agent runs |
|
Loops & verification |
|
Intelligence |
|
Shared memory |
|
Notifications |
|
For a governed verification loop, an orchestrator agent calls start_verification_loop
(by VerificationProfile slug or inline proof_requirements/verifier_agent), the
Maker (Grok/Codex) implements and calls run_verifier against the accepted spec
(never self-verifies), and log_loop_step / attach_evidence write the audit trail
to the card. When an agent runs inside a loop (SPRYNG_LOOP_ID set), the loop-scoped
tools default to that loop, so loop_id is optional.
Environment variables
Variable | Default | Description |
| — | Required. API token from Settings → API Tokens (or an agent's token, for AI Agent runs) |
|
| API base URL |
| — | Your organization slug |
| — | Default project slug |
| — | Optional. AI Agent run id this MCP is driving. When set, every write sends the |
|
| Optional. The host tool driving this bridge ( |
| — | Optional. The governed loop this MCP is running inside. When set, writes carry the |
Token scope
Your API token is restricted to your organization's board data only — cards, tasks, comments, members, iterations. It cannot access billing, account settings, or any other organization's data. Revoke it at any time from Settings → API Tokens.
What is MCP?
Model Context Protocol is an open standard for connecting AI tools to external services. Claude Code, Cursor, Windsurf, and other AI editors support it natively. Install the server once; any MCP-compatible tool can use it.
License
MIT
Available Tools
45 toolsadd_card_labelA
Add a single label to a card, preserving existing labels.
Args: card_ref: Card reference, e.g. 'ON-914'. label_id: Label id to add. Use list_labels() to find ids.
Inputs: card_ref (required), label_id (required).
add_commentA
Post a comment on a card. Markdown is supported.
Args: card_ref: Card reference, e.g. 'ON-914'. body: Comment text (markdown). Code blocks, lists, and headers all render in the ScrumDo UI.
Returns the created comment object with id and timestamp.
Inputs: card_ref (required), body (required).
archive_cardB
Archive a card by moving it to the project's Archive iteration. The card is hidden from the board but recoverable via the archive view.
Args: card_ref: Card reference, e.g. 'ON-914'.
Inputs: card_ref (required).
assign_cardA
Set the assignees on a card, replacing any current assignees.
Args: card_ref: Card reference, e.g. 'ON-914'. assignee_ids: List of user IDs. Pass an empty list to unassign all.
Inputs: card_ref (required), assignee_ids (required).
block_cardA
Mark a card as blocked with a reason.
Creates a blocker record on the card. Multiple blockers can exist simultaneously; the card remains blocked until all are resolved.
Args: card_ref: Card reference, e.g. 'ON-914'. reason: Human-readable explanation of what is blocking the card. is_show_stopper: Flag this as a show-stopper blocker (default False). external: Flag as an external dependency (default False).
Returns the created blocker object including its id (needed to unblock).
Inputs: card_ref (required), reason (required), is_show_stopper, external.
complete_taskB
Mark a task as complete.
Args: card_ref: Card reference, e.g. 'ON-914'. task_id: Task id (from list_tasks).
Inputs: card_ref (required), task_id (required).
create_cardB
Create a new card on the board.
Args: summary: Card title / summary (required). description: Rich text description (markdown supported). points: Story points / estimate. due_date: Due date in YYYY-MM-DD format. cell_id: Board column to place the card in. iteration_id: Iteration/sprint to assign the card to. assignee_ids: List of user IDs to assign. Use list_members() to find ids. label_ids: List of label IDs to attach. extra_fields: Custom field values as {field_id: value} dict.
Returns the full created card object including its assigned reference (e.g. 'ON-915').
Inputs: summary (required), description, points, due_date, +5 more.
create_taskA
Create a new task on a card.
Args: card_ref: Card reference, e.g. 'ON-914'. description: Task description (plain text or markdown). assignee_id: Optional user ID to assign the task to.
Returns the created task object.
Inputs: card_ref (required), description (required), assignee_id.
create_webhookA
Create a new webhook on the project.
Args: url: HTTPS endpoint that will receive webhook POST requests. events: List of event names to subscribe to, e.g. ['story.created', 'story.updated', 'story.moved', 'task.completed', 'comment.created']. secret: Optional HMAC secret for payload signature verification.
Returns the created webhook object with its id.
Inputs: url (required), events (required), secret.
delete_commentA
Delete a comment from a card.
Args: card_ref: Card reference, e.g. 'ON-914'. comment_id: Numeric comment id from list_comments().
Inputs: card_ref (required), comment_id (required). Returns: result
delete_taskA
Delete a task from a card.
Args: card_ref: Card reference, e.g. 'ON-914'. task_id: Task id (from list_tasks).
Inputs: card_ref (required), task_id (required). Returns: result
delete_webhookA
Delete a webhook by id.
Args: webhook_id: Webhook id from list_webhooks().
Inputs: webhook_id (required). Returns: result
find_cardA
Find a card by its reference ID (e.g. 'ON-914'). Alias for get_card — useful when you only know the ID string.
Args: card_ref: Card reference like 'ON-914'.
Inputs: card_ref (required).
find_memberA
Find a member by name, username, or email.
Args: query: Name, username, or email fragment to search.
Returns matching members from the org member list.
Inputs: query (required). Returns: result
get_activity_logA
Get the structured activity log for a card, with optional filters.
Returns only entries written via log_activity() — plain comments are excluded. Results are newest-first.
Args: card_ref: Card reference, e.g. 'ON-914'. agent: Filter by agent name (substring, case-insensitive). user: Filter by user (substring, case-insensitive). action: Filter by action label (substring, case-insensitive). environment: Filter by environment name (exact). milestone: Filter by milestone tag (exact). limit: Maximum entries to return (default 50).
Inputs: card_ref (required), agent, user, action, +3 more. Returns: result
get_all_card_fieldsA
Get all custom field values currently set on a card.
Returns the full list of custom fields with their names and current values.
Args: card_ref: Card reference, e.g. 'ON-914'.
Inputs: card_ref (required). Returns: result
get_boardA
Get a board (project) with its cells (columns), custom field definitions, and key statistics.
Args: project_slug: Board slug to fetch. Defaults to the configured project.
Inputs: project_slug.
get_board_cellsA
List the columns (cells) of a board.
Each cell has an id, name, and position. Use the id when moving cards.
Args: project_slug: Board slug. Defaults to the configured project.
Inputs: project_slug. Returns: result
get_cardA
Get a card's full detail including all custom fields, task list, comment count, labels, assignees, and linked cards.
Args: card_ref: The card reference, e.g. 'ON-914' or 'Q1-42'.
Inputs: card_ref (required).
get_card_fieldA
Get the current value of a single custom field on a card.
Args: card_ref: Card reference, e.g. 'ON-914'. field_id: Numeric custom field id from list_custom_fields().
Returns {'field_id': …, 'name': …, 'value': …} or {'field_id': …, 'value': null} if the field is not set.
Inputs: card_ref (required), field_id (required).
get_workspace_activityA
Get the activity log across ALL cards in the workspace.
Aggregates log_activity() entries from every card, sorted newest-first. Filterable by agent, user, action type, environment, and milestone.
This is the workspace-level view requested for board observability — answers questions like: • "What did claude-code do today?" • "What was deployed to stage this week?" • "Show me all activity on the book-kit milestone"
Args: action: Filter by action label (substring). agent: Filter by agent name (substring). user: Filter by user (substring). environment: Filter by environment (exact). milestone: Filter by milestone tag (exact). limit: Max entries across all cards (default 100).
NOTE: This scans recent cards; for large boards use per-card get_activity_log() for targeted queries.
Inputs: action, agent, user, environment, +2 more. Returns: result
list_blockersA
List all active (unresolved) blockers on a card.
Each blocker includes id, reason, blocked_date, blocker (user), is_show_stopper, and external flags.
Args: card_ref: Card reference, e.g. 'ON-914'.
Inputs: card_ref (required). Returns: result
list_boardsA
List all boards (projects) in the organisation.
Returns each board's slug, name, description, and member count. Use get_board() for full detail on a specific board.
Inputs: no named parameters. Returns: result
list_cardsA
List cards on the board with optional filters.
Args: cell_id: Filter by board column (cell) id. iteration_id: Filter by iteration/sprint id. assignee: Filter by assignee username or email. label: Filter by label name. status: Filter by status string. page: Page number (default 1). limit: Results per page (default 25, max 100).
Returns a dict with count, next/previous page URLs, and items list. Each item includes id, local_id, summary, points, cell, assignees, labels, extra_fields (custom fields), and created/updated timestamps.
Inputs: cell_id, iteration_id, assignee, label, +3 more.
list_commentsA
List all comments on a card, newest first.
Args: card_ref: Card reference, e.g. 'ON-914'. The card's numeric id is resolved automatically.
Returns a list of comments with id, author, body (markdown), and created timestamp.
Inputs: card_ref (required). Returns: result
list_custom_fieldsA
List all custom field definitions for the board.
Each field has an id, name, field_type, and optional choices. Use the id when calling set_card_field() or update_card(extra_fields=…).
Args: project_slug: Board slug. Defaults to the configured project.
Inputs: project_slug. Returns: result
list_epicsB
List all epics in the project.
Args: project_slug: Board slug. Defaults to the configured project.
Inputs: project_slug. Returns: result
list_iterationsB
List all iterations (sprints / milestones) in the project.
Args: project_slug: Board slug. Defaults to the configured project.
Inputs: project_slug. Returns: result
list_labelsA
List all labels defined in the project.
Args: project_slug: Board slug. Defaults to the configured project.
Inputs: project_slug. Returns: result
list_membersA
List members of the organisation or a specific project.
Each member has an id, username, email, display_name, and role.
Args: project_slug: If provided, returns project-level members only. If omitted, returns all org members.
Inputs: project_slug. Returns: result
list_tasksA
List all tasks (checklist items) on a card.
Args: card_ref: Card reference, e.g. 'ON-914'.
Returns a list of tasks, each with id, description, complete flag, assignee, and position.
Inputs: card_ref (required). Returns: result
list_time_entriesA
List time entries, optionally filtered to a specific card.
Args: card_ref: Card reference, e.g. 'ON-914'. If omitted, returns all project time entries.
Inputs: card_ref. Returns: result
list_webhooksA
List all webhooks configured on the project.
Returns each webhook's id, url, events, and active state.
Inputs: no named parameters. Returns: result
log_activityA
Write a structured activity log entry to a card.
Entries are stored as machine-parseable comments and rendered in the ScrumDo UI as human-readable updates. They are filterable via get_activity_log().
Args: card_ref: Card reference, e.g. 'ON-914'. action: Short action label, e.g. 'started', 'deployed', 'reviewed', 'snapshot', 'seeded', 'PR opened'. detail: Longer description or context (markdown). agent: Agent/bot name writing the log (e.g. 'claude-code', 'codex', 'github-actions'). user: Human user involved (username or email). environment: Environment name (stage, integration, branch). milestone: Milestone or release tag, if applicable. task_ref: Related task or sub-item reference. extra: Any additional structured data to attach.
Returns the created comment object.
Inputs: card_ref (required), action (required), detail, agent, +5 more.
log_timeA
Log time spent on a card.
Args: card_ref: Card reference, e.g. 'ON-914'. minutes: Time spent in minutes. description: What was done during this time. date: ISO date string (YYYY-MM-DD). Defaults to today. user_id: User to log time for. Defaults to the token owner.
Returns the created time entry.
Inputs: card_ref (required), minutes (required), description, date, +1 more.
move_cardA
Move a card to a different column (cell) on the board.
Args: card_ref: Card reference, e.g. 'ON-914'. cell_id: Target cell id. Use get_board_cells() to find cell ids.
Returns the updated card.
Inputs: card_ref (required), cell_id (required).
move_card_to_iterationA
Move a card into an iteration (sprint).
Args: card_ref: Card reference, e.g. 'ON-914'. iteration_id: Target iteration id. Use list_iterations() to find ids.
Returns the updated card.
Inputs: card_ref (required), iteration_id (required).
remove_card_labelA
Remove a single label from a card.
Args: card_ref: Card reference, e.g. 'ON-914'. label_id: Label id to remove.
Inputs: card_ref (required), label_id (required).
reopen_taskA
Reopen (un-complete) a task.
Args: card_ref: Card reference, e.g. 'ON-914'. task_id: Task id (from list_tasks).
Inputs: card_ref (required), task_id (required).
search_by_field_valueA
Find all cards where a custom field contains a given value.
Useful for finding cards tagged with a specific branch, PR URL, feature flag, or any other custom field content.
Args: field_id: Numeric custom field id from list_custom_fields(). value: Value to match (substring match, case-insensitive). limit: Maximum cards to scan (default 50).
Returns matching card objects.
Inputs: field_id (required), value (required), limit. Returns: result
search_cardsA
Full-text search across all cards in the organisation.
Searches card summaries, descriptions, and comments.
Args: query: Search string. Supports partial matches.
Returns a ranked list of matching cards with summary, reference, board name, and a short excerpt.
Inputs: query (required). Returns: result
set_card_fieldA
Set a single custom field on a card without touching other fields.
Args: card_ref: Card reference, e.g. 'ON-914'. field_id: Numeric custom field id. Use list_custom_fields() to look up ids. value: New field value (always a string).
Returns the updated card.
Inputs: card_ref (required), field_id (required), value (required).
unblock_cardA
Resolve (unblock) a specific blocker on a card.
If this was the last active blocker, the card's blocked flag is cleared. Use list_blockers() to find the blocker_id.
Args: card_ref: Card reference, e.g. 'ON-914'. blocker_id: Numeric blocker id from list_blockers(). resolution: Optional description of how the block was resolved.
Returns the resolved blocker object.
Inputs: card_ref (required), blocker_id (required), resolution.
update_cardA
Update one or more fields on an existing card.
Only the fields you provide will be changed — omitted fields are untouched.
Args: card_ref: Card reference, e.g. 'ON-914'. summary: New title. description: New description (markdown). points: New story points. due_date: Due date in YYYY-MM-DD format. Pass empty string to clear. iteration_id: Move card to this iteration/sprint id. Use list_iterations() to find ids. assignee_ids: Replace assignee list. Use list_members() to find ids. label_ids: Replace label list. extra_fields: Merge into existing custom fields. Existing keys not mentioned here will be preserved.
Returns the full updated card object.
Inputs: card_ref (required), summary, description, points, +5 more.
update_taskB
Update a task's description, completion state, or assignee.
Args: card_ref: Card reference, e.g. 'ON-914'. task_id: Task id (from list_tasks). description: New description (leave None to keep current). complete: True to complete, False to reopen. assignee_id: New assignee user id.
Inputs: card_ref (required), task_id (required), description, complete, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 45 tools
Each tool has a clearly distinct purpose, covering cards, tasks, comments, labels, blockers, time tracking, activity logging, webhooks, and search. Only minor aliasing like find_card=get_card, which does not cause confusion.
Most tools follow a consistent verb_noun pattern (create_card, list_tasks, etc.). However, there is some variation in prefix verbs (get vs list vs find vs search) and a few tools like log_activity and log_time use a different structure, preventing a perfect score.
With 45 tools, the set is quite large but each tool serves a specific function within a comprehensive project management domain. It borders on excessive but remains justified given the breadth of features supported.
The tool surface covers most CRUD operations for core entities but misses lifecycle operations for iterations, epics, and boards (e.g., no create/delete). Card deletion is only via archiving, which is a notable gap.
Maintenance
Related MCP Connectors
Remote MCP for Kanban AI boards—manage projects, tasks, and comments from AI tools.
Task & board management for AI agents + humans. Kanban, comments, digests via MCP.
Connect any AI agent to 1,000+ apps and 27,000+ actions through one remote MCP server (OAuth).
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI-powered project management by connecting Claude to Planka kanban boards via 75+ MCP tools for creating, updating, and managing projects, boards, lists, and cards.1GPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Planka kanban boards, including creating, updating, and organizing tasks, lists, and cards via MCP.65MIT

GitScrum MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage projects, tasks, sprints, time tracking, and more through GitScrum.137 npm5MIT- FlicenseAqualityDmaintenanceIntegrates BusinessMap (formerly Kanbanize) project management capabilities with MCP-compatible applications, enabling board management, card operations, user management, and search.9-