kensho.com

For testing and development, open the product account page for the API you want to use and copy a refresh token. The docs explicitly list Scribe account and note that each Kensho API has its own refresh-token endpoint, so the token is product-specific. Use that refresh token to mint short-lived access tokens before API calls, e.g. GET /oauth2/refresh?refresh_token=... on the product host as shown in the authentication quickstart. For the LLM-ready API specifically, go to LLM-ready API manual login, sign in with your LLM-ready API Okta credentials, and copy the refresh token as shown in the LLM-ready API authentication guide.

For production access, generate an RSA keypair locally, then email Kensho your public key and the application(s) you need. The production authentication guide says to generate private.pem/public.pem, send the PEM-encoded public key to support@kensho.com, and Kensho will reply with your Client ID. Use the Client ID together with your private key to obtain short-lived access tokens. For LLM-ready API access, the product guide says to email commercial@kensho.com to obtain LLM-ready API Okta credentials, and the same page documents keypair auth in the LLM-ready API authentication guide.

Point your MCP client at the server URL and approve access in the browser. The server supports OAuth Dynamic Client Registration (RFC 7591), so the client registers itself automatically — no developer-portal app, client_id, or client_secret to create.