@bitrix24/mcp-vibecode-api

MCP (Model Context Protocol) server for Bitrix24 via the Vibe API. Gives AI assistants 52 tools to work with CRM deals, contacts, tasks, files, users, and 40+ other entity types — plus portal, key, app, infrastructure, bot, AI-credential, placement, and feedback management.

Quick Start

npx @bitrix24/mcp-vibecode-api --key vibe_app_xxx_yyy_zz

The server connects to https://vibecode.bitrix24.tech by default. Override with --api-url:

npx @bitrix24/mcp-vibecode-api --key vibe_app_xxx_yyy_zz --api-url http://localhost:8000

Claude Desktop Configuration

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "vibe-bitrix24": {
      "command": "npx",
      "args": ["-y", "@bitrix24/mcp-vibecode-api", "--key", "vibe_app_xxx_yyy_zz"]
    }
  }
}

For a self-hosted API:

{
  "mcpServers": {
    "vibe-bitrix24": {
      "command": "npx",
      "args": [
        "-y", "@bitrix24/mcp-vibecode-api",
        "--key", "vibe_app_xxx_yyy_zz",
        "--api-url", "http://localhost:8000"
      ]
    }
  }
}

Environment Variables

Instead of CLI flags, you can set environment variables:

Tools (52)

Entity Tools (10)

Portal Tools (1)

Me Tools (1)

Key Tools (6)

App Tools (7)

Placement Tools (1)

Deployment Tools (3)

Infra Tools (3)

Bot Tools (3)

AI Credential Tools (1)

Feedback Tools (1)

API Surface Tools (15)

Typed wrappers around the rest of the V1 surface. Prefer these over call_api when available:

Supported Entities (45)

deals, contacts, companies, leads, quotes, activities, activity-types, products, product-sections, statuses, currencies, deal-categories, requisites, timelines, invoices, items, smart-processes, tasks, calendar-events, files, folders, storages, users, departments, workgroups, chats, messages, list-elements, catalog-products, catalog-sections, catalog-prices, orders, order-statuses, basket-items, payments, sites, pages, doc-templates, documents, bookings, bizproc-templates, bizproc-activities, bizproc-robots, openline-configs, telephony-lines.

Features

• Auto-pagination — requests with limit > 50 automatically paginate through all results
• Custom fields — get_fields returns user-defined fields (UF_*) alongside static schema fields
• MongoDB-style filters — $gt, $gte, $lt, $lte, $ne, $contains, $in operators in search
• Date windowing — large searches auto-split into date windows for reliability (disable with autoWindow: false)
• Cross-entity batch — combine up to 50 calls across different entities in one request via /v1/batch
• Batch search — action: "search" in batch auto-paginates each sub-call individually (up to 5000 records)
• Aggregation — count, sum, avg, min, max with groupBy support

Transports

• stdio (default) — for Claude Desktop, Cursor, and other MCP clients
• HTTP — --http flag starts an authenticated HTTP server on 127.0.0.1:3001

HTTP mode

The HTTP transport is hardened and requires a Bearer token. Start it with:

npx @bitrix24/mcp-vibecode-api \
  --key vibe_app_xxx_yyy_zz \
  --http \
  --http-token "$(openssl rand -hex 32)" \
  --allowed-origins https://your-client.example.com

Or via environment:

export VIBE_MCP_HTTP_TOKEN="$(openssl rand -hex 32)"
npx @bitrix24/mcp-vibecode-api --key vibe_app_xxx --http

Clients call POST http://127.0.0.1:3001/mcp with:

Authorization: Bearer <token>
Content-Type: application/json

HTTP flags

Response codes

The server exits with an error if --http is set without a token. Tokens are never written to logs; startup only names the source (--http-token flag or VIBE_MCP_HTTP_TOKEN env).

Resources

Prompts

API Key Types

• App key (vibe_app_...) — for entity CRUD, search, batch, aggregation, and app management
• Management key (vibe_live_...) — for portal and key management

Get your API key at vibecode.bitrix24.tech.

License

MIT