Build a taste-powered project with Qloo. One npm package gives you three ways in: a chat agent, a command-line tool, and an MCP server.
-
Install Node.js 22.19.0 or newer.
-
Install the public harness:
npm install --global @qloo/qloo-harness qloo --version
The version must be 0.1.26 or newer.
-
Run
qloo setup --qlooand enter the event-provided Qloo credential. Do not paste the credential into a repository, issue, chat, or browser app. -
Read API access and limits and safe use before making a live request.
| Route | Use it to | Also needs | Starter |
|---|---|---|---|
Chat agent: qloo explore |
Ask Qloo questions in plain language and learn what the data can answer. | A model-provider sign-in (qloo setup --model). |
Agent chat |
CLI: qloo exec, qloo api |
Call Qloo from a script or backend and get JSON back. | Nothing else. | CLI workflow |
MCP server: qloo mcp |
Give Qloo tools to an MCP desktop client or to your own app's model. | An MCP client, or a backend that can start a local process. | MCP |
qloo explore, qloo exec, and qloo mcp run the same validated workflows
and return the same result shape, so you can prototype in one and ship in
another. qloo api returns the raw API response.
To look up guides, endpoints, and parameters while you build, add the Qloo
docs MCP server, https://docs.qloo.com/mcp, to your MCP client. It is a
reference only: it needs no credential, and it is not a way to call Qloo. See
step 7 of the MCP starter.
The harness's integrate, plan, and build modes are not part of the
hackathon. Their approval controls are not an operating-system sandbox.
Use Qloo's workflows to find Qloo tags, describe an entity, discover recommendations, compare audiences, rank a shortlist, or investigate trends and geographic popularity. Qloo results describe aggregate affinities; they are not evidence of a person's identity, preferences, or future behavior.