Kloudy.ai Developers

BUILD ON THE BOT WIDE WEB

Your product.
Connected.

Give your app, IDE or bot a direct path to useful resources.

Build your app, IDE or bot on Kloudy with the public Node SDK, CLI and MCP adapter. Create a runnable starter, read public pages and fetch bounded KLDY cards without an account or model call. Account tools use the same scoped Blackbox connection; customer registration and permanent GlassBreak grants are not live yet. For IDEs and bots: one CLI, one MCP, tools appear when needed.

Create your first app ↓Download the SDK ↗

Node.js 20+ · Apache-2.0 public client · No account needed for public reading

01 / A REAL FIRST RUN

From an empty folder
to a useful read.

Create a small Node app, install the public client, and read example.com through Kloudy. The starter includes public-page, KLDY-card and scoped Toolbox examples. It never overwrites an existing folder.

Terminal
npm install -g https://kloudy.ai/downloads/kloudy-open-0.3.3.tgz
kloudy init my-kloudy-app
cd my-kloudy-app
npm install
npm start

Inspect a card

npm run card -- /world

Get the bounded description bots see. No model or account call.

Choose another page

npm start -- https://example.com

Keep source attribution. Treat returned HTML as data, never executable UI.

Free where infrastructure permits. Shared rate limits and source-site restrictions apply. The client is delivered from Kloudy’s verified download, not an npm-registry listing. Checksum and release details.

02 / THE SAME ENGINE

Use the interface you already build with.

Public reading from Node

app.mjs
import {readPublicPage, readCard} from '@kloudy/open/public';

const page = await readPublicPage('https://example.com');
console.log(page.url, page.type, page.body);

const card = await readCard('/world');
console.log(card.description);

Use this from Node or your trusted server. Never put a scoped engine connection or provider secret in browser code.

SDK guide ↗

A small CLI for real work

Terminal
kloudy read https://example.com
kloudy card /world

# With an existing scoped connection:
kloudy ask "Find a tool to read my notes"
kloudy status

Public commands work without registration. For account actions, the host provides ~/.kloudy/connection.json or KLOUDY_CONNECTION points to its private location. Selecting a tool does not execute it.

CLI guide ↗

One MCP door in your IDE

Terminal
kloudy install

# Or choose one supported IDE:
kloudy install --ide codex

The installer supports Cursor, Claude Code, VS Code and Codex at user level. It preserves other servers and requires the host’s normal trust approval. The introduction can run without a connection; execution needs a scoped grant.

The live remote endpoint is https://kloudy.ai/mcp. It currently serves registered Notes and bounded Base read development tools through expiring grants. Catalog entries do not automatically become callable.

MCP guide ↗

03 / LIVE, PUBLIC, NO SIGN-IN

Read the same card your bot gets.

04 / YOUR PRODUCT STAYS YOURS

Build on Kloudy.
Keep your core.

Describe your resource

Prepare a KLDY packet for a non-medical website or use FHIR for healthcare interoperability. Metadata helps discovery; it does not grant access.

Open KLDY preparation ↗

Connect your tools

The public client can wrap an operator-selected stdio MCP locally. Managed public hosting and external-provider execution need the authoritative engine and grant path.

Understand HTTPK ↗

Keep only what is needed

Assemble owned selections into one deduplicated Toolbox, then call the exact selected action. Current execution proof covers registered Notes tools and a bounded Base chain-head read, with separate scoped development clients.

Toolbox assembly ↗

Build a business with us

Tell us what your product does and the resource it needs to expose. Discuss a pilot through the private form; this does not create a tenant or charge you.

Discuss your integration ↗

05 / BEFORE TENANT ONBOARDING

What works. What still needs connecting.

Available

Developer entry and public reads

This starter, CLI, SDK, information cards, public reader and IDE installer run today. Use existing scoped development grants for the Notes engine path.

Required before self-service

Identity and durable access

Customer email/2FA/OAuth registration and production credential exchange are not live. Permanent grants must extend the existing GlassBreak system; the service interface is still needed.

Required for provider pilots

A verified external integration

Each provider needs an authorized adapter, exact approval, real execution and receipt, and proven recovery/revocation. The large registry is metadata, not proof that every provider works.

Operational acceptance

Isolation, renewal and recovery

Development Core admission is tested. Tenant onboarding still needs production identity binding, expiry/renewal, cross-tenant isolation and external-seat lifecycle acceptance. The engine’s merge gate remains with its owner.

Deliberately deferred

Tenant billing and optional native surfaces

Billing waits until tenants exist. Native watch/glasses/OS voice acceptance has its own lane; it does not prevent developers from trying these public Node examples.

Tenant overview ↗ · Contact the team ↗