MCP server support post

[johnnydecimal (Johnny Noble)]

This is a post for general support questions related to the MCP server.

[clappingcactus (John)]

I’m a bit confused, is the connection through oAuth and can we have an API key generated somewhere in the web-interface? That makes things easier for terminal-based agents right? My agent seems to think current API keys generated through the dashboard won’t work for the new Clerk oAuth/Bearer endpoint.

EDIT: Right, so I don’t use Claude or Codex. I use Hermes with Kimi K3. I figured out I can use Hermes’ web gateway to try to recreate your auth from the video, but this is what I get:

[ajhalili2006 (Andrei Jiroh Halili)]

I am also experiencing the same too while setting it up over at Gemini and I provided some debugging hints from my Firefox DevTools Network tab and possibly having to do with OAuth scope mishaps.

@ajhalili2006

Regarding the Claude integration flow through the JDex MCP and plus the recent video on organization stuff (from yesterday Philippine Standard Time), I am at the works for setting up the MCP server on the Google Gemini app (mainly for Spark since I have claimed the free year trial perk of Google AI Pro until October 11 with plans to switch over to the discounted student plan with YouTube Premium bundle (have the student subscription active separately)), but I am getting the Account linking is required to use this custom app. Try again. error but DevTools Network tab on Firefox has hints in the form of invalid_scope (aka The requested scope is invalid, unknown, or malformed. The OAuth 2.0 Client is not allowed to request scope 'profile'. as passed back to Google Gemini’s calback_uri from Clerk). Any plans on looking onto that?

[johnnydecimal (Johnny Noble)]

Currently it’s OAuth only, no API key. Claude Code at the terminal handles that fine – claude mcp add --transport http jd https://johnnydecimal.com/mcp and then authenticate once you’ve launched the app.

I’ve never used Hermes, sorry. If it doesn’t natively/easily support OAuth connections let me know and I should be able to add it. I won’t try it now as we’ll be on the road later today and I don’t want to break what’s there.

@ajhalili2006

The OAuth 2.0 Client is not allowed to request scope ‘profile’

I’ve just added profile to the list of available scopes at Clerk. Try again – this might fix it. Theoretically you should be able to instruct your agent not to request this scope – it doesn’t do anything. But there’s no harm in me passing it over. Hopefully this also fixes @clappingcactus.