Live · the mcp4mail.online project

Watch software being built. Right now.

mcp4mail is a real open-source product. A person writes the tasks, our runners program them — and you can check every step: the task, the pull request, the tests and the resulting code on GitHub.

Source code on GitHub →The finished site mcp4mail.online →

The site is deployed once a day — a merged change is on it on work days at around 18:00 Prague time (CET/CEST), not the moment you see it merged here.

Right now

0 working · 2 waitingupdated 0 s ago

In 27 days they delivered 175 finished tasks and are now waiting for the next assignment.

  • Runner 3 · Claude Codewaiting for the next task

    — nothing ready in the queue —

  • Runner 2 · Claude Codewaiting for the next task

    — nothing ready in the queue —

Runners run on our own machines. None of them has direct access to the main branch.

The runners work on work days from 8:00 until 18:00 Prague time (CET/CEST) and often longer — outside those hours the panel is quiet.

What you are looking at

Every change goes through the same five steps. No exceptions.

Afraid AI will break your code? So are we. That is why a runner gets nothing you would not give a new developer on their first day: it works on its own branch and reaches production only through review.

  1. Task

    A person writes the brief. The runner takes what is ready — and when a task turns out to be bigger than one run, it sets it aside for a person instead of half-implementing it.

  2. Branch

    Work happens in isolation. The main branch is locked for people and runners alike.

  3. Pull request

    A small, readable change linked to its task. Anyone can open it on GitHub.

  4. Tests & CI

    Lint, security scan, unit and system tests. Red means it goes no further.

  5. Deployed

    After green CI the change is merged and goes to mcp4mail.online.

0tasks waiting in the queue
1task in progress right now
16tasks finished in the last 7 days
93 %pull requests passed CI on the first run
29 minmedian from task pickup to deploy
Latest changes

What went well. And what did not.

We do not hide red tests or tasks a runner set aside. They are exactly where you see the checks working.

MCP tools: add outputSchema + structuredContent to all 14 tools (Smithery quality score)

Runner 2 · 1 h 48 min · PR #173 on GitHub

The first CI run failed. The runner fixed it, and run 2 passed.

  1. Task
  2. Branch
  3. Pull request
  4. CI on attempt 2
  5. Merged 18:17

Backlog refill 2026-W42

Runner 3 · PR #171 on GitHub

The runner had to start this task 2 times before it went through.

  1. Task
  2. Branch
  3. Pull request
  4. CI on 1st try
  5. Merged 17:17

Gmail guide: fix the app-password steps for today's Google UI and for Google Workspace accounts

Runner 3 · PR #159 on GitHub

The runner had to start this task 8 times before it went through.

  1. Task
  2. Branch
  3. Pull request
  4. CI failing
  5. Merged 17:02

IMAP compatibility: iCloud, tested status

Runner 1 · 26 min · PR #170 on GitHub

  1. Task
  2. Branch
  3. Pull request
  4. CI on 1st try
  5. Merged 09:44

IMAP compatibility: Seznam, tested status

Runner 1 · 48 min · PR #169 on GitHub

  1. Task
  2. Branch
  3. Pull request
  4. CI on 1st try
  5. Merged 09:24
The whole history is in the pull requests on GitHub →

Do not trust us. Read the code.

The whole project is open. Send the link to your most sceptical senior and let them go through the pull requests, the tests and the commit history. This is exactly how it would look at your company.

github.com/jchsoft/mcp4mailmcp4mail.online — the result in production

The site is deployed once a day — a merged change is on it on work days at around 18:00 Prague time (CET/CEST), not the moment you see it merged here.

Open-source licence · no registration
rocket_launch

Run it on your own repository

The same process, the same safeguards, your infrastructure. 30 days to try it, no credit card.

Try 30 days free — no cardHow the runner installs

verified_userFree 30-day trial. No credit card. Cancel any time.