Model Context Protocol (MCP) server for SCUD task management. Enables AI assistants like Claude Desktop to interact with SCUD's task management and AI-powered workflow features.
SCUD MCP wraps the SCUD CLI and exposes it through the Model Context Protocol, allowing any MCP-compatible client to:
Perfect for teams using Claude Desktop, Cline, or other MCP clients who want AI-powered task management integrated into their development workflow.
scud_init - Initialize SCUD in current directoryscud_list - List tasks (optionally filter by status)scud_next - Find next available taskscud_stats - Show epic statisticsscud_show - Show task detailsscud_set_status - Update task statusscud_tags - List all epic tagsscud_use_tag - Set active epicscud_parse_prd - Parse PRD markdown into tasksscud_analyze_complexity - Analyze task complexity (Fibonacci scale)scud_expand - Break down complex tasks into subtasksscud_research - AI-powered researchscud_create_group - Create epic group for parallel workscud_list_groups - List all epic groupsscud_group_status - Show group progressscud_assign - Assign task to developerscud_claim - Claim task for yourselfscud_release - Release claimed taskscud_whois - Show task assignmentsscud://workflow/state - Current workflow state (JSON)scud://tasks/list - All tasks in active epic (JSON)scud://stats/epic - Epic statistics (text)# Install SCUD CLI (if not already installed)
npm install -g scud
# Verify installation
scud --version
npm install -g scud-mcp
Edit your Claude Desktop config file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Linux: ~/.config/Claude/claude_desktop_config.json
Add the SCUD MCP server:
{
"mcpServers": {
"scud": {
"command": "scud-mcp",
"env": {
"ANTHROPIC_API_KEY": "sk-ant-your-api-key-here"
}
}
}
}
Note: The ANTHROPIC_API_KEY is only required for AI-powered tools (scud_parse_prd, scud_analyze_complexity, scud_expand, scud_research). Core task management works without it.
Restart Claude Desktop to load the MCP server. You should see the SCUD tools available in your conversations.
You (in Claude Desktop):
Initialize SCUD and parse my PRD file at docs/epics/epic-1-auth.md with tag epic-1-auth
Claude:
[calls scud_init]
✓ Initialized SCUD successfully
[calls scud_parse_prd with file="docs/epics/epic-1-auth.md", tag="epic-1-auth"]
✓ Parsed PRD into 12 tasks
✓ Active epic set to: epic-1-auth
You:
What's my next task?
Claude:
[calls scud_next]
Next available task:
TASK-1: Set up authentication database schema
Complexity: 5
Priority: high
Status: pending
You:
Mark TASK-1 as in-progress and show me the details
Claude:
[calls scud_set_status with task_id="TASK-1", status="in-progress"]
✓ Task TASK-1 updated to in-progress
[calls scud_show with task_id="TASK-1"]
TASK-1: Set up authentication database schema
Description: Create User and Session tables with proper indexes...
Complexity: 5 (Medium)
Priority: high
Status: in-progress
Dependencies: None
You:
Analyze the complexity of all tasks
Claude:
[calls scud_analyze_complexity]
Analyzing 12 tasks...
TASK-3: Implement OAuth2 flow
Complexity: 21 → Recommended: EXPAND
Reasoning: Involves multiple components (auth provider integration, token management,
refresh logic, error handling). Should be broken down.
TASK-7: Add login form UI
Complexity: 3
Reasoning: Simple form with email/password fields. Well-defined scope.
[... more analysis ...]
You:
Expand TASK-3
Claude:
[calls scud_expand with task_id="TASK-3"]
Expanded TASK-3 into 5 subtasks:
TASK-3-1: Research OAuth2 providers (complexity: 2)
TASK-3-2: Implement authorization endpoint (complexity: 5)
TASK-3-3: Implement token endpoint (complexity: 5)
TASK-3-4: Add token refresh logic (complexity: 3)
TASK-3-5: Add OAuth2 error handling (complexity: 3)
You:
Create a sprint group with epic-1-auth, epic-2-api, and epic-3-frontend
Claude:
[calls scud_create_group with name="sprint-1", epics="epic-1-auth,epic-2-api,epic-3-frontend"]
✓ Created group: sprint-1
[calls scud_group_status with group_id="sprint-1"]
Sprint 1 Status:
epic-1-auth: 5/12 tasks done (42%)
epic-2-api: 2/8 tasks done (25%)
epic-3-frontend: 0/15 tasks done (0%)
Overall: 7/35 tasks completed (20%)
You:
Read the current workflow state
Claude:
[reads scud://workflow/state resource]
{
"active_epic": "epic-1-auth",
"current_phase": "development",
"phases": {
"planning": { "status": "completed", "completed_at": "2025-11-15T10:00:00Z" },
"development": { "status": "in-progress", "started_at": "2025-11-15T14:00:00Z" }
},
"completed_epics": []
}
| Tool | Parameters | Description |
|---|---|---|
scud_init | - | Initialize SCUD in current directory |
scud_list | status? | List tasks (filter by status) |
scud_next | - | Find next available task |
scud_stats | - | Show epic statistics |
scud_show | task_id | Show task details |
scud_set_status | task_id, status | Update task status |
| Tool | Parameters | Description |
|---|---|---|
scud_tags | - | List all epic tags |
scud_use_tag | tag | Set active epic tag |
| Tool | Parameters | Description |
|---|---|---|
scud_parse_prd | file, tag | Parse PRD into tasks |
scud_analyze_complexity | task? | Analyze task complexity |
scud_expand | task_id?, all? | Expand complex tasks |
scud_research | query | AI-powered research |
| Tool | Parameters | Description |
|---|---|---|
scud_create_group | name, epics, description? | Create epic group |
scud_list_groups | - | List all epic groups |
scud_group_status | group_id | Show group status |
scud_assign | task_id, assignee | Assign task to developer |
scud_claim | task_id, name | Claim task for yourself |
scud_release | task_id, force? | Release claimed task |
scud_whois | - | Show task assignments |
| Resource | Description | Format |
|---|---|---|
scud://workflow/state | Current workflow state | JSON |
scud://tasks/list | All tasks in active epic | JSON |
scud://stats/epic | Epic statistics | Text |
When using scud_set_status, valid status values are:
pending - Not startedin-progress - Currently being worked ondone - Completedreview - Ready for reviewblocked - Blocked by dependencies or issuesdeferred - Postponed to latercancelled - No longer neededSCUD uses Fibonacci complexity scores:
1 - Trivial (5-15 minutes)2 - Simple (15-30 minutes)3 - Moderate (30-60 minutes)5 - Medium (1-3 hours)8 - Complex (3-8 hours)13 - Large (8+ hours, recommend expanding)21 - Too large (must expand into subtasks)The MCP server couldn't find the scud command. Install it:
npm install -g scud
Verify:
which scud # macOS/Linux
where scud # Windows
AI tools require an API key. Add it to your Claude Desktop config:
{
"mcpServers": {
"scud": {
"command": "scud-mcp",
"env": {
"ANTHROPIC_API_KEY": "sk-ant-your-key"
}
}
}
}
Initialize a project and set an active epic:
1. Run scud_init
2. Run scud_parse_prd or manually create an epic
3. Run scud_use_tag to set the active epic
which scud-mcpgit clone https://github.com/yourusername/bmad-tm
cd bmad-tm/scud-mcp
npm install
npm run build
npm link # Test locally
scud-mcp/
├── src/
│ ├── index.ts # MCP server entry point
│ ├── types.ts # TypeScript types
│ ├── tools/ # Tool implementations
│ │ ├── core.ts # Core commands
│ │ ├── epic.ts # Epic management
│ │ ├── task.ts # Task operations
│ │ ├── ai.ts # AI-powered tools
│ │ └── parallel.ts # Parallel development
│ ├── resources/ # Resource implementations
│ │ ├── workflow.ts # Workflow state
│ │ ├── tasks.ts # Task lists
│ │ └── stats.ts # Statistics
│ └── utils/
│ └── exec.ts # CLI execution wrapper
├── package.json
├── tsconfig.json
└── README.md (this file)
The SCUD MCP server is a lightweight wrapper around the fast Rust CLI:
Contributions welcome! Please:
MIT License - see LICENSE file for details
Built with ❤️ for AI-powered development workflows
FAQs
Model Context Protocol server for SCUD task management
We found that scud-mcp demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.
Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.