Connect your AI Code to Obriym CRM to search and operate permitted CRM workspace records through the secure remote MCP server.
Example path ·
https://obriym-crm.com/api/mcpAn Obriym CRM user can belong to MULTIPLE workspaces (isolated businesses). Every tool operates exactly one workspace — the one this connection is bound to. Nothing in a tool payload can change that. Sign-in (OAuth) connections of a user with several workspaces start LOCKED: every data tool first asks the client to show a workspace selection form when supported; otherwise it returns WORKSPACE_SELECTION_REQUIRED with the workspace list in structured content. Never choose a workspace for the user yourself. After the user selects a workspace, call with that organization id, then retry the user's original CRM request. Before creating or changing data in a session, verify the bound workspace with and tell the user which workspace you are operating. Before writing marketing about Obriym CRM itself, call . Keep claims within its requirements and limitations; publishing-channel readiness and old posts do not establish product capabilities or customer results. Sign-in (OAuth) connections: use to see the user's workspaces and to re-bind this connection when the user asks to work in another workspace. API-token connections are permanently fixed to the workspace that issued the token — to work in another workspace, use a token created there. Every write-tool result echoes the workspace it landed in — repeat it to the user when confirming an action. Tools are added over time, and a client keeps the tool list it read when it connected. If the user asks for something and your list has no tool for it, call : its server.tools names every tool this server has now. If the tool you need is there but missing from your list, your list is outdated — ask the user to refresh the Obriym CRM connection in their AI app (server.refreshHint says how) instead of saying Obriym cannot do it.
1 in the Claude listing