The 8 MCP tools and the scopes each one needs
The HIIE MCP server at /api/mcp exposes eight tools. Each tool is gated by a scope, and they call the identical underlying functions the REST API uses, so results match the web app.
The tools and their scopes
- list_projects (read) — list your projects.
- create_project (write) — create a new owner-scoped project.
- generate_cad (build) — generate a manufacturable part (STEP + STL + colored GLB) from a plain-language prompt.
- list_flow_templates (read) — list the built-in multi-agent flow templates.
- run_flow (build) — run a flow template or a custom flow inside a project.
- start_build (build) — start (or resume) the autonomous builder for a project.
- get_build_status (read) — poll a build job's status.
- list_artifacts (read) — list every file a project holds, each with a download URL.
How scope enforcement works
The server checks the required scope for each tool against your key's scopes (admin implies all). If your key lacks the needed scope, the tool returns a JSON-RPC forbidden error with code -32001. Build-scoped tools (generate_cad, run_flow, start_build) are the ones that consume credits.
Mapping to a workflow
A typical agent loop reads first (list_projects, list_flow_templates), acts (create_project, run_flow, generate_cad, or start_build), then polls and collects (get_build_status, list_artifacts). Give your key the build scope only if it needs to run the credit-spending tools.
Default key scopes
New developer keys come with read, write, and build by default, which covers all eight tools — narrow this down if a client only needs read access.