Incompatible auth server: does not support dynamic client registration

Khanna Ji
Tera Guru

I am using ServiceNow Out of the box Quickstart MCP server

 

I'm trying to connect Claude Desktop to a ServiceNow MCP server using mcp-remote. I have a pre-registered OAuth client (client-id and client-secret provided by ServiceNow). Despite passing these credentials, the connection always fails with:

 
Discovering OAuth server configuration...Discovered authorization server: https://<instance>.service-now.com/mcp-server/sn_mcp_server_defaultConnecting to remote server: https://<instance>.service-now.com/sncapps/mcp-server/mcp/sn_mcp_server_defaultUsing transport strategy: http-firstConnection error: Error: Incompatible auth server: does not support dynamic client registrationFatal error: Error: Incompatible auth server: does not support dynamic client registration

What I tried:

  1. Basic config with mcp-remote + --client-id + --client-secret
  2. Removed --client-secret (only --client-id)
  3. Upgraded to mcp-remote@latest (resolved to 0.1.38) + added --allow-http

All three attempts produce the same error.

 

Root cause (my understanding):

mcp-remote seems to expect the OAuth server to support dynamic client registration (RFC 7591). ServiceNow uses pre-registered clients and does not expose a dynamic registration endpoint, so mcp-remote fails before even attempting to use the provided credentials.

 

Question:

Is there a way to configure mcp-remote to skip dynamic registration and use the provided client-id/client-secret directly? Or is there an alternative approach to connect Claude Desktop to a ServiceNow MCP endpoint that uses pre-registered OAuth clients?

 

Any help appreciated!

2 REPLIES 2

Tanushree Maiti
Tera Patron

There are 10000 users in my company, do you want me to generate token for each and share with them and they update the file manually every time?