MCP authentication - Clarifeye

The Clarifeye MCP server supports two authentication flows. This page is the canonical source for token issuance UI steps — the REST API authentication page links here.

User token

Use Authorization: Bearer <X> with the token generated from your account settings. Suitable for individual or development use.

OAuth

Client ID/secret from the Deploy tab. DCR-capable clients auto-discover; for clients without DCR, paste the Client ID, Authorization URL, Token URL, Refresh URL, and Scopes manually.

Integrations and the REST API

For an integration that calls the Clarifeye REST API, such as a portal, a bot or a scheduled job, use a service account key instead of a person’s token. It has its own access to the stores it needs and keeps working when people change.

Which one should I use?

Per-client setup