docs(mcp-settings): rename page, add Getting started section, expand Functions guidance, add 5 new FAQs

[george-dilthey]

What changed

Applied the upstream Webflow delta to docs/mcp-settings.md. Specific changes from the upstream collection_item_published event:

• H1 renamed: "MCP settings" → "MCP in Clay"
• Subtitle extended with new admin-focused summary line ("manage rep access, credit limits, and Functions from one place")
• Platform list updated: Removed "Codex" (dropped from upstream); "Codex" entries also removed from "Does Clay provide an MCP server URL" FAQ and "How do I disconnect" FAQ (generalized to "Other tools")
• Microsoft Copilot added as BETA with explicit framing in Getting started links and MCP server URL FAQ
• New "Getting started" section inserted: 5-step admin onboarding guide (invite reps with Sales Rep permission type, set default credit budget, enable Functions, configure Audiences, share connection guides)
• "Enabling a function for MCP" section: typo fix ("it's" → "its"), two new sub-bullets (enrichment column requirement; name conflict warning with built-in tools), name/description bolded, "MCP app" → "function", intro updated to "their AI tool"
• "Can admins remove a rep" FAQ: updated answer from "low value" → "set their credit limit to 0, which hard-blocks further actions without removing them from the workspace" (verifier: PASS)
• Five new FAQ entries from upstream: "If a rep isn't on Audiences..."; "When a rep runs an action... does it count as a Clay action?"; "Does Clay's MCP use our data to train AI models?"; "How do Anthropic and OpenAI handle data from MCP requests?"; "What can the AI tool access in our workspace when reps connect via MCP?"
• New "## Troubleshooting" section at end linking to MCP Troubleshooting & FAQ page
• All existing local enrichments preserved: Audiences troubleshooting blocks, SSO FAQ, third-party gateway FAQ, Sales Rep role FAQ, waterfall results FAQ

Confirmed no overlap with existing open PRs:

• PR docs(mcp-settings): clarify that MCP users appear only after OAuth and mention Invite users button #1537 adds: MCP users table note about OAuth completion + invite-from-MCP-page + SSO wording — not touched by this PR
• PR docs(mcp-settings,credit-budgets): document per-user MCP spend tracking and Sequencer-MCP bundling #1525 adds: Budgets tab vs MCP tab note + Sales Rep Sequencer access FAQ — not touched by this PR

Why

Triggered by a Webflow collection_item_published webhook for https://university.clay.com/docs/mcp-settings. The upstream page received a substantial update: renamed from "MCP settings" to "MCP in Clay", Getting started section added, Codex dropped as a supported platform, Microsoft Copilot added (BETA-gated by Eppo flag), Functions section expanded with two new configuration guidance bullets, "Can admins remove" FAQ answer updated with explicit credit limit 0 instruction, and five new FAQs added covering data privacy, credit counting, and AI access scope.

Source link(s)

• Upstream Webflow page: https://university.clay.com/docs/mcp-settings
• Verifier evidence:
  • Microsoft Copilot BETA: clay-base/apps/frontend/src/components/MCPPage/ConnectPlatformsSection.tsx:40,72 — gated by useEppoFeatureFlagAsBoolean(EppoFeatureFlags.EnableCopilotMCP); server-side OAuth config live at clay-base/apps/api/v3/mcp/STATIC_OAUTH_CONFIG.md:16
  • Credit limit 0 hard-blocks (PASS): clay-base/apps/api/v3/billing/services/credit-balance.service.ts:661 — balance 0 with any cost > 0 triggers ERROR_WORKSPACE_SALES_REP_CREDIT_LIMIT_REACHED
  • Function enrichment column requirement (PASS): clay-base/apps/api/v3/mcp/tools/subroutine-tool-handlers.ts:457,537
  • Function name conflict warning (PASS): clay-base/apps/api/v3/mcp/services/mcp-exclusion.service.ts:41-47

Uncertainties

• Glean: Verifier returned FAIL — no Glean-specific adapter or OAuth client in clay-base. Glean is a generic MCP host that can connect via standard MCP protocol without Clay-specific code. LOCAL already documented Glean from a prior session and upstream explicitly includes "Using Clay in Glean" links in both old and new Webflow versions. Glean references preserved consistent with prior local enrichments and upstream, but should be confirmed with the team — if Glean isn't officially supported, Glean references across the doc need a cleanup PR.
• Data training / Anthropic & OpenAI data handling FAQs: References third-party policies. "Clay itself does not store customer table data for other customers" is a Clay legal/infrastructure claim not verified against code. Content sourced directly from upstream; links to official policy pages for current details.
• "No MCP surcharge" claim: Sourced from upstream; consistent with credit system behavior per verifier evidence but not verified against a specific code constant.

Related observations

• PR docs(mcp-settings): clarify that MCP users appear only after OAuth and mention Invite users button #1537 and PR docs(mcp-settings,credit-budgets): document per-user MCP spend tracking and Sequencer-MCP bundling #1525 are both open on docs/mcp-settings.md. This PR's content does not overlap with either — reviewer should reconcile all three at merge time.
• docs/using-clay-in-glean.md and docs/using-clay-in-microsoft-365-copilot.md don't exist in repo yet — Getting started section links to them on university.clay.com. These will need to be synced from Webflow when published.
• Frontmatter title remains "MCP settings" per sync instructions; only the H1 body heading was updated to "MCP in Clay".

Closes DOC-1131

[linear-code]

DOC-1131