DevFlow Command Center MCP Server - Agent integration for Claude Code
npm install dflowmcpbash
npm install -g dflowmcp
`
Quick Setup
The easiest way to configure is using dflowcli:
`bash
npm install -g dflowcli
cd your-project
devflow init
`
This auto-configures Claude Code's MCP settings.
Manual Configuration
Add to your Claude Code MCP config (~/.claude.json or project-level .mcp.json):
`json
{
"mcpServers": {
"devflow": {
"command": "npx",
"args": ["dflowmcp"],
"env": {
"DEVFLOW_PROJECT_ID": "your-project-uuid",
"DEVFLOW_API_URL": "https://devflow.now/api"
}
}
}
}
`
Available Tools
$3
| Tool | Description |
|------|-------------|
| get_active_task | Get the currently active task from Command Center |
| start_task | Start a task (PLANNED/BLOCKED → ACTIVE) |
| complete_task | Complete a task with summary (ACTIVE → DONE) |
| block_task | Block a task with reason (ACTIVE → BLOCKED) |
| log_progress | Log progress updates visible in UI |
| add_task_note | Add structured notes (constraint, decision, warning) |
$3
| Tool | Description |
|------|-------------|
| get_project_execution_state | Get full project state: deliverables, tasks, notes |
| get_project_activity | Get recent activity events (paginated) |
| sync_project_context | Sync all context to local markdown files |
$3
| Tool | Description |
|------|-------------|
| create_execution_proposal | Create a proposal with deliverables/tasks for review |
| commit_execution_proposal | Commit a proposal (humans only - will fail for agents) |
$3
| Tool | Description |
|------|-------------|
| wait_for_task_activation | Long-poll waiting for task activation (max 120s) |
Workflow
1. On startup: Claude Code calls get_active_task to check for assigned work
2. During work: Use log_progress to report updates visible in Command Center
3. On completion: Call complete_task with a summary of what was accomplished
4. If blocked: Call block_task with the reason
Context Sync
The MCP server can sync project context to local files:
`
.devflow-context/
├── ACTIVE.md - Current task details (auto-synced)
├── PROJECT.md - PRD, milestones, artifacts
├── CLIENT.md - Client info, communications
├── EXECUTION.md - All deliverables and tasks
├── DECISIONS.md - Decision log
└── ACTIVITY.md - Recent activity
`
Environment Variables
| Variable | Required | Description |
|----------|----------|-------------|
| DEVFLOW_PROJECT_ID | Yes | Your DevFlow project UUID |
| DEVFLOW_API_URL | No | API URL (default: https://devflow.now/api) |
| DEVFLOW_AGENT_TOKEN | No | Auth token (optional) |
Security & Permissions
$3
Agents can:
- ✅ Read project execution state
- ✅ Create execution proposals
- ✅ Start, block, and complete tasks
- ✅ Add memory notes to tasks
- ✅ Read activity streams
Agents CANNOT:
- ❌ Commit execution proposals (HUMAN only)
- ❌ Access projects outside their workspace
- ❌ Delete or modify historical activity events
Why? This ensures human oversight of project planning. Agents propose, humans approve.
Real-Time Synchronization
All changes made by agents are instantly visible in:
- Web UI (devflow.now/command-center)
- CLI (devflow watch`)