Skip to main content
Call tools/list after connecting the local product server. Read the returned schema before supplying arguments; the catalogue below is generated with the public client release. Download complete tool schemas · Connect MCP · Task Skills. A listed tool does not grant account access. The API checks the current user, organization, project, environment and action. Use the existing project context before changes, and retain mutation idempotency keys across uncertain responses.

Source tools

Sources and versions explains the source choice, revision guards, save completion and restoration. Read source_get before choosing a source. Request include_binding: true for connection/generation guards; the default GitHub status view remains unchanged, while managed source is always complete. Preserve the selected project and source. For a complete native-chat snapshot, use remote source_upload_prepare and source_blob_put, then source_upload_commit for initialize/commit or source_switch for an explicitly requested GitHub-to-managed switch. source_blob_put computes hashes and byte lengths from real file contents; keep its exact receipts for every file, including unchanged retained files. The final manifest must match all receipts from this upload. Observe the original operation with source_upload; these tools neither read a local directory nor start deployment. Complete-tree flow. MCP text reads default to content_text with encoding: "utf8", with a base64 fallback for binary files. source_changes accepts exactly one content_text or content_base64 per path; content_base64: null deletes the file. REST uses base64. The editing example includes the complete argument shape. The generated catalogue above is the local product server. Remote OAuth clients discover their own tools through tools/list; local directory tools cannot operate inside a native chat without a local filesystem. Connection and publishing permissions are described in MCP setup.