
CLEO MCP Server
Run structured task, session, release, and orchestration workflows for solo devs and coding agents through a CQRS MCP gateway.
Overview
CLEO MCP Server is a MCP server for the Build phase that exposes 177 CQRS-gated task and workflow operations to solo developers and AI coding agents via cleo_query and cleo_mutate.
What is this MCP server?
- 177 operations across 11 domains via CQRS 2-gateway pattern
- Two MCP tools: cleo_query (read) and cleo_mutate (write) spanning tasks, session, orchestrate, research, lifecycle, vali
- Publisher claims ~94% token reduction versus traditional per-tool MCP sprawl
- Anti-hallucination validation on task operations with atomic file ops, backup, and rollback
- npm package @cleocode/cleo version 2026.3.7 with stdio transport
- 2 MCP tools: cleo_query and cleo_mutate
Community signal: 156 GitHub stars.
What problem does it solve?
Coding agents sprawl dozens of MCP tools and invent task state unless you centralize reads and writes behind validated project operations.
Who is it for?
Solo builders and agent-heavy workflows that need a single CQRS MCP hub for tasks, releases, validation, and orchestration instead of a forest of one-off tools.
Skip if: Teams wanting a simple shared kanban with no local file semantics, or builders who only need lightweight notes without 177 operations and CQRS discipline.
What do I get? / Deliverables
After install, your agent uses two MCP gateways to query and mutate real task, release, and orchestration data with validation and rollback-safe file operations.
- Two-tool CQRS MCP surface (cleo_query / cleo_mutate) over 177 operations
- Validated task mutations with atomic file backup and rollback
- Agent-accessible PM, release, and orchestration operations across 11 domains
Recommended MCP Servers
Journey fit
How it compares
CQRS task-and-orchestration MCP with two tools, not a single-purpose database or browser automation server.
Common Questions / FAQ
Who is CLEO MCP Server for?
Solo developers and AI coding agents that need structured task, session, release, and orchestration control through MCP with separated read and write gateways.
When should I use CLEO MCP Server?
Use it during Build PM when your agent must read and update real project state, run validation gates, and coordinate releases without hallucinated task lists.
How do I add CLEO MCP Server to my agent?
Register the stdio npm MCP server @cleocode/cleo (2026.3.7) in Claude Code or Cursor, then call cleo_query for reads and cleo_mutate for writes across the documented domains.