An open-source MCP server built by autonomous AI developers: the numbers
说明与用途
在42天内,两人团队使用自治AI开发者完成了开源MCP服务器mcp4mail的所有编码、测试、CI和合并工作。完成182项任务、146个PR、记录140小时工作,首次CI通过率达90%。
问题
How to build and maintain an open‑source product with minimal human intervention while ensuring quality and reliability.
结果
In 42 days, 182 tasks were finished, 146 PRs merged, 140 hours logged, and 90 % of PRs passed CI on first run. The system handled CI failures automatically and required human intervention only for planning and deployment.
工作流
- 1. Create a task with brief, context, acceptance criteria and add to queue
- 2. Runner picks task, selects model (Claude Code) and starts coding CLI
- 3. Coding CLI writes code, tests, runs project tests, opens PR linked to task
- 4. CI runs lint, security scan, unit and system tests; if any fail, PR stays open
- 5. If CI passes, PR is merged after linear history and status checks
- 6. Deployed changes are picked up by hosted instance daily around 18:00 Prague time
- 7. Runner monitors progress, respects daily quota, logs, and handles failures by creating urgent tasks or retrying
证据
I run a two-person software company in the Czech Republic. For the last six weeks I have been running an experiment in public: an open-source product where the code, the tests, the pull requests and the merges are done by AI developers, and a person steps in only where a person is actually needed.
The product is called mcp4mail. This article is the story of how it was built, with the numbers, and with links that let you check every one of them yourself.
As of 30 October 2026, from the live page: Days of development 42, Tasks finished 182, Pull requests merged 146, Hours of work logged 140, Pull requests that passed CI on the first run 90 %
The runner is a single binary that runs on one of our own machines. It picks the next task that is ready, triages it, chooses a model, and starts a coding CLI.
- 记录日期: 2026-11-02T04:28:46.898Z