mcp
Operate Obriym CRM from any AI assistant: leads, deals, orders, products, guarded writes.
https://obriym-crm.com/api/mcpCurrent observation
This endpoint answered at its latest recorded check.
What this server reports about itself
Self-reported at initialize. Not verified by Licium.
- Server name
- obriym-crm
- Version
- 1.3.5
- Capability keys
- tools, resources, prompts
- Tool names
- search_leads, get_lead, search_deals, get_deal, list_orders, get_order, search_products, get_product, get_dashboard_overview, get_report, search_contacts, get_contact, search_companies, get_company, list_activities, get_activity, list_customers, get_customer, get_workspace_info, create_lead, update_lead, create_deal, create_activity, update_order_status, create_contact, update_contact, create_company, update_company, complete_activity, convert_lead, assign_lead, transition_deal, create_order, add_order_item, update_order_item, remove_order_item, list_pipeline_stages, configure_pipeline, list_lead_sources, set_lead_sources (first 40 recorded; the server may expose more)
An 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 select_workspace 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 get_workspace_info and tell the user which workspace you are operating. Sign-in (OAuth) connections: use list_workspaces to see the user's workspaces and select_workspace to re-bind this connection when the user asks to work in another workspace. API-token connections are permane
Reported Aug 17, 2026, 05:06 AM UTC.
Check history
Oldest to newest. Each row is one recorded check.
- respondsMCP initialize · 8s limit · HTTP 200 · 255ms
- respondsMCP initialize · 8s limit · HTTP 200 · 452ms
- respondsMCP initialize · 8s limit · HTTP 200 · 289ms
- respondsMCP initialize · 8s limit · HTTP 200 · 355ms