scrumdo-mcp
Connects MCP-compatible AI tools to ScrumDo boards, enabling card, task, comment, and search operations without manual copy-pasting.
README
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-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/ -v
2 — 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/claude.json |
| Cursor | ~/.cursor/mcp.json |
| Windsurf | ~/.codeium/windsurf/mcp_config.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 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 (45 total)
| Group | Tools |
|---|---|
| Boards | list_boards, get_board, get_board_cells, list_iterations, list_labels, list_epics |
| Cards | list_cards, get_card, find_card, create_card, update_card, move_card, move_card_to_iteration, set_card_field, archive_card, assign_card, add_card_label, remove_card_label |
| Blockers | list_blockers, block_card, unblock_card |
| Tasks | list_tasks, create_task, complete_task, reopen_task, update_task, delete_task |
| Comments | list_comments, add_comment, delete_comment |
| Fields | list_custom_fields, get_card_field, get_all_card_fields |
| Members | list_members, find_member |
| Search | search_cards, search_by_field_value |
| Activity | log_activity, get_activity_log, get_workspace_activity |
| Webhooks | list_webhooks, create_webhook, delete_webhook |
| Time | list_time_entries, log_time |
Environment variables
| Variable | Default | Description |
|---|---|---|
SCRUMDO_TOKEN |
— | Required. API token from Settings → API Tokens |
SCRUMDO_BASE_URL |
https://app.spryng.io |
API base URL |
SCRUMDO_ORG |
— | Your organization slug |
SCRUMDO_PROJECT |
— | Default project slug |
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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.