Any other client: The full authenticated connector.
Where it runs: Any MCP client that speaks Streamable HTTP and OAuth 2.1.
Add the connector
- Point the client at the connector URL with the Streamable HTTP transport:
https://sleeperhit.studio/mcp
- Choose the OAuth sign-in. The server advertises its metadata and registers clients dynamically (DCR) with PKCE (S256), so there is normally nothing to pre-register; the first call opens the Sleeper Hit Studio sign-in.
Signing in
A machine-readable capability manifest, with every capability's auth requirement and scopes, lives at https://sleeperhit.studio/capabilities.json; the agent-facing index at https://sleeperhit.studio/agent-index.json lists every docs page and its sections.
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 brand-new account — yours or the client's user's — is confirmed once at signup: 18 or older, and agreement to the Terms of Service and Privacy Policy, in the account's own browser. A client cannot accept that for its user, and it does not repeat at every sign-in.
- A local (stdio) variant of the connector will ship on npm as @sleeperhit/mcp-server — coming soon. Until then this remote connector is the way in.
Sources for these steps
- https://modelcontextprotocol.io (transport), and this repository's connector contract in packages/web/src/server/remote-mcp.ts
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.