Connect

Connect your AI to Tokei

One URL works in every client that supports remote MCP servers. Your AI then runs your campaigns as you.

The 60-second version

Have a Tokei Subscriber plan. API access is included.
Add the URL below to your AI client as a remote MCP server.
Sign in to Tokei when the browser opens, then ask for something.

https://tokei.io/mcp

Setup by client

Claude (claude.ai and desktop)

OAuth

Add Tokei as a custom connector. The same connector works in the desktop app.

Open Settings → Connectors and choose Add custom connector.
Name it Tokei and paste the URL below.
Choose Connect, sign in to Tokei, and press Allow.

https://tokei.io/mcp

Claude Code

OAuth

One command registers the server, then you sign in once.

Register the server.
Run /mcp inside Claude Code, pick tokei, and sign in to Tokei in the browser.

claude mcp add --transport http tokei https://tokei.io/mcp

Headless (CI, cron): an API key instead of a browser sign-in

claude mcp add --transport http tokei https://tokei.io/mcp --header "Authorization: Bearer tokei_k_..."

Any client that takes a remote MCP URL

OAuth

Point the client at the URL. It finds the sign-in page by itself.

Add a remote (Streamable HTTP) server with the URL below. Config key names vary by client.
Sign in to Tokei when the client opens the browser.

https://tokei.io/mcp

Clients that only speak stdio

OAuth

The mcp-remote bridge turns the remote URL into a local command.

Use this command as the server command in the client's MCP config.

npx -y mcp-remote https://tokei.io/mcp

Local server (no remote URL)

API key

Runs on your machine and talks to the Tokei API with a key.

Create an API key in Settings, then register the server with it.

claude mcp add tokei --env TOKEI_API_KEY=tokei_k_... -- npx -y tokei-agent mcp

CLI and REST API

API key

For agents that can run a shell or make HTTP calls, no MCP needed.

Set TOKEI_API_KEY, then run any command. Output is JSON when piped.
The REST API is documented at /docs/api, and the spec is at /openapi.json.

npx tokei-agent pages:list

When you need an API key

Scripts, cron jobs and CI have no browser to sign in with. Send a key as Authorization: Bearer tokei_k_... to the same URL. Keys are read-only by default and can expire. Create one in Settings, and read how agent-safe keys work.

Example prompts

“List my Tokei pages and tell me which ones are live.”
“Clone my last giveaway and move the end date to Friday.”
“Who are my top 10 referrers this week?”
“Show me this month's signups for my waitlist page, grouped by day.”
“Draft a new waitlist page from one of your templates, and show it to me before you publish.”
“Set up a webhook that posts new entries to https://example.com/hooks/tokei.”

Tools

The connector exposes 21 tools. Write tools are marked as writes, so your client can ask before it runs one.

Tool	What it does	Access
me	Verify API key	Read
pages_list	List promotion pages	Read
pages_get	Get promotion page	Read
stats	Get page analytics	Read
leaderboard	Get page leaderboard	Read
referrals_top	Get top referrers	Read
winners_list	Get selection-run winners	Read
entries_list	List entries	Read
surveys_list	List survey responses	Read
templates_list	List templates	Read
actions_catalog	List entry-action catalog	Read
events_catalog	List webhook event catalog	Read
pages_clone	Create page from clone or template	Write
pages_update	Update promotion page	Write
pages_publish	Publish page	Write
pages_unpublish	Unpublish page	Write
entries_create	Create entry	Write
webhooks_list	List webhooks	Read
webhooks_create	Create webhook subscription	Write
webhooks_delete	Delete webhook subscription	Write
media_upload	Upload media from a URL	Write

Good to know

Each connection is one Tokei account. Your AI sees only the pages that account owns.
Disconnect any time in Settings → API → Connected apps. The sign-in stops working at once.
Calls count against the same rate limits as the API. A 429 answer says when the quota resets.
Entrant data your AI reads can end up in that AI's conversation history. See the privacy policy.

Hand your next launch to your agent

Create an API key, point tokei-agent at it, and let Claude Code or Cursor run the busywork — you stay in the loop for anything that goes public.