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 集成