WireCat b24

dev.wirecat由 wirecat.dev 發布v0.5.0更新於 Nov 7, 2026

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

發布方自己的服務:Wire Cash: bank wire fees and transfer costs

已驗證STDIO僅桌面效率與工作流商業與電商

概覽

AI 產生的概覽

一個由本機 CLI 驅動的 MCP 伺服器,讓助理讀取與修改 Bitrix24 入口網站的 CRM:交易、潛在客戶、聯絡人、公司、銷售流程與產品。

可以做什麼
  • 列出並搜尋交易、潛在客戶、聯絡人與公司,也可從本機副本離線查詢。
  • 在銷售流程階段之間移動交易,並更新聯絡人、公司與產品記錄。
  • 呼叫任意 Bitrix24 REST 方法,支援試運行預覽及其權限檢查。
  • 把入口網站中的銷售流程、公司、聯絡人、交易與潛在客戶同步到共用的本機 WireCat 儲存區。
  • 在 WireCat 其他資料旁搜尋已儲存的 CRM 記錄,輸出 JSON 並附錯誤碼方便腳本處理。
適用情境
當助理需要處理 Bitrix24 入口網站的銷售流程時使用,例如檢視未結交易、推進階段或更新聯絡人與公司資訊,適用於終端機型代理或 MCP 用戶端。
執行需求
透過 npx 在本機執行,需要 Node.js 22.16 以上的 22.x,或 Node.js 24 以上。需要一個具備 crm 與 user 權限範圍的 Bitrix24 傳入 Webhook,在入口網站建立後貼到指定名稱的設定檔中,並保存在系統鑰匙圈。僅限桌面端;即時讀寫需要能連線到入口網站的網路。
安裝前請注意
Webhook 位址等同密碼,擁有建立它的員工的權限,應視為機密。寫入會變更入口網站資料:刪除會先詢問,把記錄指派給其他員工預設會被拒絕,階段變更可能觸發入口網站自身的機器人並寫入客戶資料。發訊息、發布與啟動自動化的方法預設會被拒絕。重複寫入可能產生重複記錄,結果不明時應先核對。B24_READ_ONLY=1 可阻止所有寫入。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 WireCat b24,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

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.

來源:README.md,提交 8055ffe

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.5.0最新Nov 7, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

其他 Wire 整合