Authentication
Scripts use personal tokens. Assistants use OAuth. Both act as you, in one workspace, with the access you gave them.
Personal tokens
For the SDK, CI and scripts. Create one in Settings, then Apps and tokens. It's shown once.
scf_live_7Hq2…D0aJOAuth
For assistants over MCP. The client opens a sign-in page and gets a token for one workspace.
https://scaffold.llc/mcpSend a token
Send it in the Authorization header as a bearer token. Test tokens start with scf_test_ and only see the sandbox workspace.
Authorization
import { Scaffold } from "@scaffold-llc/sdk"; // Reads SCAFFOLD_TOKEN when you leave token outconst scaffold = new Scaffold({ token: process.env.SCAFFOLD_TOKEN });Access
ReadEvery command that changes nothing: the GET routes, plus reads sent as POST like
record.query.WriteEverything Read can do, plus every command that changes something. Each write names the command that undoes it.
Owner onlyChanging, deleting or exporting a workspace and managing its members, whatever the token's access.
How OAuth works
- 1Your assistant calls a tool
- 2Scaffold asks you to sign in
- 3You pick a workspace and access
- 4The assistant gets a workspace token
- 5Tools run as you
Each approval covers one workspace. To switch, sign in again. Revoke an app in Settings, then Apps and tokens; its next call fails with 401.
Keep tokens safe
- Keep them in environment variables or your CI's secrets, never in code.
- Give scripts Read unless they need to change things.
- To rotate a token, create a new one, put it in your environment, then revoke the old one with
token.revoke.