A small ecosystem of open-source MCP servers, like ask-human-mcp, call-a-human-mcp and claude-slack-bridge, solves a real problem: your coding agent should ask instead of guessing. They give the agent a tool that pings you (macOS dialog, Slack, Telegram) and blocks until you answer. If you work alone, use one of them. They’re good. Orako exists for the moment that model breaks: when the person with the answer isn’t you but a teammate, when nobody should be a single point of failure, and when the same question shouldn’t get asked twice.
Key takeaways
- DIY ask-human MCP servers are the right tool for a solo developer: free, local, ten-minute setup, one human (you).
- They stop scaling at the team boundary: one hardcoded recipient, blocking calls, no escalation when that person is away, no shared record of answers.
- Orako keeps the same agent-side pattern (an MCP tool) but adds dispatch by domain, first-to-claim ownership, automatic escalation, and a team knowledge base.
- Migration is a config swap: both sides speak MCP, so your agent doesn’t change.
Side by side
DIY ask-human MCP servers compared with Orako
| DIY MCP server (ask-human-mcp & co.) | Orako | |
|---|---|---|
| Who answers | You. The recipient is wired into the config | The teammates who own the question's domain; the first to claim answers |
| Channels | Terminal, macOS dialog, Slack or Telegram depending on the project | Slack, Microsoft Teams, Discord, or the dashboard inbox, per person |
| If nobody answers | The tool call blocks until reply or timeout; the question dies with it | Nudge → back to the pool excluding the silent owner → team-channel alert |
| Answer reuse | None. Answers live in a chat scrollback | Searchable knowledge base, confidence-scored, contested answers flagged |
| Team semantics | None (single-user by design) | Organizations, domains, roles, per-member channel preferences |
| Cost & hosting | Free, open source, runs on your machine | $12/seat/month SaaS (14-day trial) or self-hosted Enterprise |
The failure mode DIY can’t fix
Every DIY server shares one assumption: the human it pings is available and is the right person. On a team, both assumptions fail weekly. The backend owner is in a meeting; the question was really for whoever owns payments; the intern answered from memory and got it wrong; the same seat-limit question got asked three times in a month. Routing, escalation, and a knowledge base aren’t features on top of ask-a-human. Past one user, they are ask-a-human.
Fair point
When a DIY server is the right callHonest rule of thumb: one human in the loop, use a DIY server. Two or more humans, or answers worth keeping, that’s the job Orako was built for. Don’t pay for seats you don’t need.