Buildory

Use this when the user wants to update richer execution details, set blocked status, or move an existing active task within its project. This extends rather than changes the published buildory_update_task contract.

buildory_manage_task

Use this when the user explicitly wants to upload a new artifact or append a revision to an existing artifact. PUT the raw file to the returned short-lived one-time URL using every returned header, then call buildory_finalize_artifact_upload. Never send base64 file content to this tool.

buildory_prepare_artifact_upload

Use this when the user asks to restore a bounded list of exact archived project items. Selecting an archived root section also restores descendants and content archived through that exact section operation. Restore a different archived parent section first when selecting its content directly; Buildory does not restore parents implicitly. This never restores an archived project or re-enables project MCP access.

buildory_restore_items

Use this when the user wants to update metadata, the primary section or related project records for an active artifact. This never replaces file bytes; append a revision through prepare/finalize.

buildory_update_artifact

Use this when the user wants to correct an existing project's title, description, category, or active lifecycle status. It never changes visibility, currency, billing, MCP settings, or archive state.

buildory_update_project

Use this when the user wants to correct an active external resource or manage its project-local section links. Converting a project-wide resource to section-scoped requires project_wide=false plus add_sections. Converting to project-wide removes every section placement.

buildory_update_resource

Use this to correct section metadata, move a section to a different active parent or root, or place it immediately before or after an active sibling. Cycles and plan-limit violations are rejected.

buildory_update_section

Add a candidate part or material to an existing Buildory project's bill of materials. Use only after the user asks to record it. Requires Pro or Creator and MCP write access.

Record work that actually happened in an existing Buildory project section. Do not use it for plans or future tasks.

Save a durable note, decision, research result, specification or reference in an existing Buildory project section. Use only when the user asks to record this knowledge.

Create an open task in an existing Buildory section. Use only after the user explicitly asks to record the task. Requires Pro or Creator and MCP write access.

Use this when the user wants a focused, read-only execution brief for Codex or another technical agent from exactly one accessible Buildory task or section. Choose one of the two fully described input variants. It returns bounded relevant context, linked artifacts with current file metadata and Markdown; it does not execute work or change the project.

Use this when the user asks what changed in one accessible Buildory project, when it changed, or who or what caused it. It returns the recent authoritative activity trail with human, MCP client, Codex return, API, automation or system provenance.

Get the structured details, child sections, tasks, parts, recent build log, knowledge, photo captions and linked resources of one accessible Buildory section.

List the Buildory projects accessible to the connected user. Use this first when the user has not identified one project unambiguously.

Get a concise summary, totals, tasks needing attention and recent build activity for one accessible Buildory project.

Search titles and text across sections, project and section tasks, BOM items, build logs, knowledge, photo captions and linked resources in one accessible project.

Update or move an existing BOM item inside the same accessible Buildory project. Include only fields the user intends to change.

Update editable fields of an existing task in an accessible Buildory project. The external status done maps to Buildory completed. Use only after an explicit user request.