Skip to main content
The customer Model Context Protocol endpoint is https://mcp.arms.cedarai.com/mcp. It is the ChatGPT / OpenAI plugin connector surface. Sign-in is OAuth with the user’s Cedar account (pass-through IAM). There is no separate MCP API key and no named MCP access config.

Recipients

Tool results are returned to the MCP client that made the call. That includes ChatGPT when a user installs the Cedar ARMS connector, and other MCP clients such as Cursor or Claude Desktop. Cedar does not send those results to a third party except as requested by the signed-in user’s client. Cedar staff operator tools (writes) are not part of this connector listing. They live on a separate MCP app path used internally and are not registered on the customer /mcp tool list that ChatGPT scans.

What tools return

Customer /mcp is read-only (list / get / search of public ARMS APIs). Sensitive fields are minimized on the highest-volume and free-text results:
  • Inventory and customer results keep operational identifiers such as resourceId, equipment initial/number, customer names, city, and state.
  • Inventory and customer results omit uuid, resourceUuid, street lines, postal/ZIP codes, email, and phone.
  • Nested waybill objects are reduced to a short summary (no party address books).
  • Inventory equipment objects omit embedded notes. Notes tools still return note records, with body text (content / snippets) and author email removed.
railcar_list_inventory also defaults to 25 rows (max 50) so a single call cannot dump an entire inventory. Other read tools can return shipment, billing, customer/business, location, or operational data that the signed-in user is already authorized to view in ARMS. Only connect an MCP client you trust to handle that data. This page describes the MCP connector’s data flow. It does not replace Cedar’s privacy policy or terms.