KLOUDY / mcpstrings
A Toolbox assembled for the task.
MCP strings are Kloudy’s custom mix of singular tools from multiple MCP servers, SDKs, CLIs and open-source libraries. Ask for the result you need; the engine selects only the relevant tools, instead of dumping whole servers into context. Passive card reads need no model. The deployed development engine assembles up to 16 owned intent selections into deduplicated tools. Each intent still selects at most one tool; executable sources are registered Notes today. External MCP/SDK wrappers remain in development. One CLI, one MCP, tools appear when needed.
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.
Mix sources, keep the selection small
A task might need a calendar tool, one SDK operation and an open-source converter. The intended Toolbox includes those operations only, with their individual inputs and permissions. The count follows the work.
Discover → read → select → execute
Find resources through SEO/GEO; read KLDY for general resources or FHIR for authorized healthcare data; ask the engine for a scoped Toolbox. Submit the selected tool’s inputs and receive the actual result. The IDE keeps its own model.
Keep useful connections through GlassBreak
A retained API connection should remain usable by code through the authorized GlassBreak path. Remove dormant definitions from active context, not arbitrary source files or the owner’s access. Permanent grants wait for the live GlassBreak system.
Recover inside the permission boundary
Compatible, authorized replacement can happen quietly after a failed connection is verified. A complaint is diagnostic feedback, not consent to new access, cost or a new co-admin. Failed replacement keeps the existing seat.
Use the working door
Install the public client and connect an operator-issued development session. CLI ask returns the engine-selected Toolbox, including an explicit empty selection when no authorized match exists. Customer registration and general provider discovery are not yet enabled.
