
BIGHUB
io.bighubPublished by bighub.iov0.2.1Updated Oct 24, 2026
Decision learning for AI agent actions. Evaluate, score, decide, and learn from outcomes.
Overview
BIGHUB's decision layer for IT agent actions: an assistant can submit a proposed action, get a run/review/block decision, and report outcomes.
- What you can do
- Evaluate proposed IT actions and get a normalized decision with mode, can_run, review and risk flags
- Build decision packets, run DecisionBrain, and resolve pending human reviews
- Report outcomes, query decision cases, precedents, calibration and retrieval signals
- Inspect insights, simulations, features, learning runs and runtime event ingestion
- Manage system integrations (Okta, Slack, GitHub, cloud and CI providers) and their polling
- Administer operating constraints, approvals, kill switch, webhooks, API keys and auth
- When to use it
- Useful when an agent proposes consequential IT actions such as granting access, rotating credentials, deploying or rolling back services, changing IAM or CI/CD settings, or exporting sensitive data, and you want a decision and review gate before execution. Not needed for agents that only answer questions or do read-only lookups.
- Requirements
- Runs locally as a Node.js 18+ process via npx over stdio. Requires a BIGHUB account and either BIGHUB_API_KEY or BIGHUB_BEARER_TOKEN; management tools for API keys, webhooks and auth need the bearer token. Optional settings include BIGHUB_BASE_URL, timeout, retries and an insecure-HTTP flag. Network access to the BIGHUB API is required.
Installation
In SourceWeft
- Open BIGHUB in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
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
Source: servers/mcp/README.md at commit 61f4e2f
Tools
0Version history
1- v0.2.1LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.