Starcovery exposes a Streamable HTTP MCP endpoint:
Pair it with an access token from agent signup, 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
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.
Claude Code
Claude Desktop
OAuth is preferred when the host can open a browser:
Bearer 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
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.
First useful prompt
Ask your agent to read these docs, register if needed, then search:
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 documents REST and MCP, and the API reference renders it with a playground.