MCP server
The same API surface exposed as MCP tools, so Claude (or any MCP client) can search creators and run the campaign workflow without integration code.
Remote server (recommended)
Roster hosts a remote MCP server at https://api.ugcroster.com/v1/mcp using the Streamable HTTP transport. Nothing to install, always current with the API, and it uses the same key, rate limits, and credit metering as the REST endpoints. Authenticate with your API key in the Authorization header.
Claude (web / desktop): Settings → Connectors → Add custom connector, then paste the URL. When prompted for authentication, use a header of Authorization: Bearer rsk_your_key_here.
connector url
https://api.ugcroster.com/v1/mcpClaude Code:
claude code
claude mcp add --transport http roster https://api.ugcroster.com/v1/mcp \
--header "Authorization: Bearer rsk_your_key_here"Cursor:
.cursor/mcp.json
{
"mcpServers": {
"roster": {
"url": "https://api.ugcroster.com/v1/mcp",
"headers": {
"Authorization": "Bearer rsk_your_key_here"
}
}
}
}Local server via npx (alternative)
Prefer a local stdio server? ugcroster-mcp on npm wraps the same REST API and runs on your machine with Node 18+. Useful for stdio-only clients.
claude_desktop_config.json
{
"mcpServers": {
"roster": {
"command": "npx",
"args": ["ugcroster-mcp"],
"env": { "ROSTER_API_KEY": "rsk_your_key_here" }
}
}
}claude code
claude mcp add roster -e ROSTER_API_KEY=rsk_your_key_here -- npx ugcroster-mcpTool catalog
Every tool is a thin wrapper over a REST endpoint, so everything in these docs (credits, rate limits, errors) applies unchanged.
| Tool | Type | Description |
|---|---|---|
| search_creators | data | Search the 1M+ creator directory by niche, followers, engagement, gender, age, and location. |
| get_creator | data | Full profile for one directory creator by pk. |
| get_usage | data | Credits used vs plan limit, rate limit, and billing period for your key. |
| get_brand_profile | brand | Your brand's profile information. |
| list_creators | brand | All creators (hired + affiliates) with performance data. |
| list_roster | brand | Hired creators on your roster. |
| add_to_roster | brand | Manually add a creator to your roster. |
| get_campaign_stats | brand | Campaign performance: one campaign or all of them. |
| create_campaign | brand | Create a recruiting campaign. |
| list_applications | brand | Applications for a campaign, filterable by status. |
| update_application | brand | Approve, reject, or hire an applicant. |
| create_brief | brand | Create a content brief. |
| list_briefs | brand | All content briefs. |
| send_message | brand | Message a creator through Roster. |
| list_conversations | brand | Recent creator conversations. |
| list_commissions | brand | Affiliate commission events, filterable by status or creator. |
| update_commission | brand | Approve, reject, or mark a commission as paid. |
| create_payout | brand | Record a payout to a creator. |
| list_payouts | brand | Payout history. |
| track_content | brand | Track a post URL for performance metrics. |
| list_tracked_content | brand | All tracked posts with views, likes, comments, shares. |
| get_analytics | brand | Aggregated overview: revenue, commissions, clicks, conversions. |
What agents can do
Once connected, ask your agent things like:
- “Find 20 fitness creators in Austin with 50k–500k followers and an email on file.”
- “Create a campaign for our spring launch, then list pending applications and approve the top three.”
- “Draft a brief for 2 Instagram Reels due March 15 and message the creators on my roster about it.”
- “Approve all pending commissions under $50 and record a PayPal payout for sarah@example.com.”
- “Track this TikTok URL and summarize how our tracked content performed this month.”
Scope follows the key
The MCP server inherits the key it is given. A brand key exposes the full toolset. A data key exposes only search_creators, get_creator, and get_usage. Every other tool returns a BRAND_KEY_REQUIRED error. Rate limits and credit metering apply exactly as they do on the REST API.