Cursor

Prerequisites: the riby and riby-mcp binaries installed and riby login completed on this machine. If not, start with the quickstart.

Add the server

Cursor reads MCP servers from mcp.json. Global (all projects):

{
  "mcpServers": {
    "riby": {
      "command": "riby-mcp"
    }
  }
}

Or per project, checked into the repo:

{
  "mcpServers": {
    "riby": {
      "command": "riby-mcp"
    }
  }
}

No arguments, no environment variables. The server reads credentials from ~/.riby/config.json, written by riby login — so a project-level config is safe to commit, and each collaborator logs in once on their own machine.

To name the session explicitly instead of the default folder · branch label, add "env": { "RIBY_SESSION_NAME": "my-session" } to the server entry (100 characters max).

Verify

Open Cursor Settings, find the MCP section, and confirm riby is listed and enabled with four tools: request_permission, request_plan_check, request_steering, check_pending. Then ask the agent for a test page:

Use the riby request_permission tool to ask me before deleting anything.

The tool call blocks until you answer from your phone or the dashboard. While it waits, Riby emits a progress notification every 20 seconds so Cursor treats the call as alive rather than hung.

Teach the agent when to page

The server is the mechanism; the policy lives in the page-your-human skill. Add its rules to your Cursor project rules so the agent pages for irreversible actions and plan sign-offs, and stays quiet otherwise.