docs(mcp-settings): clarify that MCP users appear only after OAuth and mention Invite users button

[george-dilthey]

What changed

Two targeted additions to docs/mcp-settings.md:

1. Monitoring usage section (line 48): Added one sentence clarifying that users appear in the MCP users table only after completing the OAuth connection flow — invited team members who haven't yet connected through Claude, ChatGPT, or Glean will not appear.

2. "What role should I assign…" FAQ (line 112): Added a sentence noting that admins can also invite reps directly from the MCP settings page via the Invite users button (Sales Rep role is pre-selected), as an alternative to Settings → Team.

Why

Intercom conversation #215475021457316 (Komodo Health, Enterprise): the customer asked "How do I add existing team members to the MCP section in Clay?" and clarified "I invited new users but am unable to add them in the MCP section, they only appear there once they connect clay through an MCP." The human support agent (Peter Johnston) confirmed the correct behavior — the MCP users table only populates after OAuth — but this prerequisite wasn't stated in the "Monitoring usage" section itself. The doc described what the table shows but not the condition for a user to appear in it, leaving admins confused when their invited-but-not-yet-connected members were absent.

Code verification also surfaced a second gap: an Invite users button exists directly on the MCP settings page (SalesRepsList.tsx:77-79) that the doc didn't mention, pointing only to Settings → Team.

Source link(s)

• Intercom conversation: https://app.intercom.com/a/inbox/w28k1kwz/inbox/conversation/215475021457316
• Verifier evidence — Invite users button: clay-base/apps/frontend/src/components/MCPPage/SalesRepsList.tsx:77-79; clay-base/apps/frontend/src/components/MCPPage/InviteMCPUsersModal.tsx:13-29 (modal pre-selects workspace-sales-rep role)
• Verifier evidence — OAuth required: clay-base/apps/api/v3/sales-reps/services/sales-reps.service.ts:102-116 + sales-reps.endpoints.ts:44 (endpoint hardcodes requireConnectedPlatforms: true, filtering out users with no connected platform)
• Corroborating Slack: https://clay-hq.slack.com/archives/C07481RGM7H/p1779911412849399 (Sigma workspace thread confirming the correct order: invite → accept → OAuth → appear in MCP users table)

Uncertainties

The MCP settings page is gated by Eppo feature flag EnableSalesRepCreditControlsPage (code default: false). A Slack announcement from April 22, 2026 in #all-product-progress confirmed the feature went live for Launch, Growth, and Enterprise plans — consistent with the existing doc's plan availability text. Both changes are scoped to functionality the doc already describes for those plans.

Note: pre_pr_check returned ok: false flagging the overlap with PR #1525 on the same file. I evaluated the overlap (see Related observations) and determined my changes are materially distinct — option (b) per the tool's guidance.

Related observations

• PR docs(mcp-settings,credit-budgets): document per-user MCP spend tracking and Sequencer-MCP bundling #1525 is open on the same file but covers different content: a Budgets-tab credit-tracking note and a "Can I disable Sequencer access for Sales Rep users?" FAQ. Neither addresses the OAuth prerequisite for appearing in the MCP users table, nor mentions the Invite users button. Changes here do not conflict with docs(mcp-settings,credit-budgets): document per-user MCP spend tracking and Sequencer-MCP bundling #1525.
• Minor unintended drift in the SSO section: "how users authenticate" became "how they authenticate" during file reconstruction. Semantically identical but worth a reviewer eyeball.

Closes DOC-1124

[linear-code]

DOC-1124