MCP overview
Review the implemented CreatorsJet MCP preview, shared service architecture, and release boundary.
CreatorsJet MCP is implemented as a preview in the CreatorsJet backend, but it is not publicly released. There is no supported public server URL, client configuration, or production connection guide yet.
Do not configure production clients yet
Tool names and behavior on these pages describe the implemented preview. CreatorsJet will publish the supported server URL, OAuth connection flow, and client-specific setup only when the transport is released.
How it is designed
MCP tools and Public API controllers are separate adapters over the same tenant-aware application services. MCP uses OAuth actor identity and scopes; the Public API uses API-key actor identity and scopes.
The MCP adapter does not call Public API endpoints over HTTP. Both transports reuse ownership checks, plan policies, roster operations, media-kit operations, link-in-bio operations, decks, campaigns, analytics, and safe error mapping.
Implemented preview workflows
- Validate and commit agency roster imports
- Add one creator to an agency roster
- Ensure a creator's default media kit exists
- Add or remove creator social accounts and keep the relevant default kit synchronized
- Retrieve, create, or update the authenticated creator's link in bio
- List, retrieve, create, or update agency pitch decks
- List, retrieve, create, or update creator- or agency-owned campaigns
- Answer page-view questions for owned media kits, link-in-bio pages, public rosters, decks, and campaign reports
- Find sponsorship matches for eligible Sponsorship Intelligence creator accounts
The current preview does not include a general creator-profile retrieval tool. Use the Public API creator endpoint for server-to-server profile retrieval.
Authentication boundary
The preview transport uses OAuth authorization with account-role scopes. Public API keys and CreatorsJet browser session tokens are not MCP credentials.
OAuth authorization identifies the user and grants compatible scopes. It does not subscribe the account, start checkout, or bypass product-plan allowances. Plan-sensitive tools apply the relevant product rules when invoked.
Next steps
- Review the implemented preview tools
- Understand write safety, plans, and errors
- Use Public API V1 for server-to-server integration work after Public API access is enabled
Claude, ChatGPT, Codex, and other client connection guides remain intentionally unpublished until there is a supported public MCP endpoint and verified connection flow.