- MCP — OAuth via Clerk. No API key needed — your MCP client handles login automatically.
- REST API — API keys. Required for all REST requests.
OAuth (MCP)
MCP authentication works via OAuth — the same login you use at app.clickflow.com. When you connect an MCP client like Claude, Cursor, or Windsurf, it will open a browser login on first use. You sign in with your regular ClickFlow account. No API key or manual setup required. Flow:- MCP client discovers auth requirements via
/.well-known/oauth-protected-resource - Client redirects to Clerk for login
- User authenticates and grants access
- MCP client receives a token
- All subsequent tool calls use this token automatically
OAuth metadata endpoint
API Keys (REST API)
API keys are required for the REST API. They can also be used with MCP as an alternative to OAuth (e.g., for non-interactive/automated setups). Format: Keys start withcf_ak_ followed by a random string.
Create a key: Dashboard > Settings > API Keys > Create API Key.
Headers
Every request requires anAuthorization header:
Access
API keys have full access to all tools — no scope restrictions.Key properties
| Property | Description |
|---|---|
status | active, revoked, or expired |
expiresAt | Optional expiration timestamp |
lastUsedAt | Updated on each use |
organizationId | Default org for this key |