Bee: Quantum Intelligence

io.github.heossihqPublished by GitHub account heossihqv1.0.98Updated Nov 3, 2026

Bee governed intelligence for chat, code, research, documents, and memory.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryAI & ML

Overview

AI-generated overview

Bee's MCP server gives an assistant access to HEOSSI's hosted multimodal intelligence platform for chat, code, research, documents and memory.

What you can do
  • Send chat and completion requests to Bee's hosted models through an OpenAI-compatible gateway
  • Work with code, research, documents and memory through the governed platform
  • Choose a model tier from bee-cell up to bee-swarm, subject to the API key's plan
  • Use it either as a remote endpoint or as a local process started with uvx from the bee-sdk package
When to use it
Worth adding when you want an assistant to route work to Bee's hosted models and governed platform rather than a single local model, including free-tier experimentation with the Cell tier.
Requirements
A Bee API key (bee_sk_...) in BEE_API_KEY, or OAuth via the Authorization bearer header; a key can be created in Bee Workspace and the free Cell tier works. Network access to the Bee gateway. Optional BEE_API_URL for an Enclave or staging gateway and BEE_MODEL for the default tier. The local option needs uv/uvx with the bee-sdk package.
Before you install
The API key is a secret sent as a bearer credential; keep it out of shared configs. Requests and content go to HEOSSI's hosted gateway, a third-party service. Usage may be metered or bounded by your plan, and higher model tiers depend on the key's entitlements. The model engine and gateway are proprietary, so behaviour is defined only by the public contracts.

Installation

In SourceWeft

  1. Open Bee: Quantum Intelligence in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.heossihq%2Fbee-public/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "bee-quantum-intelligence": {
      "type": "http",
      "url": "https://api.bee.heossi.com/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.

Source: README.md at commit 42d3ffe

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

21
  1. v1.0.98LatestNov 3, 2026
  2. v1.0.97Nov 3, 2026
  3. v1.0.91Oct 31, 2026
  4. v1.0.79Oct 30, 2026
  5. v1.0.78Oct 30, 2026
  6. v1.0.77Oct 29, 2026
  7. v1.0.66Oct 26, 2026
  8. v1.0.65Oct 2, 2026
  9. v1.0.63Oct 1, 2026
  10. v1.0.57Sep 30, 2026
  11. v1.0.53Sep 30, 2026
  12. v1.0.48Sep 30, 2026
  13. v1.0.41Sep 28, 2026
  14. v1.0.40Sep 27, 2026
  15. v1.0.32Sep 26, 2026
  16. v1.0.29Sep 25, 2026
  17. v1.0.28Sep 25, 2026
  18. v1.0.27Sep 25, 2026
  19. v1.0.14Sep 24, 2026
  20. v1.0.13Sep 23, 2026
  21. v0.6.10Sep 16, 2026

Score

85% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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