CLEO MCP Server

Task management protocol for solo developers and AI coding agents with 2-gateway CQRS pattern

Local serverstdioTypeScript

What is the CLEO MCP server?

Task management protocol for solo developers and AI coding agents with 2-gateway CQRS pattern. Exposed over MCP by the cleo mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Every developer who has ever returned to a project after weeks away and found only ruins knows the wound CLEO was built to heal. The agents are powerful. But power without memory is chaos. Brilliance without continuity is waste. CLEO is the companion that remembers where you left off — the one who keeps the thread when life pulls you away.

CLEO is built for the developers who build after the world goes quiet — the ones carrying six unfinished ideas and the stubborn belief that this next session might be the one where everything clicks. It solves the coordination crisis of working with multiple AI agents across complex projects by giving them something they've never had: structure, memory, and a lifecycle that survives interruption.

Its toolset

Everything the assistant can do here goes through one of these:

  • Installation — The Installation tool exposed by this server
  • Prerequisites — The Prerequisites tool exposed by this server

Adding it to your client

@cleocode/cleo on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration

  • Node.js >= 24.0.0 - pnpm >= 10.30.0 (package manager)

When to reach for it

Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. CLEO's toolset — Installation, Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by kryptobaseddev; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the cleo mcp server does with a few real requests.

Available tools

ToolWhat it does
InstallationThe Installation tool exposed by this server.
PrerequisitesThe Prerequisites tool exposed by this server.

How to install the CLEO MCP server

{
  "mcpServers": {
    "cleo": {
      "command": "npx",
      "args": ["-y", "@cleocode/cleo"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Node.js >= 24.0.0 - pnpm >= 10.30.0 (package manager)

Example prompts to try

  • Use CLEO to Installation.
  • Use CLEO to Prerequisites.

Frequently asked questions

It connects CLEO to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Installation, Prerequisites) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with CLEO directly.