JumpCloud's AI Gateway needs a refresh token from OAuth in order to work. At the moment Huntress' MCP server doesn't supply one. To the degree reasonably possible centrally managing, securing, and logging access - whether by humans or agents is important to us.

I'll apologize up front for the short Claude copy/paste below, at least it's short and to the point.

Huntress’s public OAuth settings (https://api.huntress.io/.well-known/oauth-authorization-server) list the grant types it supports:

"grant_types_supported": ["authorization_code", "client_credentials"]

Refresh_token isn’t in that list, so no Huntress sign-in will ever produce a refresh token, however many times you reconnect. The gateway’s error says it needs one: “… no refresh token stored”. It treats that as fatal instead of using the access token it already holds. So JumpCloud’s Huntress connection is built in a way that can’t work with Huntress.