Support confidential OAuth clients (client ID and secret) for the Hudu MCP server
Hudu’s MCP server currently registers every OAuth client as a public client. Dynamic client registration returns a client_id only, with token_endpoint_auth_method set to none, and there is no place in Admin > AI > MCP to create or view a client ID and client secret.
Let admins create a confidential OAuth client for the Hudu MCP server from Admin > AI > MCP. This would include:
A generated client ID and client secret
Support for client_secret_post and/or client_secret_basic at the token endpoint
Per-client redirect URIs, for example https://teams.microsoft.com/api/platform/v1.0/oAuthRedirect
The ability to rotate or revoke the secret
Use case:
MSPs standardized on Microsoft 365 Copilot who want Hudu documentation available as a federated source alongside their other Microsoft data.
Log in to comment and vote
No comments yet
Be the first to share your thoughts.