Obriym CRM logoObriym CRMCustomer flow workspace
FeaturesPricingRoadmapIntegrations
LanguageUKEN
Sign inGet started
FeaturesPricingRoadmapIntegrationsSign in
Automation · Model Context Protocol

Operate your CRM from any AI assistant

Obriym exposes a remote MCP server, so assistants like Claude, ChatGPT, Gemini or Cursor can read your pipeline and take guarded actions — over the same scoped token and permissions as the API, with no direct database access.

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 pipeline

search_leads, get_lead, search_deals, get_deal, list_orders, get_order, search_products, get_product, get_dashboard_overview, get_report.

Take guarded actions

create_lead, update_lead, create_deal, create_activity, update_order_status — each gated by the matching :write scope on your token.

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
Authorization: Bearer <your workspace API token>
Scopes
the same scopes as the REST API (products, leads, deals, orders, …)

Setup

  1. 1

    Create an API token

    In Settings → Developers → API Tokens, generate a token with the scopes you want the assistant to have.

  2. 2

    Add the server to your client

    In Claude, Cursor or any MCP client, add a remote MCP server with the endpoint URL and an Authorization: Bearer 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

  • 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. It is a remote server — you only add the URL and your Bearer token to your client.

Let an AI assistant run your CRM

Generate a scoped token and connect Obriym to your favorite MCP client in minutes.

Start for free
Obriym CRM logoObriym 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

  • Features
  • Pricing
  • Compare
  • Roadmap
  • Integrations
  • API Reference

Company

  • About OBRIYM
  • Founder
  • Contact
  • Roadmap

Developers

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

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

Terms of UseTerms of ServicePayment & RefundsPrivacy PolicyLegal detailsData DeletionPricingAPI Docs