Allow the MCP server to start without authorization for inspection#62
Merged
derek-etherton-opslevel merged 1 commit intomainfrom Jul 2, 2025
Merged
Conversation
c11fd3f to
e9c2132
Compare
e9c2132 to
e40f31d
Compare
…fail), but not an invalid one
e40f31d to
38de88c
Compare
Farjaad
approved these changes
Jul 2, 2025
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.
Problem
Third parties are unable to inspect the MCP server and its available tools without having a valid OpsLevel API token.
To better support aggregators like Glama.ai, security scanners, contributors, etc. who might use MCP Inspector or other tools without a valid OpsLevel API key, we should allow this.
Solution
Allow the server to start without authorizing, but still return 401 Unauthorized for any tool requests.
With invalid token:
With valid token:
Checklist