v0.5.0 — 多系统目标、系统说明与授权名称

让客户端认清业务系统和授权对象

例如，用户希望“先查保温杯库存，有货再把商城对应商品改为 59 元并上架”。配套客户端可以使用会话中已选的库存与商城授权，各动作保留原系统、原会话和审批归属。业务能力与两边商品映射需要预先接入并确认。

SDK 0.5.0 为这一流程提供多系统会话归档绑定、首次能力搜索前的系统说明，以及业务后端提供的授权主体名称。名称可对应组织、账户、项目或门店，只用于展示；不会取代内部连接与授权身份。完整会话范围与执行协调由 DSH 或自研宿主实现。

升级

先准备 Core 0.7.0，自研客户端安装 bailinghub-mcp-server@0.5.0 并核对目标目录、范围、持久记录和名称展示。使用 DSH 的用户安装配套 dsh-bailinghub@0.5.0，它携带精确 SDK 依赖。保留旧会话与连接，不按展示名称重建授权。旧同系统能力和现有 Client Token 模式继续兼容。

已有独立 MCP 入口保留原有工具形态；不能把升级 SDK 描述为所有 MCP 客户端自动支持多系统会话。本版限同一 Hub/审计域，未选目标不得接收本轮业务请求，介绍与名称不会扩大权限或跳过审批。

完整说明与升级步骤 · 中文 SDK 接入指南

English

SDK 0.5.0 supports the matching Core 0.7.0 / DSH 0.5.0 flow for explicitly selected business systems. It adds cross-system archive bindings, system descriptions available before tool discovery, and business-provided authorization display names. Hosts retain responsibility for scope selection, persistence and orchestration.

Install bailinghub-mcp-server@0.5.0 after upgrading Core, preserve existing connections and stored sessions, and integrate the documented host-facing fields. Names remain display metadata; permissions, approvals and invocation identities remain separate. The standalone MCP entry retains its existing tool surface. See the bilingual release notes for compatibility and validation steps.

发布维护者文档随源码提供，不包含在 npm 包内；请在线查看 release procedure / 发布流程。

BailingHub MCP / SDK 0.4.0：连接对话与业务执行记录

BailingHub MCP / Agent Client SDK 0.4.0

简体中文

把用户请求、助手可见回复和业务执行记录连起来。

例如，用户在一段对话里比较两家已经分别授权的门店。接入本版 SDK 的客户端可以把整段可见对话归档到 BailingHub，让管理员追溯“问了什么、回答了什么、每家门店实际执行了什么”，同时保留各份授权独立的执行和审批记录。

新增归档功能推荐配合 BailingHub Core 0.6.1，以及负责记录和同步对话的客户端使用；接口最低需要 Core 0.6.0。SDK 提供同步接口；它本身不会自动采集聊天或增加账号选择界面。

谁该升级，如何开始

• **使用 DSH 等原生客户端：**通过客户端的配套版本升级，按其指南选择会话可用账号。单独安装 MCP 命令不会增加多账号会话界面。

• **开发自己的 Agent 客户端：**使用 Node.js 20.15 或更新版本，安装精确 SDK 版本，再按中文 SDK 指南接入：

  npm install --save-exact bailinghub-mcp-server@0.4.0

  SDK 从 bailinghub-mcp-server/sdk 导入。新增 syncConversationArchive 支持授权成员确认、可见文本与原运行记录关联、分批上传及幂等补传；客户端负责持久保存待发送事件和恢复状态。

• **在 MCP 应用中连接固定业务路由：**原 Client Token 和 Agent Session 用法继续兼容。按中文 MCP 安装指南将包版本固定为 0.4.0。独立 MCP 工具和 Registry 入口不会自动采集对话。

升级不需要改写业务 API 声明。低于 0.6.0 的 Core 可以继续使用既有调用流程，但不支持新增归档；客户端应明确提示，而不是显示同步成功。对话补传不会重新执行业务动作，也不会放宽原有授权。合并正文仅供有权限的管理员审计，不提供 Agent Session 读取入口，不上传隐藏推理、凭据或任意工具载荷。

验证

发布提交 CI 已通过：Ubuntu 115 项测试通过，4 项 Windows 专用测试按平台跳过；Windows 4 项原生 DPAPI、重启恢复和多连接隔离测试全部通过。Client API 契约、依赖审计和打包检查通过；另已验证独立目录安装后的 SDK 导入。

完整更新记录 · npm 包

English

Follow the user's request, the assistant's visible replies and the resulting business actions together.

For example, one conversation can compare two separately authorized stores. A host using this SDK can archive the visible conversation in BailingHub, so an administrator can trace what was asked, what was answered and what each store actually executed. Each authorization keeps its own execution and approval records.

