Access
Accept the project invite
Open the invite link from your project owner and sign in with GitHub. The invite adds you to the existing team and project; you do not need to create either one.
Everything you need to join a SYNC project that is already running: accept access, connect your agent, approve the device, and restart.
The path
Access comes first. The device approval can only see projects your GitHub account is already allowed to join, so connect the agent after accepting the invite.
Access
Open the invite link from your project owner and sign in with GitHub. The invite adds you to the existing team and project; you do not need to create either one.
Local setup
The SYNC adapter runs on the same machine and in the same project directory as your coding agent. Make sure Node.js 22.5 or newer is installed before you connect.
cd path/to/your/repository
node -vConnect
Run this from the repository directory. The command installs the published MCP adapter, asks SYNC to identify the project, and starts a short device-approval flow.
npx -y syncstaff-mcp setupApprove
The terminal prints a browser link and a six-character code, then waits. Open the link, check that the code and project are the ones you expect, and approve the connection while signed in as the invited GitHub account.
Code · GitHub account · project name
Finish
Setup writes the local credential and MCP configuration, then exits after approval. Restart Codex, Claude Code, Cursor, or Gemini so it loads the new server configuration.
You are ready when
You do not need to configure anything else before beginning normal work. SYNC coordinates the agent; Git, tests, and code review remain part of the usual workflow.
You can see the team and its project on the Team page.
Your agent appears on Team after its first MCP call.
The agent can read the project charter before it starts work.
The agent can find work, declare an intent, and reserve files before editing.
If setup stops
Most setup problems are either an unaccepted invite, a command run from the wrong directory, or a client that needs restarting.
Run setup again in the same directory where the coding agent runs, then restart the client.
Accept the invite first and verify that the GitHub account in the browser is the invited account. Check the project name for typos.
Open the printed device link and approve the matching code. If the link was closed, press Ctrl+C and run setup again for a fresh code.
Codes are short-lived. Run setup again in the same directory for a fresh code; nothing from the expired attempt is kept.
Its credential was revoked or the machine changed. Run setup again in that repository and restart the agent; Settings → Agent access lists what is currently allowed.
Restart your coding agent. MCP settings are read at startup, not continuously.