docs(TOF-303): update MCP docs for default enablement - #102
Conversation
MCP is now enabled by default for all organizations. Admins can disable it in Settings → Org → Overview if needed. - Update Permissions & Access note to reflect on-by-default - Remove "MCP must be enabled" from Service Accounts prerequisites - Update Security Considerations bullet from off-by-default to on-by-default - Update Troubleshooting to say "disabled" instead of "not enabled"
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
MCP is only enabled by default for new free and growth accounts created after August 1, 2026. All other accounts still require an org admin to enable it. - Permissions & Access: two-tier note distinguishing new free/growth accounts (on by default) from all others (admin required) - Service Accounts prerequisites: restore step 4 requiring admin enablement, with caveat for new accounts - Security Considerations: restore "must be enabled by admin" bullet with note about new account default - Troubleshooting: restore original wording for admin enablement
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Confidence Score: 4/5Safe to merge after updating the Troubleshooting section to match the new default-on framing. The Troubleshooting section still directs users to 'enable MCP' without distinguishing new accounts (where MCP is on by default and may have been disabled) from legacy accounts (where it was never enabled). For a post-Aug 1, 2026 user hitting the 'MCP access is not enabled' error, the guidance is subtly misleading — they need to re-enable, not enable for the first time. Files Needing Attention: docs/mcp.mdx — Troubleshooting entries at lines 451 and 453
|
| Filename | Overview |
|---|---|
| docs/mcp.mdx | Updates MCP access docs for default enablement on new Free/Growth accounts (post Aug 1 2026); Troubleshooting section still references 'enable MCP' framing without accounting for the new default-on cohort where admins would need to re-enable, not enable |
Reviews (2): Last reviewed commit: "Merge branch 'main' into copilot/tof-303..." | Re-trigger Greptile
MCP is now enabled by default for all net new free & growth orgs — admins can disable it, but no setup is required to connect. The docs previously stated the opposite (off by default, admin must enable).
Changes in
docs/mcp.mdxFixes TOF-303