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 分