Skip to main content
These are the build tools exposed by the Zite MCP at https://mcp.zite.com/mcp. The server also exposes 17 data tools for reading and writing records. The file-editing, script, check, commit, and build 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, the marketplace tools, and send_feedback work without one.
Availability. The build tools are free for 7 days. The trial starts the first time your agent calls create_sandbox, with no card and nothing to switch on. After that they’re on the Business plan and above: they stay listed in your client, and calling one returns an upgrade message. The workspace tools, the data tools, and send_feedback are always available, and the Zite editor builds apps on any plan.

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, and file moves. Prefer the structured file tools for editing so behavior stays predictable. Output over 100 KB per stream is truncated, and the full output is saved to a file in the sandbox whose path the truncated output names. The sandbox is a git clone on main: stay on main, and never git commit or git push there. Commits go through commit.
run_one_off_script is for one-time data work (seeding, backfills, imports), integration checks, and trying a query before you put it in a workflow. Unlike bash, it has the workspace’s integration credentials. Import what workflows import (zitejs/db, zitejs/integrations, or an npm package) and end with a bare return: the value comes back as output (truncated over 20 KB). Pass appId to run as that app, so its own integration settings apply. Relative imports resolve from the app’s directory when appId is set, and from the workspace root otherwise. The script writes to the live database, so anything it seeds is real data.

Checks & logs

Use get_logs to catch runtime errors a type-check can’t. List runs first, then fetch the interesting one by its runId for the full detail. The list filters:

Ship

commit regenerates the .zite/ files, commits and pushes, then builds and snapshots in the background the apps the commit touched. The returned changedApps report buildStatus: "building". It doesn’t type-check, so run check_app first. It refuses without committing when the workspace has an unresolved merge or leftover conflict markers, a rebase in progress, a detached HEAD, commits made by hand, an invalid zite.config.json, or an invalid schedule or webhook declaration on a changed workflow, and each refusal says how to clear it. If main moved on while you worked, commit replays your changes on top and pushes, so re-read a file before you edit it again. Only when the two sides overlap does it stop with their work merged into yours in the sandbox: resolve the conflict markers, git add the files, and commit again.
build_app covers code that reached main some other way: another session committed, or a build failed and you want to retry. It fast-forwards the sandbox to main first and builds every app, or just appId. It refuses if the sandbox has uncommitted edits or local commits, which belong to commit.
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, and internal apps are published for organization members only. The result’s commitSha names the commit that went live.

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.

Marketplace

The Zite marketplace has ready-made solutions (a database plus the apps on it) to start from instead of building from scratch. search_solutions takes one to five phrasings of what you want to build and matches them as plain text against names and descriptions. use_solution copies a solution into a new workspace of your own and returns its id, which works with every other tool. It takes 30 seconds or more, and every call makes a new workspace.

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.