Permissions and safety

CreatorsJet checks your identity, account role, and approved OAuth scopes on every tool call. A connected assistant can work only with resources your account owns or is allowed to manage. Writes and premium sponsorship matching also check your current plan.

Who can use the tools?

Account	Current MCP plan requirement	Main tools
Creator	Any active account for reads; Pro for writes	Personal media kits, link in bio, socials, campaigns, analytics, eligible sponsorship matches
Agency	Any active account for reads; Pro, Scale, or Enterprise for writes	Roster, agency media kits, social identities, pitch decks, campaigns, analytics

Tools are shown only when your role and approved scopes allow them. If a client requests no scopes, CreatorsJet grants standard read scopes by default. Deal requests contain contact details, so deals:read needs separate approval. Ask your assistant to check CreatorsJet access with mcp_get_access to see granted scopes, missing write scopes, and plan eligibility. To create or edit, approve the matching write scope and reconnect so the client refreshes its tools. An OAuth scope does not override ownership or plan limits.

See the tool reference for each tool's role and scope.

Changes that need care

Roster imports: the assistant validates rows first, shows the row count, errors, and capacity impact, and waits for your approval before committing the import.
Social removal: the assistant identifies the account and gets your explicit confirmation before removing it.
Link-in-bio block removal: the assistant identifies the block and gets your explicit confirmation before removing it.
Media-kit item removal: the assistant identifies the item and gets your explicit confirmation before removing it.
Media-kit collection edits: replacing a collection removes items omitted from the replacement. Review the proposed items first.
Other edits: ask for the exact kit, page, deck, or campaign you want changed. The assistant should read the selected resource before updating it.

Tool annotations describe whether an action is read-only or destructive. The connected client controls its confirmation interface. CreatorsJet checks permissions again when the action runs.

Plans and limits

Connecting never starts checkout or subscribes you to a plan. Product allowances and MCP request limits are checked when a tool runs. If an allowance is exhausted, the result can include your current usage and a link to the appropriate creator plan, agency plan, or Sponsorship Intelligence plan. The assistant cannot purchase it for you.

Error codes

Code	What to do
`AUTHENTICATION_REQUIRED`	Reconnect and sign in again.
`SCOPE_REQUIRED`	Approve the missing permission, then reconnect.
`ROLE_FORBIDDEN`	Use an account with the required creator or agency role.
`PLAN_REQUIRED`, `LIMIT_EXCEEDED`	Check the plan or usage information in the result.
`VALIDATION_FAILED`	Correct the request details and retry.
`NOT_FOUND`	Check the resource ID; inaccessible resources are also reported as not found.
`CONFLICT`	Read the current resource or job status before retrying.
`RATE_LIMITED`	Wait for `retry_after_seconds` when provided.
`RETRYABLE_INTERNAL`	Retry later; contact support if it continues.

Errors include a safe message and a retryability flag. See troubleshooting for common connection and import problems.

Data handling

CreatorsJet does not accept API keys or browser session tokens as MCP credentials. OAuth access tokens expire after one hour; refresh-token families expire after 30 days and store token hashes rather than raw refresh tokens.

Audit events record tool name, outcome, client and user IDs, request ID, duration, result code, and queue ID when applicable. They expire after 90 days. They must not contain tool arguments, spreadsheet rows, OAuth tokens, email addresses, or social handles. Valid roster-import previews expire after 30 minutes.

Your assistant processes prompts and results under its own data practices. See the CreatorsJet privacy policy, terms, and support.