Bee — The Progressive Intelligence Engine

io.github.cuilabs由 GitHub 帳號 cuilabs 發布v0.6.0更新於 Oct 24, 2026

Bee — The Progressive Intelligence Engine: tiered LLM, 4 tools, hosted API, free tier.

已驗證STDIO僅桌面開發者工具AI 與機器學習

概覽

AI 產生的概覽

Bee 的 MCP 伺服器把託管、分層的 LLM 服務提供給助理,讓助理透過本機 stdio 程序向 Bee 模型送出對話請求。

可以做什麼
  • 向 Bee 託管、相容 OpenAI 的模型閘道送出對話補全請求
  • 在 bee-cell 到 bee-swarm 之間選擇模型層級,可用範圍取決於 API 金鑰的方案
  • 為自架或預備環境部署指定替代的閘道基礎網址
  • 在 MCP 用戶端內使用與 Bee 的 TypeScript 和 Python SDK 相同的 Bee 服務
適用情境
當你希望助理把 Bee 的託管模型當作獨立的智慧後端來呼叫(包括使用免費的 Cell 層級),而不是依賴用戶端內建的模型供應商時,值得加入。
執行需求
透過 stdio 在本機執行,使用 uvx 從 bee-sdk 套件啟動,因此需要 Python 與 uv。需要在 BEE_API_KEY 中提供 Bee API 金鑰,可在 Bee Workspace 建立,免費的 Cell 層級即可使用。選用的 BEE_API_URL 可覆寫閘道基礎網址,BEE_MODEL 設定預設層級。需要能連線到 Bee 閘道的網路。
安裝前請注意
BEE_API_KEY 中的 API 金鑰是機密,可存取你的 Bee 帳戶與方案層級,請勿放入共用設定。透過此伺服器送出的提示與內容會傳到 Bee 的託管閘道(第三方),請避免送出機密資料。超出免費層級的使用可能依方案計費。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Bee — The Progressive Intelligence Engine,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

[Bee: Quantum Intelligence]

Bee: Quantum Intelligence™

[npm] [PyPI] [MCP Registry] [License]

Website | Documentation | Packages | Machine-readable package index | System status

The public developer distribution for Bee, HEOSSI's governed multimodal intelligence platform. This repository contains the actual source of Bee's Apache-2.0 SDKs, MCP integration, API contracts, runnable examples, and public trust-verification material.

This repository is generated from reviewed, public-safe paths in the Bee monorepo. MANIFEST.json records the exact source commit and content digest for every export; SHA256SUMS and the SPDX SBOM support independent artifact inspection.

Developer surface

The canonical package catalog records each public developer distribution, exact version, registry, role, license boundary, and install command. Its machine-readable companion is PACKAGE-INDEX.json. These distributions do not expose the private Bee service monorepo.

SurfaceInstall or entry pointSource / contract
TypeScript SDKnpm install @heossihq/beesdks/typescript
Python SDKpip install bee-sdksdks/python
MCP serveruvx --from bee-sdk@latest bee-mcpmcp · server.json
OpenAI-compatible APIhttps://api.bee.heossi.com/beeopenapi.json · postman.json
Bee: Quantum Intelligence - CodeHeossi.beecodeMicrosoft Marketplace · Open VSX
Bee Code CLInpm install -g @heossihq/beecodeDownload guide
PQ assuranceSigned public coverage registertrust/pq-register

Quickstart

ts
import { BeeClient } from "@heossihq/bee";
const bee = new BeeClient({ apiKey: process.env.BEE_API_KEY! });const result = await bee.chat.completions.create({  model: "bee-cell",  messages: [{ role: "user", content: "Explain hybrid post-quantum TLS." }],});
console.log(result.choices[0].message.content);

Create an API key in Bee Workspace. The free Cell tier works with both SDKs and MCP.

Repository map

text
api/                 Versioned OpenAPI and Postman contractsdocs/                Public architecture and enterprise scenario flowsexamples/            Runnable TypeScript and Python examplesmcp/                 Client configuration and MCP setupsdks/typescript/     Published @heossihq/bee package source and testssdks/python/         Published bee-sdk and bee-mcp source and teststrust/pq-register/   Public PQ coverage register and offline verification tools

Enterprise evaluation paths

EvaluatorStart hereWhat can be verified publicly
Enterprise architectReference architecture and scenario flowsSystem boundaries, governed request flow, deployment profiles, and responsibility split
Security or risk leadSecurity policy, PQ coverage register, and diligence indexDisclosure path, released PQ claims, evidence limitations, and public control references
Platform engineerAPI contracts, SDKs, MCP, and examplesIntegration contracts, install paths, source, examples, and client configuration
Procurement or technical diligenceMANIFEST.json, SHA256SUMS, SPDX SBOM, and NOTICEExport provenance, file integrity, package inventory, licensing, and the public/proprietary boundary

Architecture and scenarios

Start with the public reference architecture, then follow the control boundary through three concrete flows:

The matching visual architecture centre is published at bee.heossi.com/docs/architecture.

Bee Code's agent path is durable, subscription-bounded, and independently metered. Workspace, mobile, desktop, SDK, and MCP requests retain their own documented execution contracts; common entitlement enforcement does not imply that every surface has local IDE tools.

Integrity and provenance

The public distribution is locally rendered from an allowlisted monorepo surface. Verify it with:

bash
sha256sum --check SHA256SUMSpython3 scripts/verify_bee_package_index.py PACKAGE-INDEX.json

SHA256SUMS covers every exported payload file except itself and the commit-specific MANIFEST.json. The manifest separately binds the export to its source commit and contains a deterministic digest of the complete payload. The SPDX document is package-level (filesAnalyzed: false); it inventories the published SDK and MCP packages without claiming a binary or deployment SBOM.

Public and proprietary boundary

The files in this repository are Apache-2.0 licensed. Bee's model engine, orchestration plane, hosted gateway, Bee Code CLI implementation, editor-extension implementation, and commercial applications remain proprietary and are not represented as open source here. Public API and package behavior is defined by the contracts and SDK source in this repository.

Support and security

Contributing

Read CONTRIBUTING.md, SUPPORT.md, and the Code of Conduct. Generated paths must be changed in their canonical monorepo source; community examples and documentation can be proposed here and are reconciled during the next local export.

License

Apache License 2.0 · Copyright 2026 HEOSSI (Pte.) Ltd.

Bee™ and the Bee knot logo are trademarks of HEOSSI (Pte.) Ltd., Singapore.

來源:README.md,提交 3130f61

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.6.0最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分