Skip to content

added FusionAuth as a provider compatible with MCP auth #79

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mooreds wants to merge 1 commit into
base: master
Choose a base branch
from
Open

added FusionAuth as a provider compatible with MCP auth #79

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion src/pages/provider-list.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand All @@ -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:
Expand All @@ -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.

<TestProvider />
<TestProvider />