MCP server
Every command is an action of a tool. Your assistant sees 26 tools: per group one that reads, one that writes and one for the commands that can't be undone. A tool's schema lists its common actions' inputs, and command_describe gives any other's.
- Server
https://scaffold.llc/mcp- Transport
- Streamable HTTP
- Sign-in
- OAuth, one workspace per approval
- Tools
- 26 tools, named like task_read and task_write
What a session looks like
Tools
Approvals
Scaffold's own agents ask a person before every deploy and rollback, and before they archive anything, change more than 10 things in one run, or close a task as Triage. No setting skips the ask for a deploy or rollback, which shows the project, the upload, any release command, the deploy it replaces and whether the database goes back too; undoing the run leaves it live, so deploy.rollback takes it back. Env vars and secrets, billing, members and tokens stay with people: an agent cannot run them at all. The run then waits, with that change not made, until the person who started it or a workspace owner approves it in the console, or denies it there or with run.deny; run.approval_list lists the changes waiting on you: your own runs', and every member's for an owner, each with who started it. Approving makes the change and the run goes on; denying stops the run. Calls from your own assistant run as you; your client asks before each call to a tool that can't be undone.