docs: OAuth MCP clients connect to /mcp without a tenant key - #215
Merged
Merged
Conversation
The OAuth endpoint required the tenant in the URL, which meant knowing a key nothing tells a self-signup user - and /mcp is also the endpoint this page gives for access tokens, so pointing an OAuth client at the documented URL failed with no way forward. The platform now takes the tenant from your membership on the bare /mcp, so that is what the page recommends. The tenant-scoped form stays documented for the case that still needs it: belonging to more than one tenant, where the connection cannot infer which you mean and says so, listing the URLs to choose from.
The table-width rule wants every row of a table the same character width, and this table was never padded. It passed until now only because the linter reports findings the pull request introduces, and nothing had touched the file since the rule arrived - editing one cell made all three rows count as ours. Padded to the repo's usual style; the content is unchanged.
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.
Why
The OAuth row told people to connect to
https://platform.steadybit.com/mcp/<tenant>— a key that nothing ever tells a self-signup user./mcpis also the endpoint this same page gives for access tokens, so pointing an OAuth client at the documented URL authenticated successfully and then failed with no way forward.The platform now takes the tenant from your Steadybit membership on the bare
/mcp(steadybit/platform#2028, merged todevelop), so that is what the page recommends.What changed
https://platform.steadybit.com/mcpfor both methodsclaude mcp addexample drop the/<tenant>suffixOne file,
integrate-with-steadybit/remote-mcp-server.md.Timing
The platform change is on
developand ships with the next platform release. Until then the bare/mcpstill rejects an OAuth token, so please hold this until that release is out — otherwise the docs describe an endpoint that does not yet behave this way. The tenant-scoped URL keeps working throughout, so nothing anyone has configured breaks either way.Verified
Both forms tested on dev: a single-tenant user connects to the bare
/mcp, and the tenant-scoped URL connects for a user who belongs to two tenants.