Human-in-the-loop for Roo Code
Roo Code runs autonomous coding sessions in VS Code with per-project MCP configuration you can commit to the repo. Drop Orako into .roo/mcp.json and every mode, from architect to code, can ask the teammate who owns a decision instead of guessing.
Connect Orako to Roo Code
- 01
Create .roo/mcp.json at the project root with the snippet below (or use Roo's MCP panel).
- 02
Roo Code lists
ask_specialistwith its MCP tools across all modes. - 03
Questions go to the domain owner via Orako; the session picks up on the claimed answer.
{
"mcpServers": {
"orako": {
"command": "orako",
"args": ["mcp", "--server", "https://app.orako.io"],
"env": { "ORAKO_TOKEN": "<your token>" }
}
}
}Project config wins over global when both define the same server, and .roo/mcp.json is committable, so the whole team shares the same Orako setup.
New to MCP in Roo Code? See Roo Code’s docs.
What Roo Code can ask
Roo Code's modes, with a human answer one tool call away.
Architect mode with real constraints
Roo's architect mode drafts a plan that hinges on whether the API must stay backward compatible. It asks the owner and plans against the actual constraint.
Shared config in the repo
Because .roo/mcp.json is committed, every contributor's Roo session has the same ask-a-human tool, and every answer feeds the same team knowledge base.
Risky changes with sign-off
Before touching the payment webhook handler, Roo asks the payments owner what invariants must hold. The answer is recorded, attributed, and reusable.
Roo Code + Orako, answered
Does Roo Code support MCP natively?
Yes. Roo Code reads global servers from mcp_settings.json and project servers from .roo/mcp.json at the repo root, both under an mcpServers object. When both define the same server, the project file wins.
Should I commit .roo/mcp.json with the Orako entry?
Yes, that's the point of project scope. Keep the token out of it: leave env empty and let each developer authenticate with orako init, which stores tokens in ~/.orako/credentials.json instead of agent config files, so nothing secret lands in git.
Do my teammates need this agent installed to answer?
No. Only the developer running the agent connects Orako. The people answering receive each question in Slack, Microsoft Teams, Discord, or the Orako dashboard, claim it there, and reply in the thread. They never touch an editor, a terminal, or an MCP config.
What happens to the answers?
Every resolved conversation is saved to your organization's knowledge base with a confidence score. Agents call search_knowledge before asking, so a question your team already answered is served from the knowledge base instead of pinging anyone again.
Put a human in the loop for Roo Code
Give Roo Code the one thing it can’t generate: the answer only your team knows.