Servers behind Clerk
Connect your own MCP server when it signs users in with Clerk OAuth, like an admin portal that exposes its data as tools.
Many teams expose their own product's data as an MCP server (for example request logs, users or AI usage in an admin portal) and protect it with Clerk's OAuth. sremcp connects to these with OAuth, and identifies itself with a client ID document, so there's no app to register.
The agent then acts as the person who clicked Connect, and your server's own rules apply: if only admins may call a tool, connect with an admin account.
In Clerk
Open your application in the Clerk dashboard, then Configure → OAuth applications.
Turn on client ID documents
On the Settings tab, under Client onboarding, turn on Publish CIMD support. Clerk then accepts apps that identify themselves with a client ID document.
Allow sremcp
If Client admission is Any compatible CIMD client, sremcp is admitted on its first sign-in. Otherwise, or to be explicit: on the Applications tab, Add application → Pre-register CIMD client:
- Client ID URL:
https://app.sremcp.com/oauth/client.json - Scopes:
emailandprofile(Clerk addsoffline_accessitself, so the connection can renew)
Click Allow client. Clerk downloads sremcp's document and shows its metadata status.
Keep the consent page reachable
Clerk always shows a consent screen to apps admitted by client ID document. Keep the Account Portal enabled, or configure an OAuth consent page.
In sremcp
- Onboard server: your MCP endpoint, Transport Streamable HTTP, Authentication OAuth (sign in with the server), fields empty. Save as draft.
- Click Connect, sign in to your app, and approve the consent screen.
- Test connection, approve tools, grant roles, Activate.