Agent-Native Calendar
Agent-Native Google Calendar - manage events, sync, and public booking
Description from the maker (original English)
Task management for AI coding agents — CQRS 2-gateway pattern, 200 ops across 10 domains
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
CLEO_PROJECT_DIRYou need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"cleo": {
"command": "npx",
"args": [
"-y",
"@cleocode/cleo",
"--mcp-server"
],
"env": {
"CLEO_PROJECT_DIR": "your-value"
}
}
}
}Run this in your terminal
claude mcp add cleo --env CLEO_PROJECT_DIR=your-value -- npx -y @cleocode/cleo --mcp-serverFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"cleo": {
"command": "npx",
"args": [
"-y",
"@cleocode/cleo",
"--mcp-server"
],
"env": {
"CLEO_PROJECT_DIR": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"cleo": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@cleocode/cleo",
"--mcp-server"
],
"env": {
"CLEO_PROJECT_DIR": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
CLEO_PROJECT_DIR envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account kryptobaseddev, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (2026.3.35) reached the registry 8 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Agent-Native Google Calendar - manage events, sync, and public booking
Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.
Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
| 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.
npm install -g @cleocode/cleo
cd your-project cleo init cleo session start --scope global --name "first session"
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.
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.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.
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:
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.cleo check canon docs) refuses new violators.docs/adr, docs/spec, docs/plan, docs/research, docs/guide, docs/concept, docs/reference, docs/migration, docs/release and docs/note.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.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.
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 |
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.
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.
If CLEO helps your workflow, consider supporting development:
MIT License - see LICENSE for details.