Document bearer token auth for CLI remote servers#932
Merged
Conversation
The CLI guide covered only OAuth/OIDC flows for remote MCP server authentication. Add a Bearer token subsection covering the --remote-auth-bearer-token and --remote-auth-bearer-token-file flags, matching the coverage already present in the UI guide. Closes #456. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
There was a problem hiding this comment.
Pull request overview
This PR closes a documentation gap in the ToolHive CLI guides by documenting bearer token authentication for remote MCP servers in the existing “Run MCP servers” guide, aligning CLI documentation with the already-documented UI workflow.
Changes:
- Adds a new “Bearer token authentication” subsection under the remote server authentication setup guidance.
- Documents
--remote-auth-bearer-tokenand--remote-auth-bearer-token-file, including security guidance about secret storage and shell history exposure. - Adds a cross-reference to the existing “Inject custom headers” section for servers that require credentials in non-
Authorizationheaders (for example,X-API-Key).
jhrozek
approved these changes
Jun 12, 2026
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
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.
Description
Bearer token support for remote MCP servers shipped in both the UI and CLI, but only the UI guide documented it. This adds a "Bearer token authentication" subsection to the CLI's "Run MCP servers" guide, covering
--remote-auth-bearer-tokenand--remote-auth-bearer-token-file, with a note that the token is held in ToolHive's secrets manager (only a reference is saved to the run config) and a pointer to forwarded headers for servers that expect a non-Authorizationheader likeX-API-Key.Type of change
Related issues/PRs
Closes #456. The UI half was already covered; this completes the CLI side. Feature reference: stacklok/toolhive#3111.