Roster

MCP

Roster exposes an MCP server at:

/mcp

MCP is the primary agent-native integration surface. It supports open-ended business routing through resolve and exact tools for project, participant, label, delegation, directory, and resolve-history workflows.

Use MCP For

• natural-language routing questions
• agent-native project and participant management
• exact membership checks
• delegation management
• resolve request history

Client Setup

Use the dedicated setup guides for client-specific connection details:

• Claude
• Codex
• ChatGPT

Tool Routing

Use resolve for open-ended business questions such as who should handle a task, who to contact, who is responsible, or who can act through an active delegation.

Use exact tools for exact data checks. For example, to check whether a user or group belongs to a project, list projects, list participants, then list participant members.

Resolve Runtime

The resolve tool accepts a natural-language query. Project references, labels, participant roles, and other constraints are extracted by the resolver. The runtime then selects matching participants and resolves associated users, including directly associated users, active members of associated groups, and active delegations.

When a query includes a threshold such as an amount, region, tier, or scope and candidate participants expose matching limits, Resolve should choose the narrowest participant that satisfies the threshold. It should not add senior, backup, or escalation participants unless the threshold exceeds the lower limit or the user explicitly asks for escalation.

When a query asks for multiple responsibilities, Resolve treats each responsibility separately and selects participants only when the provided roster data shows they handle that responsibility.

Top-level MCP response status is one of:

• ok
• configuration_error
• agent_error
• server_error

When status is ok, result.resolution_status is one of:

• success
• out_of_scope
• not_found