CLEO MCP Server

Name: CLEO MCP Server
Author: kryptobaseddev

作者：kryptobaseddev版本 2026.3.35i★ –i在你的电脑上运行

注册名称io.github.kryptobaseddev/cleo-mcp-server

安装

概览

作者提供的说明（英文原文）

Task management for AI coding agents — CQRS 2-gateway pattern, 200 ops across 10 domains

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 文档、表格与办公

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： CLEO_PROJECT_DIR

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "cleo": {
      "command": "npx",
      "args": [
        "-y",
        "@cleocode/cleo",
        "--mcp-server"
      ],
      "env": {
        "CLEO_PROJECT_DIR": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add cleo --env CLEO_PROJECT_DIR=your-value -- npx -y @cleocode/cleo --mcp-server

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "cleo": {
      "command": "npx",
      "args": [
        "-y",
        "@cleocode/cleo",
        "--mcp-server"
      ],
      "env": {
        "CLEO_PROJECT_DIR": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "cleo": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@cleocode/cleo",
        "--mcp-server"
      ],
      "env": {
        "CLEO_PROJECT_DIR": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

CLEO_PROJECT_DIR env
Path to CLEO project directory (must contain .cleo/ folder)

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 kryptobaseddev 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“文档、表格与办公”中的其他服务器比较i

星标数多于此分类中其他 2174 个服务器的 0%
发布到注册中心的时间比此分类中其他 2174 个服务器的 5% 更新
基础检查结果等于或优于此分类中其他 2174 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

CLEO MCP Server 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（2026.3.35）于8个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Agent-Native Calendar

作者：BuilderIO

Agent-Native Google Calendar - manage events, sync, and public booking

在云端运行★ 7,620MIT2个月前更新

安装

Excel MCP Server

作者：haris-musa

Create and edit Excel files with AI: charts, PivotTables, formulas. No Excel needed.

在你的电脑上运行★ 4,276MIT6天前更新

安装

MCP Server for Excel

作者：sbroenne

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

在你的电脑上运行★ 847MIT3天前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

CLEO

CLEO is the work, evidence, memory and docs layer for AI coding agents. Agents (and you) drive it through one CLI, cleo , and every call returns a single JSON envelope on stdout, so any agent harness can read it. CLEO keeps each change traceable from task to pull request to release, demands evidence before a task counts as done, remembers what was learned across sessions, and keeps documentation from rotting.

What it does

Area	What you get	Start with
Tasks	Sagas, epics and tasks with acceptance criteria, dependencies and ready waves; sessions that survive interruptions	`cleo add`, `cleo next`, `cleo focus`
Evidence	A task is done only when its gates are proven: commits and files, CI or test runs, lint and typecheck, linked to each acceptance criterion	`cleo done --plan`
Pull requests	A PR names its tasks (`Closes: T#### AC1,AC2`); an independent reviewer records a verdict per criterion; merging on green CI closes the task	`cleo done --from-merge --dry-run`, `cleo review packet`
Docs	One canonical home per doc, stable names, published mirrors and drift checks (see below)	`cleo docs query`, `cleo docs update`
Memory (BRAIN)	Observations, decisions and lessons kept across sessions and searchable	`cleo memory observe`, `cleo memory find`, `cleo briefing`
Code intelligence (Nexus)	A symbol graph of your repo: callers, blast radius, impact before you edit	`cleo nexus analyze`, `cleo nexus impact`
Release	One command tags the newest commit on main with green CI and publishes from changesets	`cleo release cut --dry-run`

Run cleo --help for the full flags of any command.

Quick start

npm install -g @cleocode/cleo

cd your-project cleo init cleo session start --scope global --name "first session"

Work is a tree: a saga at the root, epics under it, tasks under those.

cleo saga create --title "Ship the auth hardening" --acceptance "login is rate limited|sessions expire" cleo add "Auth hardening" --type epic --parent T001 --acceptance "rate limit shipped|session expiry shipped" cleo add "Rate-limit the login endpoint" --parent T002 \ --acceptance "returns 429 after 5 failed attempts|a test covers the limit"

cleo next # what to work on cleo focus T003 # identity, blockers, docs and memory for one task

Then do the work and close it.

With a pull request (the normal path): work on a branch, open a PR whose body says Closes: T003 AC1,AC2, check it with cleo done --from-merge --dry-run, get a per-criterion review (cleo review packet --task T003, then cleo review verdict), and merge on green CI. The merge sweep records the evidence and closes the task.
Without a pull request: cleo done T003 --plan names the evidence each gate needs; record it with cleo verify, then cleo complete T003.

Finish with cleo memory observe " " --title " " and cleo session end --note " ". The next session starts with cleo briefing.

Docs that don't rot

AI agents write a lot of documentation, and most of it rots. An agent that cannot find the existing doc writes a new one; names carry task ids and dates; two copies drift apart; nobody can tell which one is current. After a few months the docs folder is a pile of near-duplicates that agents keep extending.

CLEO Docs fixes this at the source:

One canonical home per doc. The store is the source of truth; files in docs/ are published mirrors. Find before you write (cleo docs query " "), and update the existing doc (cleo docs update ) instead of adding a second one. cleo docs add is for genuinely new docs.
Stable names. Every doc name and slug is lowercase kebab-case with no task id, session id or date; task and decision links live in metadata. A CI gate (cleo check canon docs) refuses new violators.
One kind per folder. docs/adr, docs/spec, docs/plan, docs/research, docs/guide, docs/concept, docs/reference, docs/migration, docs/release and docs/note.
Drift is visible. cleo docs status compares each published mirror with the store, cleo docs rot flags docs whose covered code changed after them, and cleo docs doctor repairs the store.
Messy folders can be migrated. cleo docs modernize plans a kind, a stable name and keep/rename/merge/delete for every file, and applies it with a receipt you can roll back.

The how-to is docs/guide/cleo-documentation-sop.md.

Packages

The CLI is @cleocode/cleo; it depends on the rest. The main packages:

Package	Purpose
`@cleocode/cleo`	The `cleo` command-line interface
`@cleocode/core`	The SDK: tasks, sessions, evidence, docs, memory, orchestration, release
`@cleocode/contracts`	Shared types and operation contracts
`@cleocode/lafs`	The JSON envelope format every call returns
`@cleocode/nexus`	Code intelligence and the cross-project registry
`@cleocode/caamp`	Provider registry and agent package management
`@cleocode/adapters`	Provider adapters (Claude Code, Codex, Cursor, Gemini, Kimi, OpenCode and more)
`@cleocode/skills`	The `ct-*` skills that teach agents how to use CLEO
`@cleocode/cant`	The CANT agent-definition language

Development

Requires Node.js >= 24.16.0 and pnpm.

git clone https://github.com/kryptobaseddev/cleo.git

cd cleo pnpm install pnpm run build

Repository rules (package boundaries, architecture gates, evidence) are in AGENTS.md; see CONTRIBUTING.md to contribute. Every change lands through a pull request that names its tasks; releases are cut from main with cleo release cut.

The story of CLEO

CLEO began as one developer's refusal to keep losing the thread: powerful agents that forgot too easily, ambitious projects that died on the shelf. The Founding Story tells it from the builder's side, and The Awakening Story from CLEO's.