BlockBite docs

MCP tools

Desktop tool groups, project identity, revision handling and build progress.

The local blockbite-desktop server exposes the following tool groups. Connect through Desktop’s MCP setup. Your client discovers the exact input and output schemas from the running server.

Project and context

Tools Purpose
project Read the selected project’s name and ID; takes no arguments
create_project Request Desktop’s New project dialog; the user chooses the folder and confirms installation
check Read the selected project’s setup checklist
project_context, save_project_context Read or update the brief and reference notes
flow, flow_skill, flow_open Read the saved workflow and connected skills, or open its workspace
diagnostics, diagnostic Read retained incidents and safe diagnostic details

Direct authoring

These operations use Desktop’s authoring services. Your external agent supplies the model; invoking them does not start Desktop’s internal AI build.

Tools Purpose
work, work_start, work_finish Read activity, register a task and record its outcome
brand_guide, validate_brand_guide, save_brand_guide Inspect, validate and save a Brand guide
components, component, save_component List, inspect and save supported native components
site, save_site, check_site Inspect routes, save a native page and check its desktop/mobile render
catalogue, catalogue_recipe Search and inspect connected catalogue recipes
create_catalogue_page, insert_catalogue_section Create or extend an editable page from checked recipes
import_image, add_brand_asset Import a project image and attach an asset to the Brand guide
create_brand_logo, apply_brand_logo Prepare and apply a logo candidate
update_brand_asset, use_brand_asset Record asset-use decisions and place an approved image

Read the target before changing it. Register authoring work with work_start and supply the current session or revision returned by the relevant read. Follow the connected Flow skills and prerequisites. Re-read when a revision changes; do not overwrite a newer edit.

check_site runs the project’s native pipeline. A saved file and a passing native check are separate results; inspect the rendered page and its editable controls before calling the work complete.

Desktop agent builds

Tool Required arguments Purpose
build project, prompt, request Start Desktop’s own agent build
status project, run Read tasks, results and usage
stop project, run; optional task Stop the build or a task
retry project, run, task, request Retry when Desktop permits it

build and retry use Desktop’s configured OpenRouter model, saved Flow and build allowance. A client disconnect does not stop a build: use stop. Follow progress with the exact run ID returned by Desktop.

Common rules

  • Call project first and pass its exact ID to scoped operations. Refresh it after a project or access change.
  • Mutations that accept request use a client request ID. After a lost response, repeat the identical ID and payload to recover the result.
  • Some arguments carry JSON encoded as strings. Use the discovered schema for their shape and limits.
  • create_project accepts a title, optional empty or miette starter and a request ID. It accepts no filesystem path; continue only when Desktop reports creation succeeded.
  • Tools enforce the current project’s access and source rules. They do not expose arbitrary shell commands, unrestricted file access or publishing.
  • The Tools drawer and diagnostic reports provide evidence and instructions for the task; they do not grant additional access.