Skip to content

DOCS-1534 - MCP and OAuth docs#6574

Merged
kimsauce merged 26 commits into
mainfrom
DOCS-1534
May 13, 2026
Merged

DOCS-1534 - MCP and OAuth docs#6574
kimsauce merged 26 commits into
mainfrom
DOCS-1534

Conversation

@kimsauce
Copy link
Copy Markdown
Collaborator

@kimsauce kimsauce commented Apr 11, 2026

Purpose of this pull request

Introduces a new preview doc, OAuth client setup, and updates to existing MCP Server doc. Includes structural and AEO/GEO improvements made during review.

MCP Server doc

  • Full setup instructions for three MCP clients: ChatGPT, Claude Code CLI, and VS Code
  • Authorization Code OAuth flow for ChatGPT and Claude Code CLI
  • Client Credentials OAuth flow for VS Code
  • Client-specific authentication sections (not global)
  • Available MCP tools reference (alerts, dashboards, Cloud SIEM, log search, user management)
  • Example workflows, usage guidance, cost controls, and security/data governance sections
  • FAQ as ### headings (AEO/GEO optimization)
  • ## Additional resources section with demo walkthrough link
  • Official MCP logo added in Sumo Logic brand blue (static/img/icons/mcp-logo.svg)

OAuth Client Setup doc — new doc:

  • Covers both OAuth 2.0 flows: Authorization Code and Client Credentials
  • How permissions work (intersection of roles and scopes)
  • Service account setup and OAuth client creation
  • Token generation with deployment endpoint guidance
  • Security best practices and service account content ownership sections
  • FAQ as ### headings (AEO/GEO optimization)

Revisions per SME review (kdwink):

  • Removed "You'll need a paid ChatGPT account" note — free accounts now support MCP servers
  • Updated UI path from "Administration > Security > OAuth" to "Administration > Security > OAuth Clients"
  • VS Code screenshots pending (Keith providing updated images)

Select the type of change

  • Minor Changes - Typos, formatting, slight revisions
  • Update Content - Revisions, updating sections
  • New Content - New features, sections, pages, tutorials
  • Site and Tools - .clabot, version updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

Ticket (if applicable)

https://sumologic.atlassian.net/browse/DOCS-1534

Updates the MCP server documentation to include ChatGPT as a supported client
and adds comprehensive setup instructions for the Authorization Code OAuth flow.
Restructures authentication section to clearly distinguish between Authorization
Code flow (for ChatGPT and Claude Code) and Client Credentials flow (for VS Code
and Claude Code).

Key changes:
- Add ChatGPT setup instructions with UI-based OAuth client creation
- Add Authorization Code flow setup for Claude Code
- Update status from "Closed Preview" to "Private Preview"
- Reorganize authentication section with comparison table
- Use AuthorizationCodeClient terminology to match UI

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@cla-bot cla-bot Bot added the cla-signed Contributor approved, listed in .clabot file label Apr 11, 2026
@kimsauce kimsauce self-assigned this Apr 11, 2026
@kimsauce kimsauce changed the title DOCS-1534 - Add ChatGPT support and Authorization Code OAuth flow to MCP server docs DOCS-1534 - Add ChatGPT support and 3LO flow to MCP docs Apr 11, 2026
@kimsauce kimsauce marked this pull request as draft April 11, 2026 09:51
kimsauce and others added 4 commits April 13, 2026 04:56
Add prominent note callout before Step 3 curl examples to make deployment URL requirements clearer for Preview customers reading top-to-bottom. Addresses feedback that deployment info wasn't immediately obvious.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Update OAuth doc title to "OAuth Client Setup"
- Restructure MCP authentication sections to be client-specific
- Add deployment endpoint clarifications throughout both docs
- Add tip about discovering token endpoint programmatically
- Consolidate redundant content in OAuth intro

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@kimsauce kimsauce changed the title DOCS-1534 - Add ChatGPT support and 3LO flow to MCP docs DOCS-1534 - Improve MCP and OAuth documentation structure and clarity Apr 15, 2026
@kimsauce kimsauce changed the title DOCS-1534 - Improve MCP and OAuth documentation structure and clarity DOCS-1534 - Add 3LO/OAuth doc, improve/update MCP doc Apr 15, 2026
@kimsauce kimsauce requested review from DDeC7 and ganano April 15, 2026 03:57
kimsauce and others added 2 commits April 14, 2026 21:00
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@kimsauce kimsauce changed the title DOCS-1534 - Add 3LO/OAuth doc, improve/update MCP doc DOCS-1534 - Add Auth doc, update MCP doc Apr 17, 2026
@kimsauce kimsauce added doc:update Revisions and updates to content doc:new New section or topic to content labels Apr 17, 2026
@kimsauce kimsauce requested a review from kdwink April 17, 2026 09:20
kimsauce and others added 3 commits April 17, 2026 02:54
Implements feedback from auth-code-flow-docs-update-review.pdf:

OAuth documentation changes:
- Remove MCP server parenthetical reference from intro
- Change "your application" to "an external application" in Authorization Code flow intro for clarity
- Update token expiration to reference expires_in property instead of hardcoded "1 hour"
- Update refresh token rotation language (always rotates, not configurable)
- Remove personal access key prerequisite (OAuth clients now created via UI)
- Add UI-first approach for service account ID retrieval with API as alternative
- Replace curl-based OAuth client creation with UI steps for Client Credentials flow
- Preserve API examples in collapsible sections for advanced users
- Fix highlighted field in service account JSON response (id not modifiedAt)

MCP server documentation changes:
- Change "external copilots and proprietary models" to "MCP clients (external AI models)"
- Remove em dashes and improve sentence structure per style guide

Style fixes:
- Remove all em dashes per Sumo Logic style guide
- Fix hyphenation (MCP-clients → MCP clients)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@kimsauce kimsauce changed the title DOCS-1534 - Add Auth doc, update MCP doc DOCS-1534 - MCP and OAuth docs Apr 17, 2026
Copy link
Copy Markdown

@ganano ganano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Took a first pass through the docs.

Comment thread docs/api/mcp-server.md Outdated
Comment thread docs/api/mcp-server.md Outdated
Comment thread docs/api/mcp-server.md Outdated
Comment thread docs/api/mcp-server.md Outdated
Comment thread docs/api/mcp-server.md Outdated
Comment thread docs/manage/security/oauth.md Outdated
Comment thread docs/manage/security/oauth.md Outdated
Comment thread docs/manage/security/oauth.md
Comment thread docs/manage/security/oauth.md Outdated
Comment thread docs/manage/security/oauth.md Outdated
@kimsauce
Copy link
Copy Markdown
Collaborator Author

kimsauce commented May 5, 2026

Hi @ganano , thanks for the thorough review! Here's what I addressed based on your feedback:

docs/api/mcp-server.md

  • Removed the Client Credentials flow sections from the Claude Code CLI setup. Auth Code flow is now the only documented path for Claude. VS Code remains on Client Credentials.
  • Added --scope user / --scope project options to the claude mcp add command in the Auth Code flow setup, matching the pattern used for Client Credentials. Updated the launch step to note that user scope (recommended) works from any directory.
  • Added the deployment domain tip after the MCP Server URL in the ChatGPT section, consistent with the tips that already existed for VS Code and the (now-removed) Client Credentials options.

docs/manage/security/oauth.md

  • Simplified the Auth Code flow section per your suggestion... removed the manual curl steps (Authorize, Exchange, Refresh) and replaced them with a note about the .well-known/oauth-authorization-server discovery endpoint, and a tip about the permissions intersection model (user roles ∩ client scopes ∩ requested scopes).
  • Changed service.sumologic.comapi.sumologic.com in the API call examples (token usage example and the APIs FAQ), and added deployment tips pointing to the endpoints reference page.
  • Updated the deployment placeholder in the "Discovering endpoints programmatically" tip to be consistent with the rest of the doc.
  • Scoped the "Protect client secrets" security practice to call out Client Credentials as the higher-risk case; noted that clientSecret in Auth Code flow carries less risk.
  • Updated the revoke access FAQ to cover Auth Code flow: revoking Authorization Consent causes the next token refresh to fail (current token stays valid until expiry).
  • Added a new FAQ: "What happens if a user's roles change in Authorization Code flow?" — covers how role changes take effect at next token refresh for both restrictions and expansions.

One thing I wasn't sure about, your line 49 comment mentioned adding a tip about how permissions are calculated specifically for Auth Code. I added that as a :::tip block in the "Complete the OAuth flow" section. Let me know if the wording captures it correctly or if the intersection should be described differently.

kimsauce and others added 2 commits May 4, 2026 19:19
…h.md

Replace repeated definitions in the API collapsible and two FAQ entries
with cross-references to the canonical explanations in the respective
flow sections.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…OAuth docs

- Merge repeated permissions intersection callouts into a single
  "How permissions work" tip in the oauth.md intro; replace duplicates
  with cross-references
- Standardize all deployment endpoint admonitions to :::note across
  both mcp-server.md and oauth.md
- Add explicit HTML anchor for the permissions callout to fix broken
  anchor build error

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
ganano

This comment was marked as resolved.

@kimsauce kimsauce removed the doc:update Revisions and updates to content label May 6, 2026
@kimsauce kimsauce removed request for DDeC7 and jpipkin1 May 8, 2026 00:57
kimsauce and others added 8 commits May 11, 2026 14:15
- Remove paid account requirement note for ChatGPT MCP clients
- Update UI path to Administration > Security > OAuth Clients

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Replace <a id="how-permissions-work"> with a proper heading using a
custom ID, which Docusaurus's anchor checker can resolve.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Move mcp-server.md from docs/api/ to docs/platform-services/
- Add CID redirect from old to new MCP doc URL
- Add MCP Server card to platform-services/index.md (commented out until GA)
- Add official MCP logo (mcp-logo.svg) in Sumo Logic brand blue
- Convert FAQ accordions to ### headings in mcp-server.md and oauth.md for AEO/GEO
- Add ## Additional resources section with demo link to mcp-server.md

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@cla-bot cla-bot Bot removed the cla-signed Contributor approved, listed in .clabot file label May 12, 2026
@kimsauce kimsauce added doc:update Revisions and updates to content cla-signed Contributor approved, listed in .clabot file labels May 12, 2026
Comment thread docs/api/mcp-server.md Outdated
@kimsauce kimsauce requested a review from margaret-selid May 12, 2026 22:02
@kimsauce kimsauce enabled auto-merge May 13, 2026 18:34
@kimsauce kimsauce requested a review from ganano May 13, 2026 19:17
@SumoLogic SumoLogic deleted a comment from cla-bot Bot May 13, 2026
@kimsauce kimsauce added this pull request to the merge queue May 13, 2026
Merged via the queue into main with commit fb20153 May 13, 2026
4 checks passed
@kimsauce kimsauce deleted the DOCS-1534 branch May 13, 2026 19:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed Contributor approved, listed in .clabot file doc:new New section or topic to content doc:update Revisions and updates to content

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants