Skip to main content
The Model Context Protocol (MCP) lets agents like Claude, Cursor, and VS Code call tools through a standard interface. CreatorAudit runs an official, hosted MCP server at https://mcp.creatoraudit.com/mcp that exposes the full v2 API as agent tools — list and track accounts and videos, group creators, and read analytics. There’s nothing to install: connect your client to the URL with your API key.

Set up in 3 steps

1

Get your API key

In your CreatorAudit dashboard, open the API keys page from the sidebar, click Generate key, and copy it (it’s shown only once). See Manage API keys for the full flow.Keys are organization-scoped, so every call the agent makes is confined to your workspace. Reads work with any valid key; tracking, creating, and deleting need a write-scoped key.
2

Add the server to your client

Use an HTTP transport. Header-capable clients send the key in a header; clients that take only a URL (Claude Desktop, ChatGPT) put it in the URL. Restart the client fully after editing a config file.
A URL key can be captured by server access logs, so prefer a header where your client supports one. If a client reserves Authorization for its own auth, send the key as an x-creatoraudit-api-key header instead.
3

Verify the connection

Ask the agent to run get_api_key_info (or “which organization is my CreatorAudit key for?”). It should return your organization — you’re connected. Tool discovery works without a key; every data call needs a valid one, which the v2 API validates.

Tool surface

Full v2 parity — every v2 endpoint is a callable tool, plus a call_v2_endpoint escape hatch and meta tools. To stay token-efficient, only a small pinned core appears in the standing tool list; the rest are found via search_tools or the built-in get_help catalog and stay directly callable by name. ⚠️ marks destructive writes — your client is prompted to confirm before they run. track_account returns before metrics land; the first scrape is asynchronous, so check back later. Call get_help for the full catalog plus convention notes (auth, pagination, idempotency, errors, scopes, and the track → wait → read workflow), and search_docs to query this site live.
Anything not yet wrapped as a named tool is reachable through the escape hatch: call_v2_endpoint(method, path, params, body), where path is relative to the v2 root (e.g. /accounts). The same auth, idempotency, and RFC 9457 error surfacing apply.

How auth works

You bring your own key; the server holds none of its own. It reads your key from the request — Authorization: Bearer or x-creatoraudit-api-key header, or an ?api_key= URL query parameter (a header takes precedence) — and uses it only for your calls. Concurrent callers are isolated, so one connection never sees another’s data. The key stays in your client config, never in tool arguments or responses, and writes auto-attach an Idempotency-Key so retries are deduped. Because keys are organization-scoped server-side, an agent can’t reach another org’s data even if it tries. See API setup for the shared API conventions.

Search these docs over MCP

This documentation site also hosts an MCP server at its /mcp path, with search and content-retrieval tools so your agent can look things up live.
Each page also offers Copy page, View as markdown, and Add to Cursor / VS Code / Claude in its context menu — handy for dropping a single page into your agent.

Build a custom server

For most teams the official server is what you want — it covers the whole v2 API and is maintained alongside it. Build your own only to expose a narrow subset of endpoints, add organization-specific logic (extra validation, redaction, defaults), or run on a different runtime. The example below wraps three endpoints — search, overview, and list_accounts — and passes responses through unchanged. Read the key from an environment variable; never bake it into the tools or return it in a response.
1

Set your key as an environment variable

2

Implement the server

3

Register it with your agent

Point your client at the local server (Claude Code, Python example):
Keep the key server-side, read from an environment variable. Never bake YOUR_API_KEY into a tool definition or return it in a tool response. Mint an Idempotency-Key on every write, and flag destructive tools so the client can prompt before mutating data — the official server does both for you.