Hello everyone !
I am setting up a remote MCP server and I am currently having a problem trying to define custom scopes for Role Based Access Control (RBAC).
I created 2 scopes called “mcp:access
” and “mcp:tools
”.
On the RBAC Policy page on the Stytch Dashboard, I have the following scopes :
- “
openid
”, - “
profile
”, - “
email
”, - “
phone
”, - “
offline_access
”, - “
mcp:access
”, - “
mcp:tools
”
So I have 7 scopes on the dashboard : 5 built-in scopes + 2 custom scopes.
Yet, these 2 new custom scopes are not advertised on the /.well-known/oauth-authorization-server
route of my stytch project.
During the OAuth 2.0 flow, this route is supposed to tell to the OAuth Client what are the supported scopes. But instead of getting all scopes (built-ins + custom), I only get the built-in ones:
When I request :
https://<my-stytch-project-link>/.well-known/oauth-authorization-server
I get this answer :
{
…
… "scopes_supported":["openid","profile","email","phone","offline_access"], …
… }
As you can see, the 2 custom scopes do not appear.
Consequently, my OAuth Client (Claude) asks only for the built-in scopes during the authorization request.
Am I misunderstanding something or it’s on Stytch’s side ?
Thank your for your answers !