# Connect Cursor

Cursor: The full authenticated connector.

Where it runs: Cursor editor (project or global MCP config); cursor-agent CLI reads the same files.

## Add the connector

1. Add a server entry to .cursor/mcp.json in the project (or ~/.cursor/mcp.json for every project). A remote server needs only `url`; the transport is inferred.

`.cursor/mcp.json`:

```json
{
  "mcpServers": {
    "sleeper-hit-studio": {
      "url": "https://sleeperhit.studio/mcp"
    }
  }
}
```
2. Cursor offers to sign in when the server first challenges; approve the Sleeper Hit Studio authorization in the browser.
3. In the cursor-agent terminal tool, after the same mcp.json entry, authenticate it with:

```text
cursor-agent mcp login sleeper-hit-studio
```

## Signing in

Dynamic client registration is the default path when no auth block is written, which is what Sleeper Hit Studio expects. The entry stays in mcp.json; sign-in is per session.

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](connect-any.md) for what a generic client must support.

## Good to know

- There is no `cursor-agent mcp add` command — write the mcp.json entry, then `cursor-agent mcp login`.
- If your Cursor build asks for a fixed OAuth client instead of registering one, its docs list the callback URLs that would need to be registered; the default registration path needs none.

## Sources for these steps

- https://cursor.com/docs/context/mcp
- cursor-agent `--help` on 2026-10-10 (mcp login/list only, no add)

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](/mcp) on the app host.