Connect another MCP client to Nylon

Nylon’s sign-in admits AI assistants by their OAuth redirect URL. The assistants in the sidebar are registered today. Another client can connect once we add its redirect URL.

Ask for a client to be added

Email support@usenylon.com with:

• the client’s name and a link to it;
• its OAuth redirect URL or URLs;
• whether it runs on a server, as a desktop or mobile app, or on the user’s machine.

Until it’s added, the client’s registration request returns 400 invalid_client_metadata.

What the client needs to support

Requirement	Detail
Transport	Streamable HTTP at https://mcp.usenylon.com/mcp
Discovery	OAuth protected resource metadata (RFC 9728) from the WWW-Authenticate challenge, then authorisation server metadata (RFC 8414)
Registration	Dynamic client registration (RFC 7591) with the registered redirect URL
Grant	Authorization code with PKCE S256, as a public client (no client secret)
Resource	resource=https://mcp.usenylon.com/mcp (RFC 8707) on the token request
Where sign-in runs	On a server or in a native app. Nylon’s sign-in endpoints don’t allow cross-origin browser requests, so a client running in a web page can’t complete sign-in.

The full flow is in Authentication.

Note

Nylon doesn’t support OAuth client ID metadata documents today, or clients that need a client secret. Clients that offer a choice should use dynamic client registration as a public client.