Summary
Add MCP tools for managing OIDC applications/clients. This is one of the highest-value MCP capabilities — creating and configuring OIDC clients is a common task that's currently done via the admin UI or raw SQL.
Depends on #232.
Tools
| Tool |
API Endpoint |
Description |
list_applications |
GET /{vs}/projects/{slug}/applications |
List OIDC clients in a project |
get_application |
GET /{vs}/projects/{slug}/applications/{id} |
Application detail |
create_application |
POST /{vs}/projects/{slug}/applications |
Create OIDC client (name, displayName, type, redirectUris, postLogoutRedirectUris, deviceFlowEnabled) |
update_application |
PATCH /{vs}/projects/{slug}/applications/{id} |
Update displayName, claimsMappingScript, deviceFlowEnabled |
delete_application |
DELETE /{vs}/projects/{slug}/applications/{id} |
Delete an OIDC client |
Notes
create_application should support both public and confidential types
- For confidential clients, the generated secret is returned once — the tool response should make this clear
- Redirect URI validation is handled server-side
Summary
Add MCP tools for managing OIDC applications/clients. This is one of the highest-value MCP capabilities — creating and configuring OIDC clients is a common task that's currently done via the admin UI or raw SQL.
Depends on #232.
Tools
list_applicationsGET /{vs}/projects/{slug}/applicationsget_applicationGET /{vs}/projects/{slug}/applications/{id}create_applicationPOST /{vs}/projects/{slug}/applicationsupdate_applicationPATCH /{vs}/projects/{slug}/applications/{id}delete_applicationDELETE /{vs}/projects/{slug}/applications/{id}Notes
create_applicationshould support bothpublicandconfidentialtypes