Creator data for Cursor.

Connect your data key

Create a data key in the API console with prepaid credits or an active API subscription. Merge this server into .cursor/mcp.json. Set ROSTER_API_KEY in the environment available to Cursor before starting the app. The configuration references the environment rather than storing the key.

{
  "mcpServers": {
    "roster": {
      "url": "https://api.ugcroster.com/v1/mcp",
      "headers": {
        "Authorization": "Bearer ${env:ROSTER_API_KEY}"
      }
    }
  }
}

Check the connection

Open Cursor MCP settings and enable roster. Ask the agent to call get_usage first. If authentication fails, confirm the environment variable is available to the Cursor process.

Make your first search

Find up to 20 US fitness creators with 10,000–100,000 followers. Use one search_creators call, page 1, limit 20. Budget: 10 credits, no profile reads, no retries or extra pages. Return a shortlist with available fields and state any missing data. Stop after the search, even if fewer than 20 creators match.

One search page costs 10 credits, whether it returns 1 or 20 matches. Each optional profile read costs 1 credit. Checking usage costs no credits. The prompt is an agent instruction, not a server-enforced spending cap; your application must enforce a job budget for unattended runs.

Work with the data you have

Results come from stored directory records. Location describes the creator, not their audience. An email on file is not a deliverability guarantee, and reading a profile does not trigger a live scrape. Reuse fields already returned by search before spending credits on extra profile reads.

Use a data key for these examples. It cannot send messages, create campaigns or record payouts. Do not enable brand actions for a discovery-only workflow.