s&box Collaborator
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@s&box CollaboratorWho has the player controller reserved and what's the task status?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
s&box Collaborator – server
A self-hosted server that makes a small s&box team's coding agents (Claude Code, Codex, Cursor, OpenCode, any MCP client) and s&box editors work like one team: who's doing what, tasks, file reservations, API changes, handoffs, build results and "what changed while you were away" – with GitHub as the source of truth. Pairs with the Collaborator s&box library.
Setup (about 15 minutes)
You need: a small Linux server with Docker (1 GB RAM is plenty), a domain name pointing at it
(e.g. mcp.example.com), and a GitHub account.
1. Get the code and create your settings file
git clone https://github.com/zeljkovranjes/sbox-collaborator-server.git
cd sbox-collaborator-server
cp .env.example .env2. Fill in .env (open it in any editor)
setting | what to put |
|
|
|
|
| run |
| run |
| your GitHub username (you become the admin) |
3. Create a GitHub login app – GitHub ▸ Settings ▸ Developer settings ▸ OAuth Apps ▸ New OAuth App:
Homepage URL:
https://mcp.example.comAuthorization callback URL:
https://mcp.example.com/auth/github/callback
Copy the Client ID and a new Client secret into GITHUB_OAUTH_CLIENT_ID and
GITHUB_OAUTH_CLIENT_SECRET in .env.
4. Start it (HTTPS certificates are set up automatically):
docker compose --profile caddy up -d --buildOpen https://mcp.example.com, click I already have an account ▸ Continue with GitHub. You're
the admin.
5. Create your project – Server admin ▸ Project: a name and your GitHub repo (you/my-game).
6. Invite your teammate – Server admin ▸ Invite teammate, enter their GitHub username. Send them the server address and the server key it shows (privately, it's single use).
7. Connect your coding agents – avatar menu ▸ Connect agents & keys ▸ New access key,
then copy the ready-made setup for Claude Code, Codex, Cursor or OpenCode shown on that page.
Add clients/AGENTS.md to your game repo's CLAUDE.md / AGENTS.md so the
agents follow the team workflow.
Done. Your teammate joins from the s&box editor (View ▸ Collaborator) or the website with the address + server key + GitHub login.
Related MCP server: coordinaut
Optional extras
want | how |
commits, pull requests and issues show up live | GitHub webhook + |
Discord pings for blockers, broken builds, handoffs, messages | paste a Discord webhook URL in Project ▸ Discord notifications (details) |
warn/block commits that touch a teammate's reserved files | the git hook |
nightly backups |
|
Updating later: git pull && docker compose --profile caddy up -d --build.
What's inside
For agents (MCP, 64 tools): start-of-work context sync, catch-up, atomic task claiming, file/asset reservations, handoffs with notes, change announcements (API and breaking changes), decisions, knowledge, messages, build/test results, file history, GitHub and s&box asset tools.
Dashboard: who's online and doing what, tasks, reservations, assets, git, decisions, knowledge, messages, activity, weekly digest.
Security: GitHub login plus single-use server keys to join, per-device access keys (read-only possible, revocable), nothing secret stored in plain text. See docs/security.md.
Documentation
Deployment · Configuration · MCP tools · HTTP API · Developer workflow · GitHub webhooks · Git hook · Discord & digests · Security · Database · Client setup
Development
npm install
SECRET_KEY=$(openssl rand -hex 32) npm run dev # http://localhost:8080, SQLite
npm run dev:web # dashboard with hot reload
npm test # SQLite + PostgreSQL test suitesLicense
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
- ParleyOAuthdev.weldra
Coordination hub for AI coding agents: message teammates, ask humans, audit every event.
The team layer for AI coding agents: shared contracts, collision alerts, E2EE sessions.
- projectsOAuthcloud.tri2b
Task tracking built for coding agents. Work is leased, so two agents never take the same SubTask.
- iKanbanOAuthcom.i-kanban
Tasks, sprints, releases and docs for engineering teams with AI coding agents.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceA coordination layer for coding agents that provides memorable identities, inbox/outbox messaging, searchable message history, and file lease management to prevent conflicts. Uses Git for human-auditable artifacts and SQLite for fast queries, enabling multiple agents to collaborate across projects without stepping on each other.2,156MIT
- AlicenseNot gradedqualityCmaintenanceCoordinates parallel AI coding agents by providing task ownership, scoped file locks, handoffs, and verification workflows.MIT
- AlicenseNot gradedqualityBmaintenanceEnables multiple AI coding agents to collaborate on a project by coordinating tasks, file leases, and messages through a shared hub, preventing conflicts and enabling parallel development.MIT
- AlicenseNot gradedqualityAmaintenanceEnables coordinating Claude Code and Codex across separate Git worktrees with shared issue ownership, file reservations, messages, and explicit handoffs.514 PyPIMIT