WireCat b24

dev.wirecatPublished by wirecat.devv0.5.0Updated Nov 7, 2026

A Bitrix24 portal's CRM for agents over MCP. Sign in with the b24 CLI first.

The publisher's own server: Wire Cash: bank wire fees and transfer costs

Overview

AI-generated overview

A local CLI-backed MCP server that lets an assistant read and update a Bitrix24 portal's CRM — deals, leads, contacts, companies, pipelines and products.

What you can do
  • List and search deals, leads, contacts and companies, including offline from a local copy of the CRM data.
  • Move deals between pipeline stages and update contact, company and product records.
  • Call any Bitrix24 REST method with a dry-run preview and the permissions it checks.
  • Sync pipelines, companies, contacts, deals and leads from the portal into the shared local WireCat store.
  • Search stored CRM records alongside other WireCat data, with JSON output and error codes for scripting.
When to use it
Use it when an assistant needs to work with a Bitrix24 portal's sales pipeline — reviewing open deals, moving stages, or updating contact and company details — from a terminal-based agent or an MCP client.
Requirements
Runs locally via npx and needs Node.js 22.16+ (22.x) or Node.js 24+. A Bitrix24 incoming webhook with the crm and user scopes, created in the portal and pasted into a named profile; it is stored in the system keyring. Desktop only; network access to the portal for live reads and writes.
Before you install
The webhook address acts as a password with the rights of the employee who created it, so treat it as a secret. Writes change portal data: deletes ask first, assigning records to other employees is denied until allowed, and stage changes can trigger the portal's own robots that may write to clients. Messaging, publishing and automation-starting methods are denied by default. A repeated write can create a duplicate record, so check after an unknown outcome. B24_READ_ONLY=1 blocks all writes.

Installation

In SourceWeft

  1. Open WireCat b24 in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

b24 — Bitrix24 CRM CLI for AI agents

b24 reads and changes a Bitrix24 portal's sales data from the terminal, from scripts and from AI agents: deals, leads, contacts, companies, pipelines and their stages, products and employees. It signs in with one of the portal's incoming webhooks and acts with the rights of the employee who made it. Deals and leads are copied into the local WireCat store, so lists and search work offline, beside your other WireCat tools' data.

Quick start

sh
npm install -g @wirecat/bitrix24-clib24 skill install                 # the agent skill, for Claude Code, Codex, Gemini CLI and OpenClawb24 work session start            # paste the webhook address; it is kept in the keyringb24 work sync                     # copies pipelines, companies, contacts, deals and leads into the local storeb24 work deals list status:open

work is a profile: a name you choose for one portal. It is the first word of every command that uses an account, and none is ever assumed. Make the webhook in Bitrix24 under Developer resources → Other → Incoming webhook, with the scopes crm and user. You need Node.js 22.16 or a later 22.x, or Node.js 24 or later. b24 doctor needs no network and shows what is set up.

More: installation, usage.

What you can do

sh
b24 work leads list stage:"In progress" --json      # from the store, offline toob24 work deals move deal:42 "Contract signed"       # checks deals.move, and deals.close for a won or lost stageb24 work search all kitchen                         # stored deals and leads beside your other WireCat datab24 work people update 4 --body '{"post":"Buyer"}'  # a contact, in Bitrix24's own field namesb24 work api call crm.deal.fields --dry-run         # any REST method, with every permission it checks

Every write answers an operation_id and can be previewed with --dry-run. More: usage and the command reference.

For AI agents

  • An agent with a terminal (Claude Code, Codex, Gemini CLI, OpenClaw): b24 skill install writes the skill, the agent's instruction sheet.
  • An MCP client: b24 work mcp serve, or b24 work mcp add claude-code. mcp serve --permission deals=deny tightens the levels for one server; an agent can never loosen them.
  • ChatGPT or Claude in a browser: b24 work mcp serve --http behind your own tunnel.

Text from the portal is marked untrusted in MCP answers: it is data for the agent, never instructions. api call and session start/end are never offered over MCP. With --json, every command prints one JSON value, and an error comes as JSON with a code to branch on.

More: agents.

Settings and permissions

Each profile has a permission level for every command and every REST method: allow, ask, readonly or deny. Assigning a record to another employee is denied until you allow it, a delete asks first, and methods that message people, publish or start the portal's automation are denied, reads too. A stage change can start the portal's own robots, which may write to your clients: set permissions.deals.move to ask if your portal has such robots. B24_READ_ONLY=1 refuses every write.

More: settings, security.

Limits

  • The portal allows about 2 requests a second for all its apps together; b24 keeps to that pace.
  • people, organizations, products, users and fields still ask the portal on every read and refuse --offline.
  • Bitrix24 does a repeated write again: on a live portal, a create repeated with the same Idempotency-Key made a second record. After an outcome_unknown, look at the record before you write it again.

Security

The webhook address is the password: anyone who has it can do what its employee can. b24 keeps it in the system keyring and never prints it, in output, errors or run records. Report a vulnerability as SECURITY.md says.

When it does not work

Start with b24 doctor, then troubleshooting.

Documentation

Part of WireCat

b24 is one of the WireCat tools. They share one local store, so search all and an agent see your CRM beside your messages, mail, notes and meetings.

License

Apache-2.0.

Source: README.md at commit 8055ffe

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.5.0LatestNov 7, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Wire integrations