OAuth (Claude.ai and the Anthropic Connectors Directory)
When you connect UniversalBench through the Anthropic Connectors Directory or Claude.ai, authentication is handled by the standard OAuth flow. You click Connect, sign in or create an account, and Claude.ai receives a token it uses on your behalf. There is nothing to configure manually. The OAuth endpoint is:Personal URL (Claude Desktop, Cursor, Claude Code, custom agents)
For any MCP client outside of Claude.ai, UniversalBench bakes your identity into a personal URL. Copy it from your dashboard at universalbench.dev after signup:ubk_ prefix identifies a UniversalBench key. The 64-character hex string is the secret. Paste the full URL into your client config with no extra headers needed.
Why URL-embedded auth instead of a header?Most MCP services use a shared endpoint plus an
X-API-Key header. Every client handles custom headers differently and some break silently. Embedding the key in the URL path means one paste works everywhere, including clients with no header support.Treat your URL like a password
Anyone with your URL can make calls billed to your account. To minimize risk:- Do not commit it to public repositories
- Do not paste it into screenshots or shared logs
- Rotate it immediately if you suspect exposure by clicking “Rotate key” in your dashboard
Alternative header methods
If you cannot use the URL form for some reason, the API also accepts the key via:| Method | Example |
|---|---|
| Authorization header | Authorization: Bearer ubk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |
| Custom header | X-Api-Key: ubk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |
| Query parameter | ?key=ubk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |