Aidderall MCP Server

Aidderall Visual Representation ================================ 1. Basic Structure - Tasks grow vertically, subtasks grow horizontally: ┌─────────────────┐ │ MainTask C │ ← Latest main task │ [PENDING] │ └─────────────────┘ ↑ ┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐ │ MainTask B │ ──→ │ SubTask B.1 │ ──→ │ SubTask B.2 │ │ [COMPLETED] │ │ [COMPLETED] │ │ [CURRENT] ← │ ← YOU ARE HERE └─────────────────┘ └─────────────────┘ └─────────────────┘ ↑ ┌─────────────────┐ ┌─────────────────┐ │ MainTask A │ ─→ │ SubTask A.1 │ │ [COMPLETED] │ │ [COMPLETED] │ └─────────────────┘ └─────────────────┘ 2. Living Document - Completed tasks remain visible: Before (traditional todo): After (Aidderall): ┌─────────────────┐ ┌─────────────────┐ │ ☐ Task A │ │ ✓ Task A │ ← Still visible! │ ☐ Task B │ │ ✓ Task B │ ← Context preserved │ ☐ Task C │ │ ☐ Task C │ └─────────────────┘ └─────────────────┘ Traditional: Completed = Gone Aidderall: Completed = History 3. Flexible Navigation with switch_focus: ┌─────────────────┐ │ Task D │ │ [PENDING] │ ←────────────┐ └─────────────────┘ │ ↑ │ Can jump to any task! ┌─────────────────┐ │ │ Task C │ │ │ [CURRENT] ← │ ←──────┐ │ └─────────────────┘ │ │ ↑ │ │ ┌─────────────────┐ │ │ │ Task B │ ←──────┘ │ │ [COMPLETED] │ │ └─────────────────┘ │ ↑ │ ┌─────────────────┐ │ │ Task A │ ←────────────┘ │ [COMPLETED] │ └─────────────────┘ 4. Real-world Example - Implementing a Feature: ┌─────────────────────┐ │ Add User Auth │ │ [COMPLETED] │ └─────────────────────┘ ↑ │ ┌──────────────────┐ ┌──────────────────┐ ┌──────────────────┐ └───→ │ Design DB Schema │ ──→ │ Create API │ ──→ │ Add UI Forms │ │ [COMPLETED] │ │ [COMPLETED] │ │ [CURRENT] ← │ └──────────────────┘ └──────────────────┘ └──────────────────┘ ↑ │ ┌──────────────────┐ └───→ │ Add JWT logic │ │ [COMPLETED] │ └──────────────────┘ 5. Value Propositions Visualized: Traditional Linear Todo: Aidderall Hierarchical: ======================== ========================= ☐ Research auth libraries Research Phase ☐ Design database schema │ ☐ Create user table ├─→ Auth libraries ☐ Create session table │ └─→ JWT vs Sessions ☐ Implement JWT │ ☐ Create login endpoint Design Phase ☐ Create register endpoint │ ☐ Add password hashing ├─→ Database Schema ☐ Create login form │ ├─→ User table ☐ Create register form │ └─→ Session table ☐ Add form validation │ Implementation Phase Problems: │ - No hierarchy ├─→ Backend API - No context │ ├─→ Login endpoint - Hard to see relationships │ ├─→ Register endpoint - Completed = disappeared │ └─→ Password hashing │ └─→ Frontend UI ├─→ Login form ├─→ Register form └─→ Validation Benefits: ✓ Clear hierarchy ✓ Preserved context ✓ Visible relationships ✓ Complete history 6. Zen State - Two Paths: Path 1: No tasks Path 2: All completed ┌─────────────────┐ ┌─────────────────┐ │ │ │ ✓ Task A │ │ Empty Stack │ │ ✓ Task B │ │ (Zen State) │ │ ✓ Task C │ │ │ │ (Zen State) │ └─────────────────┘ └─────────────────┘

git clone https://github.com/user/aidderall_mcp.git cd aidderall_mcp

python -m venv venv source venv/bin/activate # On Windows: venv\Scripts\activate

pip install -r requirements.txt

pip install -e ".[dev]"

python -m src.server

claude mcp add aidderall-mcp /path/to/aidderall_mcp/run_mcp.sh

{ "mcpServers": { "aidderall": { "command": "python", "args": ["-m", "src.server"] } } }

# Start with a root task create_new_task("Design new feature", "Research and design specs") # Break it down into subtasks for organization extend_current_task("Research requirements", "User research needed") extend_current_task("Interview users", "Conduct user interviews") extend_current_task("Analyze competitors", "Research competitor solutions") # Work on tasks in any order using switch_focus get_big_picture() # See all tasks with their IDs switch_focus("task-id-for-research") # Jump to research task complete_current_task() # Complete it when done # Jump to any other task switch_focus("task-id-for-interviews") # Work on interviews # ... do some work ... switch_focus("task-id-for-competitors") # Switch to competitor analysis # Create parallel work streams create_new_task("Write documentation", "Document the new feature") extend_current_task("API docs", "Write API documentation") extend_current_task("User guide", "Write user guide") # Jump between different work streams freely switch_focus("task-id-for-design") # Back to design work switch_focus("task-id-for-api-docs") # Jump to documentation # Complete tasks as they're finished, in any order complete_current_task() # Completes whatever you're currently focused on # View all tasks - completed ones remain visible get_big_picture() # Output shows: # Design new feature (pending) # Research requirements (completed) # Interview users (pending) # Analyze competitors (completed) # Write documentation (pending) # API docs (completed) # User guide (pending) # Clean up workspace by removing completed tasks remove_task("task-id-for-research") # Removes from view but keeps in history

pytest -v

pytest --cov=src tests/

black src tests isort src tests

mypy src