> ## Documentation Index
> Fetch the complete documentation index at: https://starcovery.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect over MCP

> Paste one MCP URL into Claude, Cursor, Codex, or any Streamable HTTP client. Your agent can then search creators, run campaigns, and read credits.

Starcovery exposes a Streamable HTTP MCP endpoint:

```text theme={null}
https://www.starcovery.com/api/mcp
```

Pair it with an access token from [agent signup](/docs/authentication), a Settings API key, or OAuth when your client supports it. There is no unsigned MCP.

Over MCP your agent can search creators with a plain-language query, create campaigns and generate matches, and read the credit balance. It is the same product surface the web and CLI call.

## Get a credential

```bash theme={null}
npx starcovery auth register
```

That runs the auth.md signup protocol and saves an access token to `~/.config/starcovery/config.json`. The CLI prints the config path and claim URL, never the raw token. Put the `accessToken` value in the Bearer header of your MCP host. Humans can instead mint a durable API key in [Settings](https://www.starcovery.com/app/settings/api-keys).

## Claude Code

```bash theme={null}
claude mcp add --transport http --header "Authorization: Bearer <access_token>" starcovery https://www.starcovery.com/api/mcp
```

## Claude Desktop

OAuth is preferred when the host can open a browser:

```text theme={null}
Settings > Connectors > Add custom connector
Name: Starcovery
URL: https://www.starcovery.com/api/mcp
Auth: OAuth (sign in when prompted)
```

Bearer token:

```text theme={null}
Settings > Connectors > Add custom connector
Name: Starcovery
URL: https://www.starcovery.com/api/mcp
Header: Authorization: Bearer <access_token>
```

## Cursor and other HTTP MCP hosts

Add a custom MCP server:

* URL: `https://www.starcovery.com/api/mcp`
* Auth: `Bearer <access_token>`, or OAuth when the host offers it

<Warning>
  Some hosts only accept a query parameter: `https://www.starcovery.com/api/mcp?api_key=<access_token>`. This is a last resort. Keys in URLs can leak through server logs, browser history, and the Referer header. Prefer Bearer or OAuth.
</Warning>

## First useful prompt

Ask your agent to read these docs, register if needed, then search:

```text theme={null}
Find 15 nano creators who film quiet morning coffee at home on Instagram or TikTok. Save the shortlist to a campaign named Coffee.
```

## FAQ

### Do I need the web?

No. MCP, REST, and the CLI cover search, campaigns, and credits. Humans use the web for account settings, credit packs, and durable API keys.

### Where is the API described?

[openapi.json](https://www.starcovery.com/openapi.json) documents REST and MCP, and the [API reference](/docs/api-reference/search-creators) renders it with a playground.
