atlas-mcp-server
by cyanheads
Verified
clear_all_tasks
Remove all tasks from the database.
Impact:
- Deletes ALL tasks permanently
- Removes all relationships and dependencies
- Clears all metadata and notes
- Resets database to initial state
- Cannot be undone
When to Use:
- Starting fresh project phase
- Major project restructuring
- Development environment reset
- Test environment cleanup
Best Practices:
- Export tasks before clearing
- Verify confirmation flag
- Document clear reasoning
- Consider selective deletion
- Plan new task structure
- Archive important metadata
Safety Checks:
- Requires explicit confirmation
- Validates database state
- Ensures clean deletion
- Prevents partial clears
Example: { "confirm": true, "reasoning": "Resetting task structure for Q2 planning. Previous tasks have been archived and new project structure will be implemented with updated requirements and dependencies." }
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| confirm | Yes | Explicit confirmation required to prevent accidental deletion. Note: This operation: - Removes ALL tasks from the database - Cannot be undone - Should be used with caution - Requires explicit confirmation | |
| reasoning | No | Explanation for clearing all tasks. Best practices: - Document why a complete reset is needed - Note where existing tasks are archived - Outline plan for new structure - Record migration/backup details |