MCP clients
Perplexity
Pre-registered confidential client — DCR as a public client fails
Perplexity Computer custom connectors (Account settings → Connectors → + Custom connector → Remote) speak Streamable HTTP. Set:
| Field | Value |
|---|---|
| MCP Server URL | https://oauth.servicebay.io/mcp |
| Transport | Streamable HTTP (not SSE) |
| Authentication | OAuth 2.0 with Client ID + Client Secret, or API Key |
Why a pre-registered client
Perplexity's DCR path expects a client_secret. Registering as a public client (token_endpoint_auth_method: none) fails with Dynamic client registration did not return a client_secret.
Create a confidential client in the developer portal (OAuth Clients, max 10/org, never expires, rotate-secret). Redirect URI:
https://www.perplexity.ai/rest/connections/oauth_callbackEnterprise subdomain:
https://enterprise.perplexity.ai/rest/connections/oauth_callbackPaste that Client ID and Client Secret into the Perplexity connector. Do not invent a fake secret.
API key fallback
Authentication → API Key. Perplexity sends Authorization: Bearer …. Use a Servicebay key with allowedUses including mcp.