BailingHub for Business Operations runs on your own machine — the client starts it, so there is no endpoint to ping. 148 installs a week from npm. Last commit 22 Oct 2026.
Let AI agents query and operate business systems with authorization, approval and audit trails.
We read the source, 1 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const child = spawn(executable, args, {
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add bailinghub-governance -e 'BAILINGHUB_BASE_URL=<BAILINGHUB_BASE_URL>' -e 'BAILINGHUB_CLIENT_TOKEN=<BAILINGHUB_CLIENT_TOKEN>' -e 'BAILINGHUB_ROUTE=<BAILINGHUB_ROUTE>' -- npx -y bailinghub-mcp-server
{
"mcpServers": {
"bailinghub-governance": {
"command": "npx",
"args": [
"-y",
"bailinghub-mcp-server"
],
"env": {
"BAILINGHUB_BASE_URL": "<BAILINGHUB_BASE_URL>",
"BAILINGHUB_CLIENT_TOKEN": "<BAILINGHUB_CLIENT_TOKEN>",
"BAILINGHUB_ROUTE": "<BAILINGHUB_ROUTE>"
}
}
}
}
[mcp_servers.bailinghub-governance]
command = "npx"
args = ["-y", "bailinghub-mcp-server"]
env = { BAILINGHUB_BASE_URL = "<BAILINGHUB_BASE_URL>", BAILINGHUB_CLIENT_TOKEN = "<BAILINGHUB_CLIENT_TOKEN>", BAILINGHUB_ROUTE = "<BAILINGHUB_ROUTE>" }
{
"mcpServers": {
"bailinghub-governance": {
"command": "npx",
"args": [
"-y",
"bailinghub-mcp-server"
],
"env": {
"BAILINGHUB_BASE_URL": "<BAILINGHUB_BASE_URL>",
"BAILINGHUB_CLIENT_TOKEN": "<BAILINGHUB_CLIENT_TOKEN>",
"BAILINGHUB_ROUTE": "<BAILINGHUB_ROUTE>"
}
}
}
}
{
"servers": {
"bailinghub-governance": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"bailinghub-mcp-server"
],
"env": {
"BAILINGHUB_BASE_URL": "<BAILINGHUB_BASE_URL>",
"BAILINGHUB_CLIENT_TOKEN": "<BAILINGHUB_CLIENT_TOKEN>",
"BAILINGHUB_ROUTE": "<BAILINGHUB_ROUTE>"
}
}
}
}
Put your own values in place of
<BAILINGHUB_BASE_URL> (Absolute URL of the self-hosted BailingHub deployment), <BAILINGHUB_CLIENT_TOKEN> (Dedicated BailingHub Client Token restricted to the configured route), <BAILINGHUB_ROUTE> (One allowlisted BailingHub route fixed by the operator for this server process).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
BAILINGHUB_ALLOW_INSECURE_HTTP (Optional explicit override for operator-controlled private HTTP networks).
Intent-bound action authorization for AI agents: policy, human approval, and a signed audit trail.
Shared business knowledge, tools and skills for AI agents, with citations and approval controls.
OAuth 2.1 short-link tools for AI agents with scoped tokens, approvals, audit logs, and revocation.
Keep credentials out of AI coding agents with local approvals, scoped injection, and audit trails.
SSH for AI agents: commands, files, backups and health, with approval, a vault and an audit trail
OAuth 2.0 for AI agents — scoped delegation tokens, audit trails, and revocation.
Deterministic execution authorization for AI agents and automated systems.
Audit trail and traceability for AI agents. MCP gate: evaluate, ingest, request approval.
Answers built from our own checks of this server.