
BIGHUB
io.bighub由 bighub.io 发布v0.2.1更新于 Oct 24, 2026
Decision learning for AI agent actions. Evaluate, score, decide, and learn from outcomes.
概览
BIGHUB 的决策层:助手可提交拟执行的 IT 操作,获得执行、复核或阻止的决策,并回传结果。
- 可以做什么
- 评估拟执行的 IT 操作,返回包含执行模式、can_run、复核与风险标记的规范化决策
- 构建决策包、运行 DecisionBrain,并处理待人工复核的请求
- 回传结果,查询决策案例、先例、校准与检索信号
- 查看洞察、模拟、特征、学习运行与运行时事件摄取
- 管理 Okta、Slack、GitHub、云与 CI 等系统集成及其轮询
- 管理运营约束、审批、终止开关、Webhook、API 密钥与登录认证
- 适用场景
- 适用于助手提出有实际后果的 IT 操作时,例如授予访问权限、轮换凭据、部署或回滚服务、修改 IAM 或 CI/CD 设置、导出敏感数据,并希望在执行前获得决策与复核关卡。仅回答问题或只做只读查询的助手不需要它。
- 运行要求
- 以 Node.js 18+ 通过 npx 在本地以 stdio 方式运行。需要 BIGHUB 账户,以及 BIGHUB_API_KEY 或 BIGHUB_BEARER_TOKEN 之一;API 密钥、Webhook 与认证等管理工具需要 bearer token。可选配置包括 BIGHUB_BASE_URL、超时、重试与允许不安全 HTTP 的开关。需要能访问 BIGHUB API 的网络。
安装
在 SourceWeft 中
- 打开 控制台中的 BIGHUB,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
@bighub/bighub-mcp
BIGHUB's Better Decision layer as an MCP server. Turn proposed IT agent actions into better decisions before they run from any MCP-compatible client.
MCP server for better decisions on IT agent actions.
Table of contents
Start here
- Install
- Quickstart
- When to use bighub-mcp
- Typical MCP Loop
- Better Decision primitives
- Trajectory-aware evaluation
Tool reference
- Better Decision primitives · Core loop · Actions · Outcomes · Decision cases · Precedents · Calibration · Multi-signal retrieval · Insights · Simulations · Learning · Features · Runtime ingestion · System integrations · Operating constraints · Approvals & kill switch · Events · Webhooks · API keys · Auth · Utility
Reference
Install
Requires Node.js 18+.
Quickstart
Set your API key:
Run the server in stdio mode:
Add it to your MCP client configuration:
Works with MCP-compatible clients such as Claude Desktop and Cursor.
When to use bighub-mcp
Use this server when your MCP-connected agent proposes IT actions such as:
- granting Okta access
- rotating credentials
- deploying or rolling back services
- changing CI/CD, cloud, or IAM settings
- exporting sensitive data
- posting incident or support updates
- resolving actions that need human review
If your agent only answers questions or performs read-only lookups, you don't need this. It's designed for agents that make decisions with real-world consequences.
Typical MCP Loop
- Send the proposed IT action to
bighub_decide - Let BIGHUB build or use a Decision Packet
- Run DecisionBrain and return execution mode, review/context flags, and a decision path when available
- Execute only when
can_runis true and no blocking flags are set - Route to review when BIGHUB asks for human approval or modification
- Optionally report the outcome later
Better Decision primitives
The modern MCP surface is centered on the decision flow:
bighub_decide and bighub_run_brain return a normalized decision object first:
recommended_action, mode, can_run, needs_review, needs_more_context,
should_not_run, risk, confidence, expected_regret, reason, system,
selected_model when available, decision_path when available, and counts for
verification steps and obligations. The original backend payload is still
available under raw for advanced callers. Legacy tools such as
bighub_actions_evaluate remain available for compatibility.
bighub_build_packet uses the same canonical JSON SHA-256 hashing strategy as
the Python SDK, so packet hashes match across SDK and MCP clients.
Trajectory-aware evaluation
BIGHUB evaluates actions not only in isolation, but also in the context of what happened before. As deployment, review, and outcome history accumulates, similar IT actions can receive better recommendations over time.
Complete Tool Reference
BIGHUB tools are organized by domain. The core loop tools are listed first.
Core loop
Actions
Outcomes
Decision cases
Precedents
Calibration
Multi-signal retrieval
Insights
Simulations
Learning
Features
Runtime ingestion
System integrations
Supported system providers include okta, slack, github, sentry, datadog, aws_cloudtrail, terraform, kubernetes, argocd, gitlab, jenkins, azure, prometheus, grafana, and openshift. Common aliases such as github-ci, cloudtrail, terraform-cloud, k8s, argo-cd, gitlab-ci, and ocp are normalized to backend provider IDs.
Poll snapshots and histories are redacted before persistence and exposure. They provide best-effort operational context; they are not a replacement for production monitoring.
Operating constraints
Approvals & kill switch
Events
Webhooks
API keys
Auth
Utility
Environment Variables
* One of BIGHUB_API_KEY or BIGHUB_BEARER_TOKEN is required.
Management tools (API keys, webhooks, auth) require user JWT auth via BIGHUB_BEARER_TOKEN.
Local Development
Links
- bighub.io
- GitHub - bighub-io/bighub
- npm - @bighub/bighub-mcp
- PyPI - bighub (Python SDK)
- PyPI - bighub-openai
License
Apache-2.0
来源:servers/mcp/README.md,提交 61f4e2f
工具
0版本历史
1- v0.2.1最新Sep 16, 2026
评分
已满足适用检查项的 40%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分
请在仓库或注册中心条目中声明许可证。