KLOUDY / httpk
HTTPK. The wrap that connects your tools.
Ask for Kloudy. HTTPK is Kloudy’s managed wrap around an MCP, SDK, CLI or open-source tool. Register with email and short 2FA, then keep the same session through a cookie, tag or OAuth. Your IDE receives singular tools selected from many sources, rather than a whole server. You own your upstream account and use of the asset; Kloudy maintains the wrap and reconnects through that same path within your grant. Connection is free where the provider permits; hosting, extra speech and advertising are optional. The public developer client and local wrapper are runnable; hosted registration and managed grants require the owning account and engine services.
Product overview. Public-page reading and KLDY preparation are available here. The connector, account actions and native apps described below are not connected to this site.
Ask for Kloudy. One engine.
For IDEs and bots: one CLI, one MCP, tools appear when needed.
Find with SEO/GEO, read FHIR for medical data or KLDY for other information, then select one scoped Toolbox tool when action is needed.
Passive local reads use no model calls. Narrowing 100 candidate definitions to 10 would mean 90% fewer definition fetches in that example; this is an illustration, not measured token savings.
One engine, one session
CLI, MCP and SDK are interfaces to the same engine. Ask for Kloudy from your IDE, bot or surface. The engine finds candidate resources, reads their cards and selects only the needed tool definitions. An empty Toolbox stays empty and can offer an information card; it never dumps a server’s entire catalog.
The glass door stays on the wrap
Kloudy’s maintenance access belongs to the wrap it operates. It does not make Kloudy the owner of your upstream GitHub, Tailscale or other account. Maintenance and reconnect stay within an existing scoped, revocable grant. A changed scope or new cost needs approval.
Reconnect through the same path
The intended managed service reuses the same HTTPK connection when it reconnects or rotates an eligible tool. Local-file tools stay with your computer unless you explicitly choose supported hosting. The current local wrapper runs only selected, operator-configured tools; automatic grant refresh and rotation remain engine services.