Skip to main content
The Ruolo Model Context Protocol endpoint is https://mcp.ruolo-dev.cedarai.com/mcp. Sign-in is OAuth with the user’s Cedar account and product=RUOLO (pass-through destage IAM). There is no separate MCP API key.

Recipients

Tool results are returned to the MCP client that made the call. That includes Cursor, Claude, and ChatGPT when a user installs the Ruolo connector. Cedar does not send those results to a third party except as requested by the signed-in user’s client.

What tools can do

Ruolo MCP is not read-only. Catalog tools cover destage RPCs, and a short workflow list sits on top (fill_vacancy, do_not_fill_vacancy, send_crew_call, list_open_vacancies, get_employee). Every call runs as the signed-in operator. Destructive writes require confirm=true:
  • Workflow fills, do-not-fills, and send-call, and the matching catalog tools for those same destage paths.
  • Catalog RPCs whose method is DELETE or whose name/path contains delete, revoke, abolish, award, annul, or suspend.
  • First call without confirm=true returns a preview and does not change destage.
  • Retry the same call with confirm=true after the operator approved.
Config creates and updates (for example call-sheet rules) do not need confirm=true. Destage IAM still applies. Tool results omit email, phone, and SSN fields. Responses larger than 128KiB are refused so a client cannot ingest a full roster board — scope by work area and date.

Connect

Use https://mcp.ruolo-dev.cedarai.com/mcp in Cursor, Claude, or ChatGPT.