CycleTime CE is a project orchestration framework that extends Claude Code to manage software development lifecycles through structured project data and cross-session persistence.
- MCP SSE Server: Claude Code integration via MCP protocol (v2024-11-05)
- Operational Tools: Project, issue, workflow, and session management capabilities
- Resource Providers: Context access for AI-assisted development
- Cross-Session Persistence: H2 database maintains state between sessions
- Create and manage multiple projects
- Track project lifecycle and status
- REST API for programmatic access
- Full CRUD operations with validation
- Hierarchical Structure: Epic → Story → Subtask
- Business Rules: Enforced estimation and hierarchy constraints
- Status Management: Workflow-based transitions
- Project Association: Issues linked to projects
- Define custom workflows
- Status transitions with validation
- Template-based workflow creation
- Stage-based execution tracking
- Docker Container:
ghcr.io/spiralhouse/cycletime:latest - CI/CD Pipeline: Automated testing and deployment
- Quality Gates: 90%+ test coverage, static analysis
- Database: H2 embedded with full persistence
# 1. Start CycleTime
docker run -p 8080:8080 ghcr.io/spiralhouse/cycletime:latest
# 2. Connect Claude Code
# Add MCP server configuration pointing to http://localhost:8080/mcp/events
# 3. Start orchestrating!
# Use Claude Code to create projects, track issues, manage workflowsFor Developers
- Claude Code integration through MCP protocol for AI-assisted development
- Persistent project context across coding sessions
- Structured workflow management through familiar Claude Code interface
For Teams
- Consistent project structure and tracking
- Clear issue hierarchies and dependencies
- Workflow standardization across projects
For Organizations
- MIT licensed (corporate-friendly)
- Self-hosted with full data control
- Minimal infrastructure requirements
- Architecture: Domain-Driven Design with clean separation of concerns
- Performance: Session operations < 1ms average latency (measured from SPI-346)
- Testing: 96.91% domain coverage with 60 passing tests (47 unit + 13 integration)
- Reliability: Comprehensive test coverage and error handling
- Extensibility: MCP protocol integration for custom tools and workflows
Completed Features (SPI-346):
- Session management with cross-session persistence
- Domain-Driven Design architecture implementation
- H2 database integration with Exposed ORM
- Comprehensive testing suite (60 tests, 96.91% coverage)
- Performance validation (< 1ms session operations)
In Progress:
- MCP Resource integration (SPI-290)
- Project Bootstrap functionality (SPI-354)
Next Steps:
- Complete Phase 1 MCP integration
- Enhanced context provision and dependency tracking
- Multi-provider support (Linear, GitHub, Jira)
- Observability (Week 1): Structured logging and metrics
- Documentation (Week 1): Complete user and API documentation
- Performance Testing (Week 2): Load testing and optimization
- Enhanced Features (Month 2): Based on user feedback
- Repository: github.com/spiralhouse/cycletime
- Documentation: cycletime.ai
- Support: spiralhouse.io/products/cycletime
CycleTime CE: Orchestrating software development through the power of Claude Code