buildmymcpserver/apps
Marco Sadjadi 1d845abf92
All checks were successful
Deploy to Production / deploy (push) Successful in 1m24s
fix(oauth): resolve server by path segment, not subdomain
Claude Desktop got past discovery + DCR but /oauth/authorize rejected
the resource parameter with invalid_resource. Root cause:
resolveServerByResource() extracted the slug from the URL's first
hostname label (subdomain routing), but production runs path routing —
mcp.buildmymcpserver.com/<slug>. The function saw resource
"https://mcp.buildmymcpserver.com/text-generation", tried to look up
slug="mcp", missed, returned null → 400.

Path lookup is now tried first (matches the production topology and
the resource URL we publish via /.well-known/oauth-protected-resource),
port lookup second (local dev), subdomain lookup last with an explicit
"mcp" guard so the legacy path doesn't shadow the new one.
2026-05-28 19:58:31 +02:00
..
api fix(oauth): resolve server by path segment, not subdomain 2026-05-28 19:58:31 +02:00
generator fix(runner): correct PUBLIC_URL + mount runner-map volume 2026-05-28 17:54:56 +02:00
runner-template fix(docker): healthcheck must hit 127.0.0.1, not localhost 2026-05-21 18:07:01 +02:00
web fix(oauth): allow generic RFC 7591 DCR + expand install snippets 2026-05-28 17:20:01 +02:00