Schema | bailinghub-mcp-server

bailinghub-mcp-server

Official

Describes the environment variables required to run the server.

Name	Required	Description
`BAILINGHUB_ROUTE`	Yes	The operator-configured route to use for job submission
`BAILINGHUB_BASE_URL`	Yes	The base URL of the BailingHub deployment, e.g., https://hub.example.com
`BAILINGHUB_CLIENT_TOKEN`	Yes	A BailingHub Client Token restricted to the configured route
`BAILINGHUB_ALLOW_INSECURE_HTTP`	No	Set to 'true' to allow non-loopback HTTP connections (use only in private networks)

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
submit_governed_jobA	Submit a business-system action through an operator-configured BailingHub route. BailingHub applies its configured reach, risk, approval-intent, rate-limit, and audit controls. The downstream business system still performs final authorization.
get_governed_jobA	Read the current public state and result of a BailingHub job owned by this client.
wait_for_governed_jobA	Poll one BailingHub job for a bounded period. A timeout returns the latest state and never resubmits the business action.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bailinghub/bailinghub-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server