Use Roster from Claude Code, Codex or another agent
Let an AI agent you already use hire, connect tools, change hours and review approvals in your workspace, with your rights and nothing more.
Roster has an MCP server, the standard way AI agents use apps. Point Claude Code, Codex or any agent that speaks MCP at it, and you can ask in plain words: "create a new hire that chases overdue invoices in #finance", "give Builder read access to acme/web", "what's waiting for my approval?". The agent does it in your workspace, the same way you would in the app.
How it stays safe
- It acts as you. The agent has your role in the workspace, checked on every call. As an owner or admin it can change hires and tools; as a member it can read, add notes, give feedback and do what members do. If you leave the workspace, it stops.
- One workspace. A token works only in the workspace it was made in.
- The same rules as the app. Seats, hire limits, approvals and locked tools (money moving) apply exactly as they do for you. Hires' own requests for approval still go to the person they name; the agent only decides one when you tell it to.
- Some things stay with you. Installing a hire's Slack app, making its GitHub App, signing in to a tool with OAuth and making tokens are done in the app.
- Everything is recorded. Changes an agent makes show in Settings → Activity as made by the token on your behalf, for example "API token “Claude Code” for Ada hired Dunning Desk".
Make a token
- Open Settings → Agents.
- Under What it's for, name it ("Claude Code on my laptop") and click Make a token.
- Copy the token straight away. Roster keeps only a fingerprint and can't show it again. The window also shows the setup lines below, filled in.
Each token shows when it was last used. Click Revoke to stop one at once. Owners and admins see everyone's tokens and can revoke any of them.
Connect your agent
Roster's MCP address is your Roster's address followed by /mcp, for example
https://roster.example.com/mcp. Send the token as Authorization: Bearer <token>.
Claude Code
claude mcp add --transport http roster https://roster.example.com/mcp \
--header "Authorization: Bearer <token>"Codex: add to ~/.codex/config.toml
[mcp_servers.roster]
url = "https://roster.example.com/mcp"
http_headers = { Authorization = "Bearer <token>" }Agents that only start local servers can use Roster's command line, which passes everything on to your Roster:
ROSTER_URL=https://roster.example.com ROSTER_TOKEN=<token> roster mcpAnything else: any MCP client that speaks Streamable HTTP. Answers are plain JSON; there are no sessions to keep.
Teach it Roster
The Use Roster skill explains hires, roles, responsibilities, departments, timecards, approvals and connections to the agent, with the usual ways of doing things and the gotchas. Install it in Claude Code, Codex and other agents that read skills:
npx skills add <Roster's repository> --skill rosterYour hires can have it too: it's in the skills catalog as roster. A hire with it can look things up in Roster and asks a person in the thread before changing anything.
What it can do
The agent sees a handful of tools, each with a few actions:
| Tool | What it's for |
|---|---|
roster_workspace | Start here: who you are, hires on shift, recent and upcoming work, workspace settings, known contacts, and who changed what |
roster_hires | List, read, hire (from a role template), change (hours, pause, instructions) and let go |
roster_responsibilities | What a hire does unasked: weekly, every few hours, or watching a tool |
roster_access | Put a hire in a chat app, give it a tool with an allowlist, read or write access and approvals |
roster_connections | The workspace's chat apps and tools: find a type, connect, test, choose tools |
roster_org | Departments, positions and goals |
roster_approvals | What's waiting for a decision, and deciding |
roster_skills | The skills library, the catalog and each hire's skills |
roster_people | People in the workspace and invitations |
roster_work | Timecards, feedback, work items, follow-ups and shared files |
roster_notes | A hire's notebook and the workspace handbook |
Hires and connections can be named instead of using ids. Lists come a page at a time.
Try it
Create a new hire called Dunning Desk that chases overdue invoices in #finance on weekdays at 9, using our accounting tool, and ask before it emails a customer.
A good agent lists the role templates and your connections, hires with the finance template, puts the hire in your chat with #finance as its home, gives it the accounting tool with approvals on for sending, adds the weekday responsibility, and tells you what it set up.