Stages Documentation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
262:mcpserver [2026/10/28 09:43] – Policnik, Florian262:mcpserver [2026/10/28 10:46] (current) – Policnik, Florian
Line 27: Line 27:
 To enable MCP, add a resource configuration to your IdP, typically by creating an app or client registration. If you already use OIDC, you can use that configuration. To enable MCP, add a resource configuration to your IdP, typically by creating an app or client registration. If you already use OIDC, you can use that configuration.
  
-Add the custom scope ''stages:mcp:read'' to the client. Depending on your IdP, you may find this under "Expose an API" or "Client scopes". In Microsoft Entra ID, specify the Application ID URI using this format:+Add the custom scope to the client: 
 + 
 +''stages:mcp:read'' 
 + 
 +Depending on your IdP, you may find this under "Expose an API" or "Client scopes". In Microsoft Entra ID, specify the Application ID URI using this format:
  
 ''<nowiki>https://stages.example.com/stages/api/1/mcp</nowiki>'' ''<nowiki>https://stages.example.com/stages/api/1/mcp</nowiki>''
Line 54: Line 58:
   * ''audience'': The audience value that Stages, as the resource server, checks in the JWT.   * ''audience'': The audience value that Stages, as the resource server, checks in the JWT.
   * ''usernameAttribute'': The JWT claim containing the username. This is typically the user's email address.   * ''usernameAttribute'': The JWT claim containing the username. This is typically the user's email address.
-  * Configure the filter as you would for SAML or OIDC authentication. TODO+  * Configure the filter as you would for [[.:integration:oidc|OIDC]] authentication.
  
 ==== Stages permissions ==== ==== Stages permissions ====