From 52db7dff82dea84fcbea14c7b97c108ef348ed67 Mon Sep 17 00:00:00 2001 From: Dan Moore Date: Thu, 29 Oct 2026 17:38:41 -0600 Subject: [PATCH] added FusionAuth as a provider compatible with MCP auth --- src/pages/provider-list.mdx | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/src/pages/provider-list.mdx b/src/pages/provider-list.mdx index b012dd3..6477d87 100644 --- a/src/pages/provider-list.mdx +++ b/src/pages/provider-list.mdx @@ -16,6 +16,7 @@ This list contains providers that have been tested with MCP Auth. | [WSO2 Identity Server](https://wso2.com/identity-server/) | OpenID Connect | ✅ | ✅ | ✅ | ❌ | | [Auth0](https://www.auth0.com) | OpenID Connect | ✅ | ✅ | ✅ | ⚠️[^4] | | [Descope](https://www.descope.com) | OpenID Connect | ✅ | ✅ | ✅ | ⚠️[^4] | +| [FusionAuth](https://fusionauth.io) | OpenID Connect | ✅ | ✅ | ⚠️[^5] | ✅ | If you have tested MCP Auth with another provider, please feel free to submit a pull request to add it to the list. @@ -27,6 +28,8 @@ If you have tested MCP Auth with another provider, please feel free to submit a [^4]: Auth0 and Descope support multi-resource refresh tokens (MRRT) but not full RFC 8707. Resource indicator support is limited and not standards-based. +[^5]: FusionAuth supports [Client Id Metadata Documents](https://fusionauth.io/docs/lifecycle/authenticate-users/oauth/cimd-registration-lifecycle) but not DCR. + ## Is Dynamic Client Registration required? {#is-dcr-required} [Dynamic Client Registration](https://datatracker.ietf.org/doc/html/rfc7591) is not required for MCP servers and MCP Auth. In fact, you can choose the approach that best suits your needs: @@ -42,4 +45,4 @@ If you have tested MCP Auth with another provider, please feel free to submit a Enter the URL of your authorization server's `issuer` or metadata endpoint below to check if it's compatible with MCP. - \ No newline at end of file +