CortexPilot Read-only MCP
LocalAbout CortexPilot Read-only MCP
CortexPilot Read-only MCP is a read-only MCP server for CortexPilot workflows. It exposes queue state, proof, replay and incident summaries, suiting developers who need to review how AI coding tasks ran.
Key features
- 01Read-only access to workflows and queue state
- 02Query proof and replay records
- 03Incident summaries for review
Use cases
- 01Checking the current state of tasks in a CortexPilot queue
- 02Reviewing replay and proof records of a past run
- 03Reading incident summaries for post-run analysis
MCP support
The project is an MCP server that exposes read-only CortexPilot workflow, queue, proof, replay and incident data to MCP clients.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
12Saved tool list · updated 2w ago
This tool takes no parameters.
Details
From the project README
Codeflow
AI codes overnight, you ship in the morning
What You Get • Install • How It Work • Ecosystem
Codeflow is the orchestrator for long-haul AI coding tasks. Hand it a spec, walk away, come back to a branch, a diff, and a proof of work.
┌──────────────────────────────────────┐
│ LOCAL-FIRST ████████ 100% │
│ SOURCE-TRACEABLE ████████ 100% │
│ TYPING REQUIRED ░░░░░░░░ 0% │
│ VIBES ████████ ZERO │
│ FILLER│
└──────────────────────────────────────┘
Long-running coding-agent orchestrator. Plan, run, replay, deliver.
What You Get
| Surface | What |
|---|---|
orchestrator apps | Plan it, run it, watch it, replay it. |
packages | Pluggable runners — Codex, Claude, Cline, OpenHands. |
contracts & schemas | Spec, plan, run, artifact. Every step versioned. |
design system | Calm cockpit. No flashing red. No false confidence. |
public skills | Drop into Claude/Codex/OpenClaw. Hand it a spec, get a branch. |
Important
Local-first by default. No silent telemetry. No cloud round-trip. Your data stays on your machine until you explicitly ship it somewhere.
Install
git clone https://github.com/xiaojiou176-open/codeflow.git
cd Codeflow
# follow the per-stack quickstart in INSTALL.md or docs/
Three commands. No curl | sh. No login. Read what you run.
Install break? Open your favorite agent and say "Read AGENTS.md and bootstrap Codeflow for me." Agent fix own brain. Long version: docs/.
How It Work
The repo is seven layers — exactly the seven commits in git log. New work goes in as small named PRs. No 50-file mystery commits.
| Layer | What |
|---|---|
chore: scaffold | License, governance, hygiene gates, CI scaffolding. |
feat(core) | The primary engine. The reason Codeflow exists. |
feat(modules) | Packages, adapters, services, plugins. The second floor. |
feat(contracts) | Schemas, configs, public boundaries. Other code talks here. |
test: | Receipts. Everything in this layer must run. |
feat(ops) | Scripts, infra, CI helpers, build glue. |
docs: | Public docs surface. The pretty face. |
git log reads like a building floor plan. Look once, know the whole shape.
Ecosystem
Codeflow lives in the open family: three open platforms. local-first, source-first, builder-first.
| Repo | What |
|---|---|
| OpenCampus | Canvas + Gradescope + EdStem on one calm desk |
| Codeflow (you here) | AI codes overnight, you ship in the morning |
| OpenUIStudio | brief in, React + shadcn out, proof attached |
Cross-family taste: BeamMe · BrewMe · Codeflow · proofyard.
Star This Repo
If Codeflow saves you a click, an hour, or a headache — star costs zero. Fair trade. ⭐
Also by Yifeng[Terry] Yu
- OpenCampus — Canvas + Gradescope + EdStem on one calm desk
- OpenUIStudio — brief in, React + shadcn out, proof attached
- BeamMe — beam your agent config to any planet
- BrewMe — wake up, news already brewed
- proofyard — every claim ships with its receipt
License
MIT — small print, big freedom.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.