Use BailingHub Core 0.6.1 with a host that captures and synchronizes the conversation. The archive API minimum is Core 0.6.0. The SDK provides the synchronization API; it does not automatically record chats or add an account-selection interface.

Who should upgrade, and where to start

• Native Agent Client users, including DSH: upgrade through the host's matching release and follow its account-selection guide. Installing the MCP command alone does not add a multi-account conversation UI.

• Agent Client developers: use Node.js 20.15 or newer, install the exact SDK version, and follow the SDK guide:

  npm install --save-exact bailinghub-mcp-server@0.4.0

  Import the SDK from bailinghub-mcp-server/sdk. The new syncConversationArchive API supports member confirmation, text-to-run association, bounded uploads and idempotent retries. The host owns durable pending events and recovery status.

• MCP users with a fixed business route: existing Client Token and Agent Session flows remain compatible. Pin the package to 0.4.0 using the MCP installation guide. The standalone MCP tools and Registry entry do not automatically capture conversations.

This upgrade does not require changes to business API declarations. Existing calls can continue on Core installations below 0.6.0, but the new archive API is unsupported there and hosts must report that status accurately. Archive retries never repeat business actions or broaden authorization. Combined text is available only to authorized administrators for auditing, with no Agent Session read endpoint. Hidden reasoning, credentials and arbitrary tool payloads are excluded.

Validation

Release commit CI passed: Ubuntu ran 115 passing tests and skipped four Windows-only tests; all four native Windows DPAPI, restart-recovery and connection-isolation tests passed on Windows. Client API compatibility, dependency audit and package checks passed. An isolated package installation and SDK import were also verified.

Full changelog · npm package

BailingHub MCP Server v0.3.0

BailingHub MCP Server v0.3.0 adds the stable Agent Client multi-connection lifecycle for desktop and local agent hosts.

Highlights:

• Manage multiple named BailingHub connections with connections list/add/use/remove.
• Keep different authorized business identities isolated while replacing an older local session for the same trusted identity and binding.
• Isolate host-owned local storage with an optional storage namespace.
• Store Agent Session credentials in Windows CurrentUser DPAPI, including bounded cold-start handling.
• Remain compatible with BailingHub Core v0.5.1 and preserve existing Client Token behavior.

Install:

npm install bailinghub-mcp-server@0.3.0

Verification:

• 110 cross-platform SDK tests: 106 passed on macOS, 4 Windows-only tests skipped as expected.
• 4/4 native Windows DPAPI tests passed in GitHub Actions.
• Clean public-registry install and Agent Client connection lifecycle smoke passed.
• npm package provenance and registry signatures are available for the published package.

BailingHub MCP Server v0.2.0

What changed

• Added the host-neutral Agent Client SDK for browser-authorized local agent hosts.
• Added PKCE authorization, runtime context retrieval, direct governed tool invocation, job/result polling, and execution trace transport.
• Kept the existing stdio/Client Token MCP Registry entry compatible and separate from the Agent Session credential flow.
• Added stable English and Chinese integration guides, compatibility declarations, and release checks.

Install

npm install bailinghub-mcp-server@0.2.0

import { BailingHubAgentClient } from 'bailinghub-mcp-server/sdk';

Host adapters should depend on this exact public version. Business authorization pages and server-side credentials remain owned by the corresponding integration; they are not bundled in the SDK.

Verification

• 66/66 package tests passed.
• The npm package was published with provenance and resolves from a clean project.
• Registry signatures and attestations were verified after installation.
• io.github.bailinghub/bailinghub-governance@0.2.0 is available from the official MCP Registry.

BailingHub MCP Server v0.1.1

What changed

• Added complete Simplified Chinese installation, security-boundary, and validation guidance.
• Added direct navigation between English and Chinese documentation.
• Updated the MCP SDK and pinned the Hono transitive dependency to a patched release.
• Published bailinghub-mcp-server@0.1.1 to npm and refreshed MCP Registry metadata.

Verify

npx -y bailinghub-mcp-server@0.1.1

BailingHub MCP Server v0.1.0

First public release of the BailingHub MCP Server.\n\n- Submit governed jobs to one operator-configured BailingHub route\n- Query job status and wait within a bounded interval\n- Keep routes, credentials, acting subjects, approval state, and callbacks outside model-controlled tool arguments\n- Fail closed on missing configuration, unknown states, oversized responses, and upstream errors\n- Include MCP Client API compatibility and threat-model coverage\n\nPackage: https://www.npmjs.com/package/bailinghub-mcp-server\nDocumentation: https://github.com/bailinghub/bailinghub-mcp-server#readme