Roster for ChatGPT

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.

ChatGPT helps users decide what needs to happen. Roster resolves who should act.

Add Roster to ChatGPT Read the setup guide

Last verified 07/13/2026

Move from generic assistance to organization-aware action

ChatGPT can summarize requests, analyze documents, prepare decisions, and coordinate work.

But it cannot reliably infer current organizational responsibility from a prompt alone:

“Who should approve this contract?”

“Who owns this business process?”

“Who should review this security exception?”

“Who handles this request in Canada?”

“Who is the active delegate?”

These answers change as projects evolve, people move, group memberships change, and responsibilities are delegated. Roster provides ChatGPT with an organization-specific participant-resolution app rather than forcing every user to paste names, org charts, or routing rules into each conversation.

How the Roster app works in ChatGPT

Roster exposes a remote MCP endpoint. A ChatGPT workspace administrator or authorized developer creates and approves a custom app that connects to it.

ChatGPT
    ↓ Custom MCP app
Roster
    ↓
Projects and participants
    ↓
Directory records and memberships
    ↓
Active delegations
    ↓
Resolved owner, approver, reviewer, or contact

ChatGPT's current app framework supports custom MCP-powered apps for approved tools and internal systems. Workspace administrators control app creation, publication, and access according to the available ChatGPT plan and workspace controls.

What users can do with Roster in ChatGPT

Resolve an approver

Roster returns the current approver based on project, participant role, group membership, and active delegations.

“@Roster who should approve the Atlas vendor renewal?”

Identify an owner

Ask ChatGPT to look up business-process ownership rather than pasting a stale org chart.

“@Roster who owns the customer onboarding process for Acme?”

Find a reviewer

Scope by review type — privacy, legal, security, finance — and let Roster select the participant.

“@Roster who should review this proposed data-retention exception?”

Check active delegations

Active delegations surface automatically in the resolved answer.

“@Roster who is covering for the procurement approver?”

Inspect project participants

Use exact tools to enumerate participants in a Roster project.

“@Roster list the participants in Atlas Operations.”

Review recent resolution activity

Pull recent Resolve requests for audit or context.

“@Roster show the latest Resolve request for the Atlas project.”

Create the Roster app

Your Roster deployment needs a public HTTPS MCP endpoint, OAuth enabled, ROSTER_AUTH_URL set to the public Roster origin, Roster identities mapped to ChatGPT users, appropriate mcp:* scopes, and a ChatGPT workspace that supports custom MCP apps.

Example endpoint:

https://roster.example.com/mcp

Create or approve the app using:

Name: Roster
MCP server URL: https://roster.example.com/mcp
Authentication: OAuth
Purpose: Participant resolution and Roster management tools

Users authorize the app through the Roster OAuth flow. ChatGPT should receive Roster-issued MCP OAuth tokens rather than upstream Entra ID, Okta, or other identity-provider tokens.

Recommended tool access

For read-only routing, approve the read scopes below. Add write scopes only when users should intentionally manage Roster data — write scopes do not elevate a user beyond their Roster role or project authorization.

mcp:resolve
mcp:resolve-requests:read
mcp:projects:read
mcp:participants:read

mcp:projects:write
mcp:participants:write
mcp:labels:write
mcp:delegations:write

Roster advertises MCP safety annotations so compatible clients can distinguish read-only, write, and destructive tools. Reconnect or refresh the app when tool metadata and approved permissions change.

Guide users to invoke Roster

For the most reliable first tool call in a conversation, users should select Roster from the app or tool picker, or mention the app explicitly with @Roster. After the first Roster-backed response, follow-up prompts may refer naturally to the result.

# First call — invoke explicitly
@Roster resolve who should handle vendor security review
for Atlas Operations.

# Natural follow-ups
Why were those participants selected?
Are any active delegations involved?
Show the latest related Resolve request.

# Use @Roster again when starting a separate routing task
# or when ChatGPT does not select the app automatically.

Roster's current ChatGPT documentation specifically recommends explicit initial invocation rather than promising automatic app selection for every new conversation.

Example: review a procurement request

A user uploads or describes a proposed vendor purchase and asks:

“Summarize the request, identify any concerns, and use Roster to determine who should approve it.”

ChatGPT summarizes the business request.
ChatGPT identifies the relevant project, region, or approval context.
ChatGPT calls the Roster app.
Roster evaluates the project, the approval participant, participant metadata, associated directory users or groups, current materialized membership, and active delegations.
ChatGPT presents the selected approver alongside its analysis.

Another connected system can then create an approval task, send a message, or update the relevant record.

Roster and company knowledge serve different purposes

Company knowledge and connected search sources help ChatGPT find and synthesize internal information.

Roster is designed for action-oriented participant resolution and exact organizational tools: resolve who should act, inspect participants, check memberships, include delegations, review Resolve history, and manage selected Roster resources when authorized.

Some ChatGPT company-knowledge or deep-research modes may limit custom apps to read/search behavior. Use the standard Roster MCP app workflow for the action-oriented tools described on this page.

Security and governance

Workspace approval

Administrators determine whether the custom Roster app can be created, published, and used.

User authentication

Each user signs in through Roster and receives approved MCP scopes.

Resource-level authorization

The user's Roster identity still governs which projects, participants, and administrative resources they can access.

Controlled actions

Read, write, and destructive tools can be evaluated separately during app review.

Directory isolation

ChatGPT does not directly authenticate against or browse the source enterprise directory. It calls Roster under Roster's scoped access model.

Auditable results

Roster can retain Resolve requests and relevant operational records according to its edition and configuration.

Frequently asked questions

This page describes a customer-deployed custom MCP app connected to that customer's Roster instance. Availability through a public app directory would be a separate distribution path.

Add organizational context to ChatGPT

Give users a reliable app for resolving who should approve, own, review, handle, or receive work — using the organizational data Roster already governs.

Add Roster to ChatGPT Read the ChatGPT setup guide Explore all integrations