Repository navigation
Point plain /mcp challenges at a v1-owned metadata path - #2203
Closed
RhysSullivan wants to merge 1 commit into
Closed
RhysSullivan wants to merge 1 commit into
RhysSullivan wants to merge 1 commit into
Conversation
RhysSullivan
added this pull request to stack #2205
October 8, 2026 03:37
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-cloud | c9a2516 | Oct 08 2026, 03:41 AM |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-marketing | c9a2516 | Commit Preview URL Branch Preview URL |
Oct 08 2026, 03:39 AM |
Contributor
Cloudflare previewTorn down — the PR is closed. |
@executor-js/cli
@executor-js/config
@executor-js/execution
@executor-js/sdk
@executor-js/codemode-core
@executor-js/runtime-quickjs
@executor-js/plugin-file-secrets
@executor-js/plugin-graphql
@executor-js/plugin-keychain
@executor-js/plugin-mcp
@executor-js/plugin-onepassword
@executor-js/plugin-openapi
executor
commit: |
Collaborator
Author
|
Not needed: v2 now uses mcp.executor.sh, so v1 keeps executor.sh/mcp and its discovery unchanged. Sent from my Claude |
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.
After the planned router cutover, Executor v2 serves
executor.sh/mcp's root discovery documents, including/.well-known/oauth-protected-resource/mcp. v1's 401 on plain/mcpnames that document, so a v1 client whose token expires would discover v2's authorization server and leave v1.Plain
/mcpchallenges now name/.well-known/oauth-protected-resource/_v1/mcp. v1 serves the same document there (resource: https://executor.sh/mcp,authorization_servers: [https://signin.executor.sh]). The router keeps sending requests with an expired v1 token to v1, so a client that followsresource_metadatarefreshes or signs in again on v1's AuthKit._v1can never be an org slug (slugs have no_) and is not anorg_id, so it is classified as the bare document, not an org./.well-known/oauth-protected-resource/mcpis still served.This is a no-op before the cutover: both paths return the same document on the current host.
Tests are in #2204.