Connect Claude | Sleeper Hit Docs

Claude: The full authenticated connector.

Where it runs: claude.ai on web, Desktop, and mobile; Claude Code in the terminal.

Add the connector

In Claude on web or Desktop, open Customize → Connectors and choose Add custom connector.
Paste the connector URL. Leave the OAuth client choice on "Register automatically": Sleeper Hit Studio registers the client dynamically. Sign in, then authorize.

https://sleeperhit.studio/mcp

On Team or Enterprise plans an owner adds it first under Organization settings → Connectors (Add → Custom → Web); members then connect it from Customize → Connectors.
In Claude Code, add the server:

claude mcp add --transport http sleeperhit https://sleeperhit.studio/mcp

Then run /mcp in a session, choose sleeperhit, and pick Authenticate.

Signing in

One browser sign-in covers both surfaces: the custom connector and Claude Code each finish with the Sleeper Hit Studio sign-in page. Connected means the tools list loads in the connector.

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

A curated text-development profile exists for the Anthropic directory listing (see the Claude connector directory page); the picker above is the full connector, which is what a member connection uses.
Free-plan Claude allows one custom connector.

What to ask for

"Show me my Sleeper Hit projects and what each one needs next."
"Create a Sleeper Hit project from this logline and build the Series Bible."
"Read the coverage on my Series Bible and give me the three notes that matter most."
"Draft Act 1 of episode 1 from the approved outline."
"How many Studio Credits do I have?"

Studio Credits and prices

Writing, coverage and conversation do not use Studio Credits. Table reads, cast pictures and voices, and deck, trailer and video renders do.
Anything that uses credits is priced first: Claude shows the price and what your balance would be, and the work starts only after you say go.
Claude never buys credits; top up on sleeperhit.studio. And nothing that deletes, replaces saved work, publishes or spends credits happens without asking you first.

What Claude can see

Claude receives only what a tool returns: a project, a Bible section, a page, a coverage report. It never sees your password.
Sleeper Hit Studio receives only what Claude sends in a tool call. It never reads your conversation with Claude.
The connection renews hourly while you use it, and ends after a week without use, when you disconnect, or when you change your password or sign out everywhere — the whole grant chain is cut, not just the current token.

Disconnect

Disconnect under Dashboard → API, in the Connected apps list, next to Claude. Reconnecting starts fresh; it is also the fix when a connector was approved with too little or too much access.

Troubleshooting

The sign-in window does not open, or Claude says the connector is not authorized: connect again from the connector settings. In Claude Code, run /mcp and choose Authenticate.
The tools do not appear after you connect: start a new conversation, or toggle the connector in the tools menu. Claude reads the tool list when a conversation starts.
Every request is refused as not allowed: the connector was approved with less access than the request needs. Disconnect it under Connected apps, connect again, and approve the access it asks for.
A tool says the project has to finish a stage first: that is the project's own workflow gate, not a connection fault. Finish the named stage (in Claude or on sleeperhit.studio), then ask again.
A price comes back with "not enough credits": top up on sleeperhit.studio, then ask Claude to price it again.
Something else went wrong: write to help@sleeperhit.studio with the time, the request and the message you saw.

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.