Obriym CRMObriym CRMCustomer flow workspace
AIFeaturesGetting startedPricingRoadmapIntegrationsBlog
Sign inGet started
AIFeaturesGetting startedPricingRoadmapIntegrationsBlog
Automation · Model Context Protocol

Operate your CRM from any AI assistant

OAuth shows the active CRM account before access is granted and lets you switch accounts immediately. After approval, Claude, ChatGPT, Gemini or Cursor operates only within your role and selected workspace.

Get your tokenAll integrations
obriym-crm · mcp

assistant → call tool

search_leads({ status: "stale" })

server → result

{ "data": [
    { "name": "Acme Ltd", "score": 42, "nextAction": "Call back" }
  ], "total": 7 }

scope-checked · workspace-isolated

The Model Context Protocol (MCP) is the emerging standard that lets AI assistants use external tools. Obriym ships an MCP server as a thin third boundary over the same shared operations as the Public API — every tool checks your token's scope and the workspace subscription before it runs, and nothing touches the database directly. Point any MCP-aware assistant at it and it works inside your CRM in natural language.

What an assistant can do

Read your whole CRM

search_leads, get_lead, search_contacts, get_contact, search_companies, get_company, search_deals, get_deal, list_activities, get_activity, list_customers, get_customer, list_orders, get_order, search_products, get_product, get_dashboard_overview, get_report, get_workspace_info, list_workspaces.

Take guarded actions

convert_lead, assign_lead, transition_deal, create_order with line items, create/update leads, contacts, companies and deals, create and complete activities, update order status — each gated by the matching :write scope on your token.

Inspect & tune the setup

list_pipeline_stages, list_lead_sources, configure_pipeline and set_lead_sources — the assistant can read your workspace configuration and adjust a pipeline stage or lead source.

Connection

A remote, stateless Streamable HTTP server — nothing to install.

Endpoint
https://obriym-crm.com/api/mcp
Protocol
Model Context Protocol (Streamable HTTP, stateless)
Auth
OAuth 2.1 one-click sign-in, or Authorization: Bearer <your workspace API token>
Scopes
the same scopes as the REST API (products, leads, deals, orders, …)

Connect your AI assistant

Add the MCP server to your AI client. Cursor and VS Code install in one click; the rest take the URL above and sign in with OAuth.

MCP server URL

https://obriym-crm.com/api/mcp

Sign in with your Obriym CRM account — no token or app setup needed.

Cursor

Add to Cursor
One-click

VS Code

Add to VS Code
One-click

Claude Code

claude mcp add --transport http obriym-crm https://obriym-crm.com/api/mcp

Run in your terminal, then /mcp to sign in.

CLI

ChatGPT

Manual
  1. 1Settings → Connectors → Add custom connector (Developer Mode).
  2. 2Paste the MCP server URL above and choose OAuth.
  3. 3Sign in with your Obriym CRM account.

Claude (web & desktop)

Manual
  1. 1Settings → Connectors → Add custom connector.
  2. 2Paste the MCP server URL above.
  3. 3Sign in with your Obriym CRM account.

Setup

  1. 1

    Sign in or create an API token

    For a personal AI client, choose OAuth: Obriym shows the active CRM session, name and email before approval. For server automation, create a scoped Bearer token.

  2. 2

    Add the server to your client

    Add the server URL. With OAuth, approve the displayed account or choose “Use another account”; with Bearer, pass the token in the Authorization header.

  3. 3

    Work in natural language

    Ask the assistant to find stale leads, summarize a deal, or update an order status — it calls the matching tool for you.

Safe by design

  • A per-workspace paid capability — MCP needs a Team or Scale plan. OAuth uses the active CRM session but always shows its name and email and requires explicit approval for a new AI client.
  • Multiple workspaces — explicit, no surprises: all CRM data stays blocked until selection; get_workspace_info shows the connected account and workspace, list_workspaces lists available ones, and select_workspace changes it only on your request.
  • Revoking access in the Integration Center deletes the access token, refresh token, OAuth consent and workspace binding — reconnecting requires approval again.
  • Same permissions as the API — a tool never exceeds your token's scopes.
  • Inactive paid workspaces are blocked, exactly like the API.
  • Rate-limited per tool; no direct database access — only the shared, audited operations.
  • Opt-in per deployment — the endpoint returns 404 until it is enabled.

Frequently asked questions

Which assistants work?

Any MCP-compatible client — Claude (desktop and web), ChatGPT, Gemini, Cursor, and other MCP-aware tools.

Is it the same as the REST API?

It reuses the exact same shared operations, token and scopes as the Public API — MCP is a third protocol boundary over them, not a new data surface.

Do I need to install anything?

No. Add the URL and sign in with OAuth — Obriym shows the active account before approval and lets you switch it. A Bearer token remains available for machine clients.

I have several workspaces — where does the assistant write data?

Into exactly one. With several workspaces the connection starts locked and the assistant must ask you to choose before any data read. get_workspace_info also shows the connected account name and email; list_workspaces and select_workspace let you verify or change the workspace.

Let an AI assistant run your CRM

MCP is included on the Team and Scale plans. Pick a plan, generate a scoped token, and connect Obriym to your favorite MCP client in minutes.

See plans
Obriym CRMObriym CRMCustomer flow workspace

Obriym CRM is a focused workspace for sales teams and e-commerce operations. Leads, deals, orders, and customer retention in one place.

Product by OBRIYM

  • crm@obriym.com
  • OBRIYM
  • Serhii Oberemchuk

Individual Entrepreneur Oberemchuk Serhii Oleksandrovych · State reg. 178752761226

Product

  • AI
  • Features
  • Getting started
  • Pricing
  • Compare
  • Blog
  • Roadmap
  • Integrations
  • API Reference

Company

  • About OBRIYM
  • Founder
  • Contact
  • Roadmap

Developers

  • For developers
  • OpenAPI spec
  • JS Widget
  • Lead intake API
  • Orders API

©2026Obriym CRM by OBRIYM. Built for production sales and e-commerce teams.

Terms of UseTerms of ServicePayment & RefundsPrivacy PolicySubprocessorsData ProcessingLegal detailsData DeletionPricingAPI Docs