Skip to main content
These are the build tools exposed by the Zite MCP at https://mcp.zite.com/mcp. The server also exposes 16 data tools for reading and writing records. The file-editing and check tools run inside a sandbox and take the sandboxId returned by create_sandbox. The workspace tools, get_logs and publish_app (both keyed by appId), setup_integration, and send_feedback work without one.
If the sandbox, commit, and publish tools don’t appear in your client’s tool list, app building isn’t enabled for your organization yet. The workspace tools, the data tools, and send_feedback are always available.

​
Workspaces & sandboxes

create_app is a free scaffold — it creates an empty app with no AI build, so it spends no Zite credits. The scaffold lands in the repo with the agent’s first commit.

​
Files & editing

edit_file requires oldText to appear exactly once in the file. If it matches zero times or more than once, the edit fails with guidance — include more surrounding context to make the match unique.
bash is the escape hatch for npm installs, git commands, file moves, and one-off scripts. Prefer the structured file tools for editing so behavior stays predictable. Real commits should go through commit, not raw git commit.

​
Checks & logs

Use get_logs to catch runtime errors a type-check can’t. Its filters:

​
Ship

commit type-checks, commits and pushes, then builds and snapshots in the background — the returned changedApps report buildStatus: "building". If the remote has newer commits it returns a conflict; run git pull --rebase origin main via bash, resolve, and commit again.
publish_app requires a successful build. If the latest build is still running or failed, it returns an error — wait for the build, or fix errors with check_app / get_logs and commit again. External apps publish to https://<subdomain>.zite.so.

​
Integrations

setup_integration returns the integration picture for a workspace: which third-party services can be connected, the accounts your organization has already connected (orgServices), and — when a sandboxId is passed — what’s already attached to the database and each app. Two paths from there:
  • The org already has an account for the service — the agent attaches it itself by writing the config entry with the returned connectionId. No user interaction needed.
  • No account yet — the agent shares connectUrl with you; the OAuth sign-in happens in your browser, then the agent calls the tool again to pick up the new connection.
See Integrations & secrets.

​
Feedback

Lets the agent report platform problems — broken tooling, unexpected behavior, docs gaps — straight to the Zite team. severity is one of broken_tooling, unexpected_behavior, environment_failure, bad_schema, or other. Available on every connection, with or without app building enabled.