Roster's MCP server
Model Context Protocol over Streamable HTTP, for Claude Code, Codex and other agents: send JSON-RPC (initialize, tools/list, tools/call) with Authorization: Bearer <API token>. Answers are JSON; there are no sessions. The tools do what you can do in the app, with your rights, and nothing more. See the guide "Use Roster from Claude Code, Codex or another agent".
apiTokenAuthorizationBearer <token>An API token made in the app (Settings → Agents), for Roster's MCP server.
application/json- body
jsonrpc*stringid?string|numbermethod*stringparams?The JSON-RPC answer.
application/jsoncurl -X POST 'https://app.useroster.work/mcp' \ -H 'Content-Type: application/json' \ -d '{ "jsonrpc": "2.0", "method": "string"}'{ "jsonrpc": "2.0", "id": 1, "result": { "content": [ { "type": "text", "text": "{\"items\":[{\"id\":\"3f0c…\",\"displayName\":\"Builder\"}],\"next\":null}" } ] }}Revoke an API token DELETE
Your own; owners and admins can revoke anyone's. It stops working at once.
The assistant at a glance GET
What the assistant is called on this Roster (`name`, "Front Desk" unless renamed), where you are with the first-run onboarding (`needed` while the workspace has no hires and you haven't finished or skipped it; `done`, `skipped` or `not_needed`), the onboarding conversation to carry on, your recent conversations, suggested prompts, and whether the assistant can answer on this Roster.