Skip to main content
Cedar CREW Model Context Protocol endpoints use OAuth with your Cedar account and product=CREW. There is no separate MCP API key. Access requires the railroad’s CREW entitlement and your existing IAM permissions.

Recipients

Tool results are returned to the MCP client that made the call.⁠‌​‌‌‌‌​​‌​​‌‌​​‌​​​​​​‌​⁠ That includes Cursor, Claude, and ChatGPT when a user installs the Cedar CREW 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

Cedar CREW MCP is not read-only.⁠‌​‌‌‌‌​​‌​​‌‌​​‌​​​​​​‌​⁠ Catalog tools cover Cedar CREW 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 API 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 records.
  • 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. Your railroad entitlement and IAM permissions still apply. 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

Create a new connector in Cursor, Claude, or ChatGPT using the endpoint for your environment, then sign in with your Cedar account. Call get_crew_guide for the workflow guide and list_crew_tools to see available tools.