Sleeper Hit Docs

Connect Codex

The full authenticated connector.

View as Markdown

Codex CLI: The full authenticated connector.

Where it runs: Codex CLI on macOS, Linux, and Windows.

If you're an agent reading this

You can't finish this sign-in from inside a chat or a sandboxed shell: the browser can't reach your sandbox's callback. Ask your user to sign in from their app; don't run the login yourself, and don't retry it. They run codex mcp login sleeperhit in their own terminal, outside the agent sandbox, approve in the browser, then start a new Codex session so the tools load. Never ask them to paste an API key into the chat.

Add the connector

  1. Add the server, then sign in. The first command opens Sleeper Hit in your browser. Sign in with Google or email, approve, then choose Return to Codex. Once you have approved Codex, signing in again skips the approval.
codex mcp add sleeperhit --url https://sleeperhit.studio/mcp
codex mcp login sleeperhit
  1. Working in a container, a VM, or anywhere a browser cannot hand its loopback callback back to the CLI? Add --no-browser, open the printed URL yourself, approve, then copy the link the approval page shows and paste it into Codex.
codex mcp login sleeperhit --no-browser
  1. Running Codex in a sandbox that cannot take a browser sign-in at all? Create an API key in Dashboard → Developers, export it, and add the server with the key as its bearer token. No browser is involved.
export SLEEPERHIT_API_KEY=sh_...
codex mcp add sleeperhit --url https://sleeperhit.studio/mcp --bearer-token-env-var SLEEPERHIT_API_KEY
  1. Or set it directly in the Codex config file — same URL, no commands:

~/.codex/config.toml:

[mcp_servers.sleeperhit]
url = "https://sleeperhit.studio/mcp"

Signing in

The first call (or codex mcp login) opens the Sleeper Hit Studio sign-in in your browser; the authorization page lists exactly what the connector may do. After you approve, codex mcp list shows the server connected. Then start a new Codex session: Codex loads a server's tools when a session starts, so the session you signed in from may not see them.

The connector itself needs no API key. A brand-new account is confirmed once at signup (18 or older, Terms and Privacy accepted); see Any other client for what a generic client must support.

Good to know

  • Authorization uses the OAuth 2.1 browser flow (PKCE S256 + dynamic client registration); no API key to paste.
  • If a shell cannot open a browser at all, --no-browser prints the authorization URL and accepts the callback URL by hand.

Sources for these steps

The connector URL on this page is the production one; stage members can use https://stage.sleeperhit.studio/mcp the same way. The same steps, plus every other MCP client, are on the connector page on the app host.