Setup & Configuration

Connect Claude Desktop, Cursor, Claude Code, or any MCP client to your Kasar CRM.

Prerequisites

A Kasar CRM account with an active subscription
An API token created in Settings > API

Create an API Token

Open your Kasar workspace and navigate to Settings > API
Click New token
Give it a name (e.g., "Claude Desktop", "Cursor", "Claude Code")
Optionally set an expiration (30 days, 90 days, 1 year, or never)
Copy the token (ksr_...) — it will only be shown once

The token is bound to the workspace member who creates it. Every MCP tool runs as that member: Kasar re-resolves their identity on each call and applies the same role-based permissions and record visibility they have in the app. The MCP server sees exactly what the user sees, never more.

Treat your API token like a password. Never commit it to version control or share it publicly. If compromised, revoke it immediately in Settings > API and create a new one.

Claude Desktop

Add the following to your Claude Desktop configuration file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "kasar-crm": {
      "type": "http",
      "url": "https://kasar.app/api/mcp",
      "headers": {
        "Authorization": "Bearer ksr_..."
      }
    }
  }
}

Replace ksr_... with your actual API token.

After saving, restart Claude Desktop. You should see the Kasar tools appear in the tools menu.

Cursor

Add the MCP server in your Cursor settings:

Open Cursor Settings > MCP
Click Add MCP Server
Configure:

{
  "mcpServers": {
    "kasar-crm": {
      "type": "http",
      "url": "https://kasar.app/api/mcp",
      "headers": {
        "Authorization": "Bearer ksr_..."
      }
    }
  }
}

Claude Code

Add the server from the command line:

claude mcp add kasar-crm \
  --transport http \
  --url https://kasar.app/api/mcp \
  --header "Authorization: Bearer ksr_..."

Other MCP Clients

Any client that supports the Streamable HTTP transport can connect. Provide:

Parameter	Value
URL	`https://kasar.app/api/mcp`
SSE URL	`https://kasar.app/api/mcp/sse`
Transport	Streamable HTTP (stateless, backed by a Redis session store)
Auth Header	`Authorization: Bearer ksr_...`

Most clients only need the base endpoint https://kasar.app/api/mcp. The /sse endpoint is provided for clients that require the legacy Server-Sent Events transport.

Authentication & Permissions

Property	Value
Method	Bearer token in the `Authorization` header
Token format	`ksr_...` — the same token used for the REST API
Identity	The workspace member who created the token
Permissions	Identical to that member's in-app role and record visibility

There is no separate scope to enable. A single API token grants the MCP server full access to the CRM as that workspace member — records, schema, pipelines, tasks, notes, lists, aggregations, and the connected inbox (email, LinkedIn, WhatsApp). Anything the member cannot see or do in the app is also blocked over MCP.

Read-only members get read-only tools, hidden records stay hidden, and data-model tools (creating objects, fields, lists, enum options) require an admin token. Nothing over MCP can delete CRM records, objects, or fields.

Verify the Connection

Once configured, ask your AI assistant:

"List all objects in my Kasar CRM"

The assistant should read the kasar://schema resource and return a list of your CRM objects (contacts, companies, opportunities, etc.). If you see an authentication error, double-check your token and endpoint URL.

Setup & Configuration

On this page