One organizational context layer for your directories, agents, and models.
Roster brings directory users, groups, roles, and workforce data into one participant-resolution layer—then makes it available to AI agents, workflows, applications, and your preferred model provider.
Directory connectors
Bring live users, groups, and membership into Roster from your identity provider, HRIS, directory server, or a spreadsheet.
Turn Okta users and groups into runtime routing context.
Resolve approvers, owners, escalation contacts, and delegates from the Okta users and groups your organization already maintains.
Route through Entra users, groups, and Microsoft 365 context.
Connect the Microsoft Graph directory as the organizational foundation for participant resolution across agents and workflows.
Resolve participants from Google users and groups.
Use your Workspace directory as the source of truth for who approves, owns, or acts on work in Roster projects.
Bring org structure, managers, and roles into resolution.
Materialize Workday workers, managers, and organizational relationships so routing follows the real reporting chain.
Connect self-hosted LDAP or Active Directory servers.
Search and materialize users and groups from LDAP-compatible directories, including on-prem Active Directory.
Bootstrap resolution from a spreadsheet.
Load users, groups, and memberships from a CSV file when a live directory is not yet available or not the source of truth.
AI agents
Give Claude, ChatGPT, Codex, and custom agents a governed way to answer “who should act?” over MCP.
Give Claude a reliable way to resolve who should act.
Connect Claude to Roster over MCP so it can resolve approvers, owners, reviewers, participants, and delegated contacts using current organizational context.
Let ChatGPT resolve who should approve, own, review, or handle the work.
Add Roster to ChatGPT as a custom MCP app and connect conversations to current project, participant, directory, and delegation context.
Give Codex live organizational context around the code.
Resolve service owners, reviewers, deployment approvers, and escalation contacts for engineering work — from the same participant model your team already governs.
Add a reusable “who should act?” capability to any compatible AI agent.
Roster exposes participant resolution through a Streamable HTTP MCP server so any agent, framework, or automation can call the same governed “who” primitive.
Model providers
Configure the resolver model that interprets workflow questions. Roster supports OpenAI, Anthropic, Mistral, and OpenAI-compatible gateways like OpenRouter.
Use OpenAI models to resolve who should act.
Configure an OpenAI model as Roster's resolver to interpret workflow questions and produce structured, auditable participant selections.
Use Claude models to interpret who should act.
Configure Anthropic as Roster's resolver for approval routing, ownership, review, escalation, and delegation-aware participant resolution.
Use Mistral as the resolver model behind Roster.
Configure a Mistral model to interpret workflow questions and help Roster select the right participants across approval, ownership, review, and escalation flows.
Route Roster through a unified model gateway.
Use OpenRouter or another validated OpenAI-compatible gateway to centralize model access, routing, budgets, and policy controls for Roster's resolver.