Distinguish OAuth providers (outbound) from OAuth clients (inbound)#33
Merged
Conversation
Lead the OAuth Provider and OAuth Client pages with directional authentication framing so readers grasp the distinction on first scan. Add a reciprocal IMPORTANT block to remote-mcp-clients.adoc, remove the redundant mid-page NOTE, sweep "auth" -> "authentication" in prose across both pages plus user-delegated-oauth.adoc, and replace internal "proto" jargon with "API definitions" in the provider callout. Promote Remote MCP Clients to the top of the Integrations nav and shorten its label - it is the canonical onboarding for remote-MCP integrations and the other entries are still stubs. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
✅ Deploy Preview for redpanda-agentic-data-plane ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
mcp/pages/oauth-providers.adoc) and OAuth Client (integrations/pages/remote-mcp-clients.adoc) pages with directionalIMPORTANTblocks so readers grasp on first scan that providers govern outbound authentication (ADP → upstream services) and clients govern inbound authentication (external apps → ADP).remote-mcp-clients.adoc; sweepauth→authenticationin prose across both pages plususer-delegated-oauth.adoc(CLI flag names like--auth-endpointpreserved); replace internalprotojargon withAPI definitionsin the provider callout.OAuth provider/OAuth clienthover text) ride along on Add ADP-specific glossary terms for GA docs#1691; tooltips render the new inbound/outbound framing once that PR merges.Preview pages
Test plan
npm run buildcompletes cleanly (verified locally — no new warnings on the four touched pages).oauth-providers/— newIMPORTANTblock at the top of the page, bullets call out outbound/inbound, "API definitions" replaces "proto".remote-mcp-clients/— newIMPORTANTblock before "When to use this"; no duplicate NOTE mid-page; prose now reads "authentication" throughout.user-delegated-oauth/— "In the authentication section" and "needs this server's authentication" both read correctly.glossterm:OAuth provider[]/glossterm:OAuth client[]tooltips on the glossary page render the new inbound/outbound hover text.🤖 Generated with Claude Code