Kloudy

Tools

Token cost is the o200k count of the tools list JSON, including schemas, before any tool is called.

• find_mcp_tools

  Find public MCP servers, tools and SDKs using a few task keywords. Returns a page of up to twenty relevant discovery candidates with their name, source, link, capability tags and a heuristic metadata

• kloudy_connect_card

  Show sign-in availability or the one-step install card. First call find_mcp_tools with operation ask and a short setup request. If it returns kind account or connect, call this card once with the retu

• show_tool_preferences_card

  Show three short questions about preferred tool types, where projects run, and how tool updates appear. Use when the user wants to set or change these preferences. Displays choices only; does not inst

• show_visual_setup_choices

  Offer three fixed framework layout examples (Vite, Astro, Next.js), not goal-based tool discovery. For tools matching a task, call find_mcp_tools and search the actual catalog. The IDE creates any req

• kloudy_build_start

  Consult Kloudy to assemble or improve a project using frameworks, components, MCP/HTTPK tools, APIs, SDKs, models, clouds, runners, payments or media. Resume the existing flowId and pinned stack; retu

• kloudy_build_answer

  Return the user answer to the exact Kloudy question. Interpret the relevant project capabilities into short component queries; preserve the complete useful selection independently of display pages. Ch

• kloudy_build_state

  Read the current Kloudy question, selected candidates and connection boundaries without advancing.

• kloudy_project_stage

  Review optional business-stage resources for an exact pinned project. Returns inert source metadata and planning choices, never installs, executes or grants access.