chat-recall Authentication

generated: '2026-11-03'
method: searched
source: https://chatrecall.dev/.well-known/oauth-protected-resource
docs: https://github.com/munhq/chat-recall/blob/main/docs/CONNECTORS.md
name: chat-recall authentication
schemes:
- name: mcp-oauth2
  type: oauth2
  applies_to: https://chatrecall.dev/mcp
  bearer_methods_supported: [header]
  dpop_signing_alg_values_supported: [EdDSA, ES256, ES512, PS256, RS256]
  authorization_server: https://chatrecall.dev/api/auth
  metadata: https://chatrecall.dev/.well-known/oauth-authorization-server
  authorization_endpoint: https://chatrecall.dev/api/auth/oauth2/authorize
  token_endpoint: https://chatrecall.dev/api/auth/oauth2/token
  registration_endpoint: https://chatrecall.dev/api/auth/oauth2/register
  grant_types_supported: [authorization_code, client_credentials, refresh_token]
  token_endpoint_auth_methods_supported: [none, client_secret_basic, client_secret_post, private_key_jwt]
  client_id_metadata_document_supported: true
  scopes_supported: [openid, profile, email, offline_access]
  docs_text: An assistant that cannot run the chat-recall CLI, such as claude.ai, ChatGPT or a browser IDE, connects to the remote MCP endpoint of your server. It signs in with OAuth and then uses the same tools as the local MCP server.
- name: cli-server-login
  type: other
  applies_to: chat-recall CLI to a hosted or self-hosted server
  description: Machines connect with `chat-recall login <server-url>`; a self-hosted server is bootstrapped with an ADMIN_KEY in .env (self-hosting page). The credential format the CLI stores is not documented.
note: Read from published well-known discovery documents (GET only) and the docs; no auth endpoint was called. A probe of https://chatrecall.dev/mcp returned 401 (pre-flight). Self-hosted servers expose the OAuth-backed endpoint only with AUTH_PROVIDER=better-auth.