Roster for Claude

Give Claude a reliable way to resolve who should act.

Connect Claude to Roster over MCP so it can resolve the right approver, owner, reviewer, participant, group, or delegated contact using current organizational context.

Claude knows how to perform the work. Roster resolves who should be involved.

Connect Roster to Claude Read the setup guide

Last verified 07/13/2026

Human routing requires more than a name in a prompt

Claude can research, analyze, draft, plan, and coordinate complex work.

But enterprise tasks frequently depend on organizational questions that cannot be answered reliably from the conversation alone:

“Who should approve this vendor?”

“Who owns this customer account?”

“Who should review this security exception?”

“Who handles this process in Europe?”

“Who is covering while the normal owner is away?”

The answer may depend on:

The project
The business responsibility
Directory group membership
Region or department
Participant metadata
Active status
Temporary delegation
The requesting user's access

Roster gives Claude a live participant-resolution layer instead of requiring it to infer responsibility from stale documents, previous conversations, or hard-coded names.

How Roster connects to Claude

Roster exposes its agent-native tools through a remote MCP endpoint. Claude connects to that endpoint as a custom connector.

Claude
   ↓ Remote MCP
Roster
   ↓
Projects and participants
   ↓
Directory users, groups, roles, and agents
   ↓
Active memberships and delegations
   ↓
Resolved approver, owner, reviewer, or contact

Roster's MCP surface supports open-ended participant resolution as well as exact tools for projects, participants, labels, delegations, directory records, and Resolve history.

What Claude can resolve

Approval routing

Roster evaluates the relevant project, approval responsibility, associated users or groups, metadata, and active delegations.

“Who should approve the Atlas vendor renewal?”

Project ownership

Claude can retrieve the current organizational answer rather than relying on a name copied into a document.

“Who owns the Acme onboarding project?”

Human review

Roster resolves the participant responsible for privacy, legal, security, finance, or another review function.

“Who should review this proposed customer-data export?”

Delegated responsibility

Active Roster delegations can be included in the resolved answer.

“Who is covering for the normal procurement approver?”

Escalation routing

The answer can be scoped by project, geography, product, severity, or other participant metadata.

“Who should receive this enterprise customer escalation?”

Exact organizational checks

Claude can also use exact Roster tools to inspect accessible projects, defined participants, participant members, labels, delegations, and recent Resolve requests.

Connect Roster to Claude

Your deployed Roster instance needs a public HTTPS MCP endpoint, OAuth enabled for user access, Dynamic Client Registration when Claude registers during setup, and Roster identities mapped to connecting users with the required mcp:* scopes.

Example Roster configuration:

ROSTER_AUTH_URL=https://roster.example.com

ROSTER_OAUTH_DYNAMIC_CLIENT_REGISTRATION=true
ROSTER_OAUTH_UNAUTHENTICATED_CLIENT_REGISTRATION=true

In Claude Desktop, Claude.ai, or Cowork, open Customize → Connectors and add:

Name: Roster
Remote MCP server URL: https://roster.example.com/mcp

Authorize through the Roster OAuth flow. Claude should receive a Roster-issued OAuth token — do not pass an Entra ID, Okta, or other upstream identity-provider token directly to the Roster MCP endpoint.

Teach Claude when to use Roster

Connecting the MCP server makes Roster available, but Claude may not select it automatically for every relevant prompt. Add a Roster skill so Claude knows that the connector is the source of truth for organizational routing.

# Roster

Use the live Roster MCP connector as the source of truth for current
organizational routing answers.

Do not infer current approvers, owners, reviewers, or delegated contacts
from memory, examples, or unrelated files when Roster is available.

## Workflow

1. For questions such as "who should handle this?", "who approves this?",
   "who owns this?", or "who is the delegated contact?", call Roster
   `resolve`.

2. For exact checks involving projects, participants, labels,
   delegations, or membership, use the corresponding Roster tools.

3. Include active delegations when they affect the selected participants.

4. State clearly when Roster returns no result or the request is outside
   the connected identity's scope.

5. Return only the information the user requested.

Roster's current Claude setup guide recommends a skill because making the tools available does not itself guarantee consistent tool selection.

Example: resolve a vendor reviewer

A user asks Claude:

“Review this vendor summary and determine who should handle the security review for Atlas Operations.”

Claude analyzes the supplied vendor information.
Claude recognizes that an organizational routing decision is needed.

Claude calls Roster:

resolve(
  query: "Who should handle vendor security review for Atlas Operations?"
)

Roster evaluates the Atlas Operations project, the relevant participant role, labels and metadata, associated directory users or groups, current active membership, and applicable delegations.
Claude returns the selected reviewer or group.

Claude may then draft a review request or prepare the next workflow step. Roster itself resolves the participant; it does not replace the application that sends or enforces the approval.

Roster complements Claude's other connectors

Claude may already have access to systems such as document repositories, messaging platforms, ticketing systems, CRMs, project-management tools, and source-code platforms. Those systems provide content or execute actions.

Roster answers the organizational question that often comes between understanding and execution: who should be asked, notified, assigned, or held accountable?

Claude reads the request
        ↓
Roster resolves who should act
        ↓
Another connector creates the task or sends the message

Security and governance

Per-user authorization

Each user authorizes the connector under a mapped Roster identity.

Scoped MCP access

Only approved Roster tools are available to the OAuth grant.

Project-level enforcement

Users can only resolve or inspect data allowed by their Roster permissions and project access.

Directory separation

Claude receives the result needed for the request — not unrestricted access to the source Entra, Okta, Workday, LDAP, or Google Workspace tenant.

Auditable resolution

Roster can retain Resolve history and associated operational records according to the deployed edition and configuration.

Controlled write access

Write tools should remain disabled unless the business use case requires Claude to create or modify projects, participants, labels, or delegations.

Frequently asked questions

Roster connects through Claude's support for remote MCP connectors. It does not require a proprietary Claude-only Roster API.

Connect Claude to current organizational responsibility

Give Claude access to live project, participant, directory, and delegation context — without hard-coding organizational logic into prompts.

Connect Roster to Claude Read the Claude setup guide Explore all integrations