Vibe-Kanban MCP + Codex Integration

This repository sets up an automation pipeline where the Vibe-Kanban MCP manages tasks, creates GitHub PRs, and then listens for Codex feedback in PR comments before moving on to the next task. Think of it as giving your project a smart foreman who keeps the line moving.

---

🚀 Overview

• MCP: Handles task execution, creates branches/PRs, and queues work.
• Codex: Acts as a reviewer, leaving structured comments in PR threads.
• Loop: MCP reads Codex’s reply. If ✅ approved, the MCP advances to the next task. If ❌ flagged, MCP logs the issue or retries.

---

🔧 Setup Instructions

1. Clone the repo

   git clone https://github.com/<your-org>/<your-repo>.git
   cd <your-repo>

2. Install dependencies Ensure you’ve got Python 3.10+ and Node.js 18+.

   pip install -r requirements.txt
   npm install

3. Configure GitHub access

   • Generate a GitHub Personal Access Token (PAT) with repo and workflow scopes.

   • Add it to your environment:

     export GITHUB_TOKEN=ghp_xxx

4. Configure Codex endpoint Update config.yaml with the URL/credentials for Codex’s API or comment parser.

---

🔄 Workflow

1. MCP picks the next task from the queue.

2. MCP creates a new branch and PR.

3. GitHub CI runs (tests, linting, build).

4. Codex leaves a PR comment with its review.

5. MCP reads Codex’s reply:

   • If ✅ pass → merge PR or move to next task.
   • If ❌ fail → log issue or retry.

---

✅ Acceptance Criteria

• MCP successfully parses Codex’s PR comment.
• Next task is only triggered if Codex approves.
• Workflow runs safely on a test branch/repo first.
• No impact on live main branches until validated.

---

📜 Example Task JSON

Here’s the task format MCP expects:

{
  "id": "1.0.0",
  "goal": "Test MCP-Codex integration in a safe repo",
  "guardrails": ["Use test branch", "Don’t touch main"],
  "spec": { "ui": [] },
  "files_to_change": ["scripts/mcp_workflow.py"],
  "verify_commands": ["Check Codex reply in PR comments"],
  "acceptance_criteria": [
    "Codex response parsed",
    "Next task triggered automatically"
  ],
  "completion_phrase": "The MCP-Codex integration is tested and working."
}

---

📖 Notes

• Start in a test repo until you trust the workflow.
• Keep Codex replies structured (✅/❌) so MCP can parse easily.
• Document changes as you go for clarity.

---

🏁 Completion Phrase

“The MCP-Codex integration is tested and working in the test environment.”