Human-in-the-loop for Cursor
Cursor's agent mode moves fast across your codebase, but the humans who own the answers aren't watching the editor. Connect Orako over MCP and Cursor can reach the right person the moment it's unsure. The answer comes back inline, and the resolved conversation becomes searchable team history for the next session.
Connect Orako to Cursor
- 01
Merge the snippet below into .cursor/mcp.json (project) or ~/.cursor/mcp.json (global).
- 02
Cursor prompts you to approve access in the browser the first time it calls an Orako tool. The
asktool then appears in Cursor's MCP tool list. - 03
Cursor asks through Orako whenever it needs a human decision, and continues when the answer returns.
{
"mcpServers": {
"orako": { "type": "http", "url": "https://app.orako.io/mcp" }
}
}Cursor prompts you to authorize in the browser the first time it calls an Orako tool — no separate rule file needed. The agent's guidance ships with the server itself.
New to MCP in Cursor? See Anysphere’s docs.
What Cursor can ask
Keep Cursor's agent unblocked without a Slack tab.
Ambiguous tickets, resolved inline
The ticket says "improve the onboarding" and nothing else. Cursor asks the PM who wrote it which screen matters first, and gets a reply without you alt-tabbing to Slack.
Ownership questions across services
Cursor finds two services touching the same pricing logic. It asks who owns the canonical one before editing, instead of patching both and hoping.
Design intent for empty states
The mock doesn't show what an empty dashboard looks like. Cursor asks design through Orako and implements the intended state, not a placeholder guess.
Cursor + Orako, answered
Does Cursor support MCP natively?
Yes. Cursor loads MCP servers from .cursor/mcp.json in the project or ~/.cursor/mcp.json globally. Orako connects as a remote HTTP server, declared with just a type: "http" field and a URL, so there's no binary to install and no token to configure.
Does this work in Cursor's agent mode and composer?
MCP tools are available to Cursor's agent, which is where Orako matters: long multi-file runs where one wrong assumption propagates. The agent calls ask like any other tool, and the run continues once a teammate replies.
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, Discord, or the Orako dashboard and reply in the thread. They never touch an editor, a terminal, or an MCP config.
What happens to the answers?
Every resolved conversation becomes searchable team history with its authors, date, tags and full context. Agents call search_history before asking, so a question your team already answered can be reused instead of pinging anyone again.
Put a human in the loop for Cursor
Give Cursor the one thing it can’t generate: the answer only your team knows.