Integration

Roster integrates with external systems through two main paths:

• Directory connectors materialize provider data into Roster.
• Model providers interpret resolution questions and produce auditable participant answers.
• Client surfaces expose Roster data and resolution through REST, MCP, CLI, and the platform.

Directory Data Flow

Provider
  external source of truth
        |
        v
Connector
  Roster integration code
        |
        v
Roster materialized state
  directory records, metadata, memberships
        |
        v
Resolver
  project-scoped workflow routing

Use Directory Connectors for provider sync concepts and supported MVP connectors.

Use Model Providers to configure the model runtime for OpenAI, Anthropic, Mistral, Gemini, DeepSeek, Kimi, and other approved models.

Client Surfaces

Surface	Path or package	Primary use
REST API	/api/v1	External integrations, automation, SDK generation.
MCP server	/mcp	Agent-native resolve and exact roster tools.
CLI	@rosterhq/cli	MCP-first terminal and automation workflows.
Web platform	Roster UI	Admin, project owner, connector, and observability UI.