Sleeper Hit Studio Public Discovery

Bring Sleeper Hit into the room.

A story-creation and production workspace for developing, writing, performing, packaging, and publishing narrative work. Connect Claude, ChatGPT, Codex or any other assistant to move from premise to pages, performance, coverage, and a finished package without leaving the conversation.

Start from an initial premise, notes, research, or an existing screenplay. An existing screenplay is not required.

Pick your client · same connector, same sign-in

Codex CLI

The full authenticated connector.

Runs in: Codex CLI on macOS, Linux, and Windows.

https://sleeperhit.studio/mcp

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.

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
   

2. 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
   

3. 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
   

4. Or set it directly in the Codex config file — same URL, no commands:

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

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.

• 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.

Full Codex CLI guide on the docs site

Browser approval is expected.

1. 01

   Register

   codex mcp add saves the remote server URL in Codex and starts sign-in right away.
2. 02

   Authorize

   Sign in to Sleeper Hit in the browser and approve. You come straight back to the approval after signing in; then choose Return to Codex to hand the connection back, or copy the link shown there if Codex asked you to paste one. codex mcp login repeats this whenever you need to reconnect.
3. 03

   New session

   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.

codex mcp get sleeperhit --json
codex mcp list --json

First three calls

whoami

get_agent_guidance

get_credits

Confirm identity, load live guidance, and check the balance before any tool that generates or renders an artifact.

Authentication success and tool-catalog refresh are separate events. An app loads a server’s tools when a session starts, so start a new session after signing in. Verify the latest OAuth exchange.

Connect with an API key.

If your client runs in a sandbox, a container or on another computer, the browser can’t hand the sign-in back to it: you approve, and the connection never finishes. Send a Sleeper Hit API key as the bearer token instead. No browser is involved, and the key keeps exactly the scopes you give it.

1. 01

   Create a key

   In Developers → API Keys. To create and generate, give it story:write and source:write. It is shown once.
2. 02

   Keep it in the environment

   Set SLEEPERHIT_API_KEY where your client runs, so the key never sits in a config file or a prompt.
3. 03

   Verify

   Call whoami. It answers source: "api_key" with the key’s scopes.

codex mcp add sleeperhit --url https://sleeperhit.studio/mcp --bearer-token-env-var SLEEPERHIT_API_KEY

claude mcp add --transport http sleeperhit https://sleeperhit.studio/mcp --header "Authorization: Bearer $SLEEPERHIT_API_KEY"

{
  "mcpServers": {
    "sleeperhit": {
      "url": "https://sleeperhit.studio/mcp",
      "headers": { "Authorization": "Bearer ${env:SLEEPERHIT_API_KEY}" }
    }
  }
}

If you are an agent connecting a user to Sleeper Hit

You cannot complete the sign-in from inside a chat or a sandboxed shell: the browser cannot reach your sandbox's callback, so your user approves and no token arrives. Do not run the login yourself, and do not retry it. Ask your user to do the one-time sign-in in their app:

• Codex: 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.
• Claude Code: They run /mcp, choose sleeperhit, then Authenticate.
• ChatGPT: They choose Connect on the app, then Authorize.

After that the app renews access by itself. The app loads its tool list when a session starts, so if the tools don't appear, ask your user to start a new session. A key is the fallback for a user who can’t do a browser sign-in: read it from SLEEPERHIT_API_KEY and connect with the command above. Never ask your user to paste a key into the chat.

Create privately. Explore publicly.

The endpoints are intentionally separate. Authentication never turns the public discovery server into a private creation server.

Preferred · OAuth

Connect Sleeper Hit Studio

Full story-development and production access

Your projects, source material, planning, screenplay generation, voiced table reads, music, effects, coverage, rendering, pitch packages, and publishing workflows.

Endpoint

https://sleeperhit.studio/mcp

Authorization

Browser OAuth or an API key · private account access

Public · no account

Explore public Sleeper Hit content

Read-only public discovery

Search opted-in creator profiles, selected project summaries, and creator-approved public assets. No drafts, private links, source scripts, billing data, or creation tools.

Endpoint

https://sleeperhit.studio/api/mcp

Authorization

None · public read-only data

Open public endpoint

Start with a request, not a tool name.

Paste one of these once the connection is active. Sleeper Hit guidance routes the work and pauses before expensive generation or public actions.

• “Use Sleeper Hit to show me my projects and recommend what I can continue.”
• “Use Sleeper Hit to develop a new animated series from this premise: …”
• “Use Sleeper Hit to turn my screenplay into a voiced table read.”
• “Ask Sleeper Hit for its agent guidance, then help me choose a workflow.”

What it can carry

• Develop an idea into a Series Bible
• Plan a film, pilot, episode, or limited series
• Generate and revise screenplay installments
• Attach and use source material
• Produce a voiced table read
• Add adaptive music and sound effects
• Request screenplay coverage
• Render and finalize audio or video
• Package and publish story assets
• Build a pitch package

Prefer an API key? This connector, the Story API and the local server all take a key from your dashboard instead of OAuth. Connect with an API key.