WorkBuddy Codex Hub MCP
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
WorkBuddy Codex Hub MCP v0.1
A local MCP server for coordinating two coding agents through a shared SQLite task pool and an explicit review workflow.
This project is an early v0.1 implementation. It provides a runnable MCP server, a SQLite schema, agent prompt templates, examples, and a smoke test that exercises the core tool flow. It does not yet provide autonomous scheduling, a web dashboard, hosted execution, or production hardening.
What It Does
Lets agents query open tasks from a shared SQLite database.
Lets one agent claim and submit work for a task.
Requires review by a different registered agent.
Records review decisions and scores.
Stops repeated change-request loops after
max_iterations.
Related MCP server: vibecheck
MCP Tools
Tool | Purpose |
| List open and pending-review tasks. |
| Claim an open task for one agent. |
| Store submitted code for a module and move the task to |
| Assign a different agent as reviewer and move the task to |
| Record review feedback and complete, reopen, or reject the task. |
Quick Start
npm install
npm test
npm startThe default database path is ./project_hub.db. Override it with:
HUB_DB_PATH=/path/to/project_hub.db npm startTo create sample tasks:
sqlite3 project_hub.db < examples/sample_tasks.sqlAgent Setup
Copy the relevant prompt file into each agent:
SKILL_workbuddy.mdSKILL_codex.md
Both agents must connect to this MCP server and use the same SQLite database path.
Verification
npm testThe smoke test starts the compiled MCP server and checks:
tool listing
normal query, claim, submit, review, approve flow
unknown agent rejection
double-claim rejection
self-review rejection
wrong-reviewer rejection
max-iteration rejection
Publishing
Before publishing, update repository metadata for your actual GitHub location and run:
npm test
npm audit --omit=dev --audit-level=lowThis repository includes:
smithery.yamlfor stdio startup configuration.Dockerfilefor registry or hosted builds.LICENSEwith MIT terms.
See PUBLISH_TO_SMITHERY.md for a conservative publishing checklist.
Current Limits
No automatic task scheduler.
No concurrent write locking beyond SQLite and task status checks.
No web UI.
No hosted service.
No claim that this is unique in the market.
No claim that registry installs or GitHub stars are predictable.
License
MIT. See LICENSE.
This server cannot be deployed
Maintenance
Related MCP Connectors
Coordination hub for AI coding agents: message teammates, ask humans, audit every event.
Task tracking built for coding agents. Work is leased, so two agents never take the same SubTask.
Shared task board and knowledge base for AI coding agents Give your coding agents a shared task board and knowledge base, so the plan survives between sessions and across agents.
Coding agents from Claude Code, Cursor and Codex claim jobs and lock files on one shared board.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceCoordinates parallel AI coding agents by providing task ownership, scoped file locks, handoffs, and verification workflows.MIT
- FlicenseAqualityBmaintenanceEnables coding agents to track and coordinate project work through a shared SQLite ledger, including task plans, session ancestry, claims, work locations, blockers, and commits via MCP tools.9-
- FlicenseNot gradedqualityCmaintenanceEnables two coding assistants to coordinate task creation, claiming, messages, and completion through a shared local workflow queue while using GitHub issues, branches, commits, and PRs as the source of truth.-
- AlicenseNot gradedqualityBmaintenanceEnables multiple AI coding agents to work concurrently on the same repository by coordinating task ownership, file locks, architectural decisions, investigation gaps, handoffs, and audit activity through a local SQLite-backed MCP interface.12 npmMIT