Bee — The Progressive Intelligence Engine

io.github.cuilabsPublished by GitHub account cuilabsv0.6.0Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyDeveloper Tools AI & ML

Server details

Identifier: io.github.cuilabs/bee
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account cuilabs for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.cuilabs%2Fbee.svg)](https://sourceweft.com/mcp/io.github.cuilabs%2Fbee?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Bee's MCP server exposes a hosted, tiered LLM service to an assistant, letting it send chat requests to Bee models through a local stdio process.

What you can do: Send chat completion requests to Bee's hosted, OpenAI-compatible model gateway
Choose a model tier from bee-cell up to bee-swarm, subject to the API key's plan
Point requests at an alternative gateway base URL for self-hosted or staging deployments
Use the same Bee service that its TypeScript and Python SDKs call, from inside an MCP client
When to use it: Worth adding when you want an assistant to call Bee's hosted models as a separate intelligence backend, including on the free Cell tier, rather than using a model provider already built into your client.
Requirements: Runs locally over stdio, launched with uvx from the bee-sdk package, so Python and uv must be available. Requires a Bee API key in BEE_API_KEY, created in the Bee Workspace; the free Cell tier works. Optional BEE_API_URL overrides the gateway base URL and BEE_MODEL sets the default tier. Network access to the Bee gateway is needed.

Before you install

The API key in BEE_API_KEY is a secret that grants access to your Bee account and plan tier; keep it out of shared configuration. Prompts and content sent through the server go to Bee's hosted gateway, a third party, so avoid confidential material. Usage beyond the free tier may be metered or billed according to your plan.

Installation

In SourceWeft

Open Bee — The Progressive Intelligence Engine 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

[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.

Surface	Install or entry point	Source / contract
TypeScript SDK	`npm install @heossihq/bee`	`sdks/typescript`
Python SDK	`pip install bee-sdk`	`sdks/python`
MCP server	`uvx --from bee-sdk@latest bee-mcp`	`mcp` · `server.json`
OpenAI-compatible API	`https://api.bee.heossi.com/bee`	`openapi.json` · `postman.json`
Bee: Quantum Intelligence - Code	`Heossi.beecode`	Microsoft Marketplace · Open VSX
Bee Code CLI	`npm install -g @heossihq/beecode`	Download guide
PQ assurance	Signed public coverage register	`trust/pq-register`

Quickstart

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);

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

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

Evaluator	Start here	What can be verified publicly
Enterprise architect	Reference architecture and scenario flows	System boundaries, governed request flow, deployment profiles, and responsibility split
Security or risk lead	Security policy, PQ coverage register, and diligence index	Disclosure path, released PQ claims, evidence limitations, and public control references
Platform engineer	API contracts, SDKs, MCP, and examples	Integration contracts, install paths, source, examples, and client configuration
Procurement or technical diligence	MANIFEST.json, SHA256SUMS, SPDX SBOM, and NOTICE	Export 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:

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

SDK, MCP, contract, or example defect: open an issue
Product or account support: bee.heossi.com/contact
Vulnerability disclosure: [email protected]; see SECURITY.md
Service health: status · changelog · roadmap

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

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

Source: README.md at commit 3130f61

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.6.0LatestSep 16, 2026

Score

50% 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