Agents build the app through its MCP server: files, models, fields, actions and grants
Development's MCP server now has builder tools: list, read, search, write, edit and delete the app's files, read the dev server's problems and the environment variables, and, for team owners and admins, set a variable and deploy. Five schema-level tools, create_model, add_field, change_field, create_action and grant_role, write well-formed files (storage keys set and kept on a rename, params as a plain literal, grants in permissions.ib.ts) and answer with the reference entry they produced and what a schema change does to the records that exist. Production's server keeps the reading tools alone.
Writes go through the same path as a dashboard save: each names the copy it read, so a file changed meanwhile comes back as a conflict instead of being overwritten; the generated client types follow and development's dev server hot-reloads. The Apps assistant uses the same schema tools, behind its schema approval.
The storage listing tool is now list_stored_files; it was list_files, which now lists the app's code.
More in Building through MCP